How to turn the outline into a full story

Once you generate the bullet points, expand them into a narrative that explains the problem, solution, and outcome. Mention the chain, strategy type, and why FRB was chosen. Tie the numbers back to the guardrails highlighted across Security, Refund, and Telemetry so reviewers know you operate responsibly.

Suggested structure

1. Background: who the customer is and what chain/market they trade.
2. Challenge: latency, refunds, compliance, or growth blockers.
3. Solution: FRB modules, playbooks, and supporting tools.
4. Results: measurable stats (inclusion %, gas saved) plus qualitative quotes.
5. Next steps: link to FRB pricing or install.

Document each case study in the Showcase or your internal KB so sales, compliance, and partnerships can reuse the proof points.

Example: Prop desk protecting MEV margins

Use the fields above to craft a narrative like this:

Illustrative workflow only: archive release checksums, provider status, final receipts, configuration changes, and incident notes before evaluating operational results.

Sprinkle in measurements (slippage saved, refunds prevented, hours saved) plus quotes from engineers. Potential customers want to know that your team runs the basics well before they trust the strategy alpha.

Distribution checklist

• PDF/Notion version for procurement.
• Short summary slide for investor updates.
• Excerpt for the Showcase page or blog.