Software Costs

Replace Spreadsheets With Custom Software: A Contractor's Guide

Replace spreadsheets with custom software only when the math says so: a 12-point score for dispatch boards and price books, four options priced, a plan.

Stressed man holding his head over a tall stack of tabbed paperwork at his office desk
In this article
  1. Why spreadsheets fail in ways other software doesn't
  2. The 12 signs it is time to replace spreadsheets with custom software
  3. What the spreadsheet you already have actually costs
  4. Your four options, priced side by side
  5. How to decide: the break-even you can run on your own numbers
  6. A seven-step migration plan that doesn't stop the trucks
  7. What goes wrong, and how to avoid it
  8. When the spreadsheet holds payroll, payment and customer data
  9. What the new system costs to run
  10. Putting it together
  11. Frequently asked questions
  12. Sources

You should replace spreadsheets with custom software when the spreadsheet has stopped being a calculator and started being the system that runs a part of your company: several people edit the dispatch board, data gets retyped into it from the field app, a wrong value costs a truck roll or an unbilled job, and nobody can tell you who moved the Thursday job or when. Until that happens, a spreadsheet is the cheapest and most flexible tool you own, and replacing it wastes money.

The hard part is not recognizing the pain. It is deciding which of four very different answers you need (harden the spreadsheet, buy off-the-shelf software, assemble a low-code app, or commission a custom build) and knowing roughly what each costs before you talk to anyone. This article is written for the owner or general manager of a contractor with a dispatcher, an office team and a field app, where the spreadsheets that survived are the ones the platform never quite covered: the dispatch board, the job tracker, the price book, the service agreement renewal list, the permit log.

You get three things you can use today. A 12-point risk score that tells you whether to act at all. A side-by-side three-year cost comparison for a 25-person process, built from published vendor prices and federal wage data, with every assumption stated. And a seven-step migration plan in the order that keeps trucks rolling, including the step most projects skip.

Key takeaway: Most contractors who should replace a spreadsheet should not start with a custom build. Custom wins on a short list of conditions. The rest of the time a cheaper option is the better first move, and the cost comparison below shows why.

Why spreadsheets fail in ways other software doesn't

Spreadsheets are not bad software. They are extraordinary software, which is exactly the problem: they let one person build a business-critical system in an afternoon, with no review, no tests, no permissions and no record of what happened. Every contractor has one of these. It was built by the dispatcher who left in 2021, and it still decides where the trucks go on Monday.

The research on this is unusually clear and unusually ignored. Raymond Panko's survey of spreadsheet error research concludes that errors are rare on a per-cell basis but highly likely to be present in any large spreadsheet, that they are "extremely difficult to detect and correct", and that the people who build spreadsheets are far more confident in their accuracy than the evidence supports. The last point is the dangerous one. Your team is not careless. They are human, and humans do not notice most of the mistakes they make.

The failure modes are well documented. A 2026 analysis of the European Spreadsheet Risk Interest Group's incident archive examined 121 documented spreadsheet failures from 1995 to 2026 and sorted them into twelve categories. Formula errors, data-entry slips and data-handling mistakes accounted for 71 of them, and recurred across three decades: from a missing minus sign at Fidelity in 1995 to a mistyped date that cost Norway's sovereign wealth fund roughly $92 million in 2024.

The authors' more interesting finding is that a growing share of incidents involve nothing wrong with the arithmetic. Data present in a workbook but invisible to whoever receives it (hidden rows, hidden sheets, pivot-table caches, embedded objects) has caused real harm, including a 2022 UK Ministry of Defence spreadsheet that exposed details of roughly 18,700 Afghan applicants through hidden rows. If you email workbooks to a general contractor, a property manager or a lender, that is your risk too. A price book sent to a customer with your cost column hidden but not deleted is the contractor version of the same mistake.

The limits you will eventually hit

Separately from human error, spreadsheets have hard ceilings. They are generous, which is why people are surprised when they arrive.

Limit Excel Google Sheets
Rows per sheet 1,048,576 Governed by the cell cap
Columns per sheet 16,384 Governed by the cell cap
Total cells per file Limited by available memory 20 million cells or 100 MB
Characters per cell 32,767 Cells over 50,000 characters are dropped on import
People in one shared workbook 256 Not published
Unique cell formats 65,490 Not published

