Sooner or later, someone in your sales team asks the question that decides your whole plan: when can we tell exhibitors that meeting booking opens? The date depends on more than the vendor’s setup schedule. It depends on decisions that only you can make, and most of them come before anyone touches the software.
Vendor estimates offer a useful starting point. PheedLoop, an event platform provider, puts a typical implementation at two to three weeks for a simple event, four to eight weeks for a mid-complexity event and two to four months or more for a complex one (PheedLoop, Event Tech Implementation Timelines, July 2026). These are one vendor’s figures for event technology in general, not for matchmaking alone. Use them as a starting point, then allow time for your own decisions and approvals.
This guide explains what takes time, how to work backwards from your event date and how to leave participants enough time to book meetings. Start with the day booking needs to open, then plan the decisions and setup work needed to reach it.
The short answer
For a mid-sized B2B event with pre-scheduled one-to-one meetings, plan typically around two months, roughly six to ten weeks, from contract to the first booked meeting. Configuring the matchmaking itself often takes only a few weeks of that. The rest goes into the matching rules, the registration questions, approvals for data protection and IT security, and a registration period long enough to fill the meeting diaries.
Picture an event director who has signed with a platform twelve weeks before her trade show. She has time. Her colleague who signs six weeks out does not, even if the configuration takes the same three weeks, because his participants will have less than a month to register, complete profiles and book meetings.
The software rarely sets the deadline. Your participants do.
What actually takes the time
If configuration is quick, where do the weeks go? Into five workstreams, and only one of them happens inside the platform.
- The matching rules: who may meet whom, how many meetings each group gets, how long a meeting lasts and whether buyers or sellers send the requests. This is a business decision, often between sales, the programme team and sponsors. Our guide to the buyer-to-seller ratio shows why this number belongs on paper before any setup starts.
- The registration questions: matchmaking can only work with the data you collect. Product interests, buying role, region or deal size have to be in the form before registration opens. Adding a dropdown after 600 people have registered leaves 600 profiles without an answer.
- Approvals: in Europe, a data processing agreement under the GDPR (General Data Protection Regulation) is needed before any participant data reaches the platform. Many organisations add an IT security questionnaire and a procurement step.
- Configuration and testing: meeting slots, meeting locations or tables, branding, emails and a test run with dummy profiles on both sides of the matrix.
- Communication: invitations, reminders and a clear date when meeting booking opens.
The first three items are the ones that slip. PheedLoop names the same culprits: scattered or unfinished attendee data, approvals by IT security, procurement and legal, which “run on institutional time, not project time”, and late changes to registration forms or ticket types that force finished work to be redone (PheedLoop, July 2026). For you, that means the fastest way to shorten setup is to make the decisions earlier, not to push the vendor.
A realistic timeline, working backwards from the event
Working backwards puts the meeting window first, because that is the part your participants experience. Everything before it is preparation for those few weeks.
Registration timing is the reason. Maritz analysed more than 360,000 registrations across 30 trade shows. In 2023, 45 per cent of attendees registered within four weeks of the event, and 22 per cent registered in the final week or on site (Maritz Registrations Insights Report, 2024, as reported by TSNN). If your meeting window closes four weeks before the event, almost half of your audience may register too late to book, and even a close two weeks out shuts out more than a quarter. Keep the door open for late registrants.
Event matchmaking setup, working backwards from event day
- 16 to 12 weeks out Decide and sign Write the matching rules on paper, agree the data processing agreement and start any security review.
- 12 to 8 weeks out Configure and test Registration questions, meeting matrix, slots and meeting locations; a test run with dummy profiles on both sides.
- About 8 weeks out Open registration Profiles fill as people register. Keep the matching questions short so profiles are complete.
- 6 weeks to a few days out Meeting window Requests, accepts or organiser approvals, and diaries that fill. Late registrants can still book.
- Final week Schedules and rebooking Personal agendas go out, reminders run and someone owns cancellations and rebooking.
- After the event Follow-up Meeting lists and statistics go to participants and sponsors while the conversations are fresh.
The meeting window in this model starts about six weeks out. Curated programmes can follow a similar rhythm. Oxford Global, which runs partnering meetings at its life science conferences, sends partners the attendee list six weeks before the event, asks for meeting choices typically two weeks later and sends the final schedules in the week before (Oxford Global partner knowledge base, 2026). Open self-booking formats often use shorter windows. For startup and investor events, our 90-day countdown for startup conferences explains why opening the platform too early can leave profiles cold.
Three typical timelines
Not every event needs sixteen weeks. The table maps PheedLoop’s three complexity levels to examples of matchmaking setups; the examples are ours.
| Your event | Typical setup time | What sets the pace |
|---|---|---|
| Simple: one participant group, one meeting area, no integrations | 2 to 3 weeks | Your decisions on the registration form |
| Mid-sized: buyers and sellers, approval rules, a few integrations | 4 to 8 weeks | Matching rules, data protection and IT sign-off |
| Complex: hosted buyer programme, several event parts, connection to a CRM (customer relationship management) system or association database, custom badges | 2 to 4 months or more | Integrations, procurement and hard lead times |
Source: setup ranges from PheedLoop, Event Tech Implementation Timelines (July 2026), vendor data for event technology in general. Row examples: Converve editorial.
The right-hand column matters more than the middle one. A simple event can still take six weeks if nobody decides which questions go into the form. A complex one can stay on schedule when the integrations are agreed in the first week.
Three numbers that move your start date
The badge figure looks unrelated, but it is not. If you pre-print personalised badges from the same registration data, their print date can become your registration deadline. Printing badges on site avoids that.
What slows setup down, and how to avoid it
The delays are predictable, so you can plan around most of them in the first week.
Late rules. If the matching rules are still being discussed while registration is open, you either change them for everyone already registered or live with rules you do not want. Agree them in a short workshop with sales and the programme team before the kick-off call, and write down who signs off.
Questions that keep changing. Every new registration question after launch creates profiles without an answer. Fix the matching questions first and leave nice-to-have fields out; our article on registration questions that make matchmaking work shows which ones to ask before confirmation and which ones later.
Approvals in a queue. A security questionnaire that lands in an inbox just before the summer holidays can cost weeks on its own. Send it with the contract, not after it.
Integrations without an owner. PheedLoop notes that native integrations can take days, while custom connectors can take weeks and usually depend on another vendor’s cooperation. If your CRM or association database must talk to the platform, name one person on your side who owns that connection.
No plan for the last week. Meetings booked six weeks ahead still need reminders, a cancellation path and someone who rebooks free slots. Our guide to meeting no-show rates covers what that person should do.
None of these is technical. That is why the event director, not the vendor, holds most of the timeline.
In Converve, setup means configuring a rule-based meeting matrix: which participant groups may meet one another, how many meetings each group can have, which time slots and meeting locations exist, and whether meeting requests need an approval. The registration questions feed that matrix directly. Converve’s published service plan starts with access to the project briefing on the day of signing, a kick-off within seven days and registration opening no later than four weeks after the kick-off, with one dedicated contact who sets up the matching rules with you. You can see the full plan on our services page and how the matrix works on our B2B matchmaking platform page. Recurring events can start from the previous year’s configuration.
How long setup takes is only one part of the decision. What it costs, including implementation fees, is covered in our event matchmaking software pricing guide. If your event has fewer than 150 participants, check first whether matchmaking pays off at all with the four tests in matchmaking for small events.
Frequently Asked Questions
How long does it take to set up event matchmaking?
For a mid-sized B2B event, typically around two months, roughly six to ten weeks, from contract to the first booked meeting. The configuration itself often takes a few weeks; event platform vendor PheedLoop puts implementation at four to eight weeks for mid-complexity events and two to three weeks for simple ones (PheedLoop, 2026). The rest is matching rules, approvals and a registration period long enough to fill diaries.
Can you set up event matchmaking in two weeks?
For a simple event with one participant group, no integrations and ready registration data, a setup in two to three weeks is realistic (PheedLoop, 2026). What two weeks do not give you is a long meeting window. Participants need time to register, complete profiles and book, so a late start mainly shortens the time for meetings.
When should meeting booking open before an event?
Curated partnering programmes can start around six weeks out; Oxford Global, for example, sends partners the attendee list six weeks before the event and the final schedules in the last week (2026). Open self-booking formats can start later. Keep booking open until shortly before the event, because many attendees register late: 45 per cent within four weeks of the event in Maritz’s 2023 trade show data.
What delays a matchmaking implementation most often?
Rarely the software. Typical causes are matching rules agreed too late, registration questions changed after launch, data protection and IT security approvals, and custom integrations with a CRM or member database. PheedLoop (2026) lists data readiness, integrations, approvals, scope creep and hard lead times such as badge production as the main risks.
Does a recurring event need the full setup again?
Usually not. If the rules, questions and slot structure worked last year, you can copy the configuration and adjust what changed: new participant groups, a different venue layout or new sponsors with meeting packages. Use last year’s meeting statistics to decide which rules to tighten.
Conclusion: plan from the meeting window
Setting up event matchmaking is mostly a question of decisions, not software. If the matching rules, the registration questions and the approvals are ready early, the configuration fits into a few weeks. The time you protect is the meeting window, because that is where your participants decide whether the event was worth it. When sales asks again when booking opens, you can give a date and explain it.
If you want to plan your timeline with a team that sets up matching rules every week, get in touch with Converve.
