Freelance project quote

How to use it well

• →Restate the brief in your own words before pricing it - most scope disputes trace back to the client and freelancer having quietly imagined a different final deliverable from day one.
• →Price phases around a deliverable the client can see, not around your hours - it reads as fairer, and it gives you a natural, defensible point to pause if the relationship goes sideways.
• →An assumptions section only earns its keep if it names the specific thing you expect to be given - "client supplies content" prevents more arguments than any clause about scope creep.

Part by part

## Our understanding of the brief

Restates the request in your words. It is the cheapest way to catch a mismatch, and it happens before either side has committed anything.

## Assumptions

The section that protects the price. An assumption stated in writing is a condition; one held silently is a dispute waiting for the moment it turns out to be wrong.

This quote is valid until {{valid_until}}

An expiry, so a quote cannot be accepted six months later at a price that no longer works. It also creates a reason to decide.

Common mistakes

• Quoting a price with no assumptions listed.

  Every quote rests on assumptions about what the client provides, how many rounds of review there are, and what already exists. Unstated, each one becomes an argument once it proves wrong.

• Skipping the understanding-of-brief section.

  It is where mismatches surface cheaply. Discovering after acceptance that you priced a different project is a far more expensive conversation than a paragraph would have been.

• No expiry date.

  An open-ended quote can be accepted after your rates, availability or costs have changed. The date is not pressure, it is a boundary on what you committed to.

Questions