What a small event does that a webinar cannot
A webinar or online event is a presentation with an audience. It scales well, it can be recorded and reused, and it suits education. What it cannot do is make the audience talk to each other. A small hosted event can. Senior people at the organisations a business most wants to reach will rarely sit through a vendor's webinar, but many will give an evening to hear how their counterparts at other firms are handling a problem they share. In a closed room they say things they would never type into a question box, and the host hears things about the market that no survey would show.
Small events also reach more than one person per account. A roundtable invitation can go to several roles in a buying committeeThe group of people in an organisation who influence, evaluate and approve a purchase. over a series, and a customer day brings together users, owners and budget holders who rarely meet the vendor at the same time. In the See-Think-Do-Care framework, the webinars guide places events mostly in Think and Care: people considering a purchase, and customers who already bought. Hosted events fit the same two stages, which is why the formats below divide between prospects and customers.
What small events do not do is produce volume. A roundtable reaches a handful of people at a time and costs a great deal per guest in money and staff time. That is the right trade where a few accounts carry most of the value, as in account-based marketing, which names events among its tier-one plays, and the wrong one where the market is wide and deals are small.
Formats: roundtables, customer days, user groups and dinners
The formats differ in who is in the room and why, and each needs a different part from the sellers.
| Format | Purpose | Who attends | Sellers' role | A good outcome |
|---|---|---|---|---|
| Peer roundtable for prospects | A candid discussion of a shared problem among peers | Senior people from target accounts at a similar level, with a customer or independent chair | Hosts and listeners; no presenting | Follow-on conversations with the accounts, more committee roles known, a clearer view of the problem |
| Customer day or user group | Help customers get more from the product and meet each other | Users, administrators and owners at existing customers | Account managers host; sellers meet expansion contacts | Adoption, expansion conversations, customers willing to speak for the product |
| Advisory session with customers | Input on the roadmap, the market and the messaging | A small group of customers who agreed to advise | Mostly absent; product and marketing lead | Decisions informed by customers, and customers who feel heard |
| Dinner beside a show | Time with target accounts and customers already travelling to a show | A mix of prospects and customers from the show's visitors | Hosts, seated with their accounts | Meetings booked, relationships started with accounts the stand would not reach |
A business does not need all four. Most start with one format matched to the job they most need done, run it as a series rather than a one-off, and add a second only once the first is working. The trade show tutorial covers the stand that a dinner often sits beside. When advisory sessions become a standing group, the guide to running a customer advisory board covers the charter, choosing members and turning their advice into decisions.
Building the guest list with sales
The guest list is the event. A small room with the right people beats a full one with the wrong people, and the right people come from the target account list and the committee roles mapped for each account, as the account-based marketing guide describes. The ABM account plan template records the roles for each account and is the natural place to note which role an invitation is aimed at and why.
Agree the list with the sellers who own the accounts. They know which contacts would value the discussion, which would see it as a sales trap, and which accounts are in a sensitive moment where an invitation would be unwelcome. Each seller should be able to say, for every guest from their accounts, what they hope the evening does for the relationship.
Three general practices keep a room working. Invite peers at a similar level, because a discussion between a chief information officer and a junior analyst is not a peer discussion. Mix prospects and customers in roundtables where the customers are comfortable speaking frankly, since prospects trust what a peer says more than anything the vendor says. And think about who sits beside whom: direct competitors may not speak openly in the same room, and the sellers usually know which pairings to avoid.
Record every invitee as a member of one CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. campaign for the event, with a status that moves from invited to accepted, attended or absent. Without that record, the measurement at the end has nothing to compare.
Invitations and what guests are told
The strongest invitation comes from a person: the seller who owns the account, or the host, writing to someone they know or have a reason to contact. Marketing supports it with the event page, the agenda and the logistics. Where that event page lives on LinkedIn, the tutorial on running a LinkedIn Event from a company page covers creating it, briefing the hosts and following up by what each guest did. Where marketing sends invitations by email to business contacts, those messages are electronic marketing. As the list building and consent guide summarises from the UK Information Commissioner's Office's direct marketing guidance, listed in this page's sources, the rules treat individuals and corporate subscribers differently, vary by country, and require a way to opt out in every message. This is educational, not legal advice.
The invitation should say what the guest will hear afterwards. A line such as "after the evening we will send you the notes from the discussion; we will not add you to our newsletter unless you ask" sets an expectation that the follow-up can then keep. Record what each guest was told in the CRM, so that whoever follows up knows what is allowed and what was promised. The event marketing plan template keeps the guest list, what invitees are told and the follow-up agreed with sales on one page for each event.
Send every invitation and reminder through a link carrying campaign parameters. Google's URL builder documentation, also listed in the sources, describes the parameters analytics collects from those links, and the measuring guide explains how the registration form carries the source into the CRM, so that the event's promotion can be compared by route: seller invitation, marketing email, partner, or a colleague who forwarded it.
Running the room without a pitch
The rules for running a small event are general practice rather than anything a regulator or platform documents, and they come down to one principle: the vendor is the host, not the speaker.
- A chair who is not the vendor. A customer, or an independent voice the guests respect, chairs the discussion. The vendor's role is to welcome, to make introductions and to keep time.
- An agenda built on the guests' problem. A few questions the guests actually face, ideally tested with a few of them in advance, rather than a topic chosen to lead towards the product.
- House rules agreed at the start. The chair asks the room to agree what may be repeated outside it, for example that ideas may be shared but not who said them. Guests speak more freely when they know.
- No product presentation. No slides about the product, no demonstration, no proposals on the table. If a guest asks about the product, a seller answers briefly and offers to follow up.
- Sellers as hosts. The sellers who own the guests' accounts sit among them, listen, and note what each guest cares about. That note is the most valuable thing the evening produces for sales.
A customer day or user group has more structure, with sessions on using the product and a roadmap update, but the same principle holds: customers came to learn and to meet each other, and an agenda that turns into a sales event empties the room the following year. The roadmap update is safest when it uses the confidence labels and approved slide that the guide to talking about the roadmap describes, so that nothing presented on stage becomes an unapproved promise.
Customers in the room
Customers make small events credible. A customer chairing a roundtable, a customer describing what changed after a project, a user group where customers teach each other: each carries more weight with prospects than anything the vendor says. Brief customers who speak, help with any material they want, and let them say what they think, including what did not go well.
The programme that recruits and protects those customers belongs to the guide to customer references and advocacy, which keeps a record of what each customer agreed to and when they were last asked, and covers disclosure where a customer receives anything in return. Use it rather than asking the same willing customer to chair every evening.
Customer days and user groups are also a source of two other things. They surface expansion: teams and sites at a customer that do not yet use the product, and people who were not part of the first decision, which the expansion and renewal marketing guide turns into an account plan. And they produce feedback: the questions, complaints and requests customers raise in the room belong in the business's listening programme, which the voice of the customer guide describes, so that what was heard reaches product and customer success rather than staying in an event report.
Follow-up and measurement
Follow-up starts with what was promised. If guests were told they would receive the notes, they receive the notes, promptly. Then the host or the seller who owns the account sends a personal message that refers to something the guest said. After that, the next step depends on the guest's own signal: a guest who asked for a conversation gets one with the seller; a guest who agreed to hear more can enter marketing, with material matched to their role in the committee as the guide to B2B content describes; a guest who did neither hears nothing further except the invitation to the next event in the series.
Measure each event as a cohort, as the measuring guide sets out for in-person events and the business-to-business measurement guide for programmes: the accounts and people who attended, followed over the months after it.
| What to record | Why |
|---|---|
| Invited, accepted, attended and absent, by account and role | The base for every comparison, and the measure of whether the guest list was right |
| Committee roles reached at each attending account | Whether the event widened the business's reach inside its target accounts |
| Meetings held with sellers after the event | The first sign that the evening started conversations |
| Opportunities sourced by the event | Where the event was the account's first recorded TouchpointAny interaction between a person and a brand, paid, owned or earned, before, during or after a purchase., the closest the event has to marketing-sourced pipelineValue of sales opportunities whose original source was a marketing activity. |
| Opportunities influenced by the event | Open or later opened at accounts that attended; shows reach into deals and overstates causation |
| Full cost, including staff time | Cost per attending account and per opportunity, comparable with other formats |
Where the series has invited enough similar accounts, compare those that attended with those that were invited and did not come. The measuring guide is clear that the difference is an estimate of the event's effect, not proof of it: accounts that accept an invitation may already be warmer than those that decline. Report it as an estimate, beside the counts, and judge the format over a series rather than a single evening.
A security consultancy's roundtable series (illustrative)
Brackenvault Security runs a quarterly roundtable for heads of IT
Brackenvault Security is an invented consultancy that helps mid-sized firms with security assessments and incident readiness. Its target list holds 160 accounts. It hosts a quarterly roundtable for heads of IT at those accounts, each one an evening discussion over dinner for about a dozen guests, chaired by the head of IT at a long-standing client who agreed to chair two of the four. The other two are chaired by an independent security researcher with no commercial tie to the firm. There are no product slides; the two partners who own the accounts host, sit among the guests and take notes.
Invitations go from the partners personally, with a follow-up email from marketing carrying tagged links. Every invitation says that guests will receive a summary of the discussion with no names attached, and nothing else unless they ask. Over the year, 111 accounts are invited: 41 attend at least one evening and 70 do not.
| Six months after each roundtable | Attending accounts (41) | Invited, did not attend (70) |
|---|---|---|
| Accounts with a meeting held with a partner | 15 | 9 |
| Accounts with an opportunity opened | 6 | 4 |
| Committee roles beyond IT now known | 23 | 11 |
The series costs about £5,500 per evening for the venue, dinner and the chairs' travel, plus partners' time. The team reports the gap between the two groups as an estimate rather than proof, because the heads of IT who accepted may already have been closer to buying, and decides to continue the series for a second year with the same no-pitch rules.
Common mistakes
- A guest list built by marketing alone. Sellers know which contacts would value the evening and which would see it as a trap.
- Turning the evening into a pitch. Product slides and proposals end the discussion and the series; the vendor hosts, a peer chairs.
- Inviting a mix of levels. Senior guests come to talk with their peers, not to be in a room with juniors and salespeople.
- Promising one thing and sending another. If the invitation said notes only, a newsletter afterwards breaks the promise and the rules.
- The same customer in every chair. Use the reference programme so that willing customers are not worn out.
- No CRM campaign. Without invited, attended and absent recorded by account, the event cannot be measured.
- Calling the attended-versus-absent gap proof. Accounts that accept are often warmer already; report it as an estimate over a series.
- Leaving what customers said in the event report. Feedback from user groups belongs in the listening programme, where product and customer success will see it.
