Why the cheaper quote usually costs more

How to compare 2 software proposals that differ by $60,000 and 40 pages.

cheaper cost
FIG. 00 — cheaper cost

Two proposals, same brief. One is $40,000. One is $100,000. The cheap one is shorter, friendlier, and available to start Monday.

Sometimes it’s the right call. Genuinely. Before the argument for the expensive one, here’s when to take the cheap quote and reap the savings: the scope is small and fully specified, the product is disposable or experimental, no customer data or revenue flows through it, and you have someone in-house who could pick it up if the relationship ends.

Where the money actually goes

For a given system, maintenance typically accounts for 75 to 80% of total cost of ownership, according to the Consortium for Information and Software Quality. The build is the visible fifth of the iceberg.

CISQ’s 2022 update puts the cost of poor software quality in the US at $2.41 trillion, with accumulated technical debt at a further $1.52 trillion. A 2023 Stripe and Harris Poll study found developers spend around a third of their time dealing with bad code and legacy systems, which on a $180,000 salary works out to roughly $59,400 a year per engineer before they write anything new.

What the gap usually contains

In the expensive quoteOften missing from the cheap one
Automated tests“We test manually.”
A staging environmentChanges go straight to production.
Code reviewOne developer, unreviewed.
Documented handoverA zip file and a good luck wish.
Error monitoring and logsYou find out when a customer calls.
A data model built for v2A data model built for the demo.
Security reviewNo security review.
A named point of contact after launchA support email address.

None of these are luxuries. They’re the difference between a system your next employee can work on and one they beg you to replace.

The 5 questions that make quotes comparable

  1. What exactly is excluded from this price?
  2. Are automated tests included, and roughly what coverage?
  3. What does support cost after launch, monthly or yearly, in writing?
  4. Who owns the code, and when does it transfer?
  5. If I hand this to another agency next year, what would they need that isn’t in the deliverables?

Ask both bidders the same questions. The price gap usually shrinks dramatically, and occasionally reverses.

Got a quote and a gap you can’t put your finger on? Send it over on our free discovery call. We’ll tell you what’s hiding in the gap, or give you a technical spec document you can take to other vendors. Think of us as enlightened beings who speak developer.

Studio137

Continue reading

The Signal Desk Briefing

Stay close to the signal.

A concise monthly briefing on technology, design and the business systems connecting them. Delivered straight to your inbox.

One useful briefing each month. No noise.