State-of-the-art AI matchmaking for business events
Nine hundred people in a hall. Four conversations that mattered.
Everybody in that room paid to be there, cleared two days, and flew in to meet somebody specific. Most of them went home having met nobody in particular — and told their finance director the event was fine.
B2Pair turns the room into a list. Every attendee opens the app to the people actually worth their time, ranked, with the reason attached — and you get the whole event underneath it.
Access is switched on per organiser, after we have spoken. There is no self-serve tier and no free trial.
Anna Vogel
Head of Procurement · Northwind Logistics
She is eighteen months into a retrofit programme across two chilled distribution centres and has a signed budget for Q1. You install exactly this, in this region.
Why we think so
Budget signed, decision due by Q1
— what she wrote when she registered
Two chilled sites near Rotterdam
— her company page
You ship Nordic installation partners
— your own profile
Be careful about
She cannot stop picking during a cutover. Lead with phasing, not with throughput.
An illustration of a real slate. Names and figures are made up; the shape, the sources and the caution are exactly what the product writes.
The meetings are the product. Everything else is a venue booking.
Your attendees
They came to buy or to sell something specific. You handed them a searchable list of nine hundred names and a coffee break, and asked them to find each other. Most did not.
Your exhibitors
They spent five figures on a stand and cannot tell you what it returned. When renewal comes round, “it felt busy” is the only case they can make internally — and it loses.
You
You are judged on something you have no lever over. Footfall is measurable, catering is measurable, and the one thing everybody actually came for is left entirely to chance.
The engine
Matching that shows its reasoning.
Anybody can sort a list by keyword overlap and call it AI. The hard part is being right, and then being able to say why — because an attendee who does not believe the suggestion does not act on it, and an unacted-on match is worth exactly nothing to you.
Our engine reads what both people came to do, weighs the match in both directions — a supplier who is thrilled is useless if the buyer is not — and writes the case in plain words, with the source under every claim. It refuses to introduce two people who arrived together, it knows the difference between somebody buying and somebody selling, and it says what to be careful about rather than pretending every meeting is perfect.
It reruns whenever the room changes. Somebody registering on the morning of day two rewrites the slate for everybody they matter to.
- Ranked per person, per event — not one global directory
- Scored both ways, so a match has to work for both diaries
- Every claim carries where it came from
- Says what is likely to go wrong, not only what is promising
What changes on the day.
Every attendee
arrives with a list
Not a directory to search. A ranked slate of the people worth their time, with the reason attached, waiting when they open the app.
Every exhibitor
can prove the stand paid
Meetings agreed, meetings held, and who they were with. The number a sponsor asks for when you go back to them next year.
Every organiser
gets the day, not a spreadsheet
Tickets, badges, the door, the agenda, the floor plan, the public page and the report — one system, one login, one source of truth.
What happened
Northern Logistics Expo
612
attended
1,043
meetings agreed
918
actually happened
88%
turned up
What each stand got
- ColdLine Nordics41 meetingsGold
- Retrofit Systems36 meetingsGold
- Greenfield Robotics22 meetingsSilver
The document you take into next year's budget conversation — and the one your sponsors ask for before they renew.
Illustrative figures. The shape is the report the product writes after every event.
The platform
And the whole event underneath it.
Matchmaking bolted onto a registration tool is two systems, two logins and two versions of who is coming. This is one product: the engine knows about the tickets, the badges know about the roles, and the report knows about all of it.
Matchmaking that explains itself
A ranked slate per person per event, rewritten whenever the room changes. Every match carries why, in plain words, with the source under each claim.
Ticketing and invoicing
Paid and free tickets, discount codes, VAT handling, sequential gapless invoice numbers, refunds, and a claim code that turns into a registration.
The door
QR badges you design yourself, printed on any printer in millimetres. Scan in, scan out, re-entry handled, and a live count of who is in the building.
The agenda and the floor
Sessions with real capacity and waiting lists, tracks, rooms, exhibitor stands with their teams, and a public page that shows all of it.
A public site you control
A page builder with your colours, your fonts, your logo and your words — no developer, no theme shop, and a link that renders as a proper card when somebody shares it.
The report afterwards
Who came, who met whom, what came of it, and what the room was worth. The document you take into next year's budget conversation.
What we will not do
You are handing us your customer list. We know what that costs you if we get it wrong.
We do not email your attendees behind your back
Nothing goes to your list that you did not send. No product newsletters, no cross-event promotion, no growth loops running through people who trusted you rather than us.
We do not sell or rent your data
Your attendee list is yours. It is not a dataset, it is not training material for anybody else's model, and it does not leave the event it belongs to.
Registering broadcasts nothing
Who is going to which event is commercially sensitive. Nothing about an attendee is published unless that person chooses to publish it, and the choice is asked for once.
Anybody can disappear
An attendee can make themselves invisible to a company or to one person, silently, with no mark on the other side. It holds even against the organiser running the event.
None of these are promises in a policy document. Every one is enforced in the database itself, underneath the application, where a mistake in our own code cannot get round it — and there are over two thousand one hundred automated checks that fail the build if any of it stops being true.
We switch this on one organiser at a time.
Not scarcity for its own sake. An event happens once, on a date that cannot move, and a matchmaking engine that arrives half-configured on the morning is worse than none. So we take on organisers we can support properly, and we would rather say no than be the reason your day went badly.
Tell us what you run and when it is. If it fits, we will set it up with you.