Turn Your Customer Spreadsheet Into a Real CRM

A small consulting firm told us a story recently that felt familiar. They had been running their client pipeline out of a spreadsheet for four years. The file was well-kept — company name, contact, date of first call, status, a notes column that somebody used well and somebody else used sparingly. Two hundred rows. It worked.

Then, last quarter, they lost a large engagement. The discovery call had gone well. The prospect had asked for a proposal within a fortnight. Two weeks passed. Three weeks passed. On week four the prospect told them, politely, that they had gone with another firm. When the team looked back at the spreadsheet, the contact was there. The date of the call was there. The note said "warm — follow up with tailored proposal". The follow-up had never happened, because nothing had reminded anyone that it needed to.

That gap was not in the data. The data was fine. The gap was in everything that should have happened around the data. That is the real difference between a spreadsheet and a CRM. One of them stores. The other acts.

What a spreadsheet cannot do

Spreadsheets are remarkable tools. They are one of the most flexible pieces of software ever built. They can hold almost any shape of data and express almost any calculation. What they cannot do — by design — is behave.

A spreadsheet does not notice that a contact has been sitting at the "warm" stage for fourteen days. It does not ping anyone when a stage changes. It does not generate a list of everything that should happen this week. It does not keep two editors from overwriting each other. It does not remember that the customer you spoke with yesterday has a contract renewing in three months. It does not know that an email has arrived from a contact that should bump their priority.

These are not missing features. They are the things a spreadsheet was never trying to do. For ten or twenty contacts, the operator keeps the behaviour in their head. For two hundred, the operator's head fills up. Things fall through the cracks. Deals are lost. Nobody notices until somebody looks back at the spreadsheet and realises the follow-up should have happened three weeks ago.

A CRM is a spreadsheet that behaves. It acts on the same data, with the same fields, but it does things with it. That is the change.

The walkthrough, with real timestamps

Our example is a file called clients.xlsx with one tab, two hundred and seventeen rows, and twelve columns — the kind of customer spreadsheet small teams have been keeping for years. The columns are company, main contact, email, phone, source, stage, date of first call, date of last contact, estimated value, notes, owner, and a colour-coded status.

0:00 — Upload the spreadsheet. The file goes onto the upload area. Each column is identified and its type is inferred. The colour-coded status column is read as a categorical field, not a formatting trick.

1:00 — Describe the CRM. A single prompt. You type: "A CRM for a small consulting firm. Pipeline stages: Prospect, Qualified, Proposal Sent, Negotiation, Won, Lost. Each contact has an owner. Send a reminder to the owner if a contact has been in Qualified or Proposal Sent for more than 14 days without an update. Track activity history per contact. Sales reps see only their own contacts, admins see all."

2:30 — Exepad generates the application. Every contact from the spreadsheet appears, mapped into the new data model. The stages match what you described. The owner column becomes a proper relationship with user accounts that you can invite. The notes column becomes a proper activity log.

4:00 — Review and refine. A pipeline board view appears with the stages you named. You move a few contacts into the right stage. You add a reminder rule — notify the owner when a contact has been inactive for seven days, not fourteen, for the Proposal Sent stage. You add a custom field you forgot to mention initially — "referral source" — which carries through the whole pipeline.

6:00 — Publish. The CRM is live. You invite three colleagues by email. They log in. Every row from the spreadsheet is there, with its owner set, its stage set, and its notes in the activity log. Nothing was lost. Nothing was retyped.

What carries over, what changes

Teams that have lived in a customer spreadsheet for a long time are usually anxious about one thing above all: losing institutional memory. The spreadsheet holds not just the data but a thousand small decisions that accumulated — custom columns, colour codes, an idiosyncratic notes style that everyone has learned to read. The question is always: what survives?

What carries over. Every existing contact, with every field. The owner for each contact. The stage. The notes. Any custom columns you had added over the years — referral source, close reason, renewal date, whatever your team found useful. The relationships between contacts, where the spreadsheet expressed them. The colour codes and statuses that meant something to your team, translated into proper categorical fields. None of this needs to be retyped or reinterpreted.

What changes. The behaviour around the data. Reminders fire automatically when a stage has been stale for too long. Activity history is captured per contact rather than squashed into a single notes column. Pipeline views appear — a kanban board, a weighted forecast, a "who needs a follow-up this week" list. Two or three people can edit at once without overwriting each other. Access is controlled — an intern sees only what they should see, an admin sees everything, and the old problem of one person having the master copy on their laptop is gone.

What you lose is the right to argue with yourself about which version of the file is the real one. That loss is usually welcome.

What you can do the next morning

The morning after you publish, a few things look different.

Open the CRM and there is a list waiting for you. The contacts that have gone stale. The ones where the stage has not moved in a while. The follow-ups that are due today. It is not a long list. It is the list you have been meaning to make on the back of an envelope for the last year.

Your calendar gets a little more honest. Instead of "check the pipeline" as a half-hour block that ends up being a vague scroll through the spreadsheet, the pipeline now tells you what it needs. Ten minutes, three follow-up emails, two status changes, done.

New contacts no longer need to be typed twice. They go straight into the CRM. Your team sees them. The reminder rules start working on them from day one. If someone leaves the team, their contacts are not stranded on their laptop — the owner changes in the CRM and nothing else is lost.

The difference after a quarter, in most teams, is not that the team works much harder. It is that fewer deals get lost to silence. The warm lead that would have gone cold gets a nudge. The proposal that would have sat in someone's drafts for three weeks gets sent. The engagement that would have quietly churned at renewal gets an earlier conversation. Small changes, consistently applied.

Getting started

If your customer spreadsheet is starting to feel bigger than it used to, the fastest way to find out whether this fits your team is to upload the file and see what comes back. Your existing data stays intact; nothing is deleted, nothing is retyped, and you can always export back to a spreadsheet if it does not suit.

If you have other Excel files that are not about customers — inventory, bookings, projects — the companion walkthroughs on turning any Excel file into a working app and turning an Excel file into a dashboard cover the adjacent cases. The dashboards piece is the right match if your spreadsheet is mostly numbers you want to report on; the generic app walkthrough is the right match if your data does not fit the CRM shape.

The CRM-specific tool page, with showcase examples and a short video of the process, is at /convert-excel-to-crm.