Article · 6 min read

OCR is a feature. The follow-up is the product.

The category has spent fifteen years competing on scan accuracy. The audience keeps writing the same review: the scan worked, the follow-up never went. The 72-hour window is the actual product, and the apps that optimize for OCR are losing their users to a problem they don't sell against.

The review that recurs across every category leader

Across 142 one-to-three-star reviews on the three largest business-card scanner apps, one complaint repeats more often than any other. It isn't "the scan was wrong." It's a near-quote: *"I have to spend more time editing the scan than I would spend entering the data myself. That defeats the purpose, doesn't it?"*

Twenty-four reviews say a version of that line. Each app's marketing pitches OCR accuracy as the primary value. Each app's review stream says, in the user's own words, that the OCR isn't accurate enough to be a primary value. Both things have been simultaneously true for fifteen years.

The category has been arguing with itself about the wrong feature. The actual product, the one the audience is trying to do and not finishing, sits one step downstream of the scan: the follow-up. The 72-hour window after meeting someone, when a personal note still feels personal and not perfunctory, is what the buyer is actually paying for, and not one of the category leaders surfaces it as the headline value.

Pattern 1: OCR-vs-action — the scan that goes nowhere

The first pattern is the most direct. The user opens the app, scans a card, the OCR mostly works, and then they put the phone down. The contact gets stored. The follow-up doesn't get sent.

The corpus surfaces this in different language each time but the same shape: *"Had the app for a long time and it was functional. Not used frequently but was reliable."* The data was captured. The action wasn't taken. The app's job was capture; the user's job was the follow-up; the gap between those two jobs is where every meaningful business outcome lives.

This is the foundational confusion. OCR is the act of converting a card into a record. That conversion is necessary, but it's not what the user is hiring the app to do. The user is hiring the app to convert a meeting into a relationship. The first happens in milliseconds and is now table-stakes; the second takes 72 hours of compounding effort and is invisible to every category leader's product surface.

Pattern 2: capture-vs-followup — the apps that stop at the scan

The second pattern is structural. Look at what the category leaders do, screen by screen, after the scan completes. CamCard takes you to a card-detail view. Blinq takes you to a card-detail view. ABBYY takes you to a card-detail view. None of them takes you to a draft.

The screen after the scan, in every shipping incumbent, is the screen where the contact lives, alphabetized, edit-ready. It's a rolodex screen. It's where the data goes to wait. It's also where 80% of the user's intent dies, because the user opened the app on the conference floor with a follow-up to write, and the app handed them back a contact-management view.

Nine reviews in the corpus complain about this in some form. Almost all use the same word: *"useless"*. The strongest version: *"If you trust this and it gets one digit of an email or phone number wrong you're in big business trouble. Just enter your stuff manually."* The user doesn't trust the OCR enough to skip verification, and the verification step doesn't end at a draft, so the user never gets to the action that justified opening the app. The capture screen and the follow-up screen are the same screen in zero category leaders. Met is the only app where they're connected by default.

Pattern 3: list-vs-relationship — the rolodex that nobody asked for

The third pattern is the one most invisible to the buyer until they've used the app for six months. The category leaders organize captured cards into a list. A rolodex. A searchable catalog of people the user has met. This is presented as the product, the data asset the user is accumulating.

The rolodex is also useless. Eight reviews in the corpus say a version of: *"Used to be a great app. Bought this years ago and was impressed at how well it worked. But over the past few years the app has gradually [degraded]. I have a stack of cards I've scanned and never done anything with."*

The pattern repeats across years and across apps because the underlying mistake is the same. Storage isn't the value. The category has been competing on better storage, prettier list views, more searchable contact-databases. The user keeps writing back: I have a contact-database; what I don't have is a relationship. The rolodex is a record of failed follow-ups, not a record of business contacts. Cleaning it up is busy-work; replacing it with a follow-up workflow is the actual job.

Met's wedge against this pattern is structural, not aesthetic. Captured contacts default to a draft view, with a follow-up draft generated from the meeting context (where you met, the tags you applied, the note you typed in), in the tone you specify. The follow-up is the page after the scan. The contact-list view exists, but it's not the default. The user can find it; the user doesn't have to leave the action surface to do so.

The structural reason the category got stuck

OCR-as-product is a pre-2015 framing. It was the right pitch when scanning was hard, when the OCR result was the genuine value-add, and when nobody had a smartphone camera that could read a business card cleanly. The technology matured. The pitch didn't.

The consequence is a category where the leaders all ship the same shape of product. Capture screen, card-detail screen, contact list. The differentiation is on scan accuracy and brand recognition. None of the leaders has rebuilt around the follow-up because rebuilding around the follow-up would mean breaking the existing user's mental model: where their contacts live, what the app's home screen is, how they think about their data.

The new entrant has the structural advantage of not carrying that legacy. Met starts at the follow-up. The contact list is a side-effect of the follow-up workflow, not the destination. OCR is a pipeline step, not a feature pitched in the App Store description. The audience that has been writing the same review for fifteen years can finally find a product organized around the half of the job they were trying to do.

What to test if your current scanner is the wrong half of the product

If this analysis lands and you want to test it against the scanner on your phone today, three concrete tests.

Open your scanner now and try to send a follow-up to someone you scanned at a conference last month. Count the screens between opening the app and having a draft of the message. If the count is more than two, the app isn't built for the job you're trying to do.

Look at your scanner's home screen. Is it a contact list, a capture view, or a follow-up queue? The home screen is the app's bet on what you'll do most often. If it's a contact list, the app is betting you'll search through your past meetings, not act on them.

Open the last five contacts you scanned and check whether each one led to a follow-up. If three or more didn't, the app is functioning as a capture tool only. The job-to-be-done isn't being done. The OCR worked; the product didn't.

Met is the scanner organized around the second half of the job. Capture is automatic; the draft is the destination; the contact list is incidental. We charge for the parts that turn 72-hour windows into actual relationships, and we charge once a month or once a year, with a free tier that includes 25 captures and 10 follow-up drafts so the value is visible before you pay. If your current app is shipping a 2010 product in a 2026 wrapper, the scan is fine. The product is the part it doesn't ship.

Get Met for iPhone — the scanner organized around the follow-up.

Read by founders working investor events, sales reps at field events, and anyone who's met 50+ people at a conference and still has the cards on the desk a month later.

Get Met in your inbox

Field notes on conference networking, follow-up timing, and what we ship next. No spam, no AI hype.

No spam. Unsubscribe anytime. Replies go to support@sailquery.com.