How to move from spreadsheets to a database
The signs a spreadsheet has outgrown itself, and how to move without losing the flexibility that made it work.
Stages that reflect the buyer’s decision, not your wishes — and the few fields worth tracking from day one.
A sales pipeline is the list of deals you are working on, arranged by how close each one is to a decision. Build it by naming the stages a buyer actually passes through, putting every open deal into one of them, and recording three things per deal: the amount, the expected close date and the next action. That is enough to run a small sales operation.
The mistake that kills pipelines is designing stages around what your team does — “proposal sent”, “followed up” — instead of what the buyer has decided. A stage should represent progress in their head, not activity in yours.
Track lost reasons from the first week. After thirty deals they will tell you more about your pricing and positioning than any survey.
Every field you add is a field someone has to fill in. Start with four — company, amount, stage, next action — and add more only when you have a question you cannot answer without them. Elaborate CRMs go unused for exactly this reason: they ask for data before anyone needs it.
A spreadsheet is fine for one person and a handful of deals. It stops working when two people update it at once, when you want a history of what changed, or when the next action needs to become a reminder rather than a hope. That is the point to move to a pipeline tool — and to move the data as it is, not to redesign the process on the way.
Ettex CRM keeps contacts, a visual deal pipeline and the activity behind each deal in one place, with your documents, invoices and email in the same suite — so a deal can link to the proposal itself rather than to a copy of it.
Four to six. Fewer and the stages carry no information; more and people stop moving deals because it is unclear where they belong.
When there is no next action you both agreed to. “Circling back in Q4” without a date is a lost deal that flatters your forecast.
Not on day one. You need it when deals start slipping because you forgot a follow-up — that is the signal, not the number of deals.
Weekly for most small teams. Long enough for something to change, short enough that dates stay honest.
The signs a spreadsheet has outgrown itself, and how to move without losing the flexibility that made it work.
The five sections that matter, in the order visitors read them — and what to do before you pick a template.
Separate calendars per purpose, the right level of visibility, and how to keep it readable as the team grows.