The Spreadsheet That Runs Your Company

Every company has one. It might be called Aftersales_Tracker_FINAL_v7.xlsm, or just "Sam's sheet". It sits on a shared drive, takes a while to open, and does something the business cannot do without. It might build the parts-and-labour quote, reconcile the month-end commissions, allocate stock between branches, or tell finance which invoices are ready to send.

Ask who understands it and you will get one name. One person built it over years, adding a tab here and a macro there as the business changed. They know which column must never be sorted, which sheet is hidden for a reason, and which button has to be pressed before saving. Everyone else simply trusts it.

That is key-person risk, and it rarely appears on a risk register because it does not look like risk. It looks like a reliable colleague and a useful file. It becomes visible when that colleague resigns, takes leave during a peak period, or is off sick on the last day of the month. This article covers what is inside these files, how they connect (or fail to connect) to the rest of your systems, and how to deal with them without betting the business on a big-bang replacement.

How a spreadsheet becomes infrastructure

Nobody decides to run a company on Excel. It happens in small, sensible steps.

A system does not quite produce the report the general manager wants, so someone exports the data to Excel. The export needs cleaning, so a formula is added. The formula is repeated every morning, so a macro is recorded. The macro gets a button. A second branch wants the same thing, so the file is copied to the shared drive. Then a colleague who wants to edit it at the same time uploads a copy to Google Sheets. Now there are two versions, and nobody is sure which one finance uses.

Each step made sense when it was taken. The result is unofficial infrastructure with no owner, no documentation, no testing and no change control, yet it feeds quotes, invoices and management decisions. Leadership sees the output of these files in its reports, but has no view of the process that produces it.

What is actually inside the file

It helps to be specific about what these files contain, because the risk sits in the details.

Excel workbooks. Lookup formulas pull prices from a tab that someone updates by hand. Nested IF statements encode business rules such as fleet discounts, warranty exceptions and branch-specific labour rates. Hard-coded values, such as a VAT rate typed directly into formulas, sit where nobody will think to check them. Pivot tables summarise data that was pasted in manually.

Macros. A VBA macro might import the DMS export, delete header rows, fix the way customer names in different languages and scripts are joined, split a file by branch and email the results. Macros often depend on a specific folder path, a particular Excel version or an add-in installed on one person's laptop. When that laptop is replaced, the macro stops working, and nobody can tell why because nobody has read the code since it was written.

Google Sheets. Branch teams often move to Sheets because it is easy to share. Cross-sheet links such as IMPORTRANGE and small Apps Script automations spread across several files. Many of these are owned by an individual's account. When that person leaves and the account is deactivated, the sheets that depended on it can break or lose access.

Shared drives. The shared drive is where all of this is meant to be controlled, but it usually adds confusion. There are folders of copies named "final", "final2" and "use this one". Permissions have grown over time. A file shows as "locked for editing by" someone who went home hours ago. The drive stores the files, but it does not tell you which one is correct.

A day in the life: aftersales at a multi-branch dealer group

Consider a dealer group with branches in three countries. This is a hypothetical, but most multi-location operators will recognise the shape of it.

At 8:40 a customer sends a WhatsApp voice note, in their own language, asking for the price of a 60,000 km service. The service advisor checks the vehicle history in the DMS. The DMS does not hold the current service package pricing, so the advisor opens the pricing workbook on the shared drive. One branch has its own copy, last updated before the most recent parts price change. The advisor types a quote into WhatsApp by hand, from memory and a spreadsheet.

The customer approves. The advisor re-keys the job into the DMS. One required part is not in stock, so the advisor checks the parts counter's stock sheet, which is updated twice a day, and then phones another branch to confirm a transfer. The CRM knows none of this. Two weeks later it sends the customer an automated service reminder for work already done, and the customer wonders whether anyone is paying attention.

In the afternoon, finance exports the day's invoices from the DMS and runs them through a macro that reformats them for VAT reporting. In countries that have introduced e-invoicing mandates, including Peppol-based schemes, invoice data has to be structured and consistent, so a manual spreadsheet step in the middle is a place where errors get in and are hard to trace. In countries without such mandates, the same step still creates reconciliation work when the VAT return is prepared. If the person who understands the macro is on leave, the invoices wait.

For a group, there is a further cost. Each country has its own tax rules, its own data protection obligations under laws such as GDPR, and its own copy of the file. Nobody at head office can say whether a quote in one branch matches a quote in another without asking someone to check.

Now add the pressures of the calendar. During peak seasons, working hours shift and customers want evening appointments. In the weeks around public holidays and before the summer travel season, workshop volumes climb. A spreadsheet process that was tolerable on an ordinary Tuesday becomes a bottleneck when volume rises and the only person who can fix it is away.

The same pattern in real estate and agencies

