A spreadsheet is the right first system for a startup. It costs nothing and your team already knows it, so it lasts longer than you'd expect. Then your first sales hire starts, and their first week goes to finding out which file has the right number.
The line is hard to see because the company crosses it gradually, and nothing breaks loudly on the way. Here are five signs, in the order I usually see them.
1. Which file is current depends on who you ask
Sales_Tracker_v5_FINAL.xlsx, Sales_Tracker_v6_Mikes_Edits.xlsx, Sales_Tracker_v7_ACTUAL_FINAL.xlsx. Once files are emailed around or dropped in Slack, there are five current versions, and someone is working from the wrong one right now.
Move it into a shared system and the versions go away, because there's one record and your whole team reads the same one as it changes. A CRM is usually where that starts.
2. The same data gets typed more than once
A contract signs, and someone types the customer into a spreadsheet, then into HubSpot, then into the billing tool. It's slow, and the three copies start drifting apart right away without any of them looking wrong. Meanwhile an engineer you hired to ship product is doing data entry.
3. Simple questions take an hour to answer
"What's ARR this month?" "How many pilots are up for renewal next quarter?" If the answer is "give me an hour," the number you get is already old. The trouble is plumbing, because the numbers live in five places that someone assembles by hand. Connecting billing to the CRM shows you today's number instead of last week's.
4. The simple sheet stopped being simple
The sheet now has twenty-five tabs and VLOOKUPs pointing at other VLOOKUPs. One person understands it and the rest of the team is afraid to touch it, which makes that person a single point of failure you can't hire around.
5. The file itself can't keep up
This one is the least ambiguous. The file hangs on every recalculation and locks when two people are in it, so changing one cell takes a minute. That's the end of what the tool can do, and it's time for a database with an internal tool on top of it.
What to do about it
Three or four of these usually means the company grew. The next step is a system that fits how your team works now, which is sometimes software you can buy and sometimes something built on your own database.
Either way, map how the work moves today before anyone buys anything. That map is where the Ops Audit begins.