Sources: Microsoft's Excel specifications and limits and Google's Drive file limits, both as of October 2026.

The more useful lesson is what happens near the limits rather than at them. The best-known case is the NHS Test and Trace data loss in England: more than 15,000 positive COVID-19 test results recorded between 25 September and 2 October 2020 were left out of the daily figures, and the error was reported publicly on 5 October. A technical analysis by City, University of London traced it to the legacy XLS format, which stops at 65,536 rows per sheet rather than the modern XLSX limit in the table above. Rows beyond the ceiling were not imported, and nothing checked that what went in matched what came out.

Nothing in that story required anyone to be incompetent. It required a file format with a ceiling, a volume that grew, and no automated reconciliation. A job history spreadsheet that has been appended to since 2017 has exactly those three properties.

Key takeaway: The question is not whether your spreadsheet contains errors. Assume it does. The question is whether an error in it would be caught before it costs you something.

The 12 signs it is time to replace spreadsheets with custom software

Score your spreadsheet honestly. One point for each statement that is true today: not true in a plan, and not true after the cleanup you keep meaning to do.

  1. More than one person edits it in the same week (dispatcher, office manager, owner).
  2. Someone retypes or copy-pastes data into it from the field app, the booking system or accounting.
  3. More than one copy exists, and versions travel by email or text.
  4. A wrong value in it would cost a truck roll, a callback, a missed renewal or an unbilled job.
  5. It has grown past roughly 10,000 rows or 20 tabs.
  6. It contains formulas or macros that only one person understands.
  7. It feeds a number someone outside depends on: a lender, a bonding company, an insurer, a general contractor.
  8. It holds customer addresses, gate and alarm codes, payment details or payroll data.
  9. You cannot tell who changed a given cell, or when.
  10. It needs an approval (a discount, a change order, overtime) that currently happens over text.
  11. It breaks or slows down regularly: crashes, long recalculations, broken links, file size.
  12. Workarounds have grown on top of it: a reconciliation tab, a macro, a "do not touch" sheet, or a second spreadsheet that fixes the first.
A scorecard with four bands for the 12-point spreadsheet test, from zero to three points (leave it alone) to eleven to twelve (replace it)
The 12-point spreadsheet risk score. Give one point per true statement, then read the band.

What your score means:

Score What it means What to do
0–3 A spreadsheet is still the right tool Nothing. Do not start a project.
4–7 It is straining, not failing Harden it, or move it to off-the-shelf or low-code. Custom is premature.
8–10 It is now a system without the controls of one Replace it. Start with low-code unless a blocker below applies.
11–12 It is a liability Replace it, and expect a custom build. Treat the timeline as a risk item.

The five blockers that genuinely require a custom build

A high score tells you to replace the spreadsheet. It does not tell you to commission custom software. Low-code platforms handle forms, tables, approvals, dashboards and common integrations well, and they handle them in weeks. Reach for custom software when at least one of these is true.

  1. You need a field-level history you can hand to a lender, an insurer or a lawyer: who changed what, when, from which value to which value, with a retention period you control.
  2. The workflow must write into another system of record (your accounting package or field platform) through an API a low-code tool cannot reach safely, especially where a failed write must be retried and reconciled rather than silently dropped.
  3. People outside your company will use it: homeowners, property managers, subcontractors, general contractors. Per-seat internal tooling is the wrong shape and often the wrong license. If what they need is a logged-in place to see quotes, approve work and pay invoices, our guide to customer portal development cost prices that build against off-the-shelf portals.
  4. The logic is your differentiator, not an administrative chore. If the spreadsheet encodes how you price, route or schedule better than your competitors, it belongs in software built for you.
  5. Per-seat licensing costs more than building, which happens when most users are occasional or external. Run the arithmetic below before you accept this one.

If none of the five applies, buying or assembling will almost certainly beat building, and you can revisit the decision in a year with real usage data.

What the spreadsheet you already have actually costs

Before comparing options, price the status quo. Most contractors have never done this, which is why the conversation stalls at "but the spreadsheet is free."

Here is the method, with one worked example. Swap in your own numbers.

Step 1: count the hours. Add up time spent on data entry, retyping jobs from the field app, chasing the current version of the board, reconciling disagreements between the spreadsheet and the invoice, fixing broken formulas and assembling reports by hand. Ask the people who do it, for one normal week, not an average week.

