Blog / CRM

Google Sheets as your free CRM: the automations that make it real

Somewhere in your Google Drive is a sheet called Leads 2026 FINAL (2). It was updated enthusiastically for nine days. We're not here to mock it — we're here to fix the actual problem: a sheet updated by hand is a diary, not a CRM. The moment rows write themselves and follow-ups fire themselves, the same free sheet becomes a genuinely capable CRM for a few thousand contacts.

The column structure that works

ColumnExampleWhy
Timestamp12-Aug 11:42Auto-filled; response-time truth
Name / BusinessRahul, Gupta SweetsPersonalised messages need it
Phone (10-digit)98xxxxxx21WhatsApp key — keep format clean
SourceIndiaMART / Website / Meta adTells you which channel earns
EnquirySS pipes, 50 unitsContext for follow-up
StatusNEW → CONTACTED → QUOTED → WON/LOSTOne word, one owner
Next follow-up14-AugWhat tomorrow's automation reads

Seven columns. Resist adding twenty — every extra column is a reason nobody fills it.

Automation 1 — rows write themselves

Every lead source lands in the sheet without a human: website form → webhook → new row; IndiaMART push → new row; Meta lead ad → new row. Each arrival also fires the instant WhatsApp greeting and pings your salesperson. From day one, your response time and source data are real, because no one "forgot to enter" anything.

Automation 2 — follow-ups fire from rows

Each morning, the automation reads the sheet: every row where Next follow-up = today and Status ≠ WON/LOST gets its follow-up — a WhatsApp nudge referencing the original enquiry (templates 3 and 4 here), and the row's date advances. Silent leads stop slipping through because "sheet dekhna bhool gaya".

Automation 3 — campaigns from a filter

Diwali offer to every LOST lead from the last 90 days? That's a read-rows → for-each loop → template send, straight off the sheet. Two cautions that separate professionals from spammers: opt-outs must be honoured automatically (a STOP reply blocks future sends), and message pacing matters — a burst of hundreds of identical marketing messages is how numbers get flagged. Volume campaigns really belong on the official API with proper broadcast tooling.

Dedupe rule: before adding a row, check whether the phone number already exists — update that row instead. Duplicate rows are how one customer gets three "namaste" messages and loses faith in you.

When to graduate off Sheets

  • Three people editing at once and overwriting each other,
  • You need a per-contact timeline (every message, order, note in one place),
  • Segments, opt-out enforcement and dedupe need to be guaranteed, not hoped for.

That's the point where the sheet stays as a report and the system of record moves to contacts with segments, notes and timelines — which Yantra includes built-in, alongside the same Google Sheets connector for everything above. Same flows, sturdier foundation.

Make your sheet work the night shift

"Naya lead aaye toh WhatsApp bhejo aur sheet me daalo" — describe it, it runs. Start free, 1,000 runs.

Start free

Questions we get asked

Can Sheets really work as a CRM?

Up to a few thousand contacts, yes — if rows and follow-ups are automated. Hand-updated sheets die in nine days.

How do I send WhatsApp from a sheet?

An automation reads matching rows, loops through them, and sends approved templates per contact — opt-outs enforced automatically.

When do I need a real CRM?

Concurrent editors, per-contact timelines, or guaranteed opt-out/dedupe — then Sheets becomes the report, not the record.