Ten seconds per person, and a list that survives the flight home

Built for standing up, one free hand, bad light and worse wifi.

Here's what a day at the booth looks like with it.

Getting started Back to Badge Scanner

Before the doors open

Create the event

Give it a name and a city. You're automatically its first member.

Bring the crew in

Share the event's join link. A colleague opens it on their phone, signs in, and is adding contacts to the same event before the next attendee walks up. Before you send an invite, the screen tells you exactly what it will do.

At the booth

1 · Photograph the badge

The photo is saved on the phone straight away. With a signal, the details come back in seconds. Without one, the contact waits on screen with its photo and fills in when the phone reconnects. If the badge has a QR code, the app reads that too, but it never depends on it.

2 · Confirm and correct

Check the name, title and company. Anything you type by hand is never overwritten when the app finishes reading the badge later.

3 · Dictate the note

Say what you talked about and why you'd follow up, because nobody types a paragraph in an expo hall. Flag the contact if it needs a proper email.

After the event

Open the event's list on the flight home. Filter to the flagged contacts, work down the list, add to the notes, and mark each one done.

For people you want to connect with, the app opens a LinkedIn search built from their badge. You pick the right person and connect. Save their profile link to the contact.

When you've worked through the list, export it as a CSV file for a spreadsheet or CRM import, or as a vCard for your phone. You can also copy a ready-made summary of any contact into an email. You don't have to export anything for the app to be useful: export is how you take the data elsewhere, not something you depend on.

What it's built on

Badge Scanner is built on AI Application Manager. Sign-in, usage tracking and AI access come from the platform, so the app holds no AI vendor key of its own. Badges are read by work queued in the background, which is what makes offline capture dependable.

Planned but not built yet: sending contacts straight into the CRM where they belong (NetSuite, Salesforce or HubSpot), and a notification when a colleague adds someone to the event you're working.

Working a booth soon?

Tell us the event, the dates, and how many people are staffing it.

Getting started