Step 2: use a fully loaded hourly rate, not salary. The median wage for bookkeeping, accounting and auditing clerks was $24.36 an hour as of May 2025, which is a reasonable stand-in for an office coordinator. In private industry, wages and salaries accounted for 70.0% of employer compensation costs in June 2026, with benefits making up the remaining 30.0%. That gives a fully loaded rate of $24.36 ÷ 0.70 = $34.80 an hour. For developer time, the median wage for software developers, quality assurance analysts and testers was $64.44 an hour as of May 2025, or $92.06 an hour fully loaded. Both figures are used throughout.

Step 3: multiply. Say a dispatcher, two customer service reps and an office manager each lose six hours a week to the dispatch board, the job tracker and the retyping between them. That is 4 × 6 × 52 = 1,248 hours a year. At $34.80, $43,430 a year in labor sitting inside one set of spreadsheets.

Step 4: add what the errors cost. This is the number people refuse to estimate, so estimate it badly rather than not at all. Count the incidents from the last twelve months: the job booked on two boards, the technician sent to the wrong address, the maintenance agreement that renewed a year late, the completed job nobody invoiced. Attach a cost to each. As an illustration only, with an assumption you should replace with your own billing rate: a technician sent to the wrong site wastes the drive, the lost slot and the callback, and if your loaded cost for a technician and truck is $95 an hour, a three-hour miss is $285 before you count the unhappy customer. If you genuinely cannot find incidents, that is useful information: your score is probably lower than you think.

Step 5: note the costs you cannot price. Jobs not booked because the board was not trusted on a Friday. The dispatcher who cannot take a vacation because only they understand the board. The branch you did not open because onboarding it would have broken the sheet. Write them down and leave them unpriced; they belong in the decision even though they do not belong in the arithmetic.

Key takeaway: Spreadsheets that consume 1,248 staff hours a year cost about $43,000 a year to operate. That is the budget you are comparing against, not zero.

Your four options, priced side by side

Four paths, in ascending order of cost and control. The assumptions below the table are the whole point; change them and the answer changes. The user count of 25 stands for an office team of eight to ten plus technicians who touch the process through the field app.

Option What it is Three-year total, 25 users Annualized
A. Harden the spreadsheet One owner, locked templates, validation, a single authoritative copy, documented formulas $6,200–$16,100 $2,100–$5,400
B. Buy off-the-shelf A commercial product that already does most of the process $22,000–$60,500 $7,300–$20,200
C. Low-code app A database-backed app assembled on a platform $19,000–$67,300 $6,300–$22,400
D. Custom web app Software built for your process $47,800–$138,000 $15,900–$46,000

Assumptions behind each range

A. Harden the spreadsheet. 40–120 hours of a skilled analyst or developer at $92.06 fully loaded, or $3,700–$11,000 one-time, to restructure the file, add data validation, separate inputs from calculations, document the logic and establish one authoritative copy. Plus 2–4 hours a month of owner time at $34.80, or $800–$1,700 a year. This buys you less risk, not less work, and it is the correct answer far more often than vendors will tell you.

B. Buy off-the-shelf. 25 seats at $20–$45 per user per month, the band set by published list prices: Airtable charges $20 per user per month for Team and $45 for Business on annual billing as of October 2026. That is $6,000–$13,500 a year. Add $4,000–$20,000 one-time for configuration, data migration and training. The risk is fit: if the product does 80% of your process, the remaining 20% usually ends up back in a spreadsheet, and you now pay for both. If the spreadsheet is really a sales pipeline or customer list, compare CRM seat prices instead; our custom CRM development cost guide shows the seat count at which building beats renting.

C. Low-code app. Licenses of $5,000–$18,000 over three years. The low end reflects Retool's Team plan at $10 per builder and $5 per internal user per month on annual billing, so three builders and 22 users is $140 a month. The high end reflects Power Apps Premium at $20 per user per month on annual billing, or Retool's Business plan at $50 per builder and $15 per internal user. Watch for capacity add-ons: Dataverse storage beyond the included allowance is $40 per GB per month. Watch for plan gates too: Retool lists audit logs only from the Business plan up, and single sign-on through your identity provider only on its quote-only Enterprise plan, so a security review can move you from the low end of this range to the high end. Our Retool vs custom internal tools break-even model shows where per-seat pricing overtakes a custom build as the user count grows. Add 80–320 hours of build at $92.06, or $7,400–$29,500, and 2–6 hours a month of changes thereafter.

