---
name: business-plan-template
description: Write a comprehensive business plan with executive summary, market analysis, competitive positioning, and financial projections. Use when the user asks for a business plan, financial projections, market analysis, a funding ask, competitive analysis, or a business plan template.
triggers:
  - "business plan"
  - "winning business plan"
  - "financial projections"
  - "market analysis"
  - "funding ask"
  - "competitive analysis"
  - "business plan template"
disable-model-invocation: false
title: business-plan-template
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/business-plan-template
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/business-plan-template/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/business-plan-template`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/business-plan-template`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/business-plan-template) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/business-plan-template`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/business-plan-template --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/business-plan-template --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Business Plan Template

## Intent
Use Walter Grant's How to Write a Winning Business Plan framework to produce a complete, investor-ready business plan that articulates your market opportunity, competitive positioning, operational strategy, and financial projections.

## Inputs
- Business concept and value proposition
- Market research data (TAM, SAM, SOM)
- Competitor landscape and differentiation points
- Founding team bios and organizational structure
- Historical financials (if operating) or industry benchmarks
- Funding amount sought and intended use of proceeds

## Process (SOP)
1. Step 1: Write the executive summary last but place it first — one to two pages capturing the problem, solution, market size, business model, traction, team, and funding ask.
2. Step 2: Define the problem and opportunity — quantify the pain your target customer experiences and the cost of the status quo.
3. Step 3: Describe your solution and product — focus on the customer benefit, not technical specifications; include development stage and roadmap.
4. Step 4: Conduct market analysis — estimate TAM, SAM, and SOM with bottom-up reasoning (number of target customers × revenue per customer), not top-down percentages alone.
5. Step 5: Analyze competitors — map direct, indirect, and substitute competitors; identify your unfair advantage and barriers to entry; avoid claiming you have no competitors.
6. Step 6: Define your business model — revenue streams, pricing strategy, unit economics (CAC, LTV, gross margin), and path to profitability.
7. Step 7: Outline the go-to-market strategy — primary channels, sales motion, customer acquisition cost assumptions, and key partnerships.
8. Step 8: Detail the management team — highlight relevant domain expertise, prior exits or results, and any critical hires needed with the funding.
9. Step 9: Build financial projections — 3-year P&L forecast with monthly granularity for year 1; include revenue drivers, cost structure, headcount plan, and cash flow statement.
10. Step 10: Write the funding ask — specify the round size, use of proceeds (broken into categories with percentages), key milestones the capital unlocks, and expected runway.

## Outputs
- A complete 15-25 page business plan document
- Executive summary suitable for standalone distribution
- Three-year financial projections with assumptions documented
- Competitive analysis matrix
- Funding ask with use-of-proceeds breakdown

## Evidence
Source: "How to Write a Winning Business Plan" by Walter Grant. Key concepts: executive summary structure, TAM/SAM/SOM analysis, competitive positioning and barriers to entry, bottom-up market sizing, unit economics (CAC/LTV), financial projection methodology, funding ask and use of proceeds.

## Examples
A health-tech startup writes a plan projecting $12M ARR by year 3. Their TAM analysis uses bottom-up reasoning: 40,000 target clinics × $3,000 average contract value = $120M SAM. They seek $2.5M Series A: 45% engineering, 30% sales, 15% operations, 10% G&A — unlocking 18 months of runway to reach $5M ARR.

## Metrics
- Completeness of all 10 plan sections
- Realism of financial projections vs. industry benchmarks
- Clarity and specificity of the funding ask
- Bottom-up market sizing defensibility
- Document length and readability (investor can digest in under 10 minutes)

## Anti-Patterns
- Writing the executive summary first — it will be rewritten anyway; write it last when you know the full story
- Claiming a $50B TAM with no bottom-up validation
- Listing competitors but claiming you have none — this signals naivety to investors
- Overly optimistic hockey-stick projections with no underlying driver model
- Hiding the funding ask or being vague about use of proceeds
- A plan that reads like a product brochure instead of an investment thesis
