Replace the spreadsheet running your business.

Senior engineers only. Fixed-scope rebuilds. You keep your data, your formulas, your control.

The case for replacing the spreadsheet

Every mid-market business has the spreadsheet. The one that runs payroll, or tracks inventory, or holds the master customer list, or schedules every job. It started as a quick fix in 2014. It now has 14 tabs, three hidden tabs nobody is allowed to delete, 700 rows of formulas, and exactly one person who knows how it all works.

The spreadsheet is not a bad tool. It is the wrong tool for running a business on. Multi-user editing causes overwrites. There is no audit trail. There is no real backup. There is no validation. There is no security. One careless paste, one accidental sort, one bored intern, and the whole thing breaks. The recovery process is a Slack message to the one person who knows, who is currently on holiday.

Replacing the spreadsheet is rarely about adding features. It is about making the workflow reliable, multi-user, auditable, and survivable when the spreadsheet expert goes on annual leave. A good rebuild changes nothing about what the team does. It changes everything about how confidently they can do it.

The honest moment most agencies skip: not every spreadsheet needs replacing. If only one person uses it, if the formulas are simple, if the data fits comfortably in a few hundred rows, the spreadsheet is the right tool. We will tell you. About one in six spreadsheet audits ends with our recommendation to leave it alone, or move it to Airtable for $20 per user per month. The audit cost was $2,500. The answer was “you do not need us.”

If you have a business-critical spreadsheet and the thought of losing it tomorrow makes you nervous, call 0431 000 062 today.

Symptoms to look for

The spreadsheet that runs your business has a signature. These are the patterns that tell you it has graduated from tool to system.

• One person owns the spreadsheet. When they take a day off, work stops or rolls back to a previous version. When they take annual leave, half the management team learns to dread it.
• You email the spreadsheet around. Multiple versions exist. Nobody is sure which one is current. The Friday afternoon question “is this the latest?” is now a weekly ritual.
• Formulas have stopped working as the data grew. Performance is degrading. Opening the file takes a minute. Saving takes longer. The spreadsheet has outgrown the application that hosts it.
• You have already tried to put it on a shared drive. It either runs slowly or causes locking errors. Or both. SharePoint, OneDrive, Google Drive: each one was supposed to be the solution. None of them were.
• The business rules in the spreadsheet are not documented anywhere else. If the file corrupts, you have lost critical business knowledge. The formulas are the documentation.
• Reports are generated by manually copying out of the spreadsheet. And reformatting in Word, every Monday morning. The reporting process is now a job. The spreadsheet has become a feeder for the report nobody trusts.
• You found a “salary by employee” tab nobody had locked down. Or any other sensitive data sitting one careless share away from a compliance incident. The spreadsheet has no real security model, only the polite assumption that everyone will be careful.

DIAGNOSTIC

If three or more apply, your spreadsheet has graduated from being a tool to being a system. Systems need to be built like systems.

The rebuild method

Replacing a spreadsheet with custom software follows a specific pattern. Skip steps and the rebuild fails. The order is more important than the technology choices.

Extract the actual workflow

The spreadsheet is rarely the whole workflow. Most spreadsheets are the visible part of a process that also involves emails, phone calls, manual checks, and tribal knowledge. Phase one is mapping the entire workflow, not just the cells. We sit with the spreadsheet expert and watch them work for an afternoon. Half the workflow lives in their head, not in the file.

Model the data properly

Spreadsheets store data flat. Real business data has relationships (customers have orders, orders have line items, line items reference products). We rebuild the data model with proper relationships in a real database. This is the change that makes everything else work. Validation becomes possible. Reporting becomes accurate. Multi-user editing stops causing data corruption. The flat file becomes a real system.

Web app, multi-user, audit-logged

The replacement is a web application. Multiple users at once. Every change logged. Permissions per role. Backed up nightly. Accessible from any device. The team can do everything they did in the spreadsheet, and quite a few things they could not do in the spreadsheet. The salary tab is locked down to HR. The pricing tab is locked down to management. The job list is open to everyone who needs it.

Keep what worked

Some spreadsheets contain genuinely sophisticated business logic. We do not throw it away. We re-implement the formulas as proper code, document each one, and write test cases that prove the new system gives the same answers as the old one. The spreadsheet expert is part of the rebuild team, not the casualty of it. Their work gets preserved, codified, and made survivable.

