Freelance operations guide
Proposal vs quote vs contract: what should you send a client?
Understand the practical difference between a project proposal, quotation, statement of work, and contract—and when each document belongs in your sales process.
Each document answers a different question
A proposal helps a client decide whether your recommended approach is right. A quote states the price for a defined request. A statement of work describes delivery in operational detail. A contract records the legal obligations that govern the relationship.
Small engagements sometimes combine these jobs in one accepted document. Larger or higher-risk projects usually benefit from separating the persuasive proposal from the detailed agreement.
Use a proposal when the solution still needs framing
Send a proposal when the client is choosing an approach, comparing providers, or deciding between levels of investment. It should connect the current situation to a recommended outcome, then explain scope, timing, price, assumptions, and next steps.
A proposal is most useful after discovery. Sending it before you understand the problem often produces generic language and unreliable estimates.
Use a quote when the request is already specific
A quote is appropriate when the buyer knows exactly what they need and mainly requires a confirmed price, quantity, validity period, and commercial terms. It is usually shorter and less persuasive than a proposal.
If important scope decisions remain open, label the document as an estimate or return to discovery. A precise-looking quote built on uncertain requirements creates false confidence.
Use a contract for enforceable obligations
Contracts commonly address payment obligations, intellectual property, confidentiality, warranties, liability, termination, dispute handling, and governing law. Those topics may be summarized in a proposal but often require more precise language.
QuillClose helps structure commercial proposals and acceptance records; it does not replace advice from a qualified lawyer. Review your agreement for your service, client type, and jurisdiction.
Choose a simple, repeatable sequence
A practical workflow is discovery, proposal, acceptance, agreement, deposit, and kickoff. For repeat clients, a master services agreement can govern the relationship while a new statement of work defines each project.
Whatever sequence you use, identify which document controls if terms conflict. Keep the accepted version, acceptance time, selected package, and related agreement together so both sides can reconstruct the decision later.
Common questions
Questions about this topic
Is an accepted proposal legally binding?
It can be in some circumstances, depending on its terms, the acceptance method, and applicable law. Get jurisdiction-specific legal advice for your workflow.
Can a proposal and contract be one document?
Yes, especially for straightforward engagements, provided the document clearly covers both commercial scope and the legal terms you need.
What should I send before taking a deposit?
Make sure the client has accepted the applicable scope, price, payment schedule, and governing terms before collecting the deposit.