OperatorRadar
DiscoverAI ToolsAI AgentsDecision GuidesPromptsWorkflowsInsightsCategoriesSubmitAbout
Submit a ToolFind My Solution
OperatorRadar

Find the tools, systems, and ideas that move your business forward. Timeless business thinking, rebuilt for the AI era.

Discover

  • Discover
  • AI Tools
  • AI Agents
  • Software
  • Agencies
  • Categories

Decide

  • Decision Guides
  • Compare
  • Find My Solution
  • Insights

Execute

  • Prompts
  • Workflows
  • Submit a Tool
  • Contact

Company

  • About
  • Privacy
  • Terms

© 2026 OperatorRadar. All rights reserved.

Built by Ekofi

  1. Home
  2. Prompts
  3. Decision Memo Writer
Featured
beginner
Claude or ChatGPT (verify current model choice)
v1.0.0

Decision Memo Writer

Generate a structured one-page decision memo with options, risk analysis, and a clear recommendation—ready to share with your team or board.

Full prompt

You are a business operator writing a decision memo for your team and leadership.

Write a one-page decision memo on the following:

**Decision:** {{decision_topic}}

**Context:** {{business_context}}

**Constraints:** {{constraints_and_timeline}}

**Stakeholders:** {{key_stakeholders}}

Structure the memo as follows:

1. **Decision Statement** (1 sentence): What exactly are we deciding?

2. **Options** (2–3 options): For each option, include:
   - Brief description
   - Key pros (2–3)
   - Key cons (2–3)
   - Estimated cost or resource impact

3. **Risks & Mitigants** (2–3 risks): For each risk, state the mitigation or acceptance.

4. **Recommendation**: Which option and why. Include the one strongest reason.

5. **Next Steps**: 1–2 concrete actions and owner.

Keep language clear and direct. Avoid jargon. Use numbers where available. Write as if the reader has 2 minutes.

How to use

1. Fill in the four input fields with your decision context. Be specific—vague inputs produce vague memos. 2. Run the prompt. 3. Copy the output into a Google Doc or Notion. 4. Add any company-specific financial data or timeline details. 5. Share with stakeholders 24 hours before discussion to allow async review. 6. Use the memo as the agenda for a 15–30 minute decision meeting.

Example input

**Decision Topic:** Expand to UK market vs. double down on US growth

**Business Context:** We're a US-based B2B SaaS company at $5M ARR. UK customers are requesting local support and GDPR compliance. We have two acquisition offers from UK-based competitors.

**Constraints:** $500K budget available. 6-month runway to decide. Must not distract from US product roadmap.

**Key Stakeholders:** CEO, VP Product, VP Sales, Board investor

Example output

**DECISION MEMO: UK Market Entry**

**Decision:** Do we launch a UK subsidiary with local support and GDPR compliance, double down on US expansion, or partner with a UK reseller?

**Options:**

*Option A: Launch UK subsidiary*
- Pros: Direct customer control, premium pricing, long-term moat
- Cons: $400K upfront cost, 4-month setup, diverts leadership attention
- Cost: $400K year 1, $200K ongoing

*Option B: US-only focus*
- Pros: Concentrated resources, faster US growth, lower risk
- Cons: Lose UK deals (~$200K ARR), competitors may enter
- Cost: Opportunity cost only

*Option C: UK reseller partnership*
- Pros: $50K cost, fast to market, low risk
- Cons: Lower margins (30% vs. 70%), limited brand control
- Cost: $50K + 30% revenue share

**Risks:**
- UK market smaller than expected → Mitigate: Validate 10 customers first
- Distraction from US roadmap → Mitigate: Hire dedicated UK ops lead
- GDPR compliance complexity → Mitigate: Budget $30K for legal/infrastructure

**Recommendation:** Option C (reseller partnership). Validates UK demand at low cost and risk. If reseller hits $500K ARR in 12 months, we revisit Option A.

**Next Steps:**
1. VP Sales: Identify and pitch 3 UK resellers by Feb 15
2. CEO: Approve reseller agreement template by Feb 28

Customization tips

  • Adjust the number of options based on complexity—2 options for simple decisions, 3–4 for strategic ones.
  • Add a 'Financial Summary' table if the decision involves significant budget or revenue impact.
  • Include a 'Decision Criteria' section if your team values specific factors (e.g., speed to market, risk tolerance, team capacity).
  • For time-sensitive decisions, add a 'Sunset Clause': 'We will revisit this decision in 6 months if X metric doesn't improve.'
  • If stakeholders disagree on priorities, add a 'Assumptions' section to surface disagreement early.
  • For technical decisions, replace 'Estimated cost' with 'Engineering effort (weeks)' and 'Maintenance burden.'