01
Extract the agreed scope
You separate confirmed terms from assumptions, requests, and open questions before drafting anything client-facing.
Made for Consultants
Build a One-Page Scope Summary
35 min
Intermediate
Boundaries
Get More Clients
Turn meeting notes and deal terms into a compact scope summary that a client can review and approve without digging through a long proposal.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Make the proposed engagement easy to understand while catching missing details before they cause delays, unpaid work, or disagreements.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Close the risky gaps
You decide which gaps must be settled before sending and which can be shown as explicit assumptions for client confirmation.
03
Draft and check the one-pager
You produce the scope summary, then test it for vague promises, hidden work, and unsupported terms.
Make Your Play
Build a One-Page Scope Summary
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Enter the client name or label and a short project name.
Paste the useful facts, concerns, decisions, and open questions from the client conversation.
0/10000
List each item you expect to provide and any known completion or revision limits.
0/10000
List work, expenses, systems, or extra requests that aren't included.
0/10000
Enter the planned start, major milestones, final delivery date, and schedule dependencies.
0/10000
Enter the agreed or proposed fee, payment schedule, reimbursable costs, and applicable taxes.
0/10000
Separate what you'll provide from what the client must provide, decide, or approve.
0/10000
Select how you want the client to approve the scope.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Extract the agreed scope
You separate confirmed terms from assumptions, requests, and open questions before drafting anything client-facing.
02
Close the risky gaps
You decide which gaps must be settled before sending and which can be shown as explicit assumptions for client confirmation.
03
Draft and check the one-pager
You produce the scope summary, then test it for vague promises, hidden work, and unsupported terms.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste your notes as they are. If you don’t know a term, write “not decided” instead of guessing. Review every [CONFIRM] marker before you send the summary.
Advanced instructions
Use the first draft as a scope-control review. Tighten acceptance conditions, dependencies, revision limits, and decision deadlines where your notes support them. Move legal terms into your contract rather than overloading this summary.
Use this when
Use this after a promising client conversation when the work is defined well enough to confirm the scope, fee, timing, responsibilities, and approval path.
You'll need
- Client and project
- Meeting notes
- Deliverables
- Exclusions and boundaries
- Timeline and milestones
- Fee and payment terms
- Responsibilities
- Approval route
You'll get
- A one-page scope summary that names the result, deliverables, exclusions, timeline, fee, responsibilities, assumptions, change process, and approval step
- Every [CONFIRM] item or clearly asked the client to confirm it resolved You can trace each material claim back to your notes or agreed terms.
By the end of this playbook
You will have:
- A one-page scope summary that names the result, deliverables, exclusions, timeline, fee, responsibilities, assumptions, change process, and approval step
- Every [CONFIRM] item or clearly asked the client to confirm it resolved You can trace each material claim back to your notes or agreed terms.
Examples
Progress 1 of 3