OwnerMath

Guide

What should a freelance project quote include?

A freelance project quote should define scope, deliverables, assumptions, revisions, timeline, payment terms, exclusions, and change-order rules before the work starts.

By Chris Gaglardi

Build a project quote

What should a freelance project quote include?

Use the Project Quote Calculator

A freelance project quote should do more than name a price.

A good quote explains what the client gets, what is included, what is not included, what assumptions the price depends on, how revisions work, when payment happens, and what happens when the scope changes.

A bad quote says:

Landing page: $3,000

Then everyone acts surprised when the project turns into twelve calls, four revision rounds, missing copy, surprise stakeholder feedback, and a “tiny extra section” that somehow requires design, development, strategy, and emotional support.

A project quote is not just a number.

It is a boundary document with math attached.

Quick answer

A solid freelance project quote should include:

SectionWhat it protects
Project summaryKeeps everyone aligned on what the work is supposed to accomplish
DeliverablesDefines what the client actually receives
ScopeDraws the edge around included work
AssumptionsMakes the hidden conditions behind the price visible
TimelineConnects deadlines to client feedback and dependencies
PriceShows the fixed fee, hourly/capped hourly terms, or phased cost
Payment schedulePrevents “paid someday” from becoming the business model
RevisionsLimits the feedback loop before it eats your margin
Meetings and communicationStops calls and Slack from becoming unpaid project scope
ExclusionsNames what is not included
Change-order rulesTurns extra work into approved revenue
Expiration datePrevents old quotes from haunting future calendars
Acceptance stepsTells the client how to approve and start

If the quote does not explain what changes the price, it is not finished.

It is just a number standing in traffic.

Quote vs proposal vs contract

A quote, proposal, and contract are related, but they are not the same thing.

A quote usually gives the price and the scope behind that price.

A proposal usually sells the approach, value, plan, and fit.

A contract usually sets legal obligations, payment terms, ownership terms, liability language, cancellation rules, and other formal protections.

OwnerMath is not your lawyer, accountant, or contract wizard. Use this guide for practical pricing structure and business math. Use a qualified professional when legal stakes justify it.

For everyday freelance work, though, the quote itself still needs to be clear enough that the client understands what they are buying.

If the quote is vague, the client will fill in the blanks.

Clients are rarely generous when they fill in blanks.

The purpose of a project quote

A project quote should answer five questions:

  1. What are we making?
  2. What is included?
  3. What is not included?
  4. What does it cost?
  5. What happens if the work changes?

Most bad quotes fail because they only answer number four.

That is how freelancers accidentally sell unlimited access under a fixed-fee label.

A good quote makes the price understandable. It shows the work, the assumptions, the boundaries, and the next step.

The client should be able to read it and know:

  • what they are getting
  • what they need to provide
  • how many revision rounds are included
  • what delays the timeline
  • what costs extra
  • when payment is due
  • how to approve the quote

The freelancer should be able to read it and know:

  • what work they promised
  • what work they did not promise
  • how to defend the price
  • when to issue a change order
  • how to avoid silently donating extra labor like a noble idiot with Wi-Fi

Section 1: Project summary

Start with a short project summary.

This should explain the job in plain language.

Example:

Create a five-page marketing website for Acme Studio to explain the service offer, support lead generation, and replace the current one-page placeholder site.

Good project summaries are specific enough to stop confusion later.

Bad summary:

Website project.

That is not a summary. That is a fog machine.

Better summary:

Design and build a five-page service website with Home, Services, About, Case Studies, and Contact pages, using client-provided copy and brand assets.

The summary should not be bloated. It should make the project recognizable.

Section 2: Deliverables

Deliverables are the actual things the client receives.

Examples:

  • one landing page design
  • five-page website
  • technical SEO audit
  • analytics setup
  • brand messaging document
  • email sequence
  • wireframes
  • implementation checklist
  • strategy call recording
  • handoff document
  • final source files
  • launch support window

Be specific.

Instead of:

SEO audit

Use:

Technical SEO audit covering crawlability, indexation, internal linking, page templates, Core Web Vitals risks, and prioritized implementation recommendations.

Instead of:

Landing page

Use:

One responsive landing page design and build for a single offer, including hero section, social proof section, offer explanation, FAQ section, and lead form integration.

Deliverables are where vague excitement becomes actual work.

Get them crisp.

Section 3: Scope

Scope is the boundary around the deliverables.

It answers: what work is included to produce those deliverables?

For a website quote, scope might include:

  • one kickoff call
  • sitemap confirmation
  • wireframe
  • visual design
  • responsive development
  • basic on-page SEO setup
  • form integration
  • browser/device QA
  • launch support for seven days

For a technical SEO audit, scope might include:

  • crawl review
  • indexation review
  • template analysis
  • internal linking review
  • analytics/search console review
  • prioritized findings
  • one walkthrough call

Scope should include the work that affects time, cost, and risk.

If it consumes your time, it belongs somewhere in the pricing model.

You can include it as scoped work, price it as overhead, exclude it, or bill it separately.

What you cannot do is pretend it does not exist. That is how quotes become margin compost.

Section 4: Assumptions

Assumptions are the conditions your quote depends on.

This is one of the most important sections.

Assumptions might include:

  • client provides final copy before design begins
  • client provides brand assets in usable formats
  • client feedback comes from one decision-maker
  • client approvals are provided within three business days
  • project uses the existing website platform
  • no custom backend development is required
  • no copywriting is included
  • no paid stock imagery is included
  • no legal/compliance review is included
  • integrations are limited to listed tools
  • migration is limited to listed pages or assets

Assumptions protect the quote from becoming fake certainty.

Example:

This quote assumes all final copy, images, brand assets, and login access are provided before production begins.

That sentence is not decorative.

It is a margin seatbelt.

Without assumptions, a fixed price quietly absorbs every unknown.

Unknowns are expensive little bastards.

Section 5: Timeline

A timeline should include more than a final deadline.

It should show the phases and the dependencies.

Example:

PhaseEstimated timing
Kickoff and asset collectionWeek 1
WireframeWeek 1
DesignWeek 2
DevelopmentWeek 3
Revisions and QAWeek 4
Launch supportWeek 5

Then clarify what can delay it.

Example:

Timeline depends on receiving client feedback within three business days at each review point. Delays in feedback, copy, assets, access, or approvals may move the delivery date.

Do not promise a timeline that depends on client inputs without naming the inputs.

That is how your schedule gets kidnapped by someone else’s inbox.

Section 6: Price

The quote should state the price clearly.

Examples:

Fixed project fee: $5,500
Hourly: $175/hour, capped at $3,000 for discovery phase
Phase 1 discovery: $2,500
Phase 2 implementation: quoted after discovery

If the project is fixed price, the quote should show what the price includes.

You do not need to reveal every internal calculation, but you should know it.

Behind the scenes, your fixed fee should account for:

  • delivery hours
  • admin time
  • meetings
  • revision time
  • project management
  • risk buffer
  • profit margin
  • rush pressure
  • opportunity cost

Use the Project Quote Calculator to build the number before you send it.

Your gut estimate is not a pricing system.

It is a raccoon with a calculator.

Section 7: Payment schedule

A project quote should say when payment happens.

Common structures include:

Payment structureWhen it fits
100% upfrontSmaller projects, productized services, fast turnaround work
50% upfront / 50% before launchCommon for fixed-fee projects
40% / 40% / 20%Larger projects with milestones
Monthly billingLonger projects or ongoing work
Hourly weekly billingAdvisory, debugging, discovery, and variable-scope work

For fixed-fee projects, avoid doing all the work before getting paid.

That is not client service.

That is unsecured lending with worse paperwork.

A simple fixed-fee example:

Payment schedule:
50% deposit to schedule the project.
50% due before final handoff or launch.

For larger projects:

Payment schedule:
40% deposit to schedule the project.
40% after design approval.
20% before final delivery or launch.

The exact structure can vary. The key is making payment timing explicit.

Section 8: Revisions

Revisions are where fixed-fee margins go to die wearing a friendly smile.

A quote should define:

  • how many revision rounds are included
  • what counts as a revision round
  • who consolidates feedback
  • how long the client has to provide feedback
  • what happens after included revisions are used
  • what counts as a new request rather than a revision

Example:

This quote includes two revision rounds on the page design. Additional revisions are billed at $175/hour or quoted as a change order before work continues.

