The Kickoff Call Should Confirm the Scope — Not Hunt for It
Agencies lose the first client meeting to questions a form could have asked the week before. Budgets get skimmed, deliverables stay mushy, and the estimate that follows is built on half the facts. Sending a structured discovery brief before kickoff inverts the meeting: the client arrives having already committed their objectives to writing, and the conversation starts at here is what you told us instead of so, tell us about yourselves.
The brief takes a client about eight minutes and ends with both sides holding the same document — objectives, deliverables, constraints, and the people who sign the checks.
What the Brief Extracts
| Section | The question underneath | Input format |
|---|---|---|
| Objective | What changes in your business if this succeeds? | Long text |
| Deliverables | What will you expect to hold at the end? | Multiple choice with add-ons |
| Constraints | Fixed dates, fixed budgets, compliance needs? | Dropdowns plus open text |
| Approvals | Who signs, who uses it, who can kill it? | Role picker |
| Success measure | How will we judge this in three months? | A target number or a sentence |
| Reference point | A project you admired — anywhere | Website link |
Keep the mandatory list short — the objective, deliverables, and approvals rows earn required status; the rest can breathe.
From Brief to Estimate in One Pass
- The inquiry lands; the brief goes out the same day while intent is warm — a shareable link works over email or DM.
- Finished briefs collect in the responses view for review before the call.
- The estimate is built against the client’s own stated deliverables — scope debates shrink when their words define the scope.
- Kickoff opens with the brief on screen: the meeting confirms and refines instead of discovering.
Branching by Engagement Type
A brand engagement and a systems migration share a client but not a question set. Ask the engagement type early and let per-question logic reveal only the relevant follow-ups — creative work gets audience and positioning prompts; build work gets technical constraints and integration lists. One link serves every service line, and each client answers only what applies to them.
When the Brief Sits Half-Finished
Busy stakeholders abandon forms mid-sentence — not from disinterest, but interruptions. Partial submissions preserve whatever was typed so a nudge finishes the brief instead of restarting it (plan feature; the pricing page has details). Pair that with a notification to your own inbox so no completed brief sits unread while a competitor calls first.
Frequently Asked Questions
How long should a discovery brief be?
Eight to twelve questions. Past fifteen, completion sags and answers drift from considered to automatic — and automatic answers build bad estimates.
The client says they don't know their scope. Now what?
That’s a finding, not a failure. The objective and success-measure questions work even when deliverables are fuzzy — and if the fog is real, a paid discovery phase is the honest thing to propose.
Who fills it in — client or account manager?
Client writes, account manager reads. The moment we transcribe for them, our words replace theirs, and the estimate inherits the distortion.
Can each service line run its own brief?
Yes — duplicate the form per service line and keep the core five questions identical so cross-line comparisons stay honest. Nearby formats live in the consultation templates family, with estimate forms covering the quoting step that follows.