The automotive example is not unusual. The same pattern shows up wherever the real work happens between systems.

A real estate brokerage might receive leads from listing portals, its website and WhatsApp, then log them in a Google Sheet because the CRM is too slow to update on a viewing day. Unit availability sits in one workbook, and the payment-plan calculator is another Excel file with a macro that only one sales coordinator trusts. If an agent quotes from an out-of-date price list, the client sees a number that is wrong, and the brokerage has to either honour it or retract it. Commission calculations then depend on a third file that reconciles all of the above by hand.

An agency or growth company has its own version. Retainer hours are tracked in one sheet, project status in another, and invoicing lives in finance's workbook. Utilisation reporting means someone spends the first two days of each month assembling data from all three. The account director who knows how to read that report is, again, one person.

What it costs you

The cost is rarely a single dramatic failure. It accumulates in small, repeated ways.

• Delays. Quotes, approvals and invoices wait for someone to update, run or fix a file. Work that should take minutes takes hours because it passes through a manual step.
• Exhausted teams. Skilled people spend their time copying, pasting, reformatting and checking, and the person who owns the spreadsheet becomes the unofficial helpdesk for everyone else. They cannot take leave without worry, and that is a retention risk of its own.
• Mistakes. Manual re-keying introduces errors. A stale price, a wrongly sorted column or a copy of the file that nobody updated can all produce a wrong quote or invoice. The mistake is often found only when the customer queries it.
• Frustrated customers. Customers do not see your systems. They see a quote that differs between branches, a reminder for work already done, or a WhatsApp reply that arrives hours late because the answer was in a file.
• Money leaks. Unbilled labour, missed parts charges, forgotten warranty claims, incorrect discounts and uncollected follow-ups all hide in the gaps between systems. No single report shows the total, because the gaps are exactly where the data does not flow. This is a revenue operations problem as much as an IT one, because the handoffs between sales, service and finance are where the revenue goes missing.

Why "just replace it" usually fails

The instinctive response is to buy a new system and retire the spreadsheet. It is understandable, and it often disappoints.

The first problem is that the spreadsheet's logic is undocumented. The rules in those formulas and macros are, in practice, your real business rules, including the exceptions nobody wrote down. If you migrate to a new platform without extracting them, you either lose them or rebuild them from memory, and you discover the gaps after go-live.

The second problem is that the spreadsheet exists because your systems do not talk to each other. A new system added to the pile, without connecting to the DMS, CRM, finance, service, website and messaging, simply creates a new place to export from. The spreadsheet comes back within a quarter.

The third problem is that not every spreadsheet should be killed. An analyst's working file for ad hoc analysis is fine. The ones that must be fixed are those that sit in the middle of a live process, such as quoting, invoicing, stock or commissions, and depend on one person.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner that designs the change, wires your existing systems into one operating backbone, and stays on to run it. We sell the outcome, not software. For a spreadsheet problem, the work follows three phases, and you can stop after any one of them.

Blueprint. We map your operation end to end and find every gap where work is done twice, data goes stale or money leaks. The critical spreadsheet is usually one of the first things to surface. We document what it does, which systems feed it, who depends on it and which rules are buried in its formulas. You keep the map either way. Even if you never take another step with us, the risk is no longer sitting in one person's head.

Build & Link. We build what is missing and wire your existing systems into one backbone. There is no rip-and-replace, and software you have already paid for stays. This is where the Managed Link layer applies. It is the operating layer between systems, built, owned and maintained by Ninjaz, so that your DMS, CRM, finance, service, website and messaging behave like one system. The logic that lived in the macro moves into that layer. Prices, stock and customer data flow between systems instead of being exported, cleaned and re-keyed. Where the business needs it, Managed Transformation Services covers the strategy, design and development of the change itself. Where leadership wants a single view across branches or countries, the same connected data can feed a central command center, so quotes, stock, invoices and follow-ups are visible in one place rather than reconstructed from files.

Operate. After go-live, support, monitoring and continuous improvement keep it running. This is the Managed Business Operations layer, which provides managed and remote IT support. It is your operations and IT team without the headcount, so the knowledge is no longer held by one person who might leave.

On delivery, strategy and account leadership stay close to your business in the markets where you operate, and engineering, automation and support work alongside them. For a multi-location group, that means one operating model applied consistently across sites, with local tax, language and data protection requirements handled inside the design rather than in a spare tab.

Where to start

You do not need to commit to a programme to deal with this. Start by asking your team which files they would be unable to work without, and who understands each one. Write down the names. Any file with a single name next to it, and a live process behind it, is your first candidate.

From there, the sequence is simple: document what the file does, find out which systems it depends on, and decide which parts should move into a connected, owned process. Everything else can stay in Excel, where it belongs.

If you would like help finding the spreadsheet that holds your operation together and removing the risk without disrupting the business, book a consultation.