Customer Records: Why Spreadsheets Lose You Money

A spreadsheet is a fine tool. At the start it honestly does the job: a hundred customers, one person in charge, everything under control. The trouble begins not at a breaking point but imperceptibly: the database grows, there are now three people, and one day it turns out that a loyal customer worth 400,000 a year went uncongratulated, unphoned, and unnoticed when they stopped buying six months ago.

Four ways a spreadsheet loses money

• Repeat sales. A spreadsheet does not show who has not come back for a while. The customer leaves quietly and nobody calls after them — yet winning back an old customer costs a fraction of acquiring a new one.
• Forgotten commitments. "Call back in September" lives in a salesperson's head, and salespeople resign. Part of the customer base leaves with them.
• Duplicates and divergence. Two versions of the file held by two employees — and a month later nobody knows which is current.
• Analytics that do not exist. No visibility of acquisition cost, which services carry margin or which advertising channel pays off. Decisions get made on gut feel.

Simple arithmetic of the losses

Take a database of 800 customers with an average annual spend of 25,000 roubles. If the absence of any repeat-sales work costs you just 8 percent of the base a year on top of natural churn, that is 64 customers and 1.6 million roubles of revenue. Against figures like that, 200,000–300,000 for proper record keeping stops looking like an expense. And this is not about a perfect system — it is about the basics: knowing when a customer was last here, and having a reason to get in touch.

The risks nobody thinks about

A file of personal data on a desktop breaches almost every clause of 152-FZ: no access separation, no activity log, no control over copying. Resignations are a story of their own: an employee walks off with the entire database in one move, and nothing can be proven because no trace is left. In a system with access rights and logs it is at least visible, and bulk exports can be restricted. What we check on this front during a data migration is described in the security section.

When to move

The markers are simple: more than 300–500 active customers, more than two people working with the database, or repeat sales making up a meaningful share of revenue. If at least two of those apply, the spreadsheet already costs more than a system would. If your business is one-off, you have fewer than two hundred customers and one person handles them, stay in the spreadsheet with a clear conscience and do not spend the money. An honest answer matters more here than a sale — we regularly talk people out of a rollout they do not yet need, and we discuss it at the initial consultation.

How to move without pain

The move does not start with buying a system. First comes an audit of what has accumulated: duplicates, empty records, data in the wrong columns. We covered the order of operations in detail in our piece on migrating a database out of Excel. Then a minimal set of fields, so the team does not drown in a thirty-line form. Then two weeks of running in parallel, and only then switching the file off. And you absolutely need one person responsible for data quality: without that, a year from now you will have the same mess in a new interface.

What appears after the move

The first thing owners see is a list of customers who have not returned within their usual buying cycle. Calling through that list almost always pays for the rollout within the first few months. The second is a real picture of sources: some advertising turns out to be loss-making and the budget gets reallocated. The third is the ability to measure not just sales but resources: staff utilisation, equipment availability, stock levels. That is usually the level at which the need arises for an industry product like homade or Auto555 instead of a general-purpose CRM.