The point where work gets scattered
Briefs mix goals, preferences, background and possible ideas. A proposal becomes unreliable when an appealing example is mistaken for required work or an AI draft fills missing facts with plausible details.
Sort the brief into facts, preferences and questions
Read the actual brief and relevant conversation. Extract the problem, audience, desired output, reviewer, intended date and known constraints. Keep the client’s wording where interpretation matters. Separate a confirmed requirement such as ‘three service pages’ from a preference such as ‘we like animation’ and an unresolved question such as who supplies the copy.
For a website project, unknowns might include the page list, content ownership, existing platform, accessibility expectations, integration needs and launch responsibilities. Ask the questions that change the scope first. A long questionnaire is not always necessary; a focused clarification about an integration can be more important than another paragraph of brand adjectives.
- Confirmed: what the client actually requested.
- Proposed: your recommended approach, subject to review.
- Unknown: information that could change work, price or timing.
Translate goals into inspectable deliverables
‘Improve our online presence’ is a goal, not a deliverable. A concrete first phase might be five named website pages, one responsive design direction and two consolidated design review rounds. State what the client supplies and what is excluded. If a requested result depends on traffic, sales activity or other factors outside the project, do not guarantee that result.
Sample wording: ‘You want visitors to understand the three services and send a useful enquiry. I propose a five-page site with an enquiry form. You supply approved copy and images. Paid advertising, ongoing content production and hosting migration are excluded. We will review the page list before confirming the price.’ This gives the client something specific to correct.
Connect delivery to inputs, review and price
Build the sequence around real dependencies: discovery, client inputs, first draft, review, revisions and delivery. Name who makes the client decision and how feedback will be collected. State timing relative to supplied materials when a fixed date would otherwise be misleading. Identify where additional work would require a new review.
Prepare the pricing from your actual scope and assumptions, not from a made-up industry average. Explain the payment schedule you are proposing and distinguish it from the final agreement. If a critical requirement is still unknown, offer a discovery phase, a range with explicit assumptions or a request for clarification rather than disguising uncertainty as a final quotation.
Inspect the draft against the source brief
Read each proposed deliverable and ask where it came from. Delete invented client facts, unsupported results and unnecessary private details. Check that prices and dates agree across sections. Verify names and the review contact. Make exclusions understandable: ‘no new photography’ is more useful than a broad sentence that says anything not mentioned is excluded.
Send a short review request: ‘Please check the page list, your content responsibilities and the review schedule. The open question is whether booking integration belongs in this phase. Once that is answered, I can confirm the final scope and price.’ Keep the reviewed proposal version and actual reply. A draft is a preparation step, not client acceptance or payment approval.
Keep the context with the conversation
Choose the brief and conversation context you want to use in Messages, then ask for a scope outline or clarification questions. Review the wording against the sources. Keep final document preparation in your existing process. Business can help you pick up the relationship context, while the client still reviews the actual offer and any next action.
Understand your Twin · See Business access and metered AI usage