First, what the spreadsheet already costs
The spreadsheet looks free because nobody gets an invoice for it. The costs show up elsewhere:
- Hours spent copying data in, fixing formulas and reconciling versions
- Mistakes from a broken formula, a sorted column or an overwritten cell
- Two people editing different copies and nobody knowing which is current
- The one person who understands it being on vacation, or leaving
Put an hourly figure on the first item, as in our guide to sizing a manual process. The others are harder to price, but they are often the real reason to act.
Not every spreadsheet needs custom software
Consider the cheaper options first, in this order:
- Clean up the spreadsheet: lock formulas, add validation and keep one shared copy
- Move it into an existing product that already does this job
- Connect the spreadsheet or product to the systems it copies data from
- Build a custom tool only when none of those genuinely fits
What drives the cost of a custom replacement
When a custom tool is the right answer, these are the decisions that move the price the most:
- Screens and workflows: how many distinct things people need to do, not how many tabs the spreadsheet has
- Users and permissions: one team sharing everything is simpler than roles that see different data
- Rules and calculations: formulas that must be understood, documented and tested before they are rebuilt
- Integrations: every system the tool reads from or writes to adds work and ongoing care
- Data migration: cleaning years of inconsistent rows is often a project of its own
- Reports and exports: each summary people currently build by hand needs defining
What it costs to run afterwards
Budget for the ongoing costs, not only the build:
- Hosting and any third-party services, billed to your own accounts
- Updates when a connected system changes
- Small improvements as the way you work evolves
- Your team’s time learning the new tool and retiring the old file
How to start smaller
The first version does not need to replace everything the spreadsheet does. Pick the part that causes the most errors or takes the most hours, build that well, and keep the rest in the spreadsheet for now. A smaller first release costs less, proves the approach on real work, and teaches you what the next version should include.
Keep a read-only copy of the original spreadsheet after the switch, so anyone can check a past figure while trust in the new tool builds.
Questions to answer before asking for a price
- Which part of the spreadsheet causes the most errors or takes the most time?
- Who uses it, and does everyone need to see everything?
- Which other systems does data come from or go to?
- How many rows of history need to move, and how clean are they?
- Which reports do people build from it every week or month?
Clear answers to these make any estimate, from us or anyone else, far more reliable.