Strategy brief template

A good strategy brief does one job: make the direction clear enough that people can make decisions without rereading every source document. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.

Claude can turn research notes, goals, constraints, audience insights, options, risks, and stakeholder feedback into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.

What to include in the strategy brief

• The goal, audience, and current situation.
• The strategic recommendation and why it is the best path.
• Options considered and the tradeoffs behind the choice.
• Risks, dependencies, and open questions.
• Milestones, owners, and the next decision.

Prompt to use in Claude

How to create it with Send

Give Claude research notes, goals, constraints, audience insights, options, risks, and stakeholder feedback, plus any constraints, examples, or audience notes that matter. Ask it to create the strategy brief with the Send connector so the output becomes a page instead of another loose document.

After you share it, Send helps you see whether clients and internal teams open it, come back to it, or share it internally. You can update the same link when details change.

Strategy brief structure

1. 1

   Situation

   The goal, context, audience, and constraints.

2. 2

   Recommendation

   The direction, rationale, and tradeoffs.

3. 3

   Risks and dependencies

   What could block the plan and what needs to be true.

4. 4

   Plan

   Milestones, owners, timing, and the next decision.

Why send a strategy brief as a page

Strategy work loses force when the reasoning is scattered across notes and slides. A Send page gives everyone one current version of the direction and lets you see whether the right people have read it.

Frequently asked questions