[PLATFORM_LAYER]

One record behind the sale, the door, the sponsor and the paperwork.

Producers and event managers lose hours between tools: a ticket list here, a contractor spreadsheet there, a sponsor’s leads in someone’s pocket. AdmitMe writes ticketing, inductions and exhibitor management to the same event and person records. A lapsed insurance certificate can stop a badge from printing, and an exhibitor’s stand staff reach the door without anyone re-typing them.

Start free trial Talk to a person

28-day free trial, no card needed A person replies within one business day (AEST)

Who sees what

ProducersSales by category, money in, and what each sponsor got.
Event managersWho is cleared, who is in, and what is still outstanding.
Door staffThe ticket, the name and the result. Nothing more than their role needs.
Sponsors and standsTheir own leads, and nobody else’s.

Start from the outcome

What the modules add up to.

You do not buy a module. You want a full room, a calm door, happy sponsors, clean paperwork and your money. Each of those is the work of one or two modules below.

Fill the room

Ticketing: categories, caps, sale windows, codes and wallet passes.

Explore ticketing

Run a calm door

Ticketing and access: scanning that works offline, with roles for door staff.

Run the door on show day

Give sponsors leads

Lead capture, with exhibitor management behind each stand.

Explore lead capture

Clear people in advance

Inductions, with expiry checked against your event dates.

Explore inductions

Keep the money

Direct payouts through Stripe Connect, and no ticket commission.

Get paid

Choose your seat

The same platform, read from two jobs.

For producers For event managers

The modules

What each one owns.

Module	Who it is for	What it produces	Where it enforces
Ticketing	Attendees and the public	A paid, named ticket with a scannable code and a wallet pass	At the door — the scan is the gate
Inductions	Contractors, crew, volunteers and stand staff	A dated induction record with the evidence attached and an expiry	Before dispatch — expiry blocks accreditation
Exhibitor Management	Exhibitors, sponsors and suppliers	An approved stand: forms, orders, invoices and a booth allocation	At bump-in — no approval, no build
Exhibitor Manual	Exhibitors, adapted per exhibitor type	A portal with the right information, the right tasks and a visible deadline for each	Before a task is due — chased automatically, not discovered late
Supplier Operations	Suppliers, riggers and equipment providers	An assigned order with a fulfilment state and a delivery window	At delivery — the order state gates what leaves the dock
Lead Capture	Exhibitors, sponsors and brand activations	A qualified lead with a note, an operator and a timestamp	Nowhere — it captures value rather than gating it
Access & Identity	Everyone physically on site	A printed badge, or a palm bound to the person and their zone rights	At every door — live credential status, not a list of names

Every module writes to the same event. An organiser sees one dashboard; an exhibitor sees one portal; a contractor sees one link — and the reader on the door sees the same approval record the compliance queue has been maintaining for six weeks.

The CrowdSense Ecosystem

Sensing, admission, delivery.

Three brands, deliberately separated by what they are allowed to know. CrowdSense stays anonymous by design. AdmitMe holds identity because admission requires it. Artefact Group builds and runs both.

Anonymous by design

CrowdSense

Reads the Bluetooth signals already present in a crowd, plus camera-based counting, to measure presence, dwell and movement. No identities, no personal data — which is exactly what makes it deployable at scale.

crowdsense.events

Identity-bound by necessity

AdmitMe.

Holds the named record because admission decisions require one: a ticket belongs to a buyer, an induction belongs to a worker, a stand belongs to a company. Consent is explicit and scoped to the event.

See the compliance model

Engineering and operations

Artefact Group

Designs and runs both platforms, plus the parts that are always bespoke: venue integrations, hardware installs, network and signage, and the joint deployments where sensing and admission have to agree on a site plan.

artefactgroup.au

Integrations

Connected where it counts.

AdmitMe is deliberately narrow about what it replaces. Payments, accounting and email stay in the systems your finance team already trusts.

Firebase

Auth, Firestore, Storage, Hosting and Cloud Functions, with every organisation kept apart from the first row.

Stripe & Stripe Connect

Ticket sales, stand deposits and subscription billing. Connect accounts mean money moves from the buyer to you, without sitting in an intermediary account first.

Xero — by attachment

There is no Xero API sync. You raise the invoice in Xero and attach the PDF to the exhibitor record, where the due date and payment status are tracked — so chasing happens against the same list you approve stands from, while Xero stays the book of record.

Engagement analytics — GA4

Every portal link, reminder and invoice email is tracked per exhibitor through Firebase Analytics / GA4. You can see who opened what, and when — which changes the conversation on a missed deadline.

Apple & Google Wallet

Tickets install as wallet passes with the event branding, so attendees stop hunting for a PDF at the gate.

Transactional email

Confirmations, reminders and overdue alerts send on per-event schedules you configure once — 14 days, 7 days, 1 day, then escalation.

Palm vein readers & badge printers

On-site hardware — enrolment stations, gate readers and badge printers — surveyed, installed and configured against your site plan by Artefact Group. See access & identity.

Aura asset management

Assets, bookings and custody for event equipment, by Artefact Group. Supplier Operations hands off equipment custody to Aura at shelf.artgrp.au rather than tracking it in a spreadsheet. See supplier operations.

CrowdSense

Joint deployments align the AdmitMe access model with the CrowdSense site plan, so live occupancy and credentialed presence describe the same zones.

Read the brief

Data and privacy

We do not sell your attendees.

Attendee and exhibitor data belongs to the organiser. AdmitMe does not monetise it, does not resell it, and does not use one client's list to market to another. The split with CrowdSense is deliberate: sensing stays anonymous, admission keeps identity, and neither borrows from the other without an explicit, event-scoped reason.

Role-based access. Organisers, exhibitors, suppliers and platform staff see different data, enforced at the database rules layer rather than in the UI.
Scoped portal links. Exhibitors and contractors work through tokenised links that grant access to their own record only.
Audit trail. Approvals, rejections and changes are recorded against the submission, with who and when.
Biometric templates are opt-in and revocable. Palm vein enrolment stores an encrypted template, never an image, scoped to your deployment. Delete it and the credential ceases to exist. How it works.
Lead data has a scope you set. Exhibitors retrieve only their own leads, enforced at the API. Lead sharing.
Export on request. Your data leaves in a usable format if you leave.

Talk to a person

Talk it through with a person.

If you are working out how the pieces fit your event, a person can walk you through it.

A 20-minute walkthrough. Shaped around your kind of event, with your questions first.
Help setting up your first event. We work through it with you in your trial, step by step.
Straight answers. On fit, on pricing, and on what AdmitMe does not do.

Request a 20-minute walkthrough Get help setting up my first event

Both open a short form. A person reads it and replies by email within one business day (AEST).

See it against a real event.

Bring one upcoming event across on the trial. Most organisers find the gaps between their systems in the first afternoon.

Start free trial Read the guides