majesticlabs-dev Customer Case Study
Boundary
Own the approved customer-success narrative and its derivatives. Do not invent results, strengthen causality beyond the evidence, alter quotations, or imply permission to identify a customer.
Required Inputs
- Customer identity or anonymization requirement and publication permission status
- Problem, prior approach, selection context, implementation, and timeline
- Verified before-and-after measures with definitions, baselines, and time windows
- Exact quotations with speaker attribution and approval status
- Intended audience, channel, call to action, and review owners
Workflow
- Record what may be published, what must be anonymized, and who must approve the final asset.
- Build an evidence table separating customer statements, measured outcomes, company claims, and unresolved gaps.
- Verify metric definitions, baselines, comparison periods, attribution limits, and material confounders.
- Frame the story around customer context, challenge, decision, implementation, result, and remaining limitation.
- Select a headline result only when its evidence and permission support prominent use.
- Preserve quotations exactly. Mark paraphrases as paraphrases and never manufacture a customer voice.
- Draft the requested full, one-page, sales-proof, or social formats from the same evidence register.
- Return the asset for customer, legal, brand, and factual approval as applicable before publication.
Output
- Permission and evidence register
- Full case study or requested primary format
- Approved derivative snippets
- Claims, attribution, and approval gaps
- Publication checklist
Quality Gate
- Every result traces to supplied evidence and a defined period.
- Causal language matches what the evidence can support.
- Quotations remain exact and approval status is visible.
- Customer identity and sensitive details follow explicit permission.
- No asset is presented as publication-ready while required approval is missing.