Purpose: Amazon-style narrative document for executive decision-making. Replaces slide decks with deep written context.
Instructions:
Pro Tip: Have someone outside your team read it cold. If they can't understand the business case, rewrite before sending to executives.
[Write 1 paragraph (4-6 sentences) covering: What you're proposing, why it matters strategically, quantified business impact, investment required, and recommendation.]
[Describe current state in 2-3 paragraphs. Focus on business limitations, not technical details. What can't we do today that competitors can? What customer needs can't we meet? What revenue opportunities are we missing?]
Example paragraph: "Our current system architecture was built in 2018 for a B2C market with simple feature requirements. It served us well through our initial growth phase, but we've reached an inflection point. Enterprise customers require multi-region deployment for data residency compliance, custom SLA guarantees, and advanced security features like SSO and audit logging. Our current monolith cannot support these requirements without a complete system shutdown for each deployment, making it impossible to offer the uptime guarantees enterprise customers demand. Sales has identified 14 enterprise deals worth $12M in total contract value that are blocked specifically on these technical limitations."
[2-3 paragraphs explaining market shifts, competitive landscape, and urgency. Why is this a strategic imperative vs. nice-to-have?]
| Competitor | Market Position | Technical Capability | Our Gap |
|---|---|---|---|
| [Competitor A] | [Market share/position] | [What they have] | [What we lack] |
| [Competitor B] | [Market share/position] | [What they have] | [What we lack] |
| [Competitor C] | [Market share/position] | [What they have] | [What we lack] |
[2-3 paragraphs with specific customer examples, deal losses, churn risk, or NPS impacts. Make it tangible with real stories and quantified business impact.]
[1-2 paragraphs. What happens if we don't do this? Quantify the downside: lost deals, competitive displacement, technical debt accumulation, increased operational costs, team attrition.]
Example: "If we delay this investment, we project losing $18M in enterprise pipeline over the next 12 months as competitors fill the gap. Our current architecture debt is also compounding—deployment time has increased from 8 hours to 3 weeks over the past year, and engineering productivity is declining 15% quarterly as the team spends more time fighting system limitations than building features. Additionally, three senior engineers have flagged frustration with technical constraints as a retention risk."
[2-3 paragraphs describing WHAT you'll do in business terms. Avoid technical jargon. Focus on outcomes: What capabilities will we gain? How does this solve the problems outlined above?]
| Phase | Timeline | Scope | Business Milestone |
|---|---|---|---|
| Phase 1 | [Q/Month] | [What gets built/migrated] | [Customer-visible or revenue impact] |
| Phase 2 | [Q/Month] | [What gets built/migrated] | [Customer-visible or revenue impact] |
| Phase 3 | [Q/Month] | [What gets built/migrated] | [Customer-visible or revenue impact] |
| Phase 4 | [Q/Month] | [What gets built/migrated] | [Customer-visible or revenue impact] |
[1-2 paragraphs. Who's doing the work? Do we have the talent? Do we need to hire? What about existing product roadmap—what gets deprioritized?]
| Metric | Current State | Target State | Timeline |
|---|---|---|---|
| [Business metric 1] | [Baseline] | [Goal] | [When achieved] |
| [Business metric 2] | [Baseline] | [Goal] | [When achieved] |
| [Business metric 3] | [Baseline] | [Goal] | [When achieved] |
| [Business metric 4] | [Baseline] | [Goal] | [When achieved] |
| Category | Year 1 | Year 2 | Year 3 | Total |
|---|---|---|---|---|
| Costs | ||||
| Implementation | [$X] | [$X] | $0 | [$Total] |
| Annual Operating | [$X] | [$X] | [$X] | [$Total] |
| Total Costs | [$X] | [$X] | [$X] | [$Total] |
| Benefits | ||||
| Revenue Growth | [$X] | [$X] | [$X] | [$Total] |
| Cost Savings | [$X] | [$X] | [$X] | [$Total] |
| Total Benefits | [$X] | [$X] | [$X] | [$Total] |
| Net Benefit | [$X] | [$X] | [$X] | [$Total] |
| Risk | Likelihood | Impact | Mitigation Strategy |
|---|---|---|---|
| [Risk 1] | [High/Med/Low] | [High/Med/Low] | [How we'll prevent or address it] |
| [Risk 2] | [High/Med/Low] | [High/Med/Low] | [How we'll prevent or address it] |
| [Risk 3] | [High/Med/Low] | [High/Med/Low] | [How we'll prevent or address it] |
| [Risk 4] | [High/Med/Low] | [High/Med/Low] | [How we'll prevent or address it] |
[Final paragraph restating the recommendation and specific approval you need. Include decision deadline and next steps.]
Example: "We recommend approval to proceed with Phase 1 implementation starting Q2 2026 at a cost of $1.2M. This requires authorization to: (1) allocate 8 engineers to the project for 6 months, (2) approve Phase 1 budget, and (3) deprioritize Feature X to free capacity. We need a decision by March 1 to meet the Q2 start date and deliver enterprise capabilities by Q4 to capture the holiday season enterprise buying cycle. If approved, we will provide monthly progress updates to the executive team and a comprehensive Phase 2 business case after Phase 1 completion."
Template provided by Tech Exec Insight | techexecinsight.com
Appendices (detailed technical specs, vendor analysis, reference architecture) attached separately