a partner roadshow that ends in registered deals

A partner roadshow ends in registered deals when four things are agreed before the first invitation goes out. The partner invites its own customers, personally. The agenda gives a security team something it can use on Monday. Named people follow up within days with a concrete offer. And every attendee ends in one of three states: a registered deal, a logged next step with a date, or a closed record with a reason. Tie the market development funds (MDF) to those outcomes. A roadshow measured on attendance will keep producing attendance.

why small partner events work in Europe

In most European markets the buyer of a security product already has a supplier they trust: the integrator that runs their network, their backup or their Microsoft licensing. That partner has the relationship, a meeting room the customer has been in, and often a local language session the vendor cannot staff alone. A small event lets the vendor borrow that trust for half a day.

Marketers are moving in this direction. Forrester’s Q1 2025 State of B2B Events survey of more than 250 event decision-makers found 59%59% of B2B event decision-makers planned more smaller hosted events over the next 12 months, in Forrester's Q1 2025 survey. Forrester, 2025 planning more smaller hosted events over the next 12 months. The survey covers B2B in general, but the pattern fits security, where buyers want to hear from peers and engineers before they hear from a seller.

The weakness of partner events is also well known. The vendor pays, the partner hosts, and afterwards nobody can say which deals came out of it. Everything below is about closing that gap.

choose the format by who you need in the room

Start from the person whose decision you need, then pick the format that person will attend. The costs below are illustrative assumptions for a mid-sized European city. Replace them with your own quotes.

	webinar	in-person seminar or breakfast	CISO dinner
who comes	engineers and analysts, many researching	IT and security managers from the partner’s customers	heads of security and IT directors, 8 to 15 people
what they get	a recording they can watch later	a practitioner talk, a live technical session, peers	an off-the-record conversation with peers
illustrative cost per attendee	20 to 50 EUR	100 to 250 EUR	250 to 500 EUR
what follows	content follow-up, a few requests for a demo	meetings and on-site workshops booked by the partner	one-to-one meetings, often on deals already open
the trap	registrants treated as leads	the room filled with the partner’s own staff	a sales pitch over dessert

A roadshow usually combines them: a morning seminar in each city, a dinner for the most senior guests the evening before, and a webinar recording for those who could not travel.

Which format for which audience

seniority of the people you need →

senior, little technical proofCISO dinner or roundtable, with a peer speaker.

senior, technical proof neededMorning seminar with a live session, plus a dinner for the decision makers.

hands-on staff, little proofWebinar. Cheap per head, weakest at producing meetings.

hands-on staff, technical proof neededSeminar or lab session at the partner's office.

how much the buyer must see working →

the partner invites, from its own customer list

The invitation list decides the outcome more than the venue or the speaker. Build it from the partner’s installed base: customers in your target segment, customers with an adjacent product renewing in the next two quarters, customers with an open audit finding. These are the same places first deals come from in the first 90 days of partner activation.

Ask the partner’s account managers to invite people by name, by email or phone, four to six weeks before the date, and to confirm again in the last week. A generic mailing from the vendor’s marketing system reaches people who do not know the vendor and have not agreed to hear from it. Agree a target for the room: how many people from customers in your segment, and how many seats are allowed for partner staff, students and other vendors.

The distributor earns its place here. On a multi-city roadshow it books venues, coordinates hosts, handles the budget split and makes sure each partner’s list is ready by the same week.

consent and the attendee list

Partner events move personal data between companies, so settle the rules before the registration form goes live. What follows is general information as of November 2026, not legal advice, and national rules differ.

Under Article 6 of the GDPR every processing needs a lawful basis, such as consent or legitimate interests. Recital 47 says direct marketing may be regarded as a legitimate interest, which still requires a balancing test that the attendee’s interests do not override. Article 21 gives the attendee the right to object to direct marketing at any time.

Email invitations add a second layer. Article 13 of the ePrivacy Directive requires prior consent for marketing emails to natural persons, with an exception for a company emailing its own customers about its own similar products, provided they can object easily. Each member state transposed this into national law, and Article 13(5) leaves the protection of companies, as opposed to individuals, to national rules, so check the law in each country on the route. In practice the partner, writing to its own customers, is usually in a stronger position than the vendor.