Export back to Excel where useful

Excel is still useful for ad-hoc analysis, reporting, and sharing with people outside the company. We keep Excel export as a feature of the new system. The difference is that the spreadsheet is no longer the system of record. It is now a downstream output, generated from a single source of truth. Power users keep their Excel skills. The business loses its single point of failure.

Three engagement shapes

We structure spreadsheet rebuilds one of three ways. All three start with the audit.

• Spreadsheet audit. From $2,500. Workflow map, formula inventory, fixed-scope rebuild quote. Standalone deliverable. About one in six audits ends with our recommendation to keep the spreadsheet or move to a low-cost SaaS. That recommendation is the audit deliverable, not a sales failure.
• Simple replacement. From $15,000. Single-workflow web app replacement. Multi-user. Audit-logged. Production in four to six weeks. Best when the spreadsheet’s workflow is contained and you want to lift it cleanly into a real system without changing scope.
• Integrated replacement. From $35,000. Replacement plus integrations with your existing CRM, finance, or operational systems. Best when the spreadsheet has been the band-aid for the lack of integration between two systems. The rebuild becomes the integration.

Call 0431 000 062 if you are unsure which fits. The audit is the cheapest way to find out.

Spreadsheet replacements we have delivered

Three spreadsheet rebuilds. All three names confidential at client request (spreadsheet-running businesses tend to be quietly nervous about admitting it publicly). Reference calls available under NDA.

A logistics provider, name confidential

• Problem: A 22-tab spreadsheet running freight scheduling for a fleet of 40 vehicles. One person owned it. It crashed weekly. The crash recovery involved restoring from a OneDrive version history and emailing the team to redo their last hour of work.
• Built: Symfony web app with driver portal, dispatch screen, and live status feed. Integrated with their existing accounting system. Eight-week rebuild with the spreadsheet running in parallel the entire time.
• Result: Scheduling moved from one person to a team of four. Crashes eliminated. Dispatcher time reduced by 60% per shift. The original spreadsheet expert moved into a planning role they had been wanting for years.
• Stack: Symfony 7, PostgreSQL, AWS Sydney, Doctrine ORM, custom dispatch dashboard.

A specialty manufacturer, name confidential

• Problem: Quoting was run from a master Excel file with embedded formulas going back 15 years. Quotes took 30 to 90 minutes per request. Only the founder and one sales manager could produce a quote without errors.
• Built: Web-based quoting tool with the formulas re-implemented as documented business rules. Quote templates, version history, customer-specific pricing, audit log. Test cases prove the new system matches the old spreadsheet’s output across thousands of historical quotes.
• Result: Average quote time reduced to under five minutes. Quotes now generated by sales staff rather than the founder. Founder freed for higher-value work. Quote accuracy is now provable from the audit log.
• Stack: Symfony, PostgreSQL, Vue.js frontend, formula re-implementation in PHP with PHPUnit test coverage.

A multi-clinic healthcare provider, name confidential

• Problem: Inventory across multiple clinics tracked in a shared Excel file. Reconciliations weekly. Stockouts frequent. The file was opened in read-only mode by half the team because nobody trusted that the writes were going through.
• Built: Custom inventory web app integrated with Dear Systems and Zenoti. Each clinic has its own view, plus a head-office dashboard. Real-time stock levels. Alerts for low-stock thresholds.
• Result: Reconciliation moved from weekly to daily. Stockouts down 80% in the first quarter. The Excel file is now a downstream export, used only for monthly board reporting.
• Stack: Symfony, Nexus middleware, Dear Systems API, Zenoti API, AWS Sydney.

Who you will work with

Spreadsheet rebuilds require a particular respect for the people who built the original. The original spreadsheet is usually a serious piece of work and the rebuild has to honour the business logic in it. The senior engineer who runs the audit is the same engineer who builds, deploys, and hands over.

How we ship it

Four named stages. Each one is fixed scope and fixed price. You can stop after any stage and walk away with the work to date.

Smaller spreadsheet rebuilds (single-tab, single-team) run four to six weeks total. Larger ones (multi-team, integrated with finance or CRM systems) run eight to 12 weeks. The audit will give you the exact number before you commit to the build.

Spreadsheet replacement FAQs