Most "client from hell" stories start the same way. Someone replied "sounds great, let's go!" to an email, and work began. No deposit, no written scope, no agreed feedback rules. Three weeks later the client is asking for "one more page," the invoice is 20 days late, and there is nothing to point back to.
Three short documents, agreed before any work starts, fix most of this. None of them needs to be legalese.
1. A proposal with a "Not included" line
Clients usually compare a few proposals, so yours has to do two jobs: show you understand the problem and draw a clear line around the work.
Include:
- The outcome, in the client's words, not a list of your tasks.
- Deliverables, each one specific enough that you could check it off.
- Not included: the most useful line in the whole document. "Copywriting, stock photos, and pages beyond the 5 listed are quoted separately." Anything not listed becomes a change order instead of an argument.
- A short risk section: "Here's what usually slows projects like this down, and how I handle it." This builds more trust than another portfolio link.
- Price, payment schedule, and the deposit (see below), so nobody is surprised later.
2. A plain-English services agreement
One or two pages. The clauses that prevent the most pain:
- Deposit before start. The start date is confirmed only once the deposit clears.
- Invoice terms. Net 7 or net 14, plus a late fee you actually state.
- Change orders in writing. New requests get a quick written quote before they get done.
- What a revision round means. "One consolidated list of feedback from one approver." This single sentence ends the 40-comment email chains.
- Ownership on full payment. Rights transfer when the final invoice is paid.
- Kill fee. If they cancel midway, completed work is billed.
Have a local lawyer look at your version once, then reuse it on every project. A simple agreement that both sides signed beats a perfect one that never got sent.
Here is a deposit clause you can paste in today:
Deposit. A non-refundable deposit of [percentage]% of the total project fee ($[amount]) is due before work begins. The project start date and any reserved schedule are confirmed only once the deposit is received. The remaining balance of $[amount] is due [on delivery / in installments on (dates) / within (number) days of the final invoice]. If the client cancels after work has begun, the deposit is retained and any work completed beyond the value of the deposit will be invoiced at [rate].
And if a client pushes back with "can we skip the deposit?", offer to split it across milestones rather than dropping it. There's a ready-to-send reply for that, plus the deposit request email, on this free page: https://opspack.vercel.app/deposit
3. A welcome packet
Send it the moment the deposit clears. It answers ten future emails at once:
- Key dates and milestones
- What you need from them, and by when
- Who the single approver is
- Your communication hours and channel
- Feedback rules, including what happens if their feedback is late (the timeline moves, not your weekends)
The short version
Before the next project starts, get three things in writing: a proposal with a "Not included" line, a short agreement with a deposit and a late fee, and a welcome packet with feedback rules. Most scope creep, late payments, and ghosting get a lot easier to handle once these exist.
If it does go wrong anyway, these free templates help: a final notice before collections (https://opspack.vercel.app/final-notice) and the deposit wording above (https://opspack.vercel.app/deposit).
If you'd rather not write all three from scratch: the OpsPack Proposal, Contract & Client Onboarding Pack (v2) has a proposal with a risk section and "Not included" list, a plain-English agreement, a welcome packet, 1-page / hourly-with-cap / retainer variants, a filled-in example, and a quote calculator, in Word and PDF. It's $27, or $49 bundled with the scope and invoice kits: https://opspack.vercel.app
Not legal advice. Templates are a starting point; adapt them to your jurisdiction.
