07/32proof of conceptBrand-Compliant Documents
Guidebook, Factsheet & EDM Engine
Content in, finished format out: a presentation, guidebook, factsheet or EDM.
What it solves
Presentations, guidebooks, factsheets and EDMs repeat the same brand and product content. One knowledge base feeds all four formats, with a brand check before export.
How it runs
Five steps, input to output
Goes inCopy and source files
- 01
Content in
Copy and source files go in.
- 02
Strategy
The content plan comes first.
- 03
Draft
Agents draft against the reference material in the knowledge base.
- 04
Brand check
The layout is checked against the brand.
- 05
Export
The finished format comes out: a presentation, guidebook, factsheet or EDM.
Comes outA finished presentation, guidebook, factsheet or EDM
What it does
Built with Claude Code and run locally on a detailed knowledge base.
Content goes in and the finished format comes out: a presentation, guidebook, factsheet or EDM.
It follows the Presentation Engine process: strategy first, agents drafting against the reference material, and a brand check before export.
Three decisions
What shaped the build
It runs locally on a knowledge base
Built with Claude Code and run on the laptop, against a detailed knowledge base of brand and product content.
Strategy before drafting
It follows the Presentation Engine process: the content plan is set first, then agents draft against the reference material.
A brand check before export
The layout is checked against the brand before any format is exported.
Built with
7 parts
- Claude Code
- build + agents
- Knowledge base
- brand + product content
- Content input
- copy + source files
- Strategy
- content plan first
- Brand check
- layout against the brand
- Export
- ppt · guidebook · factsheet · EDM
- Local runtime
- runs on the laptop