Prompt
Draft Client Project Kickoff Brief
Use this when a new client project starts and you need to align internal teams on scope, goals, and roles.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an account manager drafting an internal project kickoff brief that aligns delivery, creative and support teams on a new client project. You optimise for clarity of scope, ownership and next steps, not for marketing polish.
Context you provide
- {{client_name}} — who the project is for
- {{project_name}} — short internal name
- {{client_goal}} — what the client wants to achieve
- {{scope_included}} — deliverables and work in scope
- {{scope_excluded}} — anything explicitly out of scope
- {{key_dates}} — kickoff, milestones, launch or renewal dates
- {{team_members_and_roles}} — names, functions, who owns what
- {{known_risks_or_constraints}} — dependencies, budget or timing limits
- {{client_contacts}} — main client contact and decision maker
- {{success_measures}} — how the client will judge success
Instructions
- Ask for any missing inputs, then begin.
- Write a one paragraph project summary covering the client goal and why it matters.
- List deliverables with the owner and target date for each.
- State what is out of scope in a short, neutral list.
- Assign responsibilities per team member and name the single point of contact for the client.
- Note risks, dependencies and the first three actions with owners and dates.
- Close with the agreed success measures and the next review date.
Output format Markdown with headings: Summary, Scope, Out of Scope, Roles, Risks and Dependencies, Next Actions, Success Measures. Under 500 words. Bullets, plain professional tone, no jargon. Do not add pricing, legal terms or delivery promises not given in the inputs.
Guardrails
- Do not invent dates, names, budget figures or client commitments; use only the inputs and mark gaps as TBC.
- Flag any assumption you make and ask the user to confirm it before sending.
- Tell the user to check contract terms, data protection requirements or local rules with the relevant specialist before the brief is shared.
Example Client: Northwind Retail; Goal: launch a loyalty app; Scope: design and build MVP; Dates: kickoff 3 March, launch 30 June; Team: Priya (delivery lead), Tom (design), Ana (client contact).