What Causes Spreadsheet Dependency in Consulting Firms (And Why It Gets Worse as You Grow)

Spreadsheet dependency isn't a technology problem. It's a structural one. Here are the five root causes and why each one compounds as headcount increases.

---

Every partner at a consulting firm between 10 and 50 people recognizes the spreadsheet problem. What fewer understand is why it exists and why attempts to fix it so often stall or regress.

The answer isn't that the firm hasn't found the right tool yet. It's that the conditions that create spreadsheet dependency are structural to how consulting firms operate. Buying a new piece of software doesn't change the structure.

Here are the five root causes.

The five causes of spreadsheet dependency

1. 1

   Tool proliferation without integration

   A typical consulting firm uses four to six tools for core operations: a CRM for pipeline, a project management tool for delivery, a time tracker for billing, accounting software for financials, and often a separate tool for proposals and resource planning. Each tool was adopted to solve a specific problem. None of them was chosen with integration in mind. The result is a fragmented data landscape where the only way to get a whole-firm view is to manually compile from each system, which is what the spreadsheet does.

   Gets worse with growth: each new tool added to the stack adds another manual connection point.
2. 2

   Internal operations always lose to client work

   In a consulting firm, the default priority is the client. When a choice has to be made between updating the pipeline spreadsheet and finishing a client deliverable, the spreadsheet waits. This is entirely rational at the individual level and entirely destructive at the firm level. The spreadsheet falls behind. The data gets stale. The people who rely on it start to distrust it. Eventually they start maintaining their own versions which makes the problem worse.

   Gets worse with growth: more fee earners means more people making the same rational trade-off, compounding the staleness.
3. 3

   Project-based revenue makes standardization feel unnecessary

   In a subscription or product business, standardizing operations is obviously necessary, the volume of transactions requires it. In a consulting firm at 15 people with 8 active clients, it feels manageable. The partners know the pipeline. The delivery lead knows who's working on what. The spreadsheet feels like enough because the whole operation is visible to a small group of senior people. It stops being enough around 20–25 people, when the knowledge can no longer live in a few heads but by then, the spreadsheet model is entrenched.

   Gets worse with growth: what was manageable at 12 people becomes chaotic at 25 with no structural change.
4. 4

   Single-person spreadsheet ownership

   In almost every firm, the spreadsheet is owned by one person or is supposed to be. That person knows how it works, knows what the anomalies mean, knows which cells to trust and which to ignore. When that person is unavailable, on leave, or leaves the firm, the model degrades immediately. Knowledge that should be in a system lives in one person's head. This is a business continuity risk dressed up as an operational tool.

   Gets worse with growth: the model gets more complex and harder to hand off as the firm grows.
5. 5

   No dedicated operations role until it's too late

   Most consulting firms don't hire an operations manager until they're 25–35 people. Before that, operations are distributed across partners who are also running client work. The spreadsheet exists because nobody owns the problem of replacing it and the people who notice the problem most acutely are also the least available to fix it. By the time an ops hire is made, the spreadsheet model is deeply embedded in how the firm works and the cost of change has increased significantly.

   Gets worse with growth: delay compounds. Each month without a fix is another month of accumulating technical and organizational debt.

How severity scales with firm size

The five causes are present in most consulting firms from the beginning. Their severity as operational problems scales with headcount.

Firm size	Typical state	Severity
5–10 people	One spreadsheet, one owner. Mostly accurate. Annoying but workable.
10–20 people	Multiple spreadsheets. Inconsistencies emerging. 2–3 hrs/week assembly time.
20–35 people	Fragmented ownership. Partner decisions on stale data. Utilization unknown. 8–15 hrs/month.
35–50+ people	Multiple conflicting versions. High staff turnover risk on knowledge. Revenue forecasting unreliable.

Why buying a new tool doesn't fix it

The instinct when the spreadsheet problem becomes painful is to buy a tool, a better CRM, a PSA platform, an all-in-one practice management system. This usually doesn't work, for a simple reason: the problem isn't the spreadsheet itself. The problem is the five structural conditions that made the spreadsheet necessary.

A new tool that isn't integrated with the rest of the stack creates a new data silo. A tool that requires manual data entry will be abandoned when client work gets busy. A tool owned by one person has the same key-person risk as the spreadsheet it replaced.

Buying a new tool without addressing the structural conditions that created the old problem is how consulting firms end up with six tools and a spreadsheet that connects them all.

The fix is to connect what already exists so that data flows automatically, the view is always current, and no single person carries the operational knowledge of the firm in their head or their laptop.

Frequently asked questions