When Founders Hire Cheap, Here’s What Happens (We’ve Rebuilt a Lot of These)

4–6 minutes read
When Founders Hire Cheap, Here's What Happens (We've Rebuilt a Lot of These)

TL;DR

  • A low quote is not a discount on the same work. It is a smaller amount of work, and the difference is usually in what was quietly left out.
  • The cost does not disappear. It reappears as your time, as rework, and as the jobs nobody was ever paid to do.
  • But paying more does not automatically fix it: the largest, best-funded sites on the web fail the same basic checks.
  • Buy less scope rather than cheaper hours, and get the exclusions in writing before you sign.

Every founder hires cheap at some point, usually for good reasons. The money is not there yet, the job seems simple, and someone has quoted a number that makes the decision feel obvious. This is not an argument that you should always spend more. It is an account of what actually changes when the number goes down, so the decision is made with the trade visible rather than hidden.

A lower price is a smaller job, not the same job cheaper

Professional work is sold in days. Whatever the quote says, somebody has estimated how many days the job will take and multiplied by a rate. When the price halves, one of two things has happened: the rate is lower, or the days are fewer. Usually it is the days, and the days come out of the parts of the work that are least visible on delivery day.

Usually in the higher quote

  • Discovery: time spent understanding the business first
  • Writing, or at least editing, the actual words
  • Testing on real devices and real connections
  • An accessibility and performance pass
  • Revisions after you have lived with it
  • Handover, documentation and account ownership

Usually out of the lower one

  • Straight to build from whatever brief you gave
  • Your copy, pasted in as supplied
  • Tested in one browser on one laptop
  • Neither, unless something visibly breaks
  • One round, then it is a change request
  • A login emailed over, if you ask

None of that is dishonest. A cheaper supplier is often being perfectly straight about a narrower job. The failure is nearly always one of assumption: the founder believed they were buying the left-hand column at the right-hand price, and nobody said otherwise because nobody was asked.

Where the cost comes back

Money removed from a project does not vanish. It moves, and it usually moves onto the founder, who is the most expensive person in the business and the one with the least spare capacity.

  • Your hours writing the copy, sourcing the photos, chasing the amends, doing the testing nobody was paid to do
  • Rework a second supplier repeating discovery because the first left no record of the decisions
  • Delay the launch slipping by weeks while somebody who is not a designer redraws a page
  • Fragility nobody knows how it was built, so every later change is a small excavation
  • Lock-in accounts, domains and licences in a supplier's name rather than yours

The last one is worth pausing on because it converts a small saving into a permanent tax. If the hosting, the domain, the analytics and the code repository are not in the company’s name, the cheap project has bought you a landlord. Ask for ownership at the start; asking later is a negotiation.

The awkward part: expensive does not mean good

The tidy version of this argument is that quality costs money and cheap work is bad work. The evidence does not support the second half of that, and pretending otherwise would be exactly the kind of self-serving agency reasoning worth distrusting.

Consider the most basic quality check there is. The WebAIM Million survey found detected WCAG 2 accessibility failures on 95.9% of the top one million home pages in 2026, averaging 56.1 errors per page, and the figure had risen from 94.8% the year before. Those are the largest and best-funded sites on the web, built by agencies charging far more than any founder is weighing up here. Automated tools only catch part of the problem, so the true position is worse.

If nearly every large site fails the basic checks, price is clearly not the variable doing the work.

What separates good work from bad is not the invoice. It is whether the job was scoped to include the unglamorous parts, whether somebody is accountable when they are missing, and whether you knew what to ask for. A careful freelancer working to a tight brief will beat an expensive agency working to none.

What actually gets skipped, and why it matters

Two things fall out of nearly every compressed build, and both have measurable consequences.

The first is performance. In Milliseconds Make Millions, research commissioned by Google and carried out by 55 and Deloitte across 37 brands, a 0.1 second improvement in mobile site speed moved 3.2% more shoppers from a product listing to a product page and 9.1% more from that page to the basket, with retail spend up 9.2% and travel bookings up 10%. Those are retail and travel figures rather than a universal rule, but the size of the intervention is the point: a tenth of a second is nothing, and a build with no performance pass routinely gives away several times that in unoptimised images and unused scripts.

The second is the writing. Copy is the first thing cut from a quote and the last thing a founder has time to do properly, so the site launches with placeholder-quality text nobody edited. That matters more than it looks: analysing 45,237 page views, Jakob Nielsen of the Nielsen Norman Group concluded in 2008 that users have time to read at most 28% of the words on an average visit, with 20% the likelier figure. If only a fifth of your words are read, those words had better be the right ones. Unedited copy is not a small omission; it is most of what the visitor experiences.

When cheap is genuinely the right call

Cutting cost is not a character flaw, and there are situations where the cheap option is straightforwardly correct.

Buy cheap when

  • You are testing whether anyone wants the thing at all
  • The site is a placeholder while you sell by phone
  • The job is genuinely small and clearly specified
  • You can afford to throw it away in a year

Do not when

  • The site is your main route to enquiries
  • You are about to spend money driving traffic to it
  • It handles payments, bookings or customer data
  • Rebuilding it would mean rebuilding the business's systems too

The distinction is not the amount of money. It is whether the thing you are buying is disposable. Buy disposable deliberately, and label it as such, so that nobody is surprised in eighteen months when it needs replacing rather than extending.

How to buy well on a small budget

The best protection is not a bigger budget. It is a better conversation before anyone starts, and five questions do most of the work.

  1. What is excluded?

    Ask directly for the list of things not in the price: copywriting, photography, testing, accessibility, training, support. A good supplier answers immediately; a vague answer is the answer.

  2. Who actually does the work?

    The person in the meeting is not always the person building it. Ask who, and whether you will be able to speak to them.

  3. What do I own at the end?

    Domain, hosting, code, analytics, image licences — all in the company's name, confirmed in writing before the first invoice.

  4. What happens when something breaks?

    Response time, cost, and who is on the other end. "We'll sort it" is not a support arrangement.

  5. Can we do less, rather than cheaper?

    Three excellent pages beat twelve mediocre ones. Cutting scope keeps the standard; cutting rate usually cuts the standard instead.

That last question is the one worth remembering if you remember nothing else. Founders under budget pressure almost always negotiate on price when they should be negotiating on scope. Ask for a smaller, complete job rather than a large, hollow one, and most of what this article describes simply does not happen to you.

Good to know

FAQs

Is hiring cheap always a mistake?

No. If you are testing demand, need a placeholder, or the job is small and clearly specified, cheap is often the right call. The mistake is buying something disposable while believing it is permanent.

Why do cheap projects run over?

Because the work removed from the quote does not disappear — it moves to whoever is left, usually the founder. Copywriting, image sourcing, testing and chasing amends are the common culprits.

Does paying more guarantee better work?

No. Almost every large, well-funded site fails basic automated accessibility checks, so budget plainly is not the deciding variable. Defined scope and clear accountability are.

What should I always insist on, however small the budget?

Ownership of the domain, hosting, code and analytics accounts in the company’s name, and a written list of what the price excludes.

Should I cut scope or cut price?

Cut scope. Three complete pages will serve you better than twelve half-finished ones, and reducing the rate usually reduces the standard rather than the cost.

Next step

Inherited a website nobody can explain?

We pick up half-finished builds and rebuild sites properly for businesses across Brighton and London, with the scope written down first.

Request a quotation

I’m interested in…