How to Write a Freelance Quote: What to Include, What to Exclude, and How to Price It

The short answer

A freelance quote should make one decision easy: whether the client can approve the work as described, at the stated price, under the stated conditions.

That means a quote is not just a number. It is a scope document, a pricing document, and a boundary document. A good one tells the client what they are getting, what they are not getting, when the work can start, how payment works, and what happens if the scope changes halfway through.

If you do not already know your baseline price, start with the freelance rate calculator. If you want a client-ready document structure, open the free freelance quote template. This guide is about the logic behind the document, so you can write one without sounding vague, defensive, or stiff.

A quote is not the same as a proposal

Freelancers often mix up quote, estimate, and proposal. Clients mix them up too. That is part of the reason approval conversations go sideways.

Use this rule:

• A proposal sells the approach.
• A quote sells the terms of the work.
• An estimate signals that the number is still rough.

Here is the practical difference:

Document	Best use	What it answers
Proposal	Early-stage sales conversation	Why this project matters, how you would approach it, and why you are a fit
Quote	Client is close to yes and needs a decision document	What is included, what it costs, what the timeline looks like, and how approval works
Estimate	Scope is still loose or discovery is incomplete	Rough budget range before a final scope is defined

If the client is already aligned on the work and mostly needs a clean approval path, send a quote. If they are still deciding between options or need more persuasion, send a proposal or a short proposal plus quote.

What every freelance quote should include

The cleanest quotes are usually short, but they are never thin. They contain the few details that reduce confusion later.

1. Client and project summary

Start with a plain-English summary of the work. Keep it brief. Two or three sentences is enough.

Example:

This quote covers the design and build of a five-section marketing site for Acme Studio, including a responsive homepage, contact page, CMS setup, and launch support. The goal is to replace the current one-page site with a clearer offer and stronger lead capture flow.

This section matters because it confirms shared understanding before the client ever looks at price. If the summary already feels slightly off, the rest of the quote will drift too.

2. Deliverables

This is the core of the document. Do not describe effort. Describe outputs.

Good deliverables sound like this:

• One homepage and three supporting pages
• Mobile and desktop responsive implementation
• Contact form setup with email routing
• Up to two revision rounds after first review
• Deployment to client hosting account

Weak deliverables sound like this:

• Website improvements
• Ongoing support
• Strategy help
• Design polish as needed

Clients approve specifics. Vague wording feels flexible when you write it, but expensive when you deliver it.

3. Timeline and dependencies

Most quote problems are not price problems. They are sequencing problems.

You need to state two things:

• your estimated delivery timeline
• what the client must provide for that timeline to hold

For example:

• Project start: within 5 business days of approval and deposit
• First draft: within 10 business days of receiving final copy and assets
• Final delivery: within 5 business days of consolidated feedback

Dependencies matter because they stop the timeline from becoming a one-sided promise. If the client owes you copy, access, product screenshots, API credentials, or sign-off, write that down.

4. Pricing model and total fee

The price section should answer the client's main financial questions fast:

• Is this hourly or fixed?
• What is the total?
• When do I pay?
• What would make the number change?

If you are selling a fixed-scope project, present the fixed fee clearly. You do not usually need to show the internal hourly math. That math is for you. The client needs the packaged number and the conditions around it.

If you still need help deciding whether this job should be hourly or fixed, read Hourly vs Project Pricing for Freelance Developers. If you need to calculate your baseline before packaging the number, use How to Set a Freelance Rate From Your Income Target and How to Estimate Billable Hours.

5. Revision limits and change requests

This is where margin lives.

Every quote should explain what feedback is included and what counts as new work. You do not need legal language. You need clean operational language.

Example:

• Up to 2 revision rounds are included.
• Revisions apply to the agreed deliverables above.
• New pages, new flows, or changes to approved scope will be quoted separately.

The point is not to sound strict. The point is to keep the project stable enough to deliver well.

6. Payment terms and quote validity

State the payment schedule clearly. For small and mid-size freelance projects, simple usually works best:

• 50% upfront, 50% on final approval
• or 40% upfront, 30% at midpoint, 30% before launch

