Why most CRMs waste your money
Here's the pattern I see constantly. A small business owner signs up for a big-name CRM — HubSpot, Pipedrive, Salesforce, whatever was top of the Google results. They spend a weekend setting it up. They use about 5% of it. Then they keep paying $30–$150 a month for the privilege of feeling guilty about the other 95%.
The thing is, a CRM only has one actual job. Strip away the dashboards, the automation builders, the "lead scoring" and the eighteen pipeline views you'll never open, and what's left is four questions:
Who?
The person or business. A name and a way to reach them.
What stage?
Where they sit in your pipeline — lead, in conversation, proposal sent, won, lost.
Last contact?
When you last spoke. This is how you spot people going cold.
Next action?
The one thing you need to do next, so nobody slips through.
That's it. That's the whole job. And you do not need a $99/month platform to answer four questions — you need a place to keep the answers, and something smart enough to read them back to you when you ask. A spreadsheet handles the first part. Claude handles the second.
The shift
You're not buying CRM software. You're building a CRM out of two tools you already have — a Google Sheet and Claude — and the "interface" becomes you just talking to it. No new login. No new monthly bill. No learning a new app.
The honest setup (read this first)
If you saw the video that sent you here, you watched Claude build a client tracker right inside the chat as an artifact — that little live panel on the side. It looks like magic. And it is, for a demo. But there's one thing the video can't show you in 30 seconds, so let's be straight about it now.
An artifact doesn't save itself
A Claude artifact lives inside that one conversation. Close the chat, start a new one tomorrow, and your tracker is gone. Brilliant for showing an idea — useless as the place your real client list lives. So we don't use it as the database.
The version that actually survives — that you can still open in six months, that doesn't vanish — needs a real file you own. Here's the setup, and which tool does which job:
The Google Sheet
This is your database. It's the thing that's real, permanent, and yours. It holds every client and every row. It sits in your Google Drive forever, free.
- You already have it
- Costs nothing
- Opens on any device
- Survives every closed chat
Claude
This is your interface — the talk-to-it layer. You don't open the Sheet and squint at rows. You ask Claude, and it reads the Sheet and answers.
- "Who's gone cold?"
- "What's in my proposal stage?"
- "Draft a follow-up for Sarah"
- No menus, no filters — just asking
One honest limitation up front, so nothing surprises you in section 4: Claude's built-in Google Drive connector can read your Sheet brilliantly — but it can't write to it. When you add a new lead, Claude hands you a perfectly formatted row and you paste it in. One click. That's the only manual step in the whole system, and section 7 shows you how to remove even that if you want to.
What you'll need
A free Google account (for the Sheet). A Claude account — the free plan works for reading your Sheet; this all gets smoother on a paid plan. About 15 minutes. That's the entire shopping list.
Step 1 — Let Claude build your CRM Sheet
You're not going to design a spreadsheet from scratch. You're going to ask Claude to design it for you, then paste the result into a blank Sheet. Open claude.ai in one tab and a blank Google Sheet in another, and follow these three moves.
Ask Claude to build the structure
Paste the prompt below into Claude. It will give you a clean table with the right columns and a couple of example rows so you can see how it works.
Copy the table into your Sheet
Click into cell A1 of a blank Google Sheet and paste. The columns line up automatically. Delete the example rows once you understand the layout.
Name it and you're done
Rename the Sheet something obvious like "Client CRM" so it's easy to find later. That's your database built.
Here's why those six columns and not more. Every column you add is a column you have to keep filling in — and a half-filled CRM is a CRM you stop trusting. These six answer the four questions from section 1, plus a Notes column for the human stuff ("met at the Perth event", "prefers email over calls"). Resist the urge to add ten more. You can always ask Claude to add a column later if you genuinely miss one.
About the Stage column
Lead → Discovery → Proposal → Won (or Lost). That's a complete sales pipeline for most service businesses. A "Lead" is someone who's appeared. "Discovery" means you've had a real conversation. "Proposal" means a number is in front of them. If your business genuinely needs a different stage, tell Claude when you build it — but start simple.
Step 2 — Connect the Sheet to Claude
Right now Claude built your Sheet but doesn't know it exists once you've closed that chat. Connecting Google Drive fixes that — from then on, Claude can pull up your live CRM any time you ask, without you copying anything in.
To connect Google Drive in claude.ai:
Connect Google Drive (one-time, ~2 minutes)
Two quick ways to do this, and the second is the one I'd actually recommend for a CRM:
Attach it per chat
Use the + → Add from Google Drive each time you want to work on your CRM. Fine, but you re-attach it every conversation.
Use a Project (better)
Create a Claude Project called "CRM". Add the Sheet once under the Project's Files section. Now every chat inside that Project already knows your pipeline — no re-attaching.
The honest limitation — it reads, it doesn't write
Claude's Google Drive connector is read-only. It can pull your Sheet in and answer anything about it — but it cannot add a row, edit a cell, or change a stage on its own. When you add a lead, Claude gives you the row to paste. When you mark a deal "Won", you do that in the Sheet yourself. It's one click. Section 7 shows the advanced route if you want true hands-off writing.
Step 3 — Run it day to day
This is where it stops being a spreadsheet and starts feeling like a CRM. Once the Sheet is connected, you never open it to "check" things — you ask. Here are the three jobs you'll do most, and exactly how each one goes.
Adding a new lead
You say: "Add a new lead — Sarah Chen, Bloom Studio, discovery call booked for Friday."
Claude does: reads your Sheet so it matches your format, then hands you a ready-to-paste row — Name: Sarah Chen, Company: Bloom Studio, Stage: Discovery, Last Contact: today's date, Next Action: "Discovery call Friday". You click into the next empty row of your Sheet and paste. Done in five seconds.
Finding who's gone cold
You say: "Look at my CRM — who haven't I followed up with in the last two weeks?"
Claude does: reads the Last Contact column, compares it to today, and gives you a list — "Three people: Sarah (16 days), Mike (21 days), the Henderson account (19 days)." That single question is the entire reason CRMs exist. You just did it without opening one.
Drafting follow-ups
You say: "Draft a warm follow-up email for everyone sitting in Proposal stage."
Claude does: finds every Proposal-stage row, reads the Notes column for context, and writes you a tailored email for each one. You read them, tweak, send. The CRM didn't just track the follow-up — it wrote it.
Notice the rhythm: you talk, Claude reads, Claude answers. The only time your hands touch the spreadsheet is to paste a new row or update a stage — and that's a deliberate, two-second action, not "data entry". The full set of prompts is in section 8 so you can copy them straight in.
Keep it honest
The system is only as good as the Sheet. After every real conversation, update that person's Last Contact date and Next Action. Make it the last thing you do after a call — it takes ten seconds and it's what makes "who's gone cold?" actually trustworthy.
Set it up in Claude Cowork
If you use Claude Cowork — the version of Claude that works like a teammate on your actual computer, handling longer tasks across your files and apps — your CRM gets even better. Cowork can hold the tracker as a real file on your machine and check in on it on a schedule, not just when you remember to ask.
Give Cowork a home for the CRM
Make a folder on your computer — something like "Client CRM" in your Documents. Ask Cowork to build the tracker as a spreadsheet file (a .csv or .xlsx) and save it right there. Now it's a real file Cowork can open, read, and update directly.
Set it up as a Project
Point Cowork at that folder as its working project. Every time you talk to it, it already knows where the CRM lives — no attaching, no copying.
Give it a standing job
This is the Cowork advantage. Ask it: "Every Monday morning, open the CRM file and tell me who I haven't contacted in two weeks, and draft follow-ups for them." Cowork can run that on a schedule and have your week's chase-list waiting for you.
Why Cowork beats the chat for this
In a normal chat, Claude only acts when you message it. In Cowork, the CRM becomes a living file your AI teammate looks after between conversations.
Reads and writes the local file
A CRM file kept in a folder on your computer — Cowork can update rows itself, not just read them.
Runs on a schedule
"Every Monday, give me my cold-lead list." It's waiting for you before you've had coffee.
One Cowork quirk to know
Cowork works most reliably with files kept inside its own project folder on your computer. If you'd rather the CRM live in Google Drive, the Google Drive connector still applies — and it's still read-only there. The simplest, most reliable Cowork setup is a CRM file in a local folder, which Cowork can both read and update on its own. Keep the file there and you get the full hands-off experience.
For the brave — make Claude write back to the Sheet
Everything so far works for everyone, today, with zero technical setup. This section is the optional upgrade — and I want to be clear it's genuinely optional. If "paste one row" doesn't bother you, skip it. The system already works. But if you want true two-way — Claude adds the lead to the Sheet itself, no pasting — here's the honest path.
What unlocks it: an MCP connector
The built-in Google Drive connector is read-only by design. To let Claude actually write to a Sheet, you connect a Google Sheets MCP — a small "connector" that gives Claude permission to add rows, update cells, and change stages directly. Once it's connected, "add Sarah as a lead" updates the Sheet with no paste step at all.
Here's the honest trade-off, because this is where it stops being a 15-minute job:
Setting up an MCP is the kind of thing that's a 20-minute job once someone walks you through it, and a frustrating afternoon if you're guessing. It's not hard — it's just unfamiliar. So my honest advice: start with the read-only setup in sections 3–6. Live with it for a week. If the one-click paste genuinely annoys you, then it's worth doing the MCP upgrade — and that's exactly the kind of thing we walk through together inside the membership.
The takeaway
Read-only + paste = works for everyone, set up in 15 minutes. Full write access via MCP = the polished end-state, but it needs a guided setup. Neither is "the right answer" — pick the one that matches how technical you want to get. Most people are genuinely happy with read-only.
Steal these prompts
Here's the whole system as copy-paste prompts. Bookmark this section. Once your Sheet is connected (or your CRM file is in a Cowork project), these are all you need to run a CRM by talking to it.
That's the whole system
A Sheet you own, Claude on top, six prompts. No software, no monthly fee, no 95% you never touch. Run it for a fortnight before you decide you need anything fancier — most people find they don't.
Ready to go deeper?
This is one small system. Here's where you learn to build the rest.
Wright Mode Membership
Where we set up the connectors, the MCPs and the automations together — so the "for the brave" stuff stops being scary. A community of women entrepreneurs building real AI systems.
Claude Masterclass
Learn to use Claude like a pro — from prompting fundamentals to building real workflows that save hours every week. The foundation under everything in this guide.
Claude Code Masterclass
Go beyond the chat. Build automations, connect tools, and wire up the write-access setup properly — no developer experience needed.