Send Post-Discovery Client Homework With AI (Google Forms + Gmail)

Why a discovery homework questionnaire beats another “quick call”

You already send a same-day post-discovery recap. That email confirms what you heard and lists open questions. But some prospects stay friendly and vague: “Send me a proposal when you can.”

Before you spend an evening turning call notes into a scope document clients approve, ask them to do homework. A short Google Forms questionnaire sent through Gmail gives you:

• Written answers you can cite (fewer “I never said that” moments)
• Budget, timeline, and stakeholder signals before you price
• A polite filter: buyers who will not spend fifteen minutes on a form rarely approve a multi-page scope

This guide is for freelancers, consultants, and micro-agencies. It uses ChatGPT, Google Forms, and Gmail. You stay in control; AI drafts questions and summaries—you send everything.

When to send discovery homework

Situation	Send homework?
Recap sent, mutual action plan names “client shares examples/docs”	Yes — replace vague homework with a form
Open questions from recap block pricing	Yes — turn each blocker into a form field
Prospect asked for a ballpark proposal with almost no detail	Yes — form first, proposal second
You already have SOW-level notes and a verbal “go” on scope	No — skip to the scope doc
Tire-kicker who ghosted the recap	Optional — one form + one nudge, then archive

If you have not done the pre-client call brief yet, do that before the call; homework comes after the call and recap.

What to ask (six blocks, keep it under 20 questions)

Group fields so ChatGPT—and your future self—can map answers into a scope outline:

1. Outcomes — “What must be true in 90 days for this to feel successful?”
2. Users & decision makers — who uses the deliverable, who signs, who can say no
3. Current tools & data — CRM, spreadsheets, legacy systems, where files live today
4. Constraints — launch date, budget band (ranges are fine), compliance, brand rules
5. Examples & anti-examples — links, screenshots, “we hate when vendors do X”
6. Logistics — meeting cadence, timezone, preferred channel, procurement steps

For each open question in your recap, add one required field. Optional fields are for nice-to-have context.

End-to-end flow

Step 1 — Turn recap gaps into a question list (ChatGPT)

Paste your recap’s open questions and assumptions into ChatGPT with this prompt:

You are helping a freelancer write a client discovery homework form after a sales call.

Context: I already sent a recap email. I must NOT duplicate what the client already confirmed in writing.

Open questions from recap:
[PASTE]

Assumptions that need confirmation:
[PASTE]

Task:
1. Propose 12-18 form questions in plain English for a non-technical buyer.
2. Mark each as required or optional.
3. Suggest answer type: short text, paragraph, multiple choice, checkboxes, file upload, or URL.
4. Flag any question that sounds like legal advice or security audit—rephrase to ask for their existing policy or owner name instead.

Output as a table: Section | Question | Type | Required (Y/N) | Why it matters for scope

Review every row. Delete questions that sound like interrogation. Merge duplicates. Your name goes on the form description, not the model’s.

Step 2 — Build the Google Form

1. Create a new form: title like “{Client} — discovery homework (15 min)”.
2. Add a short description: recap link, deadline, and “save progress and submit when done.”
3. Use sections matching the six blocks above.
4. Turn on Collect email addresses if you need accountability (optional for B2B if they forward internally).
5. Set Limit to 1 response only if one coordinator owns answers; otherwise allow multiple for team input.
6. Add a final question: “Anything else we should know before drafting scope?”
7. Click Preview, submit a fake response, and confirm required-field validation.

Copy the form link and the edit link into a Google Doc or your CRM note so you can update questions without resending the wrong URL.

Step 3 — Send the Gmail request (template)

Subject: {Client} — quick discovery homework before scope (15 min)

Hi {Name},

Thanks again for today's call. As in my recap, I'm holding off on a full scope until we lock a few details.

Please complete this short form by {DATE}: {FORM_LINK}

It should take about 15 minutes. If something does not apply, write "N/A" so I know you saw the question.

Once it's in, I'll turn your answers into a written scope for your review—or tell you honestly if we're not a fit.

Best,
{Your name}

Send within 48 hours of the recap while context is fresh. If they need a nudge, reply on the same thread with one sentence and the link again—no guilt trips.

Step 4 — Synthesize responses for your scope doc (ChatGPT)

When responses arrive, export from Google Forms (Sheets or CSV). Prompt:

You are a freelance solutions consultant preparing inputs for a scope document.

Client name: {CLIENT}
Form responses (tab-separated or pasted rows):
[PASTE]

Task:
1. List confirmed facts vs. still-unknown items.
2. Extract: success criteria, in-scope candidates, explicit out-of-scope hints, risks, and stakeholders.
3. Propose 3 scope options (small / medium / large) with tradeoffs—not prices, just boundaries.
4. Draft 5 bullets I should clarify on a 20-minute alignment call before I write the full scope.

Tone: neutral, professional. Do not invent deliverables the client did not imply.

Paste the output into the top of your scope draft doc. Unknowns become the agenda for a short call—or reasons to decline.

Step 5 — Quality gates before you write the full scope

• Every required open question from the recap has an answer or explicit “unknown + owner”
• Budget and timeline are ranges, not silence
• At least one example link or file for visual/UX expectations (if design is in play)
• Named decision maker for scope approval
• Client acknowledged out of scope for now items from the recap

If gates fail after one nudge, pause. A commercial proposal without this foundation often becomes endless free consulting.

Common mistakes

• Twenty-page surveys — kills response rate; cap at ~20 questions.
• Pricing fields — ask for budget bands, not “what should this cost?”
• Security questionnaires you are not qualified to answer—ask who owns IT review instead.
• Rewriting the recap in the form—only ask for net-new detail.

What you should have when you are done

A timestamped Google Form response set, a ChatGPT synthesis saved next to your call notes, and a clear go/no-go on drafting the full scope. Homework does not replace a recap—it feeds the scope doc with client-owned words.

Next: Turn discovery call notes into a scope document using the form export as your primary source.