D. Custom web app. 350–900 hours of build for one clearly scoped business process at $92.06 fully loaded, or $32,200–$82,900. Hosting of $30–$150 a month covers this size of internal app comfortably: Amazon Lightsail lists a 2 vCPU, 4 GB instance at $24 a month and a standard managed database from $15 a month, as of October 2026. That is $1,100–$5,400 over three years. Maintenance at 15–20% of build cost a year adds $14,500–$49,700.

Two honest caveats on option D. First, these are labor-derived figures built from federal wage medians, so they represent the cost of the work, not a quote. Agency quotes sit above them because they include recruiting, management, testing, infrastructure and margin. Treat the range as a floor and a sanity check on bids. If you are about to take bids, our guide to how to hire a software partner covers the questions and contract clauses that decide whether you end up with something you can keep running. Second, the range assumes one clearly scoped process. Scope creep is the largest driver of overrun, and it usually arrives as "while we're in there."

Where Fleurant AI's own offers fit, and where they don't

One spreadsheet does not justify replacing your software stack, and we will say so plainly. The Operations Stack is $18,000 to build three modules plus a monthly fee set by company size ($2,000 up to 30 employees), which is $90,000 over three years. For a single dispatch board, that is more than options A to C and inside the custom range only because it also operates the result. It makes sense when the spreadsheets are one symptom of a larger problem: several subscriptions, double entry between them, and a monthly software bill above roughly $1,500, which is the floor below which replacing software does not pay back.

If the spreadsheet is the glue between two tools you want to keep, the Connector is the smaller answer: $7,500 to build and $750 a month, or $34,500 over three years, and the data moves between the tools with no one retyping it. And if you cannot tell which of these you need, the Stack Audit is $2,500, takes one to two weeks and is credited in full against a build started within 90 days. It lists every subscription and spreadsheet, maps where jobs get retyped, and ends with a costed plan and a payback period in months. It is a way to see your own numbers before spending anything on a build, and it is fine to take the document and do nothing.

What about AI app builders?

A fifth path has become realistic in 2026: describing the app to an AI builder and letting it write the code. The tools are good enough that platforms now treat their output as a starting point. In June 2026 Retool added the ability to import React apps built in tools such as Replit, Lovable and Claude Code into its own app builder, in public beta.

That makes the first version of a spreadsheet replacement cheaper and faster. It does not change what the first version needs to be right about. An AI builder will happily turn your spreadsheet's tabs into screens, which is the "web-shaped spreadsheet" failure described below, and it cannot know which of your formulas encode rules nobody has written down, such as the one that rounds a travel charge or exempts a long-standing customer. Treat generated code as a faster way through step 5 of the migration plan, not a way around steps 1 to 4, and price it as a custom build for maintenance purposes: someone still has to host, secure and change the result.

How to decide: the break-even you can run on your own numbers

The cost table is not a decision. This is: how many hours a year must your team get back for each option to pay for itself?

Divide the annualized cost by your fully loaded hourly rate. Using $34.80 an hour:

Option Annualized cost Hours a year to break even Hours a week, whole team
A. Harden the spreadsheet $2,100–$5,400 59–154 1.1–3.0
B. Buy off-the-shelf $7,300–$20,200 211–580 4.1–11.1
C. Low-code app $6,300–$22,400 182–645 3.5–12.4
D. Custom web app $15,900–$46,000 458–1,321 8.8–25.4

Read the right-hand column against the worked example. Four people spending six hours a week each were burning 24 hours a week in total. On labor alone:

  • Hardening pays back almost immediately. It needs 1.1–3.0 hours a week back out of 24. Even a modest reduction clears it.
  • Buying or low-code pays back comfortably. They need 3.5–12.4 hours a week back. Removing the retyping between the field app and the board usually gets there.
  • Custom does not pay back on labor alone at this size. At the top of the range it needs 25.4 hours a week back from a process that only consumes 24.

