Every CRM starts at lead. None of them start at card. The gap is structural.

By Tuesday morning, you have a stack of cards and a question

You came back from the conference Sunday night with sixty-three cards. You got home, ate something, slept poorly. Monday you triaged email and didn't touch the cards. Tuesday morning the stack is on the corner of your desk and you have a question that nobody who designed the modern CRM thought through.

The question is: where do these people live now?

It's the wrong question to bring to Salesforce. The Salesforce object model starts at Lead. A Lead has a stage, an owner, an estimated close date, an account, a deal, a probability. None of the sixty-three people on your desk has any of those things, and most of them never will. Forcing them into Lead means lying to the system and making the pipeline view useless.

It's the wrong question to bring to HubSpot, Pipedrive, Close, Attio, or Folk. Same shape. The whole category assumes that the contact's life with you begins at the moment they're qualified. The moment that actually defines whether you'll ever qualify them, the 48-hour window after a thirty-second handshake, is the moment the category was never built to model.

So the cards stay on the desk. By Friday they're filed in a drawer. By next Tuesday you can't remember three of them.

The pre-CRM moment, named

The pre-CRM moment is the 48 hours between meeting someone and deciding they belong in your pipeline. It has three properties that distinguish it from anything a CRM is built for.

First, the contact has no pipeline stage and may never get one. Maybe they become a lead in three months. Maybe they become a partner referral in a year. Maybe they become nothing at all, just somebody you remember the next time their name comes up at a different conference. None of those outcomes is failure. The CRM treats anyone without a stage as either a Lead-with-stage-Unqualified, which lies, or as a contact-with-no-deal, which the pipeline view filters out.

Second, the relevant data isn't a record of the company; it's a record of the conversation. Three sentences. What they said about their team, what surprised you, what they wanted to talk more about. That data isn't on their LinkedIn and isn't on their company's website. It exists for thirty seconds in your head, and the warm-window effect means it expires inside 72 hours unless you write it down.

Third, the action you take is determined by the conversation, not the company. A founder you met whose team is hiring a head of GTM in November doesn't need a CRM record yet. They need a follow-up message in 36 hours that references the hiring conversation and offers to introduce two people you know. The CRM has no place to put that intent. It expects pipeline math; you have a sentence.

Name the moment and the structural gap becomes obvious. Every CRM operates on a model that assumes the captured contact has been pre-qualified. The pre-CRM moment is everything that happens before that assumption is true.

Why every CRM has the same blind spot

The blind spot is structural, not a feature gap. Walk the major CRMs and you find the same architectural decision in each.

Salesforce was built in 1999 around the deal as the unit of analysis. Account, Contact, Opportunity. The Lead object was added to handle the qualified-prospect stage. Anything that isn't a deal-shaped engagement gets filed under Contact, which is just a directory, no temporal context.

HubSpot was built around the marketing funnel. Visitor becomes Lead becomes MQL becomes SQL becomes Opportunity. Beautiful pipeline if your contact arrives via webform. Useless if your contact arrives via handshake at a booth.

Pipedrive was built around the deal pipeline view. Even cleaner than Salesforce; the deal IS the central object. Adding a contact without a deal feels like an error to the system.

The newer entrants (Attio, Folk, Clay) are flexible enough that you can model whatever you want, but they don't ship with a default model for the pre-CRM moment either. You can build it yourself, which is what serious operators do, which is itself the proof that the category default is wrong.

This isn't because the founders of these CRMs are unimaginative. It's because the original buyer was a sales VP who needed pipeline visibility, and pipeline visibility means counting things that have stages. The pre-CRM moment is structurally invisible to that buyer. It's invisible to the product roadmap that buyer's purchase paid for. So twenty-five years later, the modern CRM still treats the contact's life as starting at the moment they became a deal.

What the moment actually needs

The pre-CRM moment has three jobs the CRM can't do for it. Naming them is the spec for what's missing.

