| name | capability-collateral |
| description | Produce and refresh branded, single-page capability one-pagers, pamphlets, and management decks/plans — brief → who/what/why-us + concrete proof → segment tailoring → brand/voice + claims check → clean layout → render HTML to PDF. Reuses an approved-claims library so claims are written once and reused (incl. proposal/expert-witness support). |
| version | 1.0.0 |
| category | marketing |
| applies-to | ["hermes","claude","codex","gemini"] |
| trigger | manual |
| auto_execute | false |
| tags | ["marketing","collateral","one-pager","pamphlet","pdf","branding","proposal"] |
Capability Collateral
The PRODUCE stage of the marketing operating system (see ../INDEX.md).
Turns the campaign message + proof into sendable, branded assets.
Use when
The user asks for a "one-pager", "capability statement", "pamphlet/brochure", "leave-behind",
"work-sample sheet", or a "PDF for management/clients", or to refresh existing collateral.
Goal
A single-page (or tight multi-page), on-brand asset that says who/what/why-us with
concrete proof, tailored to its audience, and rendered to a clean PDF — reusing pre-cleared
claims rather than re-writing them.
Inputs to gather
- Brief: audience/segment, use-context (cold intro vs live pursuit), the win-theme.
- Proof: past performance, metrics, credentials, testimonials, work samples — pulled
from
../_shared/claims-library.md where possible.
- Brand assets: logo, palette, contact block, voice.
- Output format: web page, print PDF, or both.
Method
- Write the brief (one paragraph): who it's for, where it's used, the single win-theme.
- Draft the spine: headline → who we are (credibility line) → what we do (scoped) →
why us (differentiators + proof) → one clear CTA.
- Pull proof from the claims library; if a claim isn't cleared, flag it — don't invent
numbers or imply work/relationships that don't exist.
- Tailor to the segment (operators vs EPCs vs legal/insurance vs renewables) — a general
version plus a targeted variant for live pursuits.
- Lay out in the house style: keep page 1 short/scannable; detail on following pages;
use cards, a hooks/funnel diagram, or a comparison table where it earns its space.
- Brand + voice + accuracy check.
- Render to PDF via headless Chrome — see
references/html-to-pdf.md.
- Version + store in the collateral library; provide a clickable link to the PDF.
Output
HTML source + rendered PDF (and any QR/links). Store both in the engagement's collateral
folder; keep the HTML so it can be re-rendered and versioned.
Definition of done
