First 10 buyers pay half.First 10 buyers pay half. See paid workflows
Pro Skill Packs logo PRO SKILL PACKS

Home / Freelancers and small businesses / Write a scope of work before you start

Write a scope of work before you start

Who it is for
UK freelancers who need to agree the work before starting.
What you give it
The client brief.
What you get back
Numbered deliverables, exclusions, client inputs, milestones and a payment schedule.
Get it, $5$5 $2.50 for the first 10 buyers. 30-day refund.

UK and EU buyers see local prices; VAT is added at checkout.

Free updates: when we improve it, you get the new version.

Also in the pack: Win a client job, from brief to scope, $19

You get a zip with a short guide and a text you paste into ChatGPT, Claude or any chatbot.

Before and after

The brief is a real public request for quotation from a museum for a digital installation, value £14,000.

Before (from the brief): "We're looking for an individual or organisation to deliver a 360-degree 'Immersive Art' experience. Six paintings from [the museum]'s fine art collection should each be brought to life through digital projection and interpretation… The services must include expertise both in software and hardware design and the appointed professional must be able to take the concept through to full delivery within the timeframes stated."

After (real output, unedited extract, museum name removed):

#DeliverableAccepted when
D1360-degree 'Immersive Art' experience in the Active GalleryAccepted when each of the six paintings from [the museum]'s fine art collection has its own digital projection and interpretation in the Active Gallery.
  • [DECIDE: is the hardware (projectors, speakers, computers) bought within the £14,000 in D1?]
  • [DECIDE: is installation on site in the Active Gallery included in D1?]

COMPLETENESS: 72/100
SECTIONS: 10 of 10 present, 8 with content
DELIVERABLES: 1 listed, 1 with an acceptance line
OPEN PLACEHOLDERS: 15 in total; 8 sections still need a decision

The brief's requirements on the supplier ("must include expertise both in software and hardware design") are not turned into acceptance conditions. It also listed the page the brief points to for details, which it was not given.

What it does

Paste a client brief. You get a scope of work in ten sections: numbered deliverables with a test for when each is done, what is out of scope, what the client provides, milestones, revisions, fees and payment, changes and sign-off. Whatever the brief does not settle is listed as a decision for you to make. It is a working document to agree with the client, not a contract.

The evidence

TESTED badge. Run on at least three real examples and scored against a written standard, with the record on file.4 real tenders, from 1 to 13 work items.

More on how it was tested

Each run was scored against a written rubric and checked by hand against the brief and the script output. No fee, date or legal clause was invented in any final run. Final scores: 8.5, 9, 8.5 and 8.5 out of 10. After an independent review, the last three cases were re-run on the current version; the college case's final score is from the version before that review's fixes. On a second model the first run of the college case listed a deliverable as out of scope; after a fix that case scored 8.5. The museum and brand cases scored 9 and 9 there on the version before that fix. A second, harder run (2026-10-04, Claude Sonnet, a brief with a fixed budget, unlimited changes, a missing hosting person and a late approval date): nothing invented, but the budget and unlimited-changes conflict was not named. We added a rule and re-ran: it is now a [DECIDE: conflict] with both quotes.

Read the full test

Limits

  • It is not a contract and contains no legal terms: nothing on liability, ownership of the work, termination or disputes. Use it beside your contract.
  • It works from the brief you give it. A thin brief gives a short scope with many decisions. The completeness score is low until you close them.
  • The completeness check looks at structure and open decisions. It cannot tell whether the scope is right for the job.
  • Proposed acceptance tests and the process wording in the last sections are drafts for you and the client to agree.
  • Tested on UK public-sector notices, which are more formal than a typical freelance brief.
  • For UK jobs it may quote GOV.UK's two sentences on payment periods below the scope, never inside it. That is the only legal text it gives.

Questions

How do I pay and get the files?

Checkout: Gumroad opens on this page. Click Add to cart, enter your email and card details, and check the total, with any VAT, before you pay. Prices here are in US dollars.

After you pay: a download page opens right away with the zip file, and Gumroad gives you a receipt there that you can resend. Open it, then paste the text from the prompts folder into ChatGPT and add your details.

Refunds and contact

If it does not do the job, ask and we refund you within 30 days. Reply to your receipt, or write to kaiventura.founder@gmail.com.

Contact page

Which assistants does it work with?

Works in ChatGPT, Claude, Gemini and most other AI assistants: paste in the text, or load the files if your assistant supports them. Setup steps are under For technical users. We run our release tests on Claude Sonnet and Opus. Use your assistant's strongest model: in our tests, a small, fast model added facts that were not in the source data. A small Python script (standard library only) checks the finished scope. Without code execution the scope is written but not checked.

For technical users

What is in the zip

  • LICENSE.txt
  • README.md
  • claude-ai/ (1 file: scope-of-work-builder.zip)
  • prompts/ (2 files: scope-of-work-builder-v1.0-prompts.pdf, scope-of-work-builder.md)
  • scope-of-work-builder/, the skill itself:
    • SKILL.md
    • README.md
    • scripts/ (1 file)

Using it with an AI assistant

  1. Unzip the download. It holds the scope-of-work-builder folder, ready-made zips for claude.ai in a claude-ai folder, a README and the licence.
  2. Put the scope-of-work-builder folder where your assistant looks for skills. The generic path is .agents/skills/ (or npx skills add from a folder). Tool-specific paths:
    • Claude Code: ~/.claude/skills/ (or .claude/skills/ inside one project)
    • OpenAI Codex, Gemini CLI, Cursor and others: .agents/skills/ or the skills folder their docs name
    • claude.ai: Customize, Skills, then the plus button, Create skill, Upload a skill, and upload the zip from the claude-ai folder without unzipping it (code execution must be on in Settings, Capabilities)
    • ChatGPT or any chatbot: open the skill's prompt.md, paste it into the chat, then paste your own text or link
    • Steps for each tool, with links to its official docs: how to install skills
  3. Ask for the job in plain words, for example: "Turn this brief into a scope of work we can agree with the client: ...". The skill loads by itself.
Get it, $5

Jobs that go with this