Also define what revisions are not.

A revision is usually feedback on the agreed deliverable.

A new section, new page, new integration, new audience, new strategy direction, or “actually we changed the offer” is not a revision.

That is new work trying to sneak through the dog door.

Section 9: Meetings and communication

Meetings consume capacity.

Communication consumes capacity.

Project management consumes capacity.

If the client wants lots of access, that belongs in the quote.

Define:

  • included calls
  • call length
  • communication channels
  • expected response times
  • whether extra calls are billable
  • whether async support is included
  • whether Slack/Teams access is included

Example:

This quote includes one kickoff call, one review call, and one final handoff call. Additional calls are billed at $175/hour in 30-minute increments.

This is not petty.

It is math.

If you do not price communication, communication becomes unpriced work. Then you wonder why the project felt profitable in the quote and stupid by the end.

Section 10: Exclusions

Exclusions say what is not included.

This is one of the fastest ways to prevent scope creep.

Examples:

  • copywriting is not included
  • custom illustration is not included
  • paid fonts or stock imagery are not included
  • hosting fees are not included
  • legal review is not included
  • third-party software fees are not included
  • advanced tracking setup is not included
  • ecommerce functionality is not included
  • migration of old content is not included unless listed
  • additional pages are not included unless listed
  • ongoing maintenance is not included

Good exclusions reduce awkwardness later.

Bad freelancers avoid exclusions because they do not want to sound negative.

Smart freelancers use exclusions because they want the project to survive contact with reality.

Section 11: Change-order rules

A change-order rule explains what happens when the client asks for work outside the quote.

Example:

Requests outside the included scope will be estimated separately and approved in writing before work begins. Additional work may be billed hourly at $175/hour or quoted as a fixed-fee change order.

You do not need to make this dramatic.

You just need the rule before the extra work appears.

If you wait until after the client asks for more, the conversation gets harder.

Before scope creep:

Extra work requires approval.

After scope creep:

Please pay me for the thing I already did even though I never said it would cost more.

One of these is cleaner.

Use the Scope Creep Cost Calculator when a project has already expanded and you need to see how much unpaid work actually cost.

Section 12: Client responsibilities

Your quote should say what the client needs to provide.

Client responsibilities may include:

  • final copy
  • images
  • brand assets
  • platform access
  • feedback
  • approvals
  • subject matter expertise
  • stakeholder alignment
  • legal/compliance review
  • timely decisions
  • payment

Example:

Client is responsible for providing final copy, images, brand files, CMS access, and consolidated feedback from all stakeholders.

The phrase “consolidated feedback” matters.

If five stakeholders send contradictory comments separately, your project just became a group project from hell, except everyone has a budget and no one has read the brief.

Section 13: Quote expiration date

Quotes should expire.

Example:

This quote is valid for 14 days.

Or:

This quote is valid until May 15, 2026.

Why?

Because your availability changes. Your costs change. Your workload changes. The client’s scope may change. The market may change. Your tolerance for nonsense may change dramatically after one bad Tuesday.

An expiration date prevents old numbers from crawling out of the grave months later.

Section 14: Acceptance and next steps

The quote should tell the client how to say yes.

Example:

To approve this quote, reply by email with approval and I will send the deposit invoice. The project is scheduled after the deposit is paid and all kickoff materials are received.

This removes friction.

A client should not have to guess the next step.

If you want approval, make approval easy.

Bad quote vs better quote

Bad quote:

Website redesign: $4,000

Better quote:

Project: Redesign and build a five-page marketing website.

Deliverables:
- Home page
- Services page
- About page
- Case Studies page
- Contact page
- Responsive build
- Basic on-page SEO setup
- Contact form integration

Included:
- One kickoff call
- One wireframe review
- Two design revision rounds
- One pre-launch QA pass
- Seven days of post-launch bug support

Assumptions:
- Client provides final copy and images before design begins
- Client provides consolidated feedback within three business days
- No ecommerce, membership, custom backend, or copywriting is included

Price:
Fixed project fee: $6,500

Payment:
50% deposit to schedule
50% due before launch

Out-of-scope:
Additional pages, copywriting, new integrations, extra revision rounds, and additional calls are billed separately after approval.

