Build a Client Brief

Context, setup, and planning

1. Identify the client and the piece of work the brief should cover.
2. Ask whether the user already has an account process or brief format they want followed, or wants help shaping one.
3. Build a picture of what the team delivers for this client and where the client's data lives. Ask whether Strawberry may look through relevant connected apps for existing context. Depending on what exists, useful sources may include:
   • kickoff or onboarding documents;
   • the scope of work, proposal, or winning pitch;
   • discovery-call notes or transcripts;
   • relevant email threads;
   • prior reports and client-ready deliverables.
4. If the intended voice or presentation style is not already clear, use strawberry/general/learn-writing-style with approved sent emails or client-ready examples.
5. Keep each client's sources and facts separate. Never carry another client's data, strategy, or brand details into this brief.
6. Ask only for material gaps or contradictions that cannot be resolved from the available context.

Build the brief

Capture the information that is actually supported:

• business context and desired outcome;
• audience, market, and important customer context;
• goals, KPIs, and how success will be judged;
• deliverables, scope, exclusions, milestones, and owners;
• stakeholders, reviewers, and communication cadence;
• brand voice, examples, and presentation preferences;
• connected systems, data locations, and access boundaries;
• legal, privacy, or client-specific restrictions;
• open questions, dependencies, and risks.

Keep source links beside decisions that may need to be checked. Distinguish agreed facts, interpretations, and unresolved questions.

Review and preserve

1. Present a concise, reviewable brief rather than a transcript dump.
2. Call out conflicting instructions and scope creep explicitly.
3. Let the user correct the brief before it becomes the basis for delivery or automation.
4. Once accepted, save it in the agreed client location and offer to preserve the format as a user-owned skill or onboarding checklist.
5. Reuse the structure or process across accounts only after replacing the sources, goals, brand voice, restrictions, and other client-specific context.

Suggested outcome

Create a client-ready internal brief that gives the team one reliable view of the account without inventing missing details. It should be easy to scan, linked to its sources, explicit about restrictions, and safe to reuse only for that client.