Every trade show ends with a stack of business cards. Rubber-banded in a jacket pocket, a few with notes scrawled on the back, most attached to a conversation somebody on the team half remembers. The stack is pipeline, and it decays by the day.
This post covers one thing: getting that stack into the CRM as clean, attributed records. The general sync mechanics, field mapping, Lead vs Contact, campaign setup, live in the hub at event leads to CRM. Here we deal with the card itself, mostly for Salesforce, with HubSpot alongside.
How do you scan business cards into a CRM?
Photograph the card, OCR the text, enrich the contact, then push it through the CRM's API. The alternative is typing them in on Friday.
Four steps, and each one earns its place. The photograph captures the card before it disappears into a pocket. OCR pulls the printed text into structured fields: name, title, company, email, phone. Enrichment fills what the card leaves out or what OCR misreads, matching the person against data providers to add a verified email, a LinkedIn profile, firmographics. The API push is the step most card apps skip: writing the finished contact directly into Salesforce or HubSpot as a record, deduped and attributed, instead of parking it in an export file.
Skip the pipeline and you get the default workflow. The stack rides home, somebody types the cards in at the end of the week, and follow-up starts a week after the conversation it depends on.
Why do business cards still matter at trade shows?
The card is the one lead artifact you own outright. The contact is printed on its face, no organizer system needed to read it.
Compare it to the badge. A badge barcode encodes an opaque registration ID, a license plate. Only the organizer's contracted lead retrieval system can resolve it into a name and an email, which is why scanner rentals exist and why they run $400 to $700 per device per event. Scan a badge with a generic app and you get a meaningless string.
The card has no such gate. The data is printed on the object itself. It works at every event regardless of who organizes it, and it works in the places badges never reach: the hallway conversation, the dinner after the floor closes, the flight home next to someone who turns out to run procurement. Nobody rents you access to a business card.
Which is why a card pipeline is worth building once and reusing everywhere. Badge access resets every show. Cards behave the same at all of them.
What should a business card scanner for Salesforce actually do?
Live API upsert as a Lead or Contact, dedup against existing records, event attribution, custom field mapping, under 10 seconds per scan.
Take those one at a time, because each is a place where tools quietly fall short.
Live API upsert. The scan should become a Salesforce record while you are still at the booth, written through the API as a Lead or a Contact, whichever object your org routes on. Upsert, not insert: if the record already exists, update it.
Dedup against existing records. The buyer who handed you a card may already be in the org from a webinar or a previous show. A scanner that blindly inserts gives your SDR two records for one human, and the follow-up sequence fires twice.
Event campaign attribution. The record should land attached to the event's Campaign. That one link is what lets you answer, months later, what pipeline the show produced. Without it, event ROI reporting is guesswork.
Custom field mapping. Booth notes, lead score, which product line they asked about. If the scanner cannot write your custom fields, those details live in a notes app until they die there.
Under 10 seconds, scan to record. Speed is the point of the exercise. If the record takes a day to appear, you have rebuilt the Friday typing session with extra software.
Generic OCR card apps fail most of this list. They read the card fine, then export a CSV you import by hand: a filing cabinet with a camera. The dedup, the attribution, the mapping all become your job, per show. Setup details for the direct path are on the Salesforce lead retrieval page, and how the wider tool field compares on integration depth is in lead retrieval CRM integrations.
How does card scanning work with HubSpot?
Same mechanics as Salesforce: the scanner writes contacts through the HubSpot API, dedupes by email, and tags each one with the event.
HubSpot makes the pattern simpler. Everything is a contact, dedup keys on email address, and the event lands as a property or list membership you can trigger workflows from. The bar stays the same: a live API write, not a CSV, with the scan visible in HubSpot before the prospect leaves the aisle.
Integration specifics are on the HubSpot lead retrieval page, and the full workflow, capture through sequence enrollment, is in connecting trade show leads to HubSpot.
What goes wrong between the card and the CRM?
Bad OCR on stylized cards, duplicate records across shows, missing event attribution, and the Friday CSV that stalls follow-up for days.
OCR is the visible failure. Dark backgrounds, script fonts, vertical layouts, foil logos: design-forward cards are exactly the ones OCR mangles. The fix is enrichment layered on top. If OCR gets the name and company roughly right, a data-provider match fills in the verified email and title the card art obscured. OCR reads the card. Enrichment reads the person.
Duplicates are the slow failure. The same buyer hands over a card in Chicago in March and in Vegas in September. Without dedup at sync time, that is two records, two owners, and eventually two competing sequences.
Attribution is the silent one. A card typed in or imported without an event tag becomes a sourceless contact. The show that produced it gets no credit, and next year's budget conversation suffers for it.
The lag is the expensive one. A stack that waits for Friday data entry means your first follow-up email arrives after the one from the booth across the aisle, where the scan synced the same afternoon.
Can you scan cards offline at a venue?
Yes, if the app queues scans locally. Venue WiFi is unreliable, so offline capture with sync on reconnect is the requirement.
Venue connectivity deserves your distrust. McCormick Place's own guidance caps complimentary WiFi at 768 Kbps and points exhibitors toward wired drops for anything that matters. That is before a hall full of exhibitors shares the signal, and cellular fares little better inside a concrete exhibition hall.
The workable design is a local queue. The photo and every field captured with it store on the device, the app keeps scanning at full speed, and the queued records sync in order when a connection returns. Connectivity then costs you minutes of sync delay, never a lead. An app that needs a live connection per scan fails at the exact hour the booth is busiest.
Test it before you need it: airplane mode, three scans, reconnect, confirm all three land.
Should you use a free card scanner app for events?
Fine for a handful of personal contacts. At booth volume they end at a contacts file or CSV, with no dedup, attribution, or team view.
The honest version: a free scanner app is a good tool for its actual job. One conference, a dozen cards you personally collected, contacts you want in your own phone. It handles that.
A booth is a different job. Three teammates capturing in parallel, hundreds of cards, an org full of existing records to dedup against, a campaign to attribute to, sequences waiting on the data. Free apps terminate in a personal contacts file or a CSV export, which puts you back at the manual import with none of the mapping, dedup, or attribution handled. Nobody owns the merged list, so two reps chase the same prospect or, more often, nobody does.
Use the free app for your own pocket. Use a pipeline for the booth.
How does Tendro handle business cards?
OCR plus enrichment on cards, badges, and notes, scored at capture, synced to Salesforce or HubSpot in under 10 seconds. $499 per event with unlimited team members.
Disclosure, I build Tendro, so filter accordingly.
Tendro treats the card as one input among several. Business cards, badges, QR codes, even handwritten notes run through the same OCR plus enrichment pipeline, so the stylized-card problem gets the data-provider backstop described above. Each capture gets a hot, warm, or cold score at the moment of capture, while the conversation is fresh, and scans queue offline and sync on reconnect.
Sync is native for Salesforce and HubSpot, and any CRM with a public API is reachable. Scan to deduped, event-attributed record in under 10 seconds. The broader capture workflow, badges and QR included, is on the event lead capture pillar.
Pricing is $499 per event with unlimited team members, never per device. A season pass covers teams running a full calendar. The free trial is deliberately simple: scan a stack of old business cards at your desk, free, and judge the enrichment quality yourself. CRM sync starts with your first paid event. Start at app.tendro.com.