Prompt Details
Model
(claude-4-6-sonnet)
Token size
434
Example input
[SITUATION OR TOPIC FOR THE BRIEF]: Whether to pursue European expansion in Q1 given limited engineering capacity and 18-month runway
[KEY FACTS DATA POINTS AND CONTEXT]: 4.2M ARR, 94% US customers, 11 European inbound inquiries in 6 months with no outbound effort, GDPR compliance requires 4-6 months and 180k investment, engineering at capacity through Q2, nearest competitor has 3% European market share
[BUSINESS GOALS AND CONSTRAINTS]: Grow ARR 40% this year, maintain 18+ month runway, not distract engineering from core roadmap through Q2
[KEY STAKEHOLDERS AND THEIR INTERESTS]: Board requires 500k European ARR before approving dedicated hire; BD lead has Germany and Netherlands connections; 11 potential European customers waiting; Engineering team at full capacity
[DECISION OR ACTION NEEDED]: Should we greenlight a European expansion pilot in Q1 or wait until Q3 when engineering has capacity for GDPR compliance work
Example output
HEADLINE SUMMARY
A European expansion in Q1 is premature given current engineering constraints and runway — but the inbound demand signals are too strong to ignore. The right move is a structured 60-day pilot with 2-3 anchor customers that generates real data without committing engineering bandwidth we don't have.
SITUATION ANALYSIS
The company has $4.2M ARR, 94% US-based, and 18 months runway. In the last 6 months, 11 European companies reached out without any outbound effort — a demand signal that's difficult to manufacture artificially. The nearest competitor has only 3% European market share, suggesting the market is genuinely open. However, GDPR compliance requires 4-6 months of engineering work and $180k investment, and the engineering team is at capacity through Q2. The board requires $500k in European ARR before approving a dedicated hire.
CRITICAL FINDINGS
Opportunity: 11 inbound leads in 6 months with zero outbound effort suggests organic product-market fit in Europe. This doesn't happen by accident.
Risk: Engineering is at capacity through Q2. Any formal European expansion requiring GDPR compliance work would delay the existing product roadmap by 4-6 months.
Dependency: The board won't approve a European hire until $500k ARR is established — meaning we need European revenue before we can resource European growth properly.
Assumption: We're assuming GDPR compliance is required before signing European customers. This needs legal verification — some B2B SaaS categories can operate under standard data processing agreements initially.
Key asset: The BD lead with Germany and Netherlands connections is underutilized. A structured pilot using existing relationships costs almost nothing.
STRATEGIC IMPLICATIONS
If nothing changes: the 11 inbound leads go cold, a competitor moves in while European markets are open, and we face a crowded landscape in 12-18 months when we're finally ready to expand. What this situation makes possible: a low-cost pilot that generates the $500k ARR needed to unlock board approval for a European hire — creating a self-funding expansion path that doesn't require a big budget commitment now.
RISK RADAR
Risk 1 — GDPR non-compliance exposure: Triggered if we sign European customers without adequate controls. Mitigation: Legal review of minimum viable GDPR requirements before signing any European customer.
Risk 2 — Engineering distraction from pilot customers: Triggered if pilot customers require significant customization. Mitigation: Only accept pilot customers who fit the existing product tightly; no custom development commitments.
Risk 3 — Pilot fails to reach $500k ARR threshold: Mitigation: Select pilot customers with clear expansion potential; include expansion conversation at 60-day mark.
THREE OPTIONS
Conservative — Delay until Q3: Wait until engineering finishes current roadmap, then begin formal GDPR compliance work. Upside: no distraction. Downside: market window may close; competitor could establish first-mover advantage.
Balanced — 60-Day Structured Pilot (Recommended): Engage 2-3 of the 11 inbound leads through the BD contact. Get legal clarity on minimum GDPR requirements. No new engineering work required. Upside: real data, potential for first European ARR, low risk.
Aggressive — Begin Formal European Expansion Now: Allocate engineering to GDPR compliance immediately, begin hiring for European BD. Cost: $180k and 4-6 months of engineering focus. Downside: derails Q2 roadmap, exceeds budget authority without board approval.
RECOMMENDED PATH
The Balanced option. The 11 inbound leads represent a rare opportunity to validate European demand with nearly zero investment. A 2-3 customer pilot managed through the existing BD contact gives us real ARR data to take back to the board within 60-90 days. Legal review of minimum GDPR requirements should happen immediately — it's a 1-2 week exercise that determines whether the pilot is viable.
IMMEDIATE NEXT STEPS
1. Legal to assess minimum GDPR requirements for a limited pilot — owner: General Counsel, deadline: 7 days
2. BD lead to re-engage the 3 strongest inbound leads and schedule discovery calls — owner: BD Lead, deadline: 5 days
3. CEO to brief board on pilot intent before any agreements are signed — owner: CEO, deadline: 10 days
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-6-SONNET
Executives don't need more information — they need the right information, structured for a decision. This Claude prompt transforms raw facts, data, and context into a tight intelligence brief that surfaces what matters, identifies what's at risk, and recommends a clear path forward. Modeled on how top consulting firms present to C-suite audiences. Use it for leadership updates, board prep, strategic decisions, or any situation where you need to communicate complexity without losing your audience.
...more
Added 5 days ago
