business-plan-writer
Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- business-plan-writer
- category
- business-marketing
- description
- Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.
03 SKILL.md 正文
Overview
A business plan is a structured argument that an opportunity is real, the approach is sound, and the numbers work. This skill covers writing each section — executive summary, company description, market analysis, organization, product/service, marketing and sales strategy, financial projections, and appendix — for audiences like investors, lenders, or internal stakeholders.
Plans should be lean where possible: a 15-page focused plan beats a 60-page bloated one.
When to use
-
Raising investment (seed, Series A, small business loans)
-
Applying for grants or business competitions
-
Aligning co-founders on strategy
-
Planning a major expansion or new venture
-
Creating an internal strategy document
-
Writing a one-page lean canvas before the full plan
-
Creating franchise or licensing proposals
-
Documenting strategy for a board of directors
-
Applying for bank loans or SBA financing
-
Recruiting co-founders with a concrete vision
-
Entering business plan competitions
Core concepts
Executive summary. Written last, read first. One to two pages: the opportunity, the solution, the market, the business model, traction, the team, and the ask. If a reader only reads this, they should understand the whole bet.
Market sizing (TAM/SAM/SOM). Total Addressable Market → Serviceable Available Market → Serviceable Obtainable Market. Bottom-up sizing (customers × price) is far more credible than top-down ("1% of a trillion-dollar market").
Business model clarity. How money is made: pricing, unit economics, sales motion, key partnerships. Include CAC, LTV, gross margin, and payback period if known.
Competitive positioning. Direct and indirect competitors, their strengths/weaknesses, and your differentiation. A "we have no competitors" claim destroys credibility — the alternative is always "do nothing" or a workaround.
Financial projections. 3–5 year P&L, cash flow, and balance sheet highlights. Show assumptions explicitly. Investors discount the numbers but scrutinize the logic.
Risk and mitigation. Naming risks (market, execution, regulatory, financial) with mitigation plans builds more confidence than pretending they don't exist.
Lean plan alternative. For early-stage ventures, a one-page lean canvas (problem, solution, key metrics, unfair advantage, channels, cost structure, revenue streams) often beats a 40-page plan. Write the full plan when external stakeholders (investors, lenders) require it; use the lean version for internal alignment.
Use of funds. Investors scrutinize this section closely: tie every dollar to milestones ($500k → 12 months runway → $1M ARR and 50 enterprise customers). Vague allocations (marketing: $200k) signal unfocused thinking.
Market sizing (TAM/SAM/SOM). TAM: everyone with the problem. SAM: those you can reach with your channels. SOM: what you can capture in 3–5 years. Bottom-up sizing (customers × price) beats top-down ("1% of a $50B market") — investors discount top-down math heavily. Show your arithmetic; hidden assumptions destroy credibility. Risk section. Name the top 5 risks honestly (market, execution, financial, competitive, regulatory) with mitigations. Founders fear this section; investors respect it. A plan with no risks signals naivety, not confidence.
Practical workflow
- Clarify audience and purpose. An investor plan emphasizes returns and defensibility; a bank plan emphasizes repayment ability; an internal plan emphasizes execution. Tailor accordingly.
- Research the market. Size TAM/SAM/SOM bottom-up. Profile 5–8 competitors. Document trends, regulations, and customer evidence (interviews, surveys, LOIs).
- Draft the narrative sections. Company, product, market analysis, marketing/sales strategy, operations, team. Keep each tight — one clear point per paragraph.
- Build the financials. Start from unit economics, then scale: revenue model → cost structure → monthly cash flow for year 1, annual for years 2–5. Include best/base/worst scenarios for key assumptions.
- Write the executive summary last. Distill the strongest points. End with a clear ask (amount, use of funds, terms sought).
- Review and pressure-test. Have someone skeptical read it. Fix every "so what?" and "says who?". Check that numbers tie across sections — inconsistent figures kill trust instantly.
Standard structure: Executive Summary → Company Description → Market Analysis → Organization & Management → Product/Service → Marketing & Sales → Financial Projections → Funding Request → Appendix.
Financial narrative check: for every major number, write one sentence explaining the driver (Revenue grows 3x in year 2 driven by enterprise expansion at $50k ACV). If you cannot explain a number's driver, the model needs work.
Writing order: financial model first (it exposes whether the story works) → market analysis → operations plan → then the narrative sections → executive summary last. Writing the summary first produces fiction; writing it last produces a summary. Length guide: 20–30 pages for investors, 10–15 for internal use, 1 page (lean canvas) for early validation. Match length to audience — nobody asked for a longer plan than they will read.
Common pitfalls
- Hockey-stick projections without basis. Explosive growth curves need a credible engine (proven CAC, viral loop, contracted revenue). Otherwise they're fiction.
- Top-down market sizing. "1% of $X trillion" is meaningless. Build from customers you can actually reach.
- Ignoring competition. Claiming no competitors signals you haven't looked. Name them and explain your edge.
- Burying the ask. Investors shouldn't hunt for how much you want and what it's for. State it clearly.
- Inconsistent numbers. Revenue in the summary must match the financials. Cross-check everything.
- Too long. If it takes an hour to read, it won't be read. Aim for clarity and brevity; put detail in the appendix.
- No milestones. Plans without dated milestones and KPIs are wishes. Tie funding to achievable checkpoints.
- Appendix as dumping ground. Hiding weak analysis in the appendix instead of fixing it. The appendix supports; it does not excuse.
- No sensitivity discussion. Presenting single-point forecasts as certainties. Show which 2–3 assumptions the plan hinges on.
- Hockey-stick without drivers. Revenue exploding in year 3 with no explanation of what causes the inflection. Every inflection needs a named driver.
- Ignoring competition. "We have no competitors" — the fastest way to lose credibility. Everyone has competitors, including the status quo.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).