That is the most important finding in this article, and it is the opposite of what most "replace your spreadsheets" content concludes. A custom build is rarely justified by office time savings in a process this size. It is justified when the spreadsheet sits in the revenue path: when errors send trucks to the wrong place or leave jobs unbilled, when a lender or insurer will ask for records you cannot produce, when the logic is how you beat competitors, or when the people using it do not work for you.

If your justification is labor savings only, you are probably looking at option A, B or C. If your justification is revenue, risk or reach, option D can be correct at a cost that labor savings would never support, and you should say so in the business case rather than inflating the efficiency numbers. The same method for a larger project is in our guide to what building and running office software really costs.

A seven-step migration plan that doesn't stop the trucks

The order matters more than the tooling. Most failed migrations did the right steps in the wrong sequence.

Step 1: capture the process that actually happens

Sit with the dispatcher and the office team and watch a full cycle, from the call coming in to the invoice going out. Document what really happens, including every exception, workaround and side conversation. You will find steps nobody knew existed and rules nobody wrote down. The documented process and the actual one are never the same, and the actual one is what you must replace.

Step 2: extract the rules, then judge them

Go through the formulas and write the business rules in plain English: "emergency calls after 6 p.m. carry a surcharge," "agreement customers get a priority slot." Then review each one. Some will be wrong. Some will be artifacts of a spreadsheet limitation. Some will contradict each other, and somebody has to decide which wins. Do this before any build, because this step generates decisions, and decisions take calendar time.

Step 3: measure how dirty the data is, then clean it

Count duplicate customers, blank required fields, phone numbers stored as text, addresses spelled four ways, equipment records that do not match the invoice. Report the counts. Then clean the data in the spreadsheet, where your team already knows how, rather than during migration, where every anomaly becomes a defect ticket. Migrating dirty data is the fastest way to make the new system look worse than the old one on day one.

Step 4: model the data, not the sheet

This is the step that separates software from a web-shaped spreadsheet. Tabs become tables. Repeated columns become rows. Relationships become explicit: a customer has many properties, a property has many pieces of equipment, a job belongs to one property and one piece of equipment, an invoice references the job. If the new system has a grid that looks exactly like the old spreadsheet, the modeling step was skipped, and every later problem traces back here.

Step 5: build the thinnest version that replaces one complete loop

Not one screen. One loop, end to end: the job is entered, dispatched, completed, invoiced and visible in the report someone uses. A narrow slice that works beats a broad slice that nearly works, because only a complete loop tells you whether the model from step 4 is right. Build the office side first. Technicians are the most change-resistant users in the business and the most expensive to disrupt, so the field screens come last.

Step 6: run both side by side and reconcile

Run the spreadsheet and the new system in parallel, with the same inputs, and reconcile the outputs exactly. Investigate every difference: some will be bugs, and some will be errors in the spreadsheet you have been living with for years. For a weekly process like dispatch, two full weeks is the floor; for a monthly one like service agreement billing, two complete cycles, because the first finds the bugs and the second proves the fixes. This is the step most often cut when a project runs late, and cutting it is how you discover in production that the two systems disagree and nobody knows which is right. Do not schedule the cutover for your peak weeks. An HVAC company should not switch dispatch in the first heat wave of July.

Step 7: retire the spreadsheet deliberately

Set the file to read-only, archive a dated copy, remove edit access, and tell people where the process lives now. A spreadsheet that remains editable will remain in use, and you will end up maintaining two systems that disagree. Then cancel any subscription the new system made redundant, because a tool nobody uses but everyone still pays for is the most common leftover of a finished project. Give whoever does analysis a clean export so Excel stays an analysis tool and never again the system of record.

Key takeaway: Steps 1 through 4 take longer than step 5 and generate more value. If a vendor's plan starts at step 5, they are quoting for a build and leaving the hard work with you.

What goes wrong, and how to avoid it

Rebuilding the spreadsheet as a web page. The most common failure. Users ask for the grid they know, the team obliges, and you pay custom software prices for a worse spreadsheet with fewer features. The fix is to insist on step 4 and accept that the new screens should look different because the data model is different.

No named internal owner. Software with no owner decays into the thing people work around, and then somebody builds a spreadsheet to cover the gap. Name the owner before the build starts and give them real hours for it. In most contractors that is the office manager, not the owner and not whoever is best with computers.

