What columns should a customer success spreadsheet have?

Account name, ARR (or MRR), renewal date, owner, last touch date, a health rating, and a notes column. That covers the questions a CS spreadsheet exists to answer: who do we have, what are they worth, when do they decide again, who's on it, when did we last talk, and how do they feel. Add columns only when a real decision needs them.

How do I build a customer health score in a spreadsheet?

Keep it simple: a three-value rating (green, yellow, red) set by the owner, plus a one-line reason in the notes. Formula-based scores in a spreadsheet look rigorous but run on manually entered inputs, so they're only as current as the last update. A judgment call with a written reason is more honest and takes less upkeep.

When does a spreadsheet stop being enough for customer success?

The common tell is account volume: once each person carries roughly ten or more accounts, things start slipping between updates. A renewal sneaks up, a quiet account goes unnoticed for a month. The spreadsheet didn't get worse, the book outgrew what a manually updated file can watch.

Do I need a customer success platform to replace the spreadsheet?

Not necessarily an enterprise one. The traditional platforms are built for teams with an admin to configure and run them, which is exactly what a lean team doesn't have. What you actually need are the three things the spreadsheet can't do: stay current on its own, read the signals nobody types in, and raise its hand when an account needs attention.

Running customer success on spreadsheets (how far it gets you)

If your book of accounts lives in a spreadsheet, you’re in good company. Most CS teams start there, and starting there is the right call. This is an honest look at what the spreadsheet does well, where it breaks, and what comes after, without pretending you need an enterprise platform to run twenty accounts.

01The right tool

Why the spreadsheet is the right tool at the start

The spreadsheet gets a lot of unfair criticism from people selling its replacement. The truth: at the start, it’s the best tool available. It’s free. It’s flexible, when you learn something new matters, you add a column, no vendor call required. Everyone in the company can read it, including the founder and the sales lead, with zero training. And building it forces the useful exercise: deciding what you actually need to know about each account.

A team that runs a disciplined spreadsheet knows its book. That discipline, not the tool, is what customer success is made of, and it transfers to whatever you use next.

02The columns

What a good CS spreadsheet tracks

Seven columns cover the job. In rough order of how often you’ll sort by them:

Account, the company name.
ARR, what the account is worth. This is the sort that turns a list into priorities.
Renewal date, when they decide again.
Owner, whose problem this account is.
Last touch, the date of the last real conversation.
Health, green, yellow or red, set by the owner’s judgment.
Notes, the one line of context: why the rating, what’s next.

Resist the urge to add more. Every extra column is a promise to keep it filled in, and unfilled columns rot faster than missing ones. If a column doesn’t change a decision, it’s decoration.

03The limits

The three ways the spreadsheet breaks

It’s stale the day after you update it. The spreadsheet is a photograph of your book at the moment someone last edited it. Accounts keep moving; the file doesn’t. The health column says green because it was green two weeks ago, and every reader has to silently discount everything by how old they guess it is.

It only knows what someone typed in.The signals that predict churn live in email threads, support tickets, usage logs and billing events. None of them reach the spreadsheet unless a person notices, remembers, and types. The frustrated reply that landed at 6pm on a Friday, the login curve that’s been sliding for a month: the spreadsheet can’t see any of it, so “health” means “health as of the last time someone looked.”

It never taps you on the shoulder.A spreadsheet answers questions; it doesn’t ask them. It won’t tell you a renewal is 30 days out or that an account has gone quiet. Every risk it holds is only found when someone thinks to open the file and go looking, which means the accounts nobody is worried about, the quiet ones, are exactly the ones nobody checks.

04The awkward middle

More tabs, and the Monday morning ritual

Teams rarely notice the moment the spreadsheet stops being enough, because the failure is gradual and the fix is always one more tab. A renewals tab. A tab per CSM. A pivot for the exec summary. Conditional formatting that flags anything untouched for 30 days. Each patch is sensible; together they turn a simple file into a system only its author can safely edit.

Then comes the ritual: a standing block, usually a weekly morning, where someone walks their inbox, the support queue and the CRM to refresh the file by hand. That morning is the honest price of the free tool, hours of a CSM’s week spent being a human data pipe. And the ritual has a failure mode of its own: skip one week, the file goes stale, people stop trusting it, and once people stop trusting it they stop updating it. That spiral, not any feature gap, is how CS spreadsheets actually die.

05Graduating

What comes after, without the enterprise platform

The traditional answer is a CS platform, and for a lean team it’s usually the wrong one: weeks of setup, an admin to run it, and a price that assumes a department. You’d be trading a tool you outgrew for a tool you haven’t grown into.

Graduating isn’t about more software, it’s about retiring the manual work the spreadsheet forces. Keep what it got right: one list of accounts, ARR and renewal dates front and center, an owner and a health read per account. Replace the three broken parts: the data should refresh itself from the systems where it already lives, the health read should come from real signals instead of memory, and the risks should come find you instead of waiting to be found. Judge any next step, whatever it is, by whether it gives you those three without demanding an admin.

06Where Keply fits

Start by uploading the spreadsheet you already have

Keply starts where you are: upload that same spreadsheet, or connect your tools, and you’re live in a day. From there the agent takes over the reading and the reminding, it watches email, ticket, usage and billing signals, scores every account, flags the revenue at risk, and drafts and sends the save with your approval by default. The Monday morning ritual becomes its job. Flat $299/month. See how it works.

CS spreadsheets, FAQ

What columns should a customer success spreadsheet have?: Account name, ARR (or MRR), renewal date, owner, last touch date, a health rating, and a notes column. That covers the questions a CS spreadsheet exists to answer: who do we have, what are they worth, when do they decide again, who's on it, when did we last talk, and how do they feel. Add columns only when a real decision needs them.
How do I build a customer health score in a spreadsheet?: Keep it simple: a three-value rating (green, yellow, red) set by the owner, plus a one-line reason in the notes. Formula-based scores in a spreadsheet look rigorous but run on manually entered inputs, so they're only as current as the last update. A judgment call with a written reason is more honest and takes less upkeep.
When does a spreadsheet stop being enough for customer success?: The common tell is account volume: once each person carries roughly ten or more accounts, things start slipping between updates. A renewal sneaks up, a quiet account goes unnoticed for a month. The spreadsheet didn't get worse, the book outgrew what a manually updated file can watch.
Do I need a customer success platform to replace the spreadsheet?: Not necessarily an enterprise one. The traditional platforms are built for teams with an admin to configure and run them, which is exactly what a lean team doesn't have. What you actually need are the three things the spreadsheet can't do: stay current on its own, read the signals nobody types in, and raise its hand when an account needs attention.

See the revenue at risk on your own book.

Connect your stack or drop in a spreadsheet. Live in a day.

Start free

Flat $299/mo. First month free. 30-day money-back. Cancel anytime.