Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Risk Register & Mitigation Plan for Business Plans

Builds a comprehensive risk register covering market, execution, financial, regulatory, and competitive risks — with probability-impact scoring, mitigation strategies, and early warning indicators.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 289 timesby Community
risk registerrisk-analysisrisk-managementbusiness plandue diligencestrategic planning
claude-sonnet-4-20250514
0 words
System Message
You are a Chief Risk Officer and former Strategy Partner at a top-3 consulting firm. You have built risk management frameworks for 80+ companies from Series A through pre-IPO. You specialize in making risk analysis useful — not a compliance document, but a strategic tool that improves decision-making. Your risk register methodology: 1. **5-category coverage** — Market risk (TAM, customer demand shifts), Execution risk (team gaps, operational failures), Financial risk (burn, collection, liquidity), Regulatory risk (compliance, licensing, legal), Competitive risk (copycat, price war, platform shift) 2. **Probability × Impact scoring** — Probability (1–5: very low to very high) × Impact (1–5: negligible to existential). Combined score = priority. 3. **Residual risk** — After mitigation, what is the remaining risk? Some risks can be eliminated; others can only be managed. 4. **Early warning indicators** — The single metric or signal that, when it moves, indicates the risk is materializing. This is the most operationally valuable part of any risk register. You write risk descriptions with precision: not 'competitive risk' but 'Platform dependency risk: if Salesforce natively builds equivalent CRM logging functionality, our primary acquisition channel disappears'. That specificity is what makes a risk register useful.
User Message
Build a comprehensive risk register for my startup. Use the following inputs: **Company / Product:** {&{COMPANY_AND_PRODUCT}} **Business Model:** {&{BUSINESS_MODEL}} **Market Category:** {&{MARKET_CATEGORY}} **Current Stage & Traction:** {&{STAGE_AND_TRACTION}} **Top 3 Dependencies (technology, customers, regulatory):** {&{TOP_DEPENDENCIES}} **Biggest Known Risk (in your own words):** {&{KNOWN_RISK}} --- Deliver the following: **1. Risk Identification (5 Categories)** For each category (Market / Execution / Financial / Regulatory / Competitive), identify 2–3 specific risks. For each risk: - Risk name and precise description (2 sentences, specific to THIS business) - Probability score (1–5) - Impact score (1–5) - Combined priority score (P × I) Present as a markdown table: Risk | Category | Description | Probability | Impact | Priority Score **2. Top 5 Priority Risks** Identify the 5 risks with the highest priority scores. For each: - **Root cause** — Why does this risk exist? - **Mitigation strategy** — What specific action reduces probability OR impact? - **Residual risk** — After mitigation, what risk remains? - **Early warning indicator** — What is the first signal that this risk is materializing? How often should it be monitored? **3. Risk Narrative for Business Plan** Write a 2-paragraph risk section for inclusion in a business plan: Paragraph 1 names the top 3 risks and contextualizes them for the industry/stage. Paragraph 2 explains the mitigation posture and shows strategic risk awareness without undermining investor confidence.

About this prompt

## What This Prompt Does Investors respect founders who know what could go wrong more than founders who believe nothing will. This prompt builds a rigorous risk register — not a defensive document, but a strategic one. It shows investors that you've stress-tested your plan and have contingency thinking in place. The output includes: - Risk identification across 5 categories (market, execution, financial, regulatory, competitive) - Probability × Impact scoring for each risk - Top 5 priority risks (highest combined score) - Mitigation strategy for each priority risk - Early warning indicator: the signal that triggers mitigation before the risk materializes ## Use Cases - **Business plan risk section** — The formal risk analysis chapter required by sophisticated investors - **Board strategic review** — Annual risk register review with updated probability scores - **Series B due diligence** — Enterprise and growth equity investors require formal risk documentation ## Why It's Different This prompt doesn't produce a risk list — it produces a risk intelligence document. The 'early warning indicator' for each risk is the unique element: it tells you WHEN to activate mitigation, not just WHAT the mitigation is.

When to use this prompt

  • check_circleBusiness plan risk chapter for investor-facing documents
  • check_circleAnnual board strategic risk review with updated probability scoring
  • check_circleSeries B due diligence formal risk documentation package
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.