Claude Skills for Startups: From Idea to MVP to First 100 Customers

Most startups fail at the same three transitions: they build before validating, they plan too long before building, and they wait for distribution instead of selling manually. The idea is usually fine. The market is often real. What kills early-stage companies is sequence — doing the wrong thing at the right time, or the right thing in the wrong order.

Claude Skills maps onto each transition in the founding journey. A Skill is a persistent Claude configuration — system prompt, framework logic, output format — installed once and invoked whenever you need it. The four Skills below follow the arc of early-stage company building: validate the idea and define the MVP scope before writing a line of code, compress the planning cycle from weeks to days, get to 100 paying customers through direct outreach instead of waiting for virality, and formalize the business plan for investors once the traction is real.

Each Skill handles a specific phase. Together they cover the full journey from the back of a napkin to a fundable company.

The Early-Stage Sequence Problem

The sequence problem in early-stage startups is well-documented but rarely internalized until it happens to you. A founder has an idea, gets excited, finds a developer, signs a contract for $50,000, builds for six months, and launches to an audience of twelve people — most of them family. The product worked. The market was not there. Or the market was there, but the feature set missed what customers actually needed.

The fix is not a better development process — it is doing validation work before the development contract is signed. Market sizing. Competitor research. User interview scripts. A one-page pitch that forces the idea into a coherent shape. None of this requires code. All of it reveals whether the idea deserves six months of development time and $50,000.

The planning problem is the mirror image. Once a founder decides to build, the feature list grows. Every conversation adds scope. Six weeks of planning produces a 40-feature spec that will take eight months to build and six months to learn was wrong. The MVP that should have been three core features becomes a product that tries to do everything and does nothing well.

The customer acquisition problem is the most common of all. The product ships. The founder posts on social media. A few hundred people visit the landing page. Nobody buys. The founder concludes that the product needs a better marketing strategy, or more features, or a rebrand. What the product actually needs is for the founder to talk to ten real humans who have the problem and walk them through the solution one at a time.

The four Skills below address each problem in sequence.

Skill 1: Non-Technical Founder MVP Builder — Validate Before You Build

The Non-Technical Founder MVP Builder produces the strategic foundation for an MVP without a technical cofounder: market sizing analysis, competitor landscape, MVP feature scope (what to build versus what to skip), user interview script, one-page pitch deck, and a 90-day validation roadmap.

The Skill is designed for the moment before money is spent on development. The output answers the questions an investor would ask — is the market real, who are the competitors, what is the minimum viable version of this product, and how will you know if it is working — before those questions need to be answered in a pitch meeting. A founder who has worked through the MVP Builder output is a founder who has been forced to be honest about what they know and what they do not.

The feature scope section is the most practically valuable output. It separates the features that are required for the MVP to test the core hypothesis from the features that are nice to have but not required for validation. For most products, this cuts the initial scope by 50 to 70 percent — which means the MVP costs less to build, ships sooner, and produces learning faster.

⏱ Setup: 10 minutes. Works for any business model — marketplace, SaaS, consumer app, service business. The user interview script is the highest-value output: the ten questions that will tell you whether the idea is real before you spend anything.

Skill 2: MVP Planning Accelerator — From Idea to Buildable Spec in 48 Hours

The MVP Planning Accelerator compresses the planning cycle from weeks to days: competitive analysis of five incumbents, an ICE-scored feature matrix that cuts scope by 60%, user stories for core flows, a three-sprint development plan, and a launch checklist with go/no-go criteria.

ICE scoring — Impact, Confidence, Ease — is the framework that makes feature prioritization defensible rather than subjective. Every feature gets scored on three dimensions and ranked by total score. The features that rank high on all three go into sprint one. The features that rank high on impact but low on confidence go into a later sprint once confidence is established. The features that rank high on impact but low on ease get broken into smaller versions that can be tested first.

The result of running ICE scoring rigorously is almost always the same: the MVP that felt like 40 features becomes a three-sprint plan with 12 features in sprint one, 8 in sprint two, and 6 in sprint three. The first sprint ships in three to four weeks. The product is in front of users in weeks, not months. The sprint two and three features are built on top of what the first sprint taught, not on top of what the founder assumed before launch.