It needs to capture the conversation, not the company. The minimum viable record is three things: a photo of the card or a name, one sentence of context (what they said that mattered), and one open question (what you'd ask if you ran into them next week). That's it. No required fields about industry, company size, deal value. Those come later if and when the contact graduates into a real pipeline conversation.

It needs to surface the contact in the warm window without staging them. A reminder at 36 hours that says "draft a follow-up to the founder you met about FY27 procurement timing" is doing the work. A reminder at 36 hours that says "this lead has been Unqualified for 1 day, move to next stage" is making you fight the tool to send a normal message. The temporal nudge has to live outside the pipeline view.

It needs to graduate the contact to the CRM cleanly when they earn it. Most pre-CRM contacts never become deals; that's fine, they sit as remembered relationships. The ones who do become deals should hand off into your existing CRM with the conversation intact, not with a fresh blank Lead record. Continuity matters because the conversation IS the relationship; losing it at handoff means starting cold from a position you'd already paid the social cost to leave.

Three jobs. None of them belong in pipeline software. All of them need a place to live, and the place that's currently doing the work is your desk drawer.

The shape of the tool that fits the moment

If the pre-CRM moment needs the conversation captured at meeting-time, surfaced in the warm window, and graduated cleanly to the CRM only if the contact earns it, the shape of tool that fits is small.

It's a journal, not a database. A journal accepts the conversation as the unit. The card on your desk yields a name plus three sentences plus an open question, and that's a complete record. The CRM expects fifteen fields and starts crying if you skip the company size; the journal accepts what you actually have.

It's local-first by default. The conversation is small enough to fit on your phone, sensitive enough that it shouldn't be stored on a vendor's servers, and durable enough that it should survive the next CRM migration your sales org undertakes. The local-first architecture also means the cost structure isn't a per-seat SaaS license, which means the journal can charge once and never again.

It's adjacent, not replacement. The journal lives next to your CRM and feeds into it for the contacts who graduate. Salesforce is still where deals live; the journal is where the people who haven't decided to be deals yet live. Different jobs, different objects, different failure modes if you try to merge them.

The gap between paper card on the desk and Lead record in Salesforce is forty-eight hours and one specific sentence. The tool that fits the gap is small enough to live in your phone, fast enough to capture in thirty seconds, and disciplined enough not to pretend to be a CRM.

What we built, and why we wouldn't try to be a CRM

Met is the journal that lives in the pre-CRM moment. Capture is one tap on a card or a name. The follow-up draft writes from the conversation you typed in for thirty seconds at the booth, not from a template. The reminder fires at the warm-window edge, around the 48-hour mark, when the message you'd write reads as alert and present rather than slightly behind.

What Met is deliberately not: it isn't a CRM. There's no pipeline view, no deal stage, no probability slider, no quota dashboard. We don't compete with Salesforce or HubSpot or Pipedrive on their turf. We live one step earlier in the relationship, before any of those tools have anything to model. When a Met contact graduates into a real deal conversation, the export hands off cleanly to whatever CRM your team uses. The journal stays as the record of the original conversation; the CRM picks up the deal that conversation eventually became.

The pricing follows the architecture. iCloud-only storage means no server cost on our side, which means no recurring fee on yours. Met is free for the first 25 contacts, then a modest paid tier for everything beyond. Same price for everyone, no auto-charging trial, no paywall on contacts you've already captured. The journal you build with Met belongs to you; we're providing the structure, not renting you access to your own past conversations.

None of that fixes the fact that CRMs don't model the pre-CRM moment. What it does is name the gap and offer a tool that fits it.

Three questions to ask the cards on your desk

If this analysis lands and you want to test it against your own stack, three concrete questions for the Tuesday-morning stack of cards.

1. Where would these contacts live in your current tooling? If the answer is "my CRM, as Leads with stage Unqualified, " you're paying the lying-to-the-system tax, the pipeline view is now noisier and the contacts get filtered out of normal workflows. If the answer is "a notes app, my desk drawer, my memory, " you're paying the warm-window tax, the conversation is expiring before it earns a follow-up.
2. What did you actually talk about with the third person on the stack? Not their company. The conversation. If you can't recall a specific sentence within ten seconds, the warm-window tax has already started compounding. The card alone won't recover it; the conversation needs to be written down within 48 hours of the handshake or it doesn't survive.
3. If three of these contacts become real deals six months from now, what artifact will you wish you had? Most operators answer the same way: a record of the original conversation, kept as a journal entry, retrievable with one search. That artifact doesn't exist in any CRM today, and the tool that creates it is one tap and a sentence at meeting-time, every time.

The pre-CRM moment is the part of the relationship that decides everything else. The category was built for what comes after. The journal that fits the moment is small, fast, and one phone away.