Sharing the attendee list with the vendor is a separate step. The vendor needs its own lawful basis to use the data, and Article 14 requires the attendees to be told who has their data, at the latest at the first communication or when the data is first disclosed. If partner and vendor jointly decide why and how attendee data is processed, Article 26 makes them joint controllers, who must set out their responsibilities in an arrangement. The EDPB’s Guidelines 07/2020 explain how to tell which role each party has.

The practical rules: the registration form names every company that will contact the attendee and why, the vendor receives contacts only where that basis exists, and the partner keeps ownership of its customers. GitLab’s MDF guide, as published in 2026, is a useful public model. It requires a lead list as proof for funded events, and states that its sales team will not call or nurture those leads without the partner’s written permission unless the customer has already engaged with GitLab directly.

the agenda: a local voice, a live session, regulation as context

People come to a partner event for practical, local content in their own language. A half-day morning works well for this. A shape to start from:

1. A local practitioner. A security manager from a customer, an auditor or a lawyer, explaining one problem the audience has this year. A customer who describes what went wrong in a project earns more trust than a polished success story.
2. A live technical session. An engineer showing the product doing the task on realistic data, with the audience’s questions answered on screen. This is the part people remember.
3. Regulation as context. If NIS2 or DORA matters to the audience, explain what the national law as transposed requires and by when. Show what evidence an auditor asks for. Leave fear and fines out of it.
4. A short vendor slot. Fifteen minutes on what the product does and what it costs to start.
5. A concrete offer. An assessment, a workshop at the customer’s site or a demo on their own data, booked by the partner before people leave.

Give the partner material it can reuse afterwards: the recording, the slides in the local language, a one-page summary. Those are the kind of assets a partner will actually send to the customers who could not come.

a ten-week plan, from partner choice to follow-up

A single seminar can be done faster. A roadshow across several cities with several hosts needs about ten weeks, with the follow-up counted as part of the plan.

One roadshow, ten weeks

week 0week 10

Weeks 0 to 2: pick partners and cities, agree follow-up owners, data rules and MDF terms in writing

Weeks 1 to 4: agenda, local speakers, live session rehearsed, invitation copy

Weeks 3 to 7: personal invitations by partner account managers, confirmations

Weeks 7 to 8: the events, one city per day or two

Weeks 8 to 10: follow-up, registrations, first report per partner

Put the roadshow into each host’s joint business plan, with the expected number of registered opportunities written next to it. Check your vendor’s MDF rules early: GitLab, for example, asks for requests at least 10 business days before the activity and for claims within 30 calendar days after it.

follow-up within days, and an outcome for every attendee

The event creates interest that fades in days. The same logic as the first hour after a demo request applies, at the pace of a partner.

1. day 0notes on every attendeePartner account manager and vendor engineer agree who showed interest, in what, and who calls.
2. days 1 to 2personal message from the partnerRecording, slides and the offer from the session, sent by the person who invited them.
3. days 3 to 5a callBook the assessment, workshop or demo, or learn why not.
4. day 10every attendee has a stateRegistered deal, next step with a date, or closed with a reason. No attendee left as "contacted".

Any attendee who turns into an opportunity goes through deal registration under the normal rules, with the event recorded as the origin. That one field lets you see, months later, which events and which partners produced pipeline.

MDF tied to registered pipeline

Funding paid on proof of attendance teaches partners to fill rooms. Funding tied to registered opportunities teaches them to follow up. A workable split: pay the event costs on proof that it happened, and agree that next year’s allocation for that partner depends on what the event produced. Count registered opportunities and logged next steps at 30 days, then again one and two quarters later, because security deals start slowly.

Keep the attribution honest. An opportunity the partner registered from its own customer after the event is partner-sourced. A deal already open, where the dinner helped, is influenced. Keeping those apart, as in any set of channel metrics, stops one roadshow from claiming the whole quarter.

the next roadshow

Look at the last partner event you funded and count three numbers: attendees from customers in your segment, attendees with a recorded outcome, and registered opportunities. If you cannot produce the second number, fix the follow-up before you book another venue.