# Sales collateral storyline
Create the argument and proof structure for buyer-facing sales material. Match the format to the buyer's actual need; a short email does not need a long PDF. This method produces a storyline and copy plan, not a published asset.
Workflow
1. Identify the audience, their decision, the format, the approved offer, and the action the material should support. 2. Separate verified claims, approved proof, assumptions, and proof gaps. A result cannot be named, anonymized, or repurposed without permission. 3. Build the narrative arc: buyer context, problem or desired outcome, the practical approach, scoped proof, customer responsibilities, and a clear next action. 4. Write claim-level evidence notes. Quantified results need scope, source, and conditions; do not turn a single result into a universal promise. 5. Recommend the smallest effective format and an accessible, readable page or message structure. Use a design or publishing workflow only when the user requests the actual artifact. 6. Run a final claim check: no fabricated logos, testimonials, case studies, render results, or publication status.
For a multi-page brief, use this default arc: outcome; problem or point of view; service explanation; scope; initial work; progress and measurement; evidence; people and ownership; and the next decision.
Story and production handoff
Start with the buyer decision, not the format. Sequence the material from the buyer’s current situation and desired outcome through the practical work, bounded proof, customer responsibilities, and CTA. For each proof item record scope, source, conditions, permission status, and whether it is public, approved, unavailable, or internal-only. Keep a content outline with section purpose, claim, evidence, and owner for any missing input.
If a user requests an artifact, propose the appropriate design, accessibility, rendering, and publishing checks as separate host work. Do not report visual QA, upload, publication, or link preservation without retained evidence. That work should render every page, inspect full-page and close-up text fit, check headings, repeated layout, CTA placement, link targets, and the downloaded artifact before it is called complete.
Output
Return an audience statement, one-sentence promise, ordered storyline, proof plan, content outline, CTA, and a list of missing evidence or approvals.
Boundaries
Do not publish, upload, send, claim legal clearance, or claim visual QA that was not actually performed.