Business Plan Prompts with Explicit Assumptions

This reviewed prompt collection is for founders, students, consultants, and small-business owners. It supports planning and questioning; it is not financial, legal, tax, or investment advice.

When to use these prompts#

Use this page when you need modular prompts for assumptions, market, operations, risks, milestones, and financial-input questions that clearly label unverified estimates. Replace every bracketed variable with verified, non-sensitive information before using a template in your own AI product.

Inputs to prepare#

• business concept and operating location
• customer problem and evidence
• product, service, and business model
• known competitors and alternatives
• team capabilities and operational constraints
• verified costs, prices, and capacity data
• assumptions requiring validation
• milestones, risks, and intended audience for the plan

Draft prompt templates#

1. Assumption map before the plan#

Purpose: Separate evidence from guesses before drafting prose.

Build an assumption map for [BUSINESS CONCEPT]. Use [KNOWN FACTS] as evidence and [CURRENT ASSUMPTIONS] as hypotheses. Organize customer, problem, solution, channel, revenue, cost, operations, legal, and capacity assumptions. For each include evidence, confidence, cheapest validation step, owner, and decision deadline. Do not invent market size, growth, costs, or conversion rates.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

2. Modular business plan draft#

Purpose: Create a reviewable plan from supplied data.

Draft a business plan for [VENTURE] for [AUDIENCE]. Use only [VERIFIED DATA] and clearly label [ASSUMPTIONS]. Include executive summary, customer and problem, offer, market evidence, go-to-market, operations, team, milestones, risk register, and financial-input table. Where numbers are missing, ask a question or show a formula with blank inputs rather than estimating.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

3. Risk and evidence challenge#

Purpose: Stress-test a draft without pretending to predict success.

Review [BUSINESS PLAN] as a skeptical operator. Identify unsupported assumptions, circular reasoning, missing constraints, single points of failure, regulatory questions, and milestones that lack measurable evidence. Return a prioritized validation backlog and questions for qualified legal, tax, financial, or industry advisers. Do not provide a success probability.

Before use, remove irrelevant fields, replace every placeholder, and verify that the requested judgment can be supported by the material you supplied.

Why the structure matters#

A business plan is useful when it makes assumptions testable. These prompts discourage invented market figures, force unknowns into an evidence backlog, and keep specialist advice separate from model-generated planning.

Weak prompt and what it misses#

Write a winning business plan with realistic financial projections for my new app.

No customer evidence, location, business model, cost data, or assumptions are supplied. “Realistic” projections would still be invented, and “winning” implies an outcome the document cannot guarantee.

Human review checklist#

• Label every estimate with its source, date, and owner.
• Review legal, tax, employment, and regulatory questions with qualified professionals.
• Test customer and pricing assumptions before treating them as facts.
• Check that milestones have measurable acceptance criteria.
• Keep scenario calculations separate from forecasts presented to others.

Testing and maintenance#

1. Use original, non-sensitive sample values when testing a prompt.
2. Retest examples after material changes to the prompt, page, or AI product.
3. Check factual preservation, requested format, missing-data behavior, and task-specific risks.
4. Update the visible test date when a material retest is completed.
5. Keep the site operator responsible for the final human review.

A dated operator attestation is sufficient for the site's internal publication check; full chat transcripts are not retained or published.