Counting stages without a system is entirely possible by hand

4 days ago
3 min read

Updated: 2 days ago

Introduction

The usual answer to funnel measurement is a CRM. It is a reasonable answer for a business with a sales team, and a poor one for a business of three people, because the software costs money, takes weeks to set up properly, and is abandoned within a quarter when nobody has time to keep it current. The measurement then stops entirely, which is worse than the situation before.

Counting by hand is not a compromise. A spreadsheet with one row per enquiry and five columns produces every number a small funnel needs, and it has the significant advantage of being maintained by the person who already knows what happened. It fails only if nobody updates it, and that failure is visible immediately rather than three months later.

The point is to start counting now with what you have, and let the volume decide when software becomes necessary.

1. Counting stages without a system starts with one row per enquiry

The structure.

Every enquiry gets a line the day it arrives. Not a summary at month end, which is where accuracy goes. The discipline is in the immediacy, not in the tool.

2. Five columns is enough

The minimum.

Date, name, source, stage, value. That is a functioning funnel record and it fits on a phone screen. Add columns later only when a specific question demands one.

3. Record the source while you still know it

The perishable field.

A week later nobody remembers whether they found you through a search or a recommendation. Ask on the first call and write it down. This single column answers more questions than the rest combined.

4. Use a small fixed set of stage names

The consistency point.

Enquiry, quoted, won, lost. Four words, always the same four, chosen once. Free text in a stage column destroys the ability to count anything.

5. Update the stage, do not add rows

The maintenance rule.

One enquiry stays one line for its whole life, with the stage overwritten as it moves. Adding a row per event turns counting into a project. The history you lose is rarely worth the complexity.

6. Record the date of the outcome

The time measure.

A second date column, filled when the enquiry is won or lost, gives you elapsed time for nothing. That is the most useful derived number in the sheet. It costs one keystroke per enquiry.

7. Count at month end, not continuously

The cadence.

Ten minutes with a filter produces all five numbers. Watching the sheet daily produces anxiety and no information. Put the ten minutes in the calendar.

8. Keep one sheet, not one per person

The single source.

Two people keeping separate records produces two different answers and an argument. A shared sheet that everybody writes to is worth more than a better structured private one. Access matters more than design.

9. Move to software when the sheet breaks

The upgrade trigger.

Roughly when you pass a few hundred open enquiries, or when more than two people need to update it at once. Before then the sheet is genuinely better. Migrating a year of clean rows into a CRM is straightforward.

Be careful about starting with an elaborate spreadsheet. Conditional formatting, dashboards and formulas make the sheet fragile and make other people reluctant to touch it, and the value is entirely in the rows being current rather than in how they are displayed.

Conclusion

Open a spreadsheet today and give every enquiry one row.

Keep to five columns, capture the source on the first call while somebody still knows it, use four fixed stage names rather than free text, overwrite the stage instead of adding rows, record the date the outcome lands so elapsed time comes free, count once a month rather than continuously, keep a single shared sheet, and move to software only when volume or the number of people updating it genuinely breaks the sheet.