Build a Brand Positioning and Messaging Kit with an Editable PowerPoint
Turn a reviewed brand brief into positioning, evidence-linked channel drafts and a practical rollout. Test the fictional sample, edit the deck and rebuild the actual PowerPoint.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Use Brand Strategy Studio to prepare positioning and a messaging handoff from my reviewed facts. Start with the fictional example, reconcile sources, channel drafts and consecutive rollout weeks. Keep hypotheses and targets labeled. Edit one slide, export edits JSON and rebuild PowerPoint into a new folder; verify that strategy source files are unchanged by presentation-only edits. Do not publish messages or call a paid API.
What does a brand positioning kit deliver?
Brand Strategy Studio v1.0.0 turns your reviewed audience, alternatives, promise and supporting evidence into a browser review room, native editable PowerPoint and source-linked strategy files. It suits a positioning decision or brand-team handoff. The individual package costs USD 4.99; Python 3.10+ and the pinned python-pptx dependency build the files locally without a paid API.
Choose this workflow when the decision is what to promise, to whom and with which supporting proof. Use a general presentation workflow for unrelated slide content. The builder formats authored strategy; it does not conduct market research, validate customer demand or publish channel messages.
Prepare the positioning before choosing the visual theme
Read SKILL.md and references/input.md. Begin with examples/brand.json and rewrite the actual strategy, rather than only changing the brand name. A known evidence ID makes a reference traceable, not true. Review whether its note supports the promise. Alternative clarity/guidance scores are editorial estimates; measurement targets are future goals, not achieved results.
| Input | A useful reviewed entry |
|---|---|
| Audience and decision | One audience, its situation, the job and the intended decision |
| Evidence register | Unique IDs with observed, hypothesis or fictional status and supporting notes |
| Positioning | For whom, which need, what promise and why this differs |
| Messaging pillars and channels | Reasons to believe, linked evidence, full draft copy and a specific next action |
| Rollout and measures | Named owners, consecutive phase weeks, baseline and target methods |
Build and reconcile the Root & Ritual practice
Run these commands from the complete installed package. The bundled Root & Ritual business is fictional and needs --demo. Choose a new output directory. The builder does not overwrite an existing delivery. On Windows use .venv\Scripts\python.exe after creating the environment. Installing dependencies needs internet; generation makes no provider calls.
- Open brand-room/index.html and review all 12 slides, speaker notes and the overview. Read the strategy and CSV files alongside the presentation.
- The example has four channel drafts and three consecutive phases: weeks 1–3, 4–8 and 9–12. Check touchpoints.csv, not only the slide preview.
- quality.json reports zero observed, one hypothesis and four fictional source records. The example is not customer research. Verify all listed SHA-256 hashes in delivery-manifest.json.
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
.venv/bin/python scripts/build-brand.py --input examples/brand.json --demo --output ./brand-roomEdit the deck and rebuild the actual PowerPoint
Use Edit this slide to change one title, summary or speaker note, then apply it. Download edits JSON and copy the downloaded deck-edits.json into the installed directory, or use its absolute path in the command. Rebuild into a fresh folder. The existing PowerPoint download remains the previously generated file until you rebuild.
Compare the edited text in deck.json, speaker-notes.md and the native PowerPoint objects. Presentation edits change deck text and theme; they do not rewrite brand-brief.md, messaging.csv or the original strategy. Change the input JSON when the actual positioning changes, then rebuild and review all linked claims.
.venv/bin/python scripts/build-brand.py --input examples/brand.json --demo --edits deck-edits.json --output ./brand-revisedHand off a decision, its sources and one next test
Deliver the browser room, presentation.pptx, speaker notes, positioning brief, audiences, voice guide, complete channel drafts, evidence/alternatives/touchpoint CSVs, measurement plan, input and integrity manifest. Inspect native text, notes and long copy in the intended presentation application before using the deck with a team.
For real work, set fictional:false in your reviewed input and omit --demo. Preserve unresolved assumptions and the owner of the next pilot. No email, ad or website is sent or published by the package; agent/model access is separate from package access.
Build a factual launch kit after approving the brand claims