The Conversational CRM: How to Replace Your Sales Stack With a Spreadsheet and a Bot

Dan
The Conversational CRM: How to Replace Your Sales Stack With a Spreadsheet and a Bot

The Conversational CRM: How to Replace Your Sales Stack With a Spreadsheet and a Bot

The average CRM gets used for about three weeks before becoming a graveyard of half-entered contacts and overdue follow-up reminders nobody reads anymore.

This isn't a discipline problem. It's an interface problem. Salespeople and founders don't avoid CRMs because they don't want to be organized. They avoid them because the act of logging a call, updating a status, and drafting a follow-up in a separate tool is tedious enough that it doesn't happen consistently. The friction compounds until the system is more trouble than it's worth.

There's a better architecture. It requires a Google Sheet, Gmail access, a calendar connection, and a personal agent that ties them together. The interface is a text message. You talk to it like a colleague. It does the logging.

Why Traditional CRMs Fail

Salesforce, HubSpot, and their competitors are powerful tools with one fundamental design flaw: they require you to come to them. You finish a call and have to open another application, find the contact, update the stage, log the notes, set a reminder, and draft the follow-up. That's five steps that happen after the thing you actually care about already ended.

The result is predictable. It doesn't get done. Or it gets done inconsistently. Or it gets done days later, when you've forgotten the details that made the conversation meaningful.

A conversational CRM eliminates most of those steps by moving the interface to where you already are. If you're on Telegram, you update your CRM in Telegram. Your agent handles the rest.

The Architecture

The Data Layer: One Google Sheet

Your CRM lives in a single Google Sheet. No platform fees. No licenses. No onboarding. One file your agent can read and write, accessible from any device.

The structure is simple: Name, Company, Last Contact Date, Status, Notes, Next Action. You can add columns over time, but starting simple means you'll actually use it.

Your agent has read and write access to this sheet. It reads it when you ask questions. It writes to it when you have new information to log. Nothing goes in the sheet that you haven't told the agent, and nothing stays out of the sheet because updating it was too much friction.

The Communication Layer: Gmail, WhatsApp, Telegram

Your agent reads your Gmail. It knows when you last emailed someone, what the thread said, what was promised. When you ask "who do I need to follow up with?" it cross-references the CRM sheet against your email history and gives you an accurate answer, not just what the sheet says, but what it knows from your inbox.

Your agent can also write to Gmail. At the most conservative setting, it drafts emails you review before sending. At the most confident setting, it sends directly. Most people start with drafts and graduate to send access once they trust the output quality.

WhatsApp integration takes this further. Your agent can open WhatsApp as you and send messages to contacts. You tell it what to say, or give it enough context to draft the message, and it handles the mechanics.

Telegram is your command interface. All your questions, instructions, and updates flow through a dedicated Telegram group for your work. It's where the CRM becomes conversational.

The Context Layer: Calendar

Your agent reads your calendar passively. It knows when you had a meeting with someone, which gives it context your CRM sheet might not have. Someone you met with last Tuesday and haven't followed up on will surface in the follow-up list even if you forgot to log the call.

Calendar access is read-only. The agent never creates or modifies calendar events unless you explicitly ask it to.

What It Looks Like in Practice

Morning check-in:

You open Telegram and type: "Who do I need to follow up with today?"

Your agent checks the Google Sheet, reviews your Gmail for recent correspondence, cross-references your calendar for recent meetings, and returns a prioritized list of contacts with context: when you last spoke, what was discussed, what you said you'd do.

Instant follow-up drafting:

You see the list and type: "Use the templates and write Gmail drafts for the top three."

Your agent generates personalized drafts based on your saved templates and the specific context for each contact. You open Gmail, review three drafts, make minor adjustments, and send. Total time: four minutes.

WhatsApp outreach:

For contacts where WhatsApp is the right channel, you type: "Send [contact name] a message on WhatsApp checking in on the proposal we sent."

Your agent opens WhatsApp, finds the contact, and sends a natural-sounding message you would have written yourself. You don't touch the phone.

Logging a new contact:

You just mention them in conversation. "I met Sarah at Marker from the Acme deal today, she's the decision-maker on their real estate budget, follow up in a week." Your agent logs a new row in the sheet with everything you said, sets the appropriate next action date, and confirms.

You never opened the CRM.

Setting It Up

Step 1: Create the Google Sheet. Keep it simple to start. Six columns is enough. Share it with the service account your agent uses.

Step 2: Connect Gmail. Start with read access only. Once you're comfortable with the agent's output quality, add draft access. Only add send access when you trust it enough to skip review on routine messages.

Step 3: Connect Calendar. Read-only. Takes about five minutes to configure and immediately improves follow-up accuracy.

Step 4: Connect WhatsApp (optional). This requires OpenClaw's managed browser. Log into WhatsApp Web in the agent's browser profile. The agent can then use that session to send messages on your behalf.

Step 5: Build your templates. Save three to five follow-up email templates in a file your agent can reference. These don't need to be perfect; they're guides. Your agent personalizes them per contact. The value is in giving it a starting structure, not a copy-paste script.

Step 6: Create a dedicated Telegram group for work. Set a system prompt: "This is my sales and client management channel. You have access to my CRM sheet, Gmail, and calendar. Help me stay on top of follow-ups and never let a lead go cold."

The Difference That Actually Matters

The best CRM is the one you actually use. If logging a contact requires opening a dedicated application and filling in six fields, you'll log 60% of contacts on a good week. If logging a contact means saying something into Telegram while you walk back from a coffee meeting, you'll log 100% of them.

The conversational interface changes the compliance rate. High compliance is what makes a CRM valuable. A perfect system used inconsistently is worse than a simple system used every day.

What This Unlocks Over Time

After 90 days of consistent use, your conversational CRM becomes something more powerful than any traditional tool could offer: a system that genuinely knows your relationships. It knows which clients have been warm and gone quiet. It knows how long your sales cycles typically run. It knows which contacts you've been meaning to re-engage. And when you ask "where are we with the Acme deal?" it can give you a real answer from actual data, not whatever you last remembered to update.

That's the unlock. Not just automation; genuine intelligence about your pipeline, available in a text message, any time.

Based on a conversation with Moritz Kram on the Startup Ideas podcast.

Related Articles