Every CRM starts at 'lead.' You started at a person.

The Sunday-night pile

Sunday night. The lanyard's still coiled on the kitchen counter, and next to it sit forty-something business cards fanned out like a losing poker hand. You remember maybe six faces cleanly. There's the guy who runs procurement at the company you've been trying to reach for a year, and you cannot for the life of you remember whether his name was Dan or Dave. There's a card with 'follow up re: Q3 pilot' scrawled on the back in your own handwriting, and no memory attached to it at all.

Someone told you the fix is a CRM. So you open a free trial, and the very first thing it asks you to do is assign each of these strangers a deal stage. Prospecting. Qualification. Proposal. You close the tab. The pile stays a pile. By Wednesday it's anonymous.

The pipeline tax

Here's what nobody tells you when they say 'just get a CRM.' A CRM is not a memory tool. It's a pipeline tool that happens to store names. Its entire shape assumes you already know these people are opportunities, that each one belongs somewhere in a sales process, and that you or someone on your team will keep dragging them from stage to stage until money changes hands.

The person on that card is none of those things yet. They're a hallway conversation you might want to reference in three months. You don't have a pipeline problem. You have a recall problem, and you're being sold a forecasting machine to solve it. That's the pipeline tax: paying, in setup time and monthly seats and abandoned trials, for a system built around a stage you haven't reached.

A CRM manages a pipeline you don't have yet. The problem in front of you is a person you'll forget by Thursday.

Why 'just use a CRM' is bad advice for most people

The advice isn't wrong for a sales team with a defined motion and a manager who lives in the dashboard. It's wrong for almost everyone else who meets people for a living. Recruiters. Consultants. Financial advisors. Founders working a conference floor. ICs who network reluctantly and hate every minute of it.

For them, the CRM's cost isn't the sticker price. It's the maintenance. A CRM only works if it's fed, and a system that demands a stage update from you every week is a system you'll abandon by the second month. The graveyard is full of CRMs with nine contacts in them, all stuck in 'new,' last touched the day they were imported. And the worst part is what that failure does to your head: once the tool is stale, you stop trusting it, and you're back to the pile on the counter, except now you're also paying for a subscription to feel guilty about.

What the category actually optimizes for

Look at how the major sales CRMs open and the pattern is hard to miss. Salesforce, HubSpot, and Pipedrive all build around a deal or opportunity object, with the pipeline as the home screen and the contact as an attribute hanging off it. The person is a field on the deal, not the other way around. That's not an accident or a UX oversight. It's the product working exactly as designed, because the buyer they're built for is a revenue team, and per-seat pricing that starts at roughly Pipedrive Essential plan costs $14 per seat per month (billed annually) or $24 per seat per month with monthly billing. ([source](https://www.method.me/blog/how-much-does-pipedrive-cost/)) per seat per month only pencils out when there's a quota behind it.

Survey after survey on CRM adoption tells the same story: a large share of seats go effectively unused, and the most common reason cited is that reps find the data entry more expensive than the payoff (55% of CRM implementations fail to meet objectives, mostly due to data entry friction and poor user adoption. ([source](https://wavecnct.com/blogs/crm-statistics))). Read that back. The tool fails at the exact moment it's asked to be a memory system for people who aren't yet deals.

The pattern in practice

Take a recruiter at a two-day career fair. Thirty candidates, back to back, six minutes each. One of them mentioned she's relocating to Austin in the fall and won't be looking until then. Another has the exact backend stack an open role needs but is happy where he is for now, so it's a spring conversation, not a this-week one.

Drop all thirty into a CRM and here's what happens. You spend Sunday night creating thirty records, guessing at a stage for each, and by the time you're on candidate eleven you've stopped writing down the thing that actually mattered: Austin, fall, backend, spring. The context is what makes the follow-up land in March. The stage is what the tool wanted. You gave it the stage and lost the context, and in three months you'll send a generic 'just checking in' that gets ignored, because the detail that would've made it land is gone.

Capture the person instead. Name, face, where you met, the one thing they said. That's the whole job at this stage. Everything a CRM adds on top is weight you'll carry and never use.

What changes if you stop trying to run a pipeline

The reframe is small and it changes everything downstream. Stop asking 'where does this person sit in my funnel' and start asking 'will I remember why this person mattered.' Once that's the question, the toolbox you need shrinks dramatically. No stages. No pipeline hygiene. No seat you're guilting yourself into justifying.

You need three things, and only three: to capture context fast enough that you actually do it in the moment, to keep that context attached to the right face, and to be able to pull it back up when the follow-up window opens. A pipeline is something you graduate into if and when a relationship becomes a deal with real stages worth tracking. Most of the people you meet never get there, and that's fine. They still deserve a follow-up that proves you were listening.

Capture, not pipeline

This is the ground Met was built on. Not as a lighter CRM, but as a different category: a tool for the pre-CRM person whose next opportunity depends on remembering a six-minute conversation, not on managing a forecast. Event Mode keeps the room captured while you keep talking, so the context goes in at the moment it's fresh instead of on Sunday night when it's already fog. The person is the unit, not the deal. There's no stage to update and nothing to let go stale.

And because the whole thing lives in iCloud rather than on someone's server, the network you're building stays yours. No ads reading your contacts. No data sold out the back. For a recruiter, a consultant, or a founder who's been pitched a thousand times and smells overhead from across the room, that's the point: the tool disappears into the moment instead of demanding you feed it. If a relationship ever does become a real pipeline, graduate it to a CRM then. Until it does, you were never the customer that software was built for.

What we're watching

The open question is whether the CRM category ever ships a real 'capture-first' mode, or whether the pipeline object is too load-bearing to their business to let go of. Our bet is the latter: a forecasting tool can't become a memory tool without abandoning the customer it prices for. The person stuck at the Sunday-night pile isn't a smaller version of a sales team. They're a different job entirely, and the tools that serve them will be built from the person up, not the pipeline down.