⏱ Setup: 10 minutes. Works for SaaS, consumer apps, marketplaces, and internal tools. The ICE scoring output is the artifact to show your developer or technical cofounder — it makes the prioritization decisions explicit and defensible.

Skill 3: First 100 Customers — Manual Selling Before You Scale Anything

The First 100 Customers Playbook is a concentric-circles sales system built for early-stage founders: a list of ten warm contacts to pitch first, ten community members to reach next, a personalized cold outreach template, a pricing strategy for the first customers, and weekly sales goals that create accountability without requiring a sales team.

The playbook is built on a principle that most founders resist: the first 100 customers cannot be acquired through marketing, content, or virality. They can only be acquired through conversations — one at a time, starting with people who already have a reason to trust you and want you to succeed. The founder who sends 100 personalized emails to people they know, or to people in communities they participate in, will get more customers than the founder who runs $5,000 in Facebook ads and waits for the funnel to convert.

The concentric circles structure matters because it sequences the sales effort correctly. The innermost circle — friends, family, former colleagues — gives you your first real feedback before you talk to strangers. The middle circle — community members, social followers, people who know your work — gives you your first customers who do not have a personal relationship with you. The outer circle — cold outreach — is only credible when you have case studies and testimonials from the inner two circles to cite.

⏱ Setup: 10 minutes. Works for any B2C or B2B product with a price point under $500. The first 100 customers cannot be automated — this Skill prepares the manual work, not a shortcut around it.

Skill 4: Business Plan Generator — Investor-Ready When the Traction Is Real

The Business Plan Generator produces a complete investor-ready business plan: executive summary, TAM/SAM/SOM market sizing, three-year financial projections, competitive positioning, and go-to-market strategy — in the format that accelerator applications, angel investors, and seed-stage VCs expect.

The business plan comes last in this sequence deliberately. A business plan written before there are customers is a document full of assumptions dressed up as analysis. TAM/SAM/SOM numbers that come from top-down market research rather than bottom-up customer evidence are exactly the kind of projections that experienced investors dismiss immediately. The business plan that raises money is the one where the financial projections are grounded in what has already happened — the cost per customer acquisition that was proven with the first 100 customers, the churn rate that was measured over the first three months, the expansion revenue from customers who upgraded.

The Skill produces the full plan structure — executive summary that opens with the problem and the traction evidence, market sizing built from the bottom up using customer data, financial projections that follow from the unit economics already observed, competitive landscape with an honest differentiation analysis, and a go-to-market plan for the next stage of growth. Investors read this plan and see a founder who knows their numbers because they have already been selling, not a founder who researched what investors want to hear.

⏱ Setup: 10 minutes. Works for accelerator applications, angel rounds, and seed-stage VC pitches. The plan is only as strong as the traction data you bring to it — which is why it comes last in the sequence.

The Founding Sequence: Each Skill Unlocks the Next

The four Skills are designed to be used in order. The MVP Builder produces the validation output — market sizing, competitor landscape, core feature scope — that the MVP Planning Accelerator uses as its starting point. The MVP Planner produces the three-sprint development plan that determines what ships first. The First 100 Customers Playbook runs while and after the product ships, building the customer base and generating the traction data. The Business Plan Generator takes that traction data and turns it into the investor narrative that closes the seed round.

Each Skill can be used independently — a technical founder who does not need the MVP Builder can start with the MVP Planner; a bootstrapped founder who is not raising can skip the Business Plan Generator entirely. But the sequence matters for the founders for whom it applies, because the output of each phase is the input to the next. A business plan built without traction is fiction. First customers acquired without a validated product scope are evidence of the wrong product. A development plan built without competitive analysis is missing the context that determines what actually needs to be built.

The arc from idea to MVP to first 100 customers to fundable company is not a straight line — it involves pivots, wrong guesses, and iterations that no plan fully anticipates. What the four Skills do is make each phase of that arc more deliberate: the right questions asked before the money is spent, the right features built before the launch, the right conversations had before the marketing campaign, the right traction built before the investor deck is finalized. The judgment stays with the founder. The structure gets handled.

Get the Startup Skills

Each Skill is a one-time install. Use them in sequence for the full founding journey, or drop into any phase where you need structure.