A quote only protects you if everyone agrees what it covers. Here is what a good written quote should spell out.
Scope
What will be built, in plain English. Screens, features and who uses them. “A website” is not a scope. “Five pages, a contact form and a content editor” is.
Assumptions
The things the price depends on: when content arrives, how many user roles there are, which payment provider is used. If one of them changes, the quote should be revisited, openly and before the work.
Milestones
The job split into stages, each with a date and a price. You review each one before you pay for it.
What is not included
The most useful section, and the one most often missing. Content writing? Photography? Hosting? Third-party subscriptions? If it is not listed, assume it is not included and ask.
Who owns what
You should own the code, the domain and the data once you have paid. If the developer keeps anything, such as a reusable library, the quote should say so and give you a licence to use it.
How changes work
Small tweaks inside the scope should be free. Anything bigger should be quoted in writing before work starts, so there are no surprise invoices.
How and when you pay
The deposit, which milestones trigger which payment, how many days you have to pay, and what methods are accepted.
Checklist
- Scope in plain English
- An assumptions list
- Milestones with dates and prices
- A “not included” list
- Ownership of code, domain and data
- A written change process
- Payment terms
See how we work for how our own quotes and milestones are set out, and our pricing for starting prices. For what drives the number, see how much a custom web app costs.
Wondering how the payments should be split? Read how milestone payments protect both sides. Not sure what to put in the scope? See what a scoping phase is.
Deciding between an agreed price and hourly billing? Read agreed price vs hourly.
Not sure you need custom work at all? Try the custom software or off the shelf test first.