When a spreadsheet stops being good enough

Replacing one that genuinely runs part of your business costs $35,000 – $54,000. A narrower first version is $18,000 – $27,000. Plenty of businesses aren’t there yet, and this page will tell you if you’re one of them.

$18,000 – $27,000: One workflow, one kind of user, done properly
$35,000 – $54,000: Several people, permissions, and reports
$44,000 – $67,000: That plus search, files, and moving your old data in

Written by

WhatWillMyAppCost

We build the estimator this site runs on, and we design and build custom mobile and web software for a living. Every figure below is the estimator’s own output, except the subscription prices, which are read off each vendor’s pricing page and dated.

Four people edit it. Two of them overwrite each other most weeks. Nobody notices for days. Somebody keeps a copy on their desktop because the shared one is too slow. Nobody is completely sure which version is right anymore, and the person who built the thing left in March. You’ve started saying "let me check" before you answer questions you used to know the answer to.

That’s a normal stage and it doesn’t automatically mean you need software built. Here’s how to tell whether you’ve actually outgrown it, what replacing it costs, and how to work out whether the numbers justify it.

How do you know you’ve outgrown it?

When the spreadsheet costs you money instead of time. Slow is survivable. The things below aren’t, and if three or more are true you’ve probably crossed over.

Two people regularly overwrite each other, and you find out days later.
Somebody has to be careful, and when they’re on vacation things go wrong.
You can’t let people see it, because it holds things they shouldn’t see.
Somebody spends hours a week retyping the same data into another system.
You’ve been burned by a mistake nobody could trace back to who made it.
You’ve stopped adding to it because you’re afraid of breaking a formula.

If none of those are true, stay put. A spreadsheet that annoys people is not the same as one that’s costing you, and rebuilding a merely annoying spreadsheet is the most common way this money gets wasted.

What does replacing it cost?

$18,000 – $27,000 for one workflow with sign-in and one kind of user, over 10–15 weeks. $35,000 – $54,000 once several people use it, they need different permissions, and somebody wants reports out of it. That second one is where most of these land.

$35,000 – $54,000: The version most businesses actually need
$26,000 – $39,000: A narrower first cut, 27% less

Add search, file attachments, and moving what’s in the spreadsheet now across, and it’s $44,000 – $67,000. The last of those three is the one people forget. Ten years of accumulated exceptions in a spreadsheet is not a clean import, and somebody has to decide what happens to the rows that don’t fit.

What actually costs the money?

Not the screens. It’s that different people should see different things. A spreadsheet can’t do that, and it’s most of why you’re replacing it.

What a spreadsheet does: Everybody who can open it can see everything in it and change anything in it. There is no version where somebody sees their own rows and not yours. That is the whole reason a copy ends up on somebody’s desktop.
What replacing it means: Each kind of person gets their own screens and their own rules about what they can touch. That’s real design and real testing, and it’s the difference between $18,000 – $27,000 and $35,000 – $54,000. It’s also the thing you actually wanted.

Reports are the other half. A spreadsheet is a report, which is why nobody notices they’re asking for one. In a real tool somebody has to build each one, and the useful move is to write down the three questions you ask the spreadsheet every week and only build those.

Does it actually pay for itself?

Often, and unusually for software you can check before you spend anything. Add up the hours a week your people lose to retyping, chasing, fixing, and asking each other which version is right. Multiply by what those hours cost you. Multiply by fifty.

If that number is $30,000 a year, a $35,000 – $54,000 tool pays back inside two years and keeps paying. If it’s $6,000 a year, it doesn’t, and you should fix the spreadsheet instead. Do this arithmetic honestly, including the weeks nothing goes wrong.

Count the mistake you haven’t had yet. Most businesses that build this had one bad week that cost more than the software, and they can name it. If you can’t name yours, you may genuinely not need this yet.

Before any of that, price the off-the-shelf option. If what you do is ordinary, somebody sells it for a few hundred a month and it works on Monday. Custom earns its money when the thing you do isn’t ordinary, which is exactly why it never fits the products. What a field service business faces is the same decision in one specific trade.

Replacing a spreadsheet that genuinely runs part of the business costs $35,000 – $54,000, and permissions, not screens, are where the money goes.

Check the off-the-shelf option first, do the hours-lost arithmetic honestly, and if the number doesn’t clear the cost, fix the spreadsheet and revisit in a year.

FAQ

Questions about leaving the spreadsheet behind

How much does it cost to replace a spreadsheet with an app?

$18,000 – $27,000 for one workflow and one kind of user. $35,000 – $54,000 once several people need different permissions and somebody wants reports, which is where most land. $44,000 – $67,000 with search, file attachments, and moving your existing data across.

Could a no-code tool do this instead?

For a lot of these, yes, and it’s worth trying first. Tools in that category handle forms, approvals and simple dashboards well and cost a fraction of this. The limits are real: you’re renting the platform, you’ll hit a ceiling on how much you can change, and moving off later is a rebuild. For proving a workflow is worth automating, that’s a good trade.

What about just using Airtable or a database?

Same answer, one step up. They fix the overwriting problem and give you some permissions, which is most of what people actually want. They don’t fix the case where your process has rules a table can’t express. Try it before you build, because if it works you’ve saved most of this money.

Can we move our existing data across?

Yes, and it costs more than people expect. Clean, consistent rows are a script. Ten years of a spreadsheet where three columns changed meaning and somebody used the notes field for four different things is archaeology, and somebody at your company has to make the decisions about the rows that don’t fit.

How long does it take?

10–15 weeks for a narrow first version, 14–20 weeks for the version most businesses need. Keep running the spreadsheet alongside it for a few weeks after it launches. Cutting over on a single day is how you find out what nobody mentioned.

Do we need to build it all at once?

No, and you shouldn’t. Build the one workflow that’s costing you money, keep the spreadsheet for everything else, and add to it once people are using the first part daily. That first cut is around $26,000 – $39,000.

Will people actually use it instead of the spreadsheet?

Only if it’s faster for them than the spreadsheet was. That usually means fewer clicks to do the thing they do forty times a day, even at the cost of the thing they do twice a year being slower. Watch somebody do their actual job before anyone designs a screen.