Business cards in, structured contacts out.

The problem we started with

Everybody who works a trade show comes home with a stack of cards and good intentions. The cards sit on a desk. A week later the conversation has faded, the follow up never happens, and the money spent on the stand quietly goes to waste.

Typing them up is nobody’s job and so it is nobody’s priority. The tools that promise to help usually want the whole team to learn something new during the one week of the year they have no time to learn anything.

What we built instead

One thing, done properly. Photograph a card, and the parsed contact appears in a dashboard your team can search, filter and export. From there it syncs into Google Sheets or your CRM, so nobody has to move it by hand a second time.

• Scanning works with no signal. Cards queue on the phone and upload themselves when the connection comes back.
• A field the parser is unsure about is flagged for a person to check, never quietly guessed.
• The original photograph is kept for seven days so a correction can be made against the card itself, then deleted.

How we think about your data

The contacts in CardParse are real people who handed a card to somebody at an event. They did not sign up to us and they cannot see what we hold. That asymmetry is the reason we are careful.

Card data is stored in the United States. Photographs are deleted on a schedule rather than kept in case they are useful. We do not sell data, we do not build a shared contact graph across customers, and one customer’s records are isolated from another’s at the database itself rather than only in application code.

Where we are

CardParse is a small team. That shows up in the product as a narrow set of things that work well rather than a broad set that mostly work, and it shows up in support as a reply from somebody who can change the software.