Tutorials Education

Proposals and Scoping: Turning an Enquiry Into a Job

By Infinite Creation · Beginner · ~22 min

Overview

Most freelance work that goes badly went wrong at the proposal, not during the job. A proposal is where the work is defined, and anything left undefined there becomes an argument later, usually one you lose because the client genuinely believed it was included. The document has one job: to describe the work precisely enough that both sides mean the same thing by the word finished.

What You Need

A conversation with the client before you write anything, because a proposal written from a brief alone is a guess
Your own cost floor, which is what a rate calculator gives you and a competitor's rate does not
A template you reuse, so that the thinking goes into the work rather than the formatting

Steps

Find out what the work is actually for

The stated request and the underlying need are frequently different. A client asking for three videos may need something that works in a sales meeting, and knowing that changes what you propose and often what it is worth. Ask what happens with the finished thing and who has to approve it.

Find out who decides

The person briefing you is often not the person who signs off. Ask directly, early, and without embarrassment, because a project with an unnamed approver acquires one halfway through and every assumption gets reopened.

Ask about budget before you quote

A client who will not name a figure will usually name a range if you offer one first. If they genuinely will not, propose the version of the work you think is right and price it honestly. Quoting into silence and hoping is how a job becomes unprofitable before it starts.

Write the deliverables as countable things

One edited video, up to three minutes, delivered as a single H.264 file and one subtitled variant. Not video production. The test is whether a stranger could look at what you handed over and say whether it matches, because at some point someone will.

Name what is not included

Exclusions do more work than inclusions. Scripting, music licensing, travel, additional shoot days, and versions for other platforms are the ones most often assumed. A short list of what is outside scope costs a line each and prevents most disputes.

Define a revision round and count them

A revision round is one consolidated set of notes from the client, not one change. Two rounds is a normal offer. Without this, feedback arrives one comment at a time from several people and the job never ends.

Price the work, not the hours

Quote a figure for the deliverables. Hourly pricing punishes you for getting faster and invites a client to audit your working. Use your hourly cost floor to check that the fixed price clears it, then quote the price.

Give the proposal an expiry

Thirty days is conventional. It protects you against a client accepting a quote nine months later when your rates and your availability have changed, and it gently signals that the offer is a decision rather than an open shelf.

Offer options rather than one number

Two or three scoped versions at different prices turn the conversation from whether to hire you into which version to buy. It also reveals the real budget faster than asking does.

Pro Tips

A proposal a client cannot understand is a proposal they cannot approve. Write it for the person who signs, who is often not the person who briefed you.
If the scope is genuinely unknowable, propose a small paid discovery stage that ends in a scoped proposal. It is better than guessing and cheaper for both sides than getting it wrong.
Send the proposal and the contract together. Two documents arriving weeks apart is two chances for terms to be renegotiated.
Keep every proposal you send. The rejected ones tell you where your pricing sits, and the accepted ones become your template.

Knowledge Base

Reference Notes

Two things decide whether a proposal holds up: how scope creep actually happens, and what to do when a client will not talk about money.

How scope creep actually happens

It is rarely one large request. It is a series of small ones, each individually reasonable, each easy to say yes to, and each arriving after the price is fixed. A version for another platform, a slightly different ending, one more round of notes. None of them feel like a renegotiation to the person asking.

The defence is not refusing them. It is having written down what was included so that a request outside it can be recognised and priced without anyone feeling accused. A proposal that lists deliverables and exclusions turns an awkward conversation into an administrative one, which is the whole purpose of writing it down.

When a client will not name a budget

Sometimes this is a negotiating position and sometimes the client honestly does not know what the work costs, which is common with anyone commissioning for the first time. Treating both as bad faith loses you the second kind of client, who is often the better one.

The productive move is to give them something to react to: name a range for work of this shape and ask whether that is the territory they had in mind. If the answer is far below, you have found out cheaply, and you can propose a smaller version rather than discounting the full one. Discounting the same work teaches a client that your first number was not real.

Where This Fits

Scoping sets what a job is worth, and The Creator Business, End to End covers pricing from real operating costs.

FAQ

Q: How long should a proposal be?
A: Long enough to define the work and no longer. One or two pages is normal for most freelance jobs, and a long document usually signals that the scope was not clear enough to state briefly.

Q: Should I put the price on the first page?
A: Yes. Burying it reads as apologetic, and the client will look for it first regardless. State the work, then the price, then the terms.

Q: What if they ask me to lower the price?
A: Reduce the work rather than the price. Cutting the fee for the same deliverables tells the client the first figure was arbitrary, and it sets the starting point for every future job.

Q: Do I need a proposal for small jobs?
A: Something in writing, yes, even if it is a short email listing deliverables, price and revision rounds. Small jobs go wrong the same way large ones do.

Vocabulary

Scope The specific work a price covers, written as countable deliverables. Anything left out of it is not excluded by default in the client's mind, which is why a short list of exclusions prevents more disputes than a long list of inclusions.

Revision round One consolidated set of client notes, not one change. Defining it this way stops feedback arriving a comment at a time from several people, which is the most common way a fixed-price job stops ending.

Discovery stage A small paid piece of work that ends in a scoped proposal, used when the job genuinely cannot be specified in advance. It is cheaper for both sides than pricing a guess and then discovering what the work was.