Client Commercial Docs
Most freelancers and small agencies lose money in the same place — vague scope, missing exclusions, informal agreements that unravel when expectations diverge. Client Commercial Docs produces the proposals, SOWs, and change orders that make the invisible visible before it becomes an argument.
What this skill does
The best commercial documents are precise without being bloated. Every exclusion you write down is a future argument you prevent — a fact most freelancers learn the expensive way, by absorbing scope that was never priced. This skill produces four document types: proposals, statements of work, change orders, and standalone assumptions and exclusions addenda. Each one has a specific job and a structure designed to do that job without padding.
The proposal opens with an executive summary readable on its own, restates the brief in the client's own language to prove you listened, then leads with outcomes before features. The SOW is the operational document — more detailed, with numbered deliverables, explicit acceptance criteria, client responsibilities, and a change control section that exists specifically so you can point to it later. The change order is factual, not apologetic — the client requested extra work, you priced it, here is the new timeline. The assumptions document captures the dozens of implicit conditions that quietly determine whether the project stays profitable.
It also enforces a red-flag phrase swap. "Unlimited revisions" gets replaced with a defined number. "Best efforts" becomes a specified deliverable. "ASAP" becomes a date. "Ongoing support" becomes a defined window. "As discussed" gets replaced with the actual agreement quoted in writing. These swaps are the single most useful edit on most commercial documents — they protect both parties without making the language adversarial.
What it deliberately doesn't do: write legal contracts. That's a lawyer's job. This skill sits in the space between the conversation and the signature — the business documents that win work and protect it. It also won't bloat a £2K project with a 14-page SOW. A short, detailed email is the right answer for small work with existing clients, and the skill says so rather than over-engineering the deliverable to look professional.
When this triggers
- ·You're drafting a proposal and the last one led to scope creep you absorbed for free
- ·You need an SOW that ties payments to milestones and lists what isn't included
- ·The client wants 'one more thing' and you need a change order that prices it without sounding defensive
- ·You're tired of writing 'unlimited revisions' and 'ASAP' and then regretting both
- ·You need an assumptions and exclusions addendum for a project with too many moving parts
Example
Trigger
User: 'Write me an SOW for a £12K brand refresh — logo, guidelines, 6-page website. Client is a 40-person consultancy.'
Output
SCOPE — DELIVERABLES (numbered, with acceptance criteria): 1. Logo system — primary mark, secondary mark, monochrome variant. Two rounds of revisions. Acceptance: written client approval within 5 business days of presentation. 2. Brand guidelines PDF — 18-22 pages, covering logo usage, colour, typography, voice, application examples. 3. Website — 6 pages (home, about, services, 2 case studies, contact). Design only. Build excluded — see Section 4. SCOPE — EXCLUSIONS (numbered, explicit): 1. Copywriting — client provides final copy by [date]. 2. Photography / illustration sourcing. 3. Website build, hosting, CMS setup. 4. SEO optimisation beyond on-page tag structure. 5. Print collateral (business cards, letterhead). CHANGE CONTROL: Any work outside this SOW requires a written Change Order with revised timeline and pricing. Red-flag phrase swap: "unlimited revisions" → "two rounds included, additional rounds billed at £140/hr."
Get this skill + 13 more
Included in the The Freelancer Stack — win clients, deliver work, get paid. Save $100+ vs buying individually.
Get The Freelancer Stack — $99What you get
- 173-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Business Operations
Not academic exercises — practical documents that force clarity on the questions that actually determine whether a business will work: who's paying, how much, how often, and what it costs to deliver
A great onboarding process is the difference between a client who trusts the user from day one and one who micromanages because they're anxious about their investment
Not surface-level observations ("they have a nice website") but strategic analysis: how they position themselves, where they're vulnerable, what they do better, and what the user can learn or exploit
The best investor updates are the ones that make investors want to help — and that happens through consistent, honest reporting that clearly communicates what's working, what's not, and where help is…
Socratic — doesn't tell them their niche, asks the right questions in the right order until they discover it themselves
An offer is not a list of deliverables — it's a promise of a specific transformation for a specific person at a specific price
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles