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.
Why one system
Every integration is a place the truth splits in two.
The usual arrangement is a registration platform, a badge printer, an agenda tool, a website, a matchmaking add-on and a spreadsheet holding them together. Each pair is a nightly sync, and every sync is a window in which two systems disagree about who is coming.
That is not a tidiness complaint. It is where the day goes wrong: the person who upgraded their ticket this morning whose badge says the old tier, the matchmaking that ranked forty people who cancelled last week, the sponsor report that cannot say which of the meetings actually happened because attendance lives somewhere else.
Here there is one record of a person at an event, and everything reads it. The engine ranks the people who really registered. The badge prints the tier they really hold. The report counts the meetings that really happened, because the same system scanned them in.
Ticketing and invoicing
Money handled like money.
Selling a ticket is the easy half. The half that gets an organiser in trouble is the invoice: the number that has to be sequential, the VAT that has to be right, the refund that has to leave a paper trail.
Paid and free, in one flow
Ticket types with their own prices, limits and windows. Free events skip the money entirely rather than pretending to charge zero.
Invoices that survive an audit
Sequential, gapless invoice numbers per event. VAT handled with the rate on the line rather than reconstructed later, and a credit note when something is refunded.
Discount codes that behave
Percentage or fixed, with a usage cap and a window. Applied before tax, shown on the invoice, and impossible to stack into a negative total.
A claim code becomes a person
Buy five seats for a team you have not named yet. Each seat carries a code that turns into a real registration when the person who is coming uses it.
Card details never reach us — payment goes through a payment provider, and the sale is between you and your buyer. You set the price, the tax treatment and the refund policy, and the money is yours.
The door
The two hours that decide what people remember.
Nobody praises a registration desk. They only ever remember the queue. The door is built to be worked by somebody hired for the morning, on their own phone, with no training and no room for a mistake that costs anybody their afternoon.
Badges you design
A layout editor in millimetres, with your logo, your colours and the fields you want on it. Prints correctly on the printer you already have, not a proprietary one.
Scan in, scan out
A QR badge and any phone. Re-entry is handled properly — somebody stepping out for a call comes back in rather than being told they are already inside.
A live count of the room
Who is in the building right now, not who has ever arrived. The number a venue asks for and the one a safety officer needs.
Somebody on the door sees the door
Door staff scan badges and nothing else. They cannot read what your attendees came to buy, and they cannot see the takings.
The agenda and the floor
What is on, where it is, and who fits in it.
A programme is not a PDF. It decides who is free when, which decides which meetings can be offered, which is the whole matchmaking product — so it lives in the same place as everything else rather than beside it.
Sessions with real capacity
A seat limit that is enforced when the seat is taken rather than when the page loaded, so twenty seats means twenty even when two hundred people press at once.
Waiting lists that move
A full session queues rather than refusing. The queue is ordered by when somebody joined, promotes the moment a seat frees, and tells the person who got in.
Stands, and the people on them
Exhibitor stands with their team, their tier and their story. Buyers reach a named person rather than a company inbox, because five people on a stand are not interchangeable.
The agenda drives the diary
A session somebody is attending is time nobody can be offered a meeting in. One source of truth for where everybody is, rather than two calendars that disagree.
And it answers the question a programme usually cannot: when a workshop fills, you can see how many people are still queueing for a seat. That is the only measure of demand a full session has, and it is the argument for next year’s floor plan.
Lead capture
What your exhibitors came for.
An exhibitor does not buy a stand for the carpet. They buy the people who walk up to it, and every show in the world hands them a badge scanner and a spreadsheet of names that arrives a week late.
Here the scan happens in the same product that already knows why that person came, so what an exhibitor ends up holding is not a name and an email but a sentence explaining what to say next. And because the attendee decided in advance what to hand over, the exchange is deliberate on both sides rather than something one party did to the other.
Scan a badge, get a card
Your exhibitors scan the people they talk to and get their name, company, contact details and — the part paper cannot do — what that person said they came for.
Consent you can prove
The attendee chooses what is on their card and is told it is shared when somebody scans them. What they had chosen at that instant is stored with the lead, so an exhibitor's own compliance team has an answer.
It works with no signal
A hall is a shed full of metal and a thousand phones. Scans are kept on the device and sent when there is something to send them on, so the busiest hour is not the one that fails.
One list for the stand
Everybody on a stand scans into the same pipeline. The same person met twice is one lead seen twice, not two rows — and it downloads as a spreadsheet for whatever they use afterwards.
Somebody who has made themselves invisible to an exhibitor cannot be scanned by them. That holds whatever the organiser has switched on.
Your public site
The event’s front door, without a developer.
The page people see before they trust you with a card number. It should be yours, it should be changeable at nine on a Sunday evening, and it should never be a week of somebody else’s time.
A page builder, not a theme shop
Your colours, your fonts, your logo, your words, arranged in blocks. No developer, no ticket to an agency, and no waiting a week to change a date.
Shares as a proper card
A link posted anywhere renders with the event's own image and title, generated from what you built rather than from a default nobody set.
The programme, published
Sessions, speakers, stands and the floor, drawn from the same data the event runs on. A public page that cannot drift from the agenda, because it is the agenda.
Nothing injected
No tracking pixels are added to your page by us. What is on it is what you put on it.
Your team
Seven roles, and none of them see everything.
A big event is run by people you hired for a fortnight. Giving all of them the same login is how an attendee list ends up somewhere it should not be, and “we trust our staff” is not an access model.
So what somebody can do is a named set of capabilities attached to their role, and it is enforced by the database on every single query rather than by hiding a link. Somebody working the door scans badges. Somebody in marketing edits the public page. The takings are visible to the people who run the business and nobody else.
- Owner, admin, and five working roles beneath them
- Twelve capabilities, granted by role and checked per request
- A hidden link is a convenience; the rule is enforced on the query
- Every use of an administrator's access is logged with a reason
Afterwards
The document you take into next year.
An event ends and the argument starts: was it worth it, who should come back, what do we charge for a stand. Most organisers answer that from a badge-scan count and a feeling.
Because the meetings, the door and the agenda are the same system, the report can say what actually happened rather than what was planned — per exhibitor, per sponsor, per stand. Meetings agreed, meetings held, and who did not turn up.
That last number is the one exhibitors renew on. A stand that can show eleven meetings held with named buyers does not need to be sold a stand next year.
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.
And what it will not do
The part a buyer should read twice.
You are handing over your customer list. Everything we refuse to do with it is written down, in the privacy policy and in the data processing terms — and the ones that matter are enforced in the database, not promised in a paragraph.
- We do not email your attendees. Nothing goes to your list that you did not send
- We do not sell, rent or train on your data
- Registering broadcasts nothing about who is attending what
- Anybody can make themselves invisible, including to you
Bring us your hardest event.
Organiser accounts are opened after a conversation rather than by signing up, because we only take on events we can support properly. Tell us what you run and when it is.