Articles · Hiring

2027-02-18 12 min EN / FR

Reading a quote: what's missing from most of them

Three quotes for the same project can look similar on the last line and mean three different jobs. The price is rarely the useful comparison. What is included, what is assumed, and what happens after delivery matter more.

A quote is a proposal to do a defined piece of work under defined conditions. If the definition is thin, the number at the bottom is a guess dressed as certainty. Good reading starts before you look at the total.

If your brief was vague, every provider invents a different project. Fix that first with a clear brief (see how to brief a developer so you get a useful quote), then apply the steps below to each response.

Step 1: Match the quote to your brief

Print or open your brief next to the quote. For each requirement you wrote, mark one of three states:

  • Covered: the quote names it explicitly
  • Assumed: it might be implied, but it is not written
  • Missing: it is not there at all

Assumed items become change requests later. Ask for them in writing before you compare prices. A cheap quote that skips half your list is not cheap.

Step 2: Spot what is usually missing

Most incomplete quotes share the same gaps. Check for each of these in plain language, not marketing phrases:

  • Out of scope: what is explicitly not included (content migration, design, third-party fees, training)
  • Environments: staging, production, how deployments work
  • Hosting and domains: who creates accounts, who pays, who stays admin
  • Data migration: volume, cleanup, who validates the result
  • Integrations: which systems, whose APIs, what happens if a third party is late
  • Documentation: what is delivered (runbook, admin guide, architecture notes)
  • Handover and ownership: code in your org, credentials in your vault, an exit plan
  • Warranty and bug window: how long after go-live fixes are included
  • Maintenance: what happens after the project ends, at what rate
  • Change process: how new requests are estimated and approved

If ownership and handover are vague, treat that as a risk equal to a large budget overrun. Contract ideas that protect you are listed in contract clauses to demand from any tech provider.

Step 3: Understand the pricing model

The same headline amount can sit on very different commercial models:

  • Fixed price: a set fee for a set scope. Works when the brief is clear and change will be rare. Weak when requirements will evolve weekly.
  • Time and materials: you pay for hours at stated rates, often with a ceiling or phases. Transparent when the work is exploratory. Dangerous when there is no weekly burn report and no decision gate.
  • Hybrid: discovery or design at time and materials, build at fixed price once the scope is frozen. Often the honest middle path.
  • Retainer or package: a monthly block of hours or a productised offer. Fine for ongoing work, poor as a substitute for a project quote with deliverables.

Ask which model applies, what triggers a new estimate, and who can approve overruns. A fixed price with undefined scope is not fixed. It is a dispute waiting for a signature.

Need a second reading of a quote?

We can review scope, ownership, and handover gaps before you commit, or help you turn a brief into comparable proposals.

Send a quote to review Custom solutions

Step 4: Check the numbers, not only the total

Look past the bottom line:

  • Assumptions: number of pages, users, languages, environments, content readiness, third-party licences already paid
  • Unit rates: day rate or hourly rate by role (senior, junior, project lead)
  • Phases and milestones: amounts tied to delivery, not only calendar dates
  • Payment schedule: deposit, midpoints, final payment after acceptance criteria
  • Excluded costs: hosting, licences, fonts, SMS, payment fees, stock photos, travel
  • Validity: how long the quote holds, and what happens if your start date slips
  • Currency and taxes: VAT, who invoices which entity

If two quotes differ by a lot, the cause is almost always a different assumption list, not a secret discount. Ask each provider to state the same assumptions in the same format.

Step 5: Evaluate the provider

Price without trust and fit is noise. For each candidate, note:

  • Do they restate your problem in their own words, or only paste your bullet list?
  • Do they name risks and dependencies, or promise a smooth path with no caveats?
  • Who will actually do the work (named roles, not only a sales contact)?
  • Can they show comparable deliveries, with references you can call?
  • How do they handle accounts, code ownership, and documentation by default?
  • How do they communicate progress (weekly written update, demo, ticket board)?

A clear, slightly higher quote from someone who writes ownership into the offer often costs less than a low bid that leaves you locked to their tools and logins.

Step 6: Compare side by side

Copy the grid below into a spreadsheet. Fill one column per provider. Prefer short answers: yes, no, partial, or a number. Empty cells are answers too.

Criterion Provider A Provider B Provider C
Scope matches brief (covered / assumed / missing count)
Out of scope listed
Pricing model (fixed / T&M / hybrid)
Total fee (ex. VAT)
Assumptions written
Environments and deployment included
Accounts in your name
Source code under your organisation
Documentation delivered
Exit / handover plan
Bug-fix window after go-live
Change process defined
Named team / roles
Start date and duration
Risks called out

Score the grid against your priorities. Do not average every row. Ownership and scope clarity usually outweigh a small price difference.

Questions to ask before signing

  • What does "done" mean for each milestone, in one sentence each?
  • Who accepts the delivery on our side, and with what criteria?
  • Where will the code, designs, and credentials live on day one?
  • What is excluded that we might wrongly assume is included?
  • How are change requests estimated and approved?
  • What happens if a dependency we control is late (content, decisions, access)?
  • What happens if a third-party API or licence blocks progress?
  • Who supports the system in the first 30 days after go-live?
  • What is the notice period and handover if we stop mid-project?

Write the answers into the quote or a short annex. Verbal clarifications disappear when people change.

Red flags

  • A one-page price with no scope, or a scope that only restates your email
  • "Everything included" with no out-of-scope list
  • Accounts, domains, or repositories created under the provider's name by default
  • Refusal to put ownership, documentation, or handover in writing
  • Large deposit with no milestones, or final payment before you can test
  • Pressure to sign this week because "the slot will disappear"
  • No named technical contact, only a sales intermediary
  • Hostility when you ask for assumptions or references

When quotes are far apart

If one quote is half the price of another, do not celebrate yet. Align the briefs:

  • Ask each provider to quote the same scope list, same out-of-scope list, and same assumptions.
  • Check whether the cheap offer omits staging, migration, documentation, or post-launch fixes.
  • Check whether the expensive offer includes discovery, design systems, or long warranty you did not ask for.
  • Ask for a phase split: discovery first, then a fixed build once the scope is real.

After alignment, a remaining gap often means different quality bars or different risk buffers. That is a choice you can make consciously. Before alignment, the gap is mostly noise.

Common mistakes

  • Comparing totals without comparing scope
  • Choosing the lowest bid to "save money", then paying twice for a rebuild
  • Ignoring ownership because "we will sort that later"
  • Accepting a vague fixed price without a change process
  • Skipping acceptance criteria, then arguing about whether something is a bug or a feature
  • Signing under calendar pressure instead of under clarity
  • Forgetting internal cost: your time for decisions, content, and testing

Checklist

  • Brief and quote lined up, with covered / assumed / missing marked
  • Out of scope, assumptions, and change process are written
  • Pricing model understood (fixed, T&M, or hybrid)
  • Numbers checked: rates, milestones, excluded costs, validity
  • Accounts, code, and credentials stay in our name
  • Documentation and handover / exit plan are deliverables
  • Comparison grid filled for every serious candidate
  • Questions answered in writing before signature

Related

Choosing between quotes?

Share the proposals you have. We can help you compare scope, ownership, and risk before you sign.

Start a conversation All articles