Turn discovery call notes into a scope doc clients approve

Short answer: After every discovery call, turn your raw notes into a one-page scope document the same day. You decide what is in and out of scope; AI only organizes your bullets into plain language and flags gaps. You edit every line before the client sees it. Send it for comment, not as a surprise attachment a week later.

This guide is for freelancers and small agencies who sell fixed-fee or milestone projects—not hourly “we’ll see” work. Jordan runs a three-person Shopify studio in Austin. A local retailer wants a refresh before Black Friday. The call is Tuesday at 10 a.m. Jordan has forty-five minutes to capture outcomes, boundaries, and what happens if the client adds a fourth payment provider mid-build.

If you already struggle with getting paid after delivery, start with follow-up on unpaid invoices with AI. This post is about preventing scope fights before you write line one of code.

Not legal advice. If your contract is high-stakes, have a lawyer review the final scope and master agreement.

What to capture during the call (before AI touches anything)

Open a doc titled Discovery — [Client] — [date]. Do not record the call without consent where you operate. Take notes in the client’s words when they describe pain.

Minimum fields:

• Outcome: What does “done” look like on go-live day?
• Audience: Who uses the store admin daily?
• In scope: Pages, integrations, migrations, training, support window.
• Explicitly out: Features they mentioned but you are not pricing now.
• Dependencies: Who provides copy, SKUs, brand assets, DNS access?
• Timeline: Hard dates (Black Friday) vs soft (“whenever”).
• Budget band: Even a range stops fantasy scope.
• Decision maker: Who can approve change orders?

Jordan’s notes after the retailer call include: “Must keep existing POS sync,” “No custom mobile app,” “They’ll write product descriptions,” “Launch by Nov 15 or we pause ads.”

After the call, Jordan spends twelve minutes cleaning typos—not rewriting strategy. That cleaned block is what goes into the AI prompt. If a bullet says “maybe loyalty later,” it lands in Out of scope immediately so nobody treats “maybe” as a promise.

Same-day structure for the scope document

One page in Google Docs (or Word). Sections:

1. Project summary (three sentences max)
2. Goals & success metrics (2–4 bullets)
3. Deliverables (numbered, testable)
4. Out of scope (bullets—this section saves marriages)
5. Client responsibilities (assets, approvals, logins)
6. Timeline & milestones (dates + what “approval” means)
7. Change process (how extras get priced)
8. Assumptions (hosting, licenses, third-party fees)

Send with a short email: “Please comment inline or reply with corrections by [date]. Work starts after written approval.”

Paste-ready prompt for ChatGPT or Claude

Paste your raw notes below this block. Replace bracketed fields.

You are helping a freelance consultant write a client-facing scope document.

Rules:
- Use plain English, short sentences, no hype.
- Never invent features, dates, prices, or integrations not in my notes.
- If a field is missing, write [TBD — ask client] instead of guessing.
- Separate "In scope" and "Out of scope" clearly.
- Flag contradictions in my notes in a section called "Open questions for client".

My notes:
[PASTE DISCOVERY NOTES]

Output format:
# Project scope — [Client name]
## Summary
## Goals
## Deliverables (numbered)
## Out of scope
## Client responsibilities
## Timeline
## Change requests
## Assumptions
## Open questions for client

Run the draft once. Then run a second pass yourself: delete anything that sounds like marketing, fix numbers, and move anything fuzzy to Open questions.

Three edits humans must make every time

1. Deliverables must be testable. “Better checkout” becomes “Guest checkout enabled; Apple Pay live in Shopify Payments; shipping zones for TX + OK.”
2. Out of scope must name the thing they asked for. “Custom iOS app” belongs here if you are not building it.
3. Change process needs a price hook. “Additional work is quoted within two business days at $X/hr or fixed fee per change order.”

Jordan removes ChatGPT’s suggestion to “optimize SEO” because it was not discussed and adds a line: “SEO plugin configuration is out of scope unless added via change order.”

Mini example (deliverable wording)

Weak: “Improve product pages.”
Strong: “Up to 40 collection templates use new brand CSS; PDP shows size guide PDF; no custom 3D viewers.”

The strong version is what you put in section 3 so QA on launch day is a checklist, not a debate.

Optional: lightweight automation (draft only)

If you live in Gmail and Google Docs, you do not need automation for the first month. When you repeat this weekly, Make can watch a Google Drive folder for new scope docs and create a draft reminder email to yourself—never auto-send to the client. Same discipline as invoice follow-ups: human sends.

QA before you hit Send

• Every date matches your calendar, not the model’s guess.
• Payment terms and deposit match your master contract.
• No tool names the client did not agree to pay for.
• Link to the doc uses https and the client’s correct email domain.

When the client approves (email reply or comment), save a PDF export to your project folder. That PDF is what you reference when someone asks for “one more thing” in week three.

If the client goes quiet for more than a week, send one nudge that restates the approval deadline and what slips if they miss it (launch date moves, deposit non-refundable after X). Keep it factual—scope docs fail when they become guilt trips instead of shared checklists.