Here's the trap. You do not want a CRM yet, a spreadsheet is already annoying you, and somebody suggests running the whole thing through an assistant instead. It works beautifully for three weeks. Then a colleague needs to see the pipeline.
An assistant with a connected database is a genuinely good system of record for one person. Claude at $17 a month on annual billing, or $20 monthly, plus a free Notion database, and you can ask your pipeline questions in English instead of writing formulas.
It fails at exactly the point a spreadsheet fails, for exactly the same reason, and knowing that in advance is what makes it a sensible choice rather than a trap.
What does the setup actually look like?
One database, connected to the assistant, with the four objects any CRM has: companies, people, deals and activities. In a single Notion database that flattens to one table with a status property, a value, a next step and a date.
- Capture by conversation. After a call, tell the assistant what happened and have it write the record. This is the part that beats a spreadsheet, because the friction of opening a sheet and typing into the right row is exactly the friction that produces incomplete records.
- Review by question. Ask which deals have not moved in two weeks, or which have a next step in the past. These are queries you would otherwise write as filters, and asking is faster than building.
- Weekly rollup as a standing prompt. One saved instruction that produces the same summary every Monday: what moved, what stalled, what needs a decision.
- Drafting in the same place. Since the context is already there, the follow-up email gets written against the actual history rather than against your memory of it, which is where the prompt library attaches.
What does it cost?
Seventeen dollars a month, if you pay annually and $200 up front, or twenty billed monthly. Notion's free tier covers the database. There is no third component, which is the point.
Against that, the cheapest real CRM in our directory is free: both HubSpot and Attio have genuine free tiers. So this is not a cost argument, and anyone selling it as one is being careless. It is a friction argument, and friction is a real reason to choose something.
Where does it break?
At the same four thresholds that end a spreadsheet, which we set out in when you actually need a CRM. Three of them arrive the same way here. One arrives harder.
- Concurrency, and this is the one that ends it. Two people cannot sensibly drive the same database through separate assistant conversations. Neither sees what the other just wrote, and the assistant will confidently answer from a state that changed thirty seconds ago. A shared spreadsheet at least shows you the conflict.
- Relational structure. One company with four contacts and two deals is awkward in a single flat database, exactly as it is in a sheet. Notion can model it properly with relations, and at that point you are administering a database rather than using a CRM.
- Nothing arrives automatically. No email sync, no calendar capture, no call logging. Every record exists because you told the assistant about it, which works precisely as well as your discipline does.
- Volume. Around twenty open deals, the same as any memory-assisted system, though this one holds up slightly better because the assistant is doing the remembering.
Notice that three of the four are shared with a spreadsheet and the assistant genuinely improves two of them. The one it makes worse is concurrency, because a spreadsheet at least surfaces a conflict and a conversation quietly answers from stale context.
So who should actually do this?
- Solo founders and single-rep operations. This is the intended case and it is genuinely good. You get conversational capture, conversational review, and no software to administer.
- Anyone already running the manual outbound stack. If you built the $17 a month motion, this is the same database doing a second job and costs nothing additional.
- Not a team of two. The moment a second person touches customer records, move to a free CRM tier. The migration from a Notion database is a CSV export and an afternoon, and it gets harder the longer you leave it.
- Not anyone who needs the history to outlive the tooling. The database is yours and portable, which is the good news. But make sure the record lives in Notion rather than in a chat transcript, because a system of record is the thing that survives cancelling everything else.
The answer to the question in the title is yes, for one person, properly, and the thing that ends it is not sophistication or scale but the second human being. That is a much earlier limit than the people recommending this setup usually mention, and it is the only one that matters.