Skip to content

Meet someone at a stand. Capture them in seconds. You decide how it reaches your CRM.

Scan a business card, speak a voice note or type a few details. Every capture lands in a single list, even while your CRM connection is down.

Three ways in, one record out

A card scan reads name, company, title, email, phone and whatever else is legible, and shows you the result before anything is sent anywhere. A voice note produces the same kind of record from a transcript — the raw audio itself is never stored. Typing works when there's no card and no time to record anything: just something identifying is enough to keep the conversation from getting lost.

Card scan, voice note or manual entry — pick whichever fits the moment
Every extraction is shown back to you for correction before it goes anywhere
An unreadable card tells you so, rather than saving a silently empty record
A scanned card, a voice note and a typed entry all producing one capture record
A scanned card, a voice note and a typed entry all become the same kind of capture record.

Your CRM gets a lead when you say so

A capture is a complete, durable record the moment it's made — before we've talked to your CRM at all. It reaches your CRM when someone on your team syncs it, or automatically once an admin turns on auto-sync, and every automatic write is in the audit log. A retry never creates a second record for a capture that already produced one.

Leads sync on a click, or automatically once an admin turns on auto-sync
Anything the assistant suggests changing waits for your Approve or Reject
A capture is safe on a bad connection: it's saved before any CRM call is attempted
A proposed CRM write pausing at an approval gate, with a decline path that stops it
A change the assistant proposes waits at the gate. Approve it and it reaches your CRM; reject it and it stops there.

Everything you captured, in one place

Your captures live in a list of their own — not a view onto your whole CRM contact base — and it renders without a single CRM call, so it works even when your connection doesn't. Every row shows what was captured, how, when, by whom, and whether it's reached your CRM yet, still awaiting approval, failed, or was declined. Scan the same person twice and their captures group into one entry instead of cluttering your list with duplicates.

Search and filter by source, date, sync state or the teammate who captured it
An unambiguous state on every row: pending, awaiting approval, synced, failed or declined
Repeat captures of the same CRM record group into one entry, not several
One list of captures from every source, with repeat captures of the same person grouped together
One list, every source. Two captures of the same person sit grouped under one entry.

What this doesn't do yet

Worth knowing before you switch, rather than after.

  • No automatic retry on a failed sync. A capture that didn't reach your CRM, or a tag or note that went stale after a re-attribution, is shown clearly on its detail page — but it isn't re-sent for you. Clear or re-apply it in your CRM directly if it needs to match.
  • The captured value is a snapshot, not a live read. What a card or voice note captured is exactly what was true at that moment, labelled with the date it was captured. It isn't refreshed from your CRM afterward — for that, ask the assistant about the person directly.
  • Raw audio is never kept. A voice note is transcribed to populate the capture, and the transcript is what's used. The audio itself is never stored anywhere.
  • We never invent our own idea of "the same person." Captures group together only when they resolved to the same record in your CRM. We don't run our own matching or merging logic on top of that.

Capture the lead. Approve the write. Move on to the next conversation.

Lead capture is included with every RareMachine workspace — there's no separate seat to buy.