Introduction
Most freelance disputes come from unclear expectations, not bad intent. Verbal okays, half sentences in Slack, and email threads contradict each other later. A written proposal and contract set the rules upfront.
This article covers proposal vs contract, SOW contents, payment and revision clauses, and a copyable proposal outline. It is not legal advice—a practical frame to protect your work. For critical deals, consult a lawyer.
Proposal vs Contract
A proposal sells and summarizes scope: problem, approach, price, timeline. A contract carries binding terms: parties, payment, IP, confidentiality, termination. Small jobs can combine them; larger jobs should separate them.
The SOW is the operational definition of work: deliverables, acceptance criteria, assumptions, and exclusions. Without a SOW, 'it is not done' arguments are inevitable.
- Proposal: why you, what you deliver, price, when
- SOW: deliverables, acceptance, assumptions, exclusions
- Contract: payment, IP, NDA, liability, termination
Proposal Outline
A strong proposal restates the problem in the client's language, briefly explains your approach, and gives a clear next step. One or two relevant case studies beat a long portfolio dump. Split price across milestones.
Sending a written proposal within 24 hours improves close rates. Paste discovery notes and ask for confirmation. Even an approval email becomes a useful reference later.
1. Executive summary (problem + outcome)
2. Scope and deliverables (bulleted)
3. Explicit exclusions
4. Timeline and milestones
5. Investment / price and payment plan
6. Revision rounds and change-request process
7. Assumptions and client responsibilities
8. Next step: approval + deposit + kickoffPayment and Revision Clauses
Do not start without a 30–50 percent deposit. Tie interim payments to deliverables: design approval, staging handoff, go-live. State Net 15/30 terms and your right to pause work on late payment.
Limit revision rounds by count and scope. Unlimited revisions means unlimited time. Price new requests via change orders—fair and educational for scope.
- Deposit → kickoff
- Milestone 1 payment → interim delivery
- Final payment → source / production access
- Change order → written approval for extra work
IP, Confidentiality, and Termination
Clarify when IP transfers—usually after final payment. Keep your libraries and open-source components under license. Sign NDAs before sharing sensitive materials if required.
Termination clauses protect both sides: notice period, payment for completed work, deposit application. Define pause and file-delivery rules if the client goes silent.
Contracts do not ruin relationships; ambiguity does.
Practical Checklist
Reuse the same skeleton for speed and consistency. Leave blanks for acceptance criteria, assumptions, and exclusions—and do not price until they are filled.
Align templates with your accountant for invoicing. For international clients, state currency, tax responsibility, and governing law.
- Are legal entity names correct?
- Are deliverables measurable?
- Are deposit and payment dates clear?
- Is the change-request process written?
Conclusion
Strong proposals and contracts continue the sale: they create trust, freeze scope, and secure payment. Build the template once and customize per project.
Solve ambiguity in writing, not with goodwill alone. A clear SOW and fair payment plan are the foundation of long-term client relationships.