The Hidden Cost of Excel Heroics in Hard Services

Every hard services company has one. The person who knows the data. They maintain the master spreadsheet that finance depends on. They know which columns to trust and which to ignore. They built the pivot tables that appear in board packs every quarter, and they know exactly which manual adjustments to make before anything goes to leadership. They are valuable, hardworking, and carrying an operational risk the organisation has never formally acknowledged.

The visible cost vs. the real cost

The visible cost of Excel heroics is the person's time. If your best analyst spends 60% of their week cleaning and preparing data rather than analysing it, that is inefficiency most organisations have normalised. The real costs are less visible but more significant:

• Delayed decisions. When producing a spend report takes a week, decisions get made on last month's data. In a tendering environment, a delayed cost estimate is a missed bid.
• Version risk. Multiple spreadsheets maintained by multiple people diverge silently over time. The procurement team's version and the finance team's version tell different stories by end of quarter.
• Audit exposure. Manually prepared reports cannot be traced back to a clean source of truth.
• Scale ceiling. The system that works for 50 sites cannot work for 200 without hiring more people to do the same thing.
• Key person dependency. If the person who maintains the master file is unavailable, the organisation loses its ability to produce reliable reporting.

Are you in Excel heroics territory?

A few diagnostic signs:

• Producing a spend or cost report takes more than a few hours of work
• Someone needs to sense-check the numbers before they go to leadership
• A new analyst would need weeks to understand the data structure
• Your reporting would be affected if a specific person was unavailable for two weeks
• You have more than one version of the same dataset maintained by different people

What the migration away from Excel heroics looks like

Stage 1: Establish a data baseline. Before any automation is introduced, the data needs to be in a known, clean state. This stage reveals the manual work that has been done to make the data usable — the lookup tables, the correction rules, the adjustment notes in cells. Those rules get documented and formalised so they can be applied systematically rather than personally.

Stage 2: Automate the repeatable corrections. Deduplicating supplier names, standardising descriptions, filling missing category fields, flagging anomalies for review — these can be automated. The analyst's time shifts from doing the corrections to reviewing the system's work.

Stage 3: Build ongoing quality control into the data flow. New data entering the system gets validated against the established structure automatically. Quality is maintained by the process, not by a person.

"Pearstop built a system that automatically pulls the right items from our visiting reports into a clean proposal document. It saves our team a lot of time by eliminating the repetitive tasks of combining the correct items."

What the other side looks like

After this transition, the analyst who was maintaining the master file does not lose their role. Their role changes. They move from data preparation to data analysis — from keeping the system running to using it to generate insights.

"For the first time, I feel like I actually do the job I was hired for — analysis, not admin."

Neharika Kishore

Content & Visibility, Pearstop

Neha works on content and visibility at Pearstop. She writes articles on procurement data quality for facilities management, construction and infrastructure teams, and supports The Data Edge podcast. She also runs outreach to procurement and finance leaders, which keeps her writing close to the problems those teams are actually raising.

LinkedIn →