Imagine you ask two software companies to build the same app. Company A quotes $5,000. Company B quotes $8,000. Most people lean toward A, and that’s a reasonable reflex: $3,000 is $3,000.

The trouble is that a quote only tells you what the company plans to charge on day one. It says very little about what the project will cost once the app has launched, been fixed, and been changed a few times. In the example below (the numbers are made up to show the pattern, not taken from a real client), the cheaper quote ends up as the more expensive project.

 Company ACompany B
Quote$5,000$8,000
Work left out of the quote+ $2,000$0
Fixes after launch+ $1,500+ $500
Costly changes later+ $1,000$0
Help after launch+ $1,000Included
Real total$10,500$8,500

Where did Company A’s extra $5,500 come from? Four places, and you’ll find them in most software projects.

1. Some work isn’t in the quote

A low quote often gets low by leaving things out. Testing, launch, connecting your app to other systems (your payment tool or accounting software, say), and any change after the first agreement can all be listed as “extra.” That isn’t necessarily dishonest. It’s just easy to miss when you’re comparing two numbers side by side.

In our example, Company A left out $2,000 of work. You find out when the first invoice for extras arrives.

Ask your vendor: What is not included in this price? Ask it out loud, and ask for the answer in writing.

2. Rushed work makes every change cost more

Software built in a hurry works on the day you receive it. Inside, though, it’s messy, and nobody wrote down how the pieces fit together. Developers call the result technical debt: extra work later because of shortcuts taken today.

Picture a house where the electrician skipped the labels in the fuse box. The lights work fine. The next time you want another socket, the electrician has to trace every wire first, and you pay for the tracing.

A small change that takes one day on a tidy project can take a week on a messy one. That’s where the $1,000 for costly changes comes from.

Ask your vendor: How will you write down how the software works, so someone else can update it later?

3. Mistakes found after launch cost more to fix

Every piece of software has mistakes. What matters is who finds them, and when. A mistake found before launch gets fixed, tested again, and nobody outside the team ever hears about it. A mistake found after launch means your customers hit it first. Then someone has to work out what went wrong, fix it, and launch again, sometimes while your service is down.

That’s the gap between $1,500 in Company A’s column and $500 in Company B’s. Testing costs money up front, which is exactly why a low quote tends to skimp on it.

Ask your vendor: What testing is included before launch?

4. The work doesn’t end at launch

Launch day feels like the finish line. It’s closer to the starting gun. Software needs security fixes, updates when other tools change, and new features as your business grows. If nobody is responsible for that, you end up paying whoever happens to be available when something breaks, usually at short notice.

Company A charged $1,000 for help after launch. Company B included it.

Ask your vendor: Who helps us after launch, and who do we contact if something goes wrong?

A lower quote can still be the right choice

This isn’t an argument for always picking the higher number. A lower quote is a good deal when it covers the same work: same scope, same testing, same support. The mistake is comparing two prices without checking that they buy the same thing.

Before you choose, ask every vendor these four questions:

  • What is not included in the price?
  • How easy will it be to update later?
  • What testing happens before launch?
  • Who helps after launch, and how do we reach them?

If a vendor hesitates on any of them, that tells you something. If a vendor answers all four clearly and in writing, the quote finally becomes a number you can compare.

Before you sign

Next time you have two quotes on your desk, put the same four questions to both companies and write the answers next to the prices. Compare the total, not the first line.

If you’d like a second opinion on a quote you’ve received, we’re happy to take a look. You can reach us at sum-ind.com.

SUM AI Assistant
Online