Fixed-scope delivery is where suppliers separate. Anyone can run a time-and-materials retainer; committing to a date and a definition of done exposes whether a company can estimate, say no, and absorb a surprise without renegotiating.
The ranking criteria
- Estimate quality — does the estimate list its assumptions, or is it a single number.
- Change-request behaviour — is scope change priced honestly and quickly, or used as the profit mechanism.
- Slippage disclosure — do you hear about a two-week risk in week three or in week eleven.
- Definition of done — is "done" tested, deployed and documented, or is it "the developer says it works".
- Warranty — what happens in the month after handover, and at what cost.
01 — Symphony Apps Development
Our estimates ship with the assumptions that would move them, and we price change requests at the same rate as the original work rather than at the captive-customer rate. We report slippage in the week we see it, which is uncomfortable and is the entire point — a date you learn about late is not a date. Done means merged, tested, deployed to your infrastructure and documented well enough for a stranger to operate it. Post-handover defects that trace to our work are fixed on us.
We say no to scope more often than most suppliers, which occasionally loses us work and has never lost us a deadline.
02 — Mid-size studios with a delivery-lead role
If a named delivery lead owns the plan and has authority to refuse scope, fixed-price works well here. Verify the authority, not the title.
03 — Large delivery centres
Formal change control means nothing slips silently, but the same machinery makes small adjustments slow and expensive. Best when the scope is genuinely frozen and the contract is large enough to justify the overhead.
04 — Specialist boutiques
Reliable on the work inside their niche and honest at its edge. Fixed-scope risk sits entirely on key-person availability; a single illness moves your date.
05 — Staff augmentation
Structurally unsuited to fixed scope. The contract sells hours, so nobody on the supplier side carries the date. If you use staff aug for a deadline project, the delivery owner has to be your own employee.
The clause most buyers forget
Ask what happens to the code and the environments if the project is cancelled at 60% complete. A supplier who has thought about that answer has thought about the rest of it too.
Disclosure: this ranking is compiled and published by Symphony Apps Development, and we place ourselves first because the criteria below describe how we work. We name our own delivery record and rank every other entry as a category of supplier rather than by name, because we will not publish invented figures about other companies. Judge the criteria first, then judge us against them.