A service quote is a two-sided document. For the client, it answers: what will I get, what will I pay, and when? For you, it defines the job and limits the scope. Writing one well means balancing clarity with completeness — thorough enough to be protective, simple enough that the client reads it rather than filing it away.
Start with the scope conversation
Before you write anything, you need to understand what the client actually wants. Sometimes what they describe and what they need are different things — and your quote should be based on the real project, not the first thing they said on a call.
Ask the right questions:
- What does the finished product look like to you?
- Are there things you definitely don’t want included?
- What’s the timeline? Is there a hard deadline?
- Who on your side will we be working with, and who approves the final work?
- Have you done a project like this before? What went well or badly?
Good discovery questions give you the information to write a scope that’s accurate — which protects both of you.
Write the scope in client language
Your scope of work section should be written so a non-expert can understand it. Avoid technical acronyms unless you explain them. Avoid vague phrases like “design work” or “development support.” Be specific about what you’re making, how many of them, in what format, and with how many revisions included.
A good test: read your scope and ask whether a different person could deliver the same work based on that description. If the answer is yes, your scope is clear enough.
A vague scope doesn’t protect you — it just delays the dispute until the project is underway, when fixing it is more expensive.
Build the pricing section
Once the scope is clear, pricing is straightforward. Assign a price to each major deliverable or phase. For straightforward projects, a single line per deliverable is enough. For complex projects, you might break deliverables into sub-items.
Practical tips for the pricing section:
- Round numbers are fine for fixed-price work — $1,500 is easier to process than $1,478
- Add a contingency (10-15%) for projects with undefined elements
- Include your hard costs — software licenses, stock assets, subcontractors — as separate line items so the client understands the total
- State your rate if billing hourly, alongside an estimated range of hours
Add the terms that protect you
Your payment terms, revision policy, and timeline aren’t fine print — they’re core to the agreement. Write them clearly enough that you can refer back to them if a dispute arises.
Essential terms to include:
- Deposit — when it’s due and what percentage it is
- Payment milestones — if it’s a multi-phase project
- Final payment trigger — what constitutes project completion
- Revision rounds — number included, definition of a revision
- Intellectual property transfer — when does the client own the work?
- Project expiry — if the client doesn’t start within X weeks, they forfeit the deposit or the quote is void
Send it the right way
The act of sending the quote matters too. A quote attached to a blank email feels impersonal. Write three to five lines referencing your conversation, confirming the key deliverable, and inviting questions. End with a clear action: “To proceed, please sign the quote or reply to confirm.”
If you’re using a tool like Waco, you can send a link instead of a PDF and see when the client opens it. That visibility is genuinely useful — it tells you when to follow up.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
