A CRM for Google Sheets

Most small businesses already run their pipeline in a spreadsheet. The rows are there, the columns mean something to the people who made them, and the problem is not the data — it is that a spreadsheet does not chase anyone. Gsheet CRM connects to that one file and gives it the parts a CRM is supposed to have:

• A board. Your status column becomes stages — New, Contacted, Won, or whatever you call them — and each row becomes a card you drag between them. A drag writes the new status straight into the cell.
• Follow-ups. Put a reminder on any customer and see them grouped as overdue, today, tomorrow, this week and later. Due reminders can also be emailed to the person they are assigned to, during working hours in your workspace’s own timezone.
• Reports. Funnel by stage, what is stuck, wins by month, who is handling what — computed from the sheet every time you open them, with nothing stored on our side. The app can also write a Dashboard tab into the workbook itself, built from native Sheets formulas that recalculate without the app.
• Roles. People join as Owner, Manager or Team member. A team member sees only the leads assigned to them (or their team’s, if they lead one); managers always see everything. You can open it up so everyone sees all rows, or narrow it to own rows only — enforced on the server when the sheet is read, not just hidden in the interface.
• Linked tables. Keep properties, courses or packages in their own tab and point a lead at one; keep viewings or payments in a child tab and have their count or total roll up onto the customer’s card.
• Small automations. When a lead is created or reaches a stage, set a follow-up, add a note, set a field, or hand the lead to whoever has the fewest open leads.

Open the spreadsheet any time — it is the same data, because it is the data. If you are weighing this against a database-style tool, the Airtable comparison says plainly where each approach is stronger.

The rule is written down in our data policy and enforced in code: we keep the schema, never the volume. Our database holds which spreadsheet is connected, what each column means, who on your team maps to which owner name, when follow-ups are due (their time and row — not their text), and a log of what the app did and who asked. That is configuration, and it is small.

Your leads, notes and numbers are read from the sheet when a screen needs them and held only in a short-lived, encrypted cache that expires on its own within ten minutes and is cleared whenever the workspace is written to. Even the audit trail’s before-and-after values go into a Changes tab inside your own workbook, so the record of what a field used to say lives beside the field.

Access is Google’s narrowest Drive permission, drive.file: the app can open the spreadsheet it created for you, or one you explicitly picked, and nothing else in your Drive. If you stop using the app, the sheet simply stays where it always was — a normal Google Sheet that works without us. The FAQ covers what happens to your data when a subscription ends.

The best reason to keep a CRM in a spreadsheet is that a spreadsheet can calculate. A Commission column of =Budget*0.02 is a CRM field nobody had to build, and the app treats it as one: a formula column shows in the app like any other field, and the app detects formula columns and refuses to write over them. A computed column is read-only from the app’s side rather than something an inline edit could replace with the number it happened to show.

You can also build one from inside the app by referring to columns by their header names — {Budget} * 0.02 — and the app writes it as an array formula that fills the whole column and keeps filling it for every new lead. Add a column straight in Sheets and it appears in the app on the next read; the app adds columns of its own but never renames or deletes yours.

It suits a team that already lives in a sheet and wants it to chase people: real estate agents, travel desks, clinics, admissions offices, recruiters, dealers, studios, traders. Ready-made setups exist for a dozen of those, each creating a working sheet in your own Drive with stages and dropdowns in place.

It is deliberately not a general-purpose database: linked tables are capped at a handful per workspace and there is no app builder on top. Plans differ in room — people, leads and linked tables — and the larger plan adds the developer side (a REST API and signed webhooks) and quotes generated from Google Docs. The live figures for your region are on the pricing section of the home page. Teams selling on WhatsApp should read about the Team Inbox integration, and anyone with renewal dates in a column should look at reminders that run inside the sheet.