Quote valid for 14 days.

The better quote is not longer because we enjoy paperwork.

It is longer because reality has teeth.

How this connects to your pricing math

Before sending a quote, calculate your internal number.

At minimum, know:

  • your baseline hourly rate
  • expected delivery hours
  • expected admin and communication time
  • expected revision time
  • risk buffer
  • desired profit margin
  • rush or complexity pressure
  • opportunity cost

Start with the Freelance Hourly Rate Calculator if you do not know your baseline rate.

Use the Billable Hours Calculator if your hourly baseline feels too high and you suspect your billable-hours assumption is doing parkour over reality.

Then use the Project Quote Calculator to convert the work into a fixed-fee quote.

After delivery, use the Effective Hourly Rate Calculator to see if the quote held up.

That audit matters because the invoice total can lie.

A $5,000 project can be great at 20 hours and painful at 70 hours.

Same revenue. Very different business.

Freelance project quote checklist

Use this before sending the quote:

  • Project summary is clear
  • Deliverables are specific
  • Included scope is listed
  • Key assumptions are visible
  • Timeline includes dependencies
  • Price is clear
  • Payment schedule is clear
  • Revision rounds are limited
  • Meetings and communication are defined
  • Exclusions are listed
  • Change-order rules are included
  • Client responsibilities are listed
  • Quote expiration date is included
  • Approval next step is clear
  • Internal quote math supports the price

If you cannot check these off, the quote is probably not ready.

It may still sell.

That does not mean it is safe.

Lots of bad deals sell. That is why they are dangerous.

The biggest mistake

The biggest mistake is thinking a quote gets better by being shorter.

Short can be good.

Vague is not good.

A one-page quote can work if it is clear. A ten-page quote can still be useless if it dodges scope, revisions, assumptions, and change orders.

The goal is not to make the client read a novel.

The goal is to prevent the client from accidentally buying one thing while you silently agree to deliver three things and a small haunted circus.

Clarity protects both sides.

It protects the client from surprise costs.

It protects you from surprise labor.

That is the whole game.

What to do next

Before you send your next fixed-fee quote:

  1. Calculate your baseline hourly rate.
  2. Estimate delivery, admin, meeting, and revision time.
  3. Add risk and margin.
  4. Define scope and assumptions.
  5. Limit revisions and meetings.
  6. Name exclusions.
  7. Add change-order rules.
  8. Send a quote that protects the work.

Use the Project Quote Calculator to build the number.

Then tighten the quote language so the number has boundaries.

Once you have a draft, use the Freelance Quote Sanity Checker to catch missing scope, revision, payment, and margin details before you send it.

A project quote without boundaries is not client-friendly.

It is just underpricing with nicer formatting.

FAQ

What should a freelance project quote include?

A freelance project quote should include the project summary, deliverables, scope, assumptions, timeline, price, payment schedule, revision limits, exclusions, change-order rules, client responsibilities, expiration date, and approval next step.

Should a freelance quote include revisions?

Yes. A quote should say how many revision rounds are included, what counts as a revision, who provides feedback, and what happens when the included revisions are used.

Should a quote include what is not included?

Yes. Exclusions are one of the best ways to prevent scope creep. Name work that is not included, such as copywriting, extra pages, custom integrations, extra meetings, or additional revision rounds.

How long should a freelance quote be?

A quote should be as long as needed to define the work clearly. Short is fine when the work is simple. Vague is not fine. A good quote explains the price, scope, assumptions, and boundaries.

Should I include payment terms in a project quote?

Yes. The quote should explain when payment is due, such as upfront, milestone-based, monthly, or split between deposit and final payment.

What is a change order?

A change order is an approved update to the original scope, price, or timeline. It turns extra work into agreed revenue instead of unpaid labor.

Should a freelance quote expire?

Yes. A quote should include an expiration date so old prices do not apply after your availability, costs, timeline, or scope assumptions change.

Is a project quote the same as a contract?

No. A quote explains the work and price. A contract usually handles formal legal terms. OwnerMath helps with pricing structure and business math, not legal advice.


Disclaimer: OwnerMath provides educational business math, not financial, tax, legal, or accounting advice. Use these models for planning, then verify important decisions with a qualified professional when needed.