Reports specified last. Somebody outside the team depends on a report built from the spreadsheet (your bookkeeper, your lender, the owner's Monday morning view), nobody asks them what they need, and the project ends in a scramble. Ask early who consumes the outputs.

Permissions as an afterthought. "Everyone can see everything" is easy to build and hard to unwind later, especially with payroll, margins and pricing in the system. Decide who sees what during step 4. A technician does not need the cost column of the price book.

No export. Analysts will keep using spreadsheets for analysis, and they are right to. If the new system cannot export cleanly, they will export messily, and the shadow spreadsheet returns within a quarter.

Pointing AI at a messy workbook. A language model reading an inconsistent dispatch history produces confident answers drawn from inconsistent data. Fix the data and the process first, then add automation on top of a clean system, which is the order our write-up of what to automate first argues for.

When to leave the spreadsheet alone

Honest counsel, because this is where the money is usually wasted.

  • One person uses it occasionally. A personal scratchpad is not a system.
  • The work is modeling and what-if analysis. What a 4% price increase does to margin by trade is exactly what spreadsheets are for.
  • The process is changing in the next six months. Build after it settles, not during, or you will specify the wrong thing. If you are about to add a second branch or a new trade, wait.
  • Volume is low. A process that runs a few dozen times a month rarely justifies more than hardening.
  • Nobody internal can own it. Without an owner, the new system becomes abandoned software, which is worse than a spreadsheet because it is harder to change.

When the spreadsheet holds payroll, payment and customer data

If the spreadsheet holds payroll, card or bank details, or customer access information such as gate and alarm codes, the decision stops being a productivity calculation. A shared workbook has file-level sharing, not per-record permissions. Version history is not an audit trail you can produce for one record on demand, and a file that anyone with the link can overwrite does not protect records from accidental change.

Two practical consequences. First, move payment and bank details out of spreadsheets whatever else you decide; card data belongs with your payment processor and payroll belongs in your payroll system, both of which a replacement should integrate with and never take over. Second, the migration gets a short access review: who can see what, who can export it, and what happens to the old copies. This is general operating guidance, not legal advice; confirm your obligations around customer and employee data with your counsel or insurer.

What the new system costs to run

A build is a one-time number. Running the result is forever, and that is where budgets get surprised.

For an internal app replacing one spreadsheet-driven process, expect four ongoing lines.

  • Hosting and database. $30–$150 a month covers this size comfortably, using the Lightsail list prices above. Costs rise with data volume and backup retention, not usually with user count at this scale. Job photos are the exception: they only accumulate.
  • Platform licenses, if you chose low-code. Per-seat fees keep accruing whether the app changes or not, and they scale with headcount, which is the one cost line a custom build does not have.
  • Maintenance and small changes. Budget 15–20% of the build cost a year. Below 15%, the app stops matching the business. Above 20%, you are effectively still building.
  • Someone's attention. The owner from step 1 needs real hours every month. Unowned software is the most expensive kind, and it is how today's new app becomes tomorrow's legacy system; our guide to legacy application modernization cost shows what that costs to unwind.

Two things reliably drive run costs higher than planned: integrations that break when the other system changes, and reporting that grows faster than the app. If the app will be the source of truth for other people's numbers, scope reporting as a feature with a budget.

Putting it together

The decision is simpler than the vendor conversation makes it sound.

  1. Score the spreadsheet against the 12 statements. Below four, stop: you do not have a software problem.
  2. Price the status quo in fully loaded hours, plus whatever last year's errors cost.
  3. Check the five blockers. If none applies, you are choosing between hardening, buying and low-code, in that order of cost.
  4. Run the break-even. Divide annualized cost by your loaded hourly rate and ask whether the team can realistically give back that many hours a week.
  5. If a blocker does apply, make the case on revenue, risk or reach rather than efficiency, and expect the custom range above to be a floor rather than a quote.
  6. Follow the seven steps in order, and protect step 6. Two weeks of running both side by side is not padding.

The pattern worth remembering: the spreadsheet is almost never the problem. The problem is that a process outgrew the tool, and the honest question is which of four tools it has grown into. Most contractors who ask about replacing spreadsheets need a smaller answer than they expected, and the ones who genuinely need software built for how their business runs can usually name a blocker in thirty seconds.

If you want a second opinion on your own score, bring the spreadsheets and last year's error list and talk to a specialist. A specialist replies within one business day, and it will usually tell you which of the options fits. You can also browse our other guides on software costs or see what we build if you are earlier in the process.

If you'd like one clear, practical take on the software that runs your business each month, subscribe to the Fleurant AI Briefing: one email a month, unsubscribe any time.

Frequently asked questions

When should a contractor replace spreadsheets with custom software?

When the spreadsheet runs a process rather than analyzing one: several people edit the dispatch board or job tracker, data is retyped from the field app or accounting, a wrong value costs a truck roll or an unbilled job, and nobody can say who changed what. Score it with the 12-point test in this article. Below four points, leave it alone. Above eight, replace it, but start with a cheaper option unless one of the five blockers applies.

How much does it cost to replace a spreadsheet with custom software?

For one business process used by about 25 people, the three-year totals in this article work out to roughly $6,200–$16,100 to harden the spreadsheet, $22,000–$60,500 for off-the-shelf software, $19,000–$67,300 for a low-code app, and $47,800–$138,000 for a custom web app. These are labor-derived figures using BLS wage data; vendor quotes sit above them because they include overhead and margin.

Is low-code good enough, or do I need a custom app?

Low-code is good enough for most spreadsheet replacements: forms, tables, approvals, dashboards and simple integrations. Five things push you toward custom: a field-level history you can hand an insurer or a lender, writes into your accounting or field software that a low-code platform cannot reach safely, customers or subcontractors as users, logic that is your actual edge, and per-seat licensing that costs more than building because most users are occasional.

How long does a spreadsheet-to-software migration take?

Plan it in phases rather than to a date. Extracting the rules and cleaning the data usually takes longer than the build. The hard floor is set by running both side by side: for a weekly process like dispatch, at least two full weeks of overlap, and for a monthly one like service agreement billing, two full cycles. Never cut over in the middle of your peak season.

What are the warning signs that a spreadsheet has become a risk?

Multiple copies in circulation, retyping between the field app and the spreadsheet, formulas only one person understands, no record of who moved a job or changed a price, approvals happening over text, and workarounds built on top of workarounds. Hidden rows and stale pivot caches are a specific disclosure risk: the EuSpRIG incident corpus records cases where invisible data in a shared workbook caused the harm, not a wrong formula.

Can my office keep using Excel after we replace the spreadsheet?

Yes, and you should plan for it. Spreadsheets are genuinely better than any software for modeling, what-if analysis and one-off questions such as what a price increase does to margin. The goal is to move the process of record (entry, approval, status, history) into software, then give whoever does the analysis a clean export so the spreadsheet never becomes the system of record again.

What usually goes wrong in these projects?

Four things, in order of frequency: rebuilding the spreadsheet grid as a web page instead of modeling the data properly, migrating dirty data and inheriting every old inconsistency, launching without a named internal owner, and discovering at the end that nobody specified the reports. The migration plan in this article puts each of those before the build, not after it.

Sources

  1. Excel specifications and limits, Microsoft
  2. Files you can store in Google Drive, Google
  3. Anatomy of a Spreadsheet Failure: Analysing the EuSpRIG Horror Story Corpus, Simon Thorne and Angela Collins, arXiv
  4. What We Don't Know About Spreadsheet Errors Today: The Facts, Why We Don't Believe Them, and What We Need to Do, Raymond R. Panko, arXiv
  5. What really caused the Excel error in the NHS Test and Trace COVID-19 system?, City, University of London
  6. Bookkeeping, Accounting, and Auditing Clerks: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
  7. Software Developers, Quality Assurance Analysts, and Testers: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
  8. Employer Costs for Employee Compensation, June 2026, U.S. Bureau of Labor Statistics
  9. Power Apps pricing, Microsoft
  10. Airtable pricing, Airtable
  11. Retool pricing, Retool
  12. React app import (changelog, June 3, 2026), Retool Docs
  13. Amazon Lightsail pricing, Amazon Web Services

Free, no-obligation consultation

Have a question about replacing spreadsheets with software?

Tell us what you're working on or what you'd like to know. A specialist will get back to you with practical next steps, whether or not we end up working together.

  1. 1Send your question or project details (takes 2 minutes)
  2. 2A specialist reviews it and replies within 1 business day
  3. 3Get clear, practical next steps, free