Ask a small business owner where a specific job is and you often get a search: check the inbox, check the calendar, ask the person doing it, look for the invoice.
The information exists. It is just in four places with nothing connecting them, and nobody can see the whole thing at once.
What a complete view needs
Every job passes through the same stages, whatever you call them:
- Inquiry — someone made contact
- Qualified — worth quoting
- Quoted — number sent
- Won or lost
- Scheduled
- In progress
- Complete
- Invoiced
- Paid
Nine stages. If you can see how many jobs sit in each one right now, you can run the business. If you cannot, you are working from memory.
What you learn from it
Where things stall. A pile at "quoted" means follow-up is not happening. A pile at "complete" means invoicing is slow, which is cash flow. A pile at "invoiced" means collections.
Each blockage has a different fix and you cannot tell them apart without stage visibility.
Your actual conversion rates. Inquiry to quote, quote to won, won to paid. Most owners know none of these.
How long each stage takes. Where the days go between someone contacting you and money arriving.
What is at risk. Anything sitting in a stage far longer than normal, before it becomes a problem.
The minimum viable version
You do not need a platform. You need one place where every job exists with a stage attached, and a rule that it gets updated.
A spreadsheet with one row per job and a stage column genuinely works at small scale. Columns: customer, job, value, stage, date entered stage, next action, owner.
That is enough to answer every question above.
The reason it usually fails is not that a spreadsheet is inadequate. It is that nobody updates it, because updating it gives the updater nothing. Our note on why your team ignores the CRM covers that trap.
Make the update automatic where you can
The stages that can move themselves without anyone remembering:
- Inquiry created when a form is submitted or a call comes in
- Quoted when the quote is sent
- Scheduled when it lands on the calendar
- Invoiced when the invoice goes out
- Paid when payment clears
That leaves only the genuinely human transitions — qualified, won or lost, complete — needing a person. Three updates instead of nine, and the three that remain are moments where someone is already taking an action.
That difference is usually what decides whether the system survives.
The rule that keeps it honest
One place. If it is not in the system, it does not exist.
The moment there is a parallel notebook or a "I'll remember that one," the view is incomplete and untrustworthy, and an untrustworthy view stops being used.
That has to include the owner. Systems die when the person at the top keeps their own list.
What to watch weekly
Four things, ten minutes:
- Anything stuck in a stage longer than it should be
- The count at "quoted" — that is your follow-up backlog
- The count at "complete but not invoiced" — that is cash you have earned and not asked for
- The count at "invoiced but not paid" past terms
Those four catch nearly every operational problem while it is still small.
Growing into something bigger
Start with the spreadsheet. When it genuinely stops coping — too many rows, too many people editing, too much manual updating — you will know exactly what you need from a real tool, because you will have been running the process for months.
That is the right order. Buying a platform first, hoping it creates the process, is the version that ends with software nobody uses.