Add a validity window too. A quote should not stay open forever. Seven to fourteen days is common.

That protects you if your calendar changes or if the client comes back months later expecting the same timeline and number.

What to exclude or move into assumptions

Most freelancers think about what to include. Fewer think about what the client may quietly assume is included.

That is where trouble starts.

Create a short exclusions or assumptions section for items like:

• copywriting
• stock photography licenses
• ongoing maintenance after handoff
• third-party software fees
• complex integrations not listed in scope
• SEO work beyond basic on-page implementation
• extra stakeholders beyond the agreed review process

This section is not there to make the quote feel smaller. It is there to keep the quote honest.

If an item is still unknown, do not hide it inside vague wording. Call it an assumption or move it into a paid discovery phase.

Why this matters more than freelancers think

Weak quotes create weak margins. That is true even when the client says yes.

One useful data point comes from PMI's 2024 Pulse of the Profession. In its 2023 survey data, the reported average scope creep rate was 30%, while top-performing organizations reported 23%. That is not freelance-only data, so I would not treat it as a direct benchmark for solo client work. But it is a useful proxy: when work is defined and managed more clearly, scope tends to drift less.

Freelancers feel this in a more personal way. A few extra calls, a few "small" additions, a few rounds of feedback from new stakeholders, and the effective rate drops fast. The quote is where you either create that drift or reduce it.

A simple quote structure you can reuse

If you want a structure that works without turning the document into a mini contract, use this order:

1. Project summary
2. Deliverables
3. Timeline
4. Investment
5. Payment terms
6. Revisions and exclusions
7. Acceptance or next step

That order works because it follows the way clients read:

• first, "Is this the work I asked for?"
• then, "What exactly do I get?"
• then, "How long will it take?"
• then, "What does it cost?"
• then, "What are the rules?"

You can build this from scratch, but it is faster to start with the free template and edit it for the current project.

Example: turning a baseline into a client-ready quote

Say your baseline rate from the calculator is $120/hour.

You estimate a brochure-site project like this:

• Planning and structure: 4 hours
• Design direction and page layout: 10 hours
• Implementation: 16 hours
• QA, launch, and handoff: 6 hours
• Total internal estimate: 36 hours

Your internal baseline would be 36 x $120 = $4,320.

If the scope is clean and you have built similar work before, you might quote a fixed fee of $4,800 rather than presenting it as hourly billing. Then you package it like this:

• Fixed project fee: $4,800
• Includes: homepage, about page, services page, contact page, responsive implementation, basic on-page SEO setup, launch support
• Excludes: copywriting, custom illustrations, advanced CMS migrations, ongoing maintenance
• Payment terms: 50% upfront, 50% before launch
• Revisions: up to 2 rounds
• Valid for: 10 days

Now the client sees a decision-ready document. You still used hourly logic underneath, but you sold a clean outcome instead of a moving timer.

When not to send a fixed quote yet

Sometimes the smartest quote is no quote.

Do not force a fixed project number when:

• the client cannot define what done looks like
• the codebase or existing site is messy and undocumented
• technical dependencies are unknown
• the client expects strategy, production, and iteration to happen at once
• stakeholders are still changing the priority list every few days

In those cases, sell a paid discovery, audit, or scoped planning phase first. That gives you the information needed to produce a real quote instead of a polite guess.

Common mistakes that make quotes harder to approve

• Writing the quote from your workflow instead of the client's decision needs
• Listing tasks instead of deliverables
• Forgetting to define what is out of scope
• Hiding revision limits in a footnote
• Sending a fixed price before the work is fully scoped
• Leaving the quote open-ended with no validity period
• Using vague phrases like "support as needed" or "minor edits included"

The pattern behind all of these is the same: unclear boundaries create extra negotiation now and extra unpaid work later.

Final takeaway

A good freelance quote does not try to impress. It tries to remove ambiguity.

Write the work in plain English. Define deliverables. State the price cleanly. Put revision limits and exclusions where the client can actually see them. If the scope is not clear enough for a fixed quote, say so early and sell discovery first.

That is what makes a quote easier to approve and safer to deliver.