Contracts, Proposals and Protecting Yourself
A winning proposal
- The problem in the client's words.
- The outcome you will deliver and why it matters to them.
- Scope: what is included and, just as important, what is not.
- Timeline with milestones.
- Price and payment terms, with options if appropriate.
- Next step: how to accept (sign and pay the deposit).
Keep it short and specific. Proposals that read like the client's own goals win.
Contract essentials
Use a contract reviewed by a lawyer in your jurisdiction. It should cover:
| Clause | Why it matters |
|---|---|
| Scope and deliverables | prevents disagreements about what was promised |
| Change requests | extra work is quoted and approved before you do it |
| Payment terms and late fees | when and how you are paid |
| Intellectual property | who owns the code, and when ownership transfers (often on full payment) |
| Your pre-existing code and libraries | you keep the right to reuse your own components; open-source licences respected |
| Client responsibilities | content, feedback and access delivered on time |
| Warranty and support period | e.g. bug fixes for 30 days after launch |
| Limitation of liability | caps your liability, often at the fees paid |
| Confidentiality | protects both sides' information |
| Termination | how either side can end the contract and what is owed |
| Hosting and maintenance | separate monthly agreement and what it covers |
Selling source code
When you sell source code (like PandaDev's premium projects), a licence defines what buyers may do: use it in one project or many, modify it, resell it or not. State it clearly at purchase.
Scope creep
"Could you just add…" is how fixed-price projects become unprofitable. Respond positively and formally: "Happy to. That's outside the agreed scope; I'll send a quick change request with the cost and timeline impact."
Client red flags
Pressure to start without a contract or deposit, unclear decision makers, "it's a quick job", disrespect for your time, or asking for unpaid spec work.
Exercise
Write a proposal template and a checklist of contract clauses you need, and get your contract template reviewed by a local lawyer. Practise a change-request email for a mid-project feature request.
Check yourself
- Why state what is not included in a proposal?
- When does IP typically transfer to the client?
- How should you respond to a request outside the scope?
Your progress is saved in this browser only.
Submit for review (10 points)