Startup Strategy logo

Startup Strategy

Organization
cosmicstack-labs
startup-strategy

A comprehensive skill for building and scaling startups — covering lean methodology, product-market fit, growth frameworks, fundraising strategy, team building, and common pitfalls that kill young companies.

Overview

Publishercosmicstack-labs
Repositorymercury-agent-skills
Skill namestartup-strategy
Stars
485
Forks
63
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by cosmicstack-labs on GitHub. Read the source before you install it.

Installation

Install the Startup Strategy AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/business/startup-strategy
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills.git /tmp/mercury-agent-skills
mkdir -p .claude/skills
cp -r /tmp/mercury-agent-skills/categories/business/startup-strategy .claude/skills/startup-strategy
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Startup Strategy in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Startup Strategy on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Startup Strategy is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Startup Strategy Skill

Core Principles

Startups are not smaller versions of big companies. They are temporary organizations designed to search for a repeatable and scalable business model. Until you find product-market fit, everything is an experiment. After you find it, everything is about execution and growth.

The Five Commandments of Startup Strategy

  1. Build something people want. This sounds obvious, yet most startups fail because they build something nobody needs. Everything else is secondary.

  2. Speed is your only advantage. Big companies have resources, brand, distribution, and talent. Your only edge is the ability to move faster, iterate, and learn.

  3. Measure what matters. Vanity metrics (page views, registered users) feel good but lie. Actionable metrics (retention, revenue, activation) tell the truth.

  4. Founder-market fit is non-negotiable. You must deeply understand the problem and the customer. Outsiders can't build what insiders can see.

  5. Fundraising is a means, not an end. Raising money is not a milestone. It's fuel. The destination is a sustainable, scalable business.

Startup Maturity Model

StageNameKey QuestionDurationRisk
1IdeaIs this problem worth solving?1-4 weeksBuilding the wrong thing
2ValidationWill anyone pay for this?1-3 monthsFalse positives/negatives
3TractionCan we acquire customers efficiently?3-12 monthsRunning out of runway
4GrowthCan we scale what's working?12-24 monthsBreaking the product/team
5ScaleCan we build a lasting company?2-5+ yearsLosing the culture

Critical insight: Each stage has a different playbook. Don't try to scale before you have traction. Don't optimize before you validate. Match your strategy to your maturity level.


Lean Methodology

Build-Measure-Learn Loop

The fundamental unit of progress in a startup is not features shipped — it is validated learning.

[Ideas] → [Build] → [Product] → [Measure] → [Data] → [Learn] → [Ideas]
                ↑                                            |
                └────────────────────────────────────────────┘

How to run a BML loop:

  1. Identify the riskiest assumption in your current strategy
  2. Design the smallest experiment to test it
  3. Define success criteria before running the experiment
  4. Build only what's needed to run the test
  5. Measure the outcome objectively
  6. Decide: Pivot (change strategy) or Persevere (double down)

Example:

Assumption: B2B customers will pay $99/month for an AI scheduling tool. Experiment: Build a landing page with pricing, run $500 in ads, measure signup intent. Success criteria: 5% of visitors click "Start Free Trial." Result: 1.2% click-through. → Pivot: Reduce price to $49 or target different segment.

MVP — Minimum Viable Product

An MVP is the smallest thing you can build that starts the learning loop. It is not a prototype. It is not a beta. It is a real product with minimal features.

MVP types (choose based on your riskiest assumption):

MVP TypeBest ForExample
Landing pageTesting demandDescribe the product, collect emails
Concierge MVPTesting value propManually deliver the service
Wizard of OzTesting UXFake the backend, deliver manually
Single-feature MVPTesting core mechanicOne feature, done well
Video MVPTesting explanationDemo video before building
Pre-sale MVPTesting willingness to payCharge before building

Common MVP mistake: Building a "minimum viable product" that still takes 6 months. Your MVP should ship in weeks, not months. If it takes longer, you're building too much.

Validated Learning

Learning is validated when it is based on real data from real customers, not opinions or assumptions.

Techniques:

  • Customer interviews: 10-20 interviews reveal 90% of insights
  • Smoke tests: Measure intent before investing in build
  • A/B testing: Compare two versions of a hypothesis
  • Cohort analysis: Track behavior of groups over time
  • Retention curves: The single best indicator of product-market fit

Anti-pattern: "We learned that users want X." → Is this based on what they said (unreliable) or what they did (reliable)? Watch behavior, not words.


Product-Market Fit

Product-market fit (PMF) is the point where your product satisfies a strong market demand. Before PMF, everything is hard. After PMF, things that were hard become easy.

Signs of PMF

  • Retention curve flattens — users keep coming back week after week
  • Organic growth accelerates — word-of-mouth, referrals, virality
  • Users are disappointed when you go down — they need your product
  • Support volume shifts — from "how do I use this" to "please add this feature"
  • Sales cycle shortens — less education required, faster decisions
  • Churn drops below 5% monthly (B2B SaaS) or below 40% annual

The Supergraphic / Sean Ellis Test

The most practical PMF measurement comes from Sean Ellis: "How would you feel if you could no longer use the product?"

ResponseScore
Very disappointedPMF signal
Somewhat disappointedPre-PMF
Not disappointedNo PMF
N/A — I no longer use itChurned

The threshold: If ≥40% say "Very disappointed," you have product-market fit.

How to run it: Send a one-question survey to active users (who have used the product in the last 2 weeks). Collect at least 100 responses. Segment by user type.

Measuring Retention

Retention is the single most important metric for PMF. Growth can mask retention problems.

The retention curve framework:

  • Day 1 retention: Was the onboarding successful? (Target: 60%+)
  • Week 1 retention: Did they return after first use? (Target: 40%+)
  • Month 1 retention: Is there a habitual use case? (Target: 30%+)
  • Month 12 retention: Does the product have staying power? (Target: 80%+ of M1)

Cohort analysis: Track groups of users who signed up in the same week. Plot their retention over time. If the curve flattens to a plateau, you have retention. If it trends to zero, you have a leaky bucket.


Growth Frameworks

AARRR / Pirate Metrics

Developed by Dave McClure. Five metrics that map the customer journey:

StageMetricDefinitionBenchmark
AcquisitionTraffic, signupsHow users find youDepends on channel
Activation% who reach "aha" momentFirst meaningful experience20-40% of signups
RetentionReturning users, cohortsDo they come back?>30% monthly
RevenueARPU, LTV, MRRAre they paying?LTV > 3× CAC
ReferralVirality coefficient, NPSDo they bring others?K-factor > 1

How to use AARRR:

  1. Map your current funnel with real numbers
  2. Identify the biggest drop-off point
  3. Run experiments to improve that stage
  4. Measure impact on the next stage
  5. Repeat until the funnel is healthy

"If you could only track one thing, track retention. Everything else is a leading indicator of retention." — Sam Altman

Loops vs. Funnels

Funnels are linear: Acquisition → Activation → Retention → Revenue → Referral.

Loops are circular: Each user brings more users.

FunnelLoop
Linear, endsCircular, self-reinforcing
Requires constant paid acquisitionCompounds over time
Easier to measureHarder to measure
Good for early stageEssential for scale

Examples of growth loops:

  • Virality loop: User invites friend → Friend signs up → Friend invites more
  • Content loop: User creates content → Content attracts users → Users create more content
  • Network effect loop: More users → More value → More users
  • SEO loop: Content ranks → Traffic arrives → Content improves → Higher ranking

Build loops, not funnels. A funnel leaks. A loop compounds.

North Star Metric

The single metric that best captures the core value your product delivers. It aligns the entire company.

Criteria for a good North Star:

  • Measures outcome, not output (not "features shipped")
  • Correlates with long-term retention
  • User-facing (not revenue — revenue is a result)
  • Actionable by the team

Examples:

CompanyNorth Star Metric
SpotifyTime spent listening
AirbnbNights booked
FacebookDaily active users
SlackMessages sent
UberRides completed

Fundraising Strategy

Stages Overview

StageTypical RaiseRevenue ProfileKey MetricsInvestors
Pre-seed$100k-$1M$0Team, vision, customer interviewsAngels, friends & family, micro-VCs
Seed$1M-$5M$0-$100k MRRMVP, early traction, retention > 20% MoMSeed funds, angels, accelerators
Series A$5M-$15M$100k-$1M+ MRRPMF proven, retention, unit economicsVCs, growth funds
Series B+$15M-$50M+$1M-$10M+ MRRGrowth rate, LTV/CAC > 3, scalabilityGrowth equity, later-stage VCs

Metrics Per Stage

Pre-seed / Seed:

  • Customer interviews conducted (10-20+)
  • Prototype or MVP built
  • Early retention data (30-day)
  • CAC from pilot channels
  • Founder-market fit narrative

Series A:

  • Monthly Recurring Revenue (MRR): $100k+ (SaaS)
  • Month-over-month growth: 15-20%+
  • Gross Margin: 70%+
  • Net Dollar Retention: 100%+
  • Payback period: <12 months

Series B+:

  • ARR: $2M+ growing 100%+ YoY
  • LTV/CAC ratio: >5:1
  • CAC payback: <6 months
  • Gross Margin: 75%+
  • Clear path to $100M ARR

Pitch Deck Essentials

The classic 10-12 slide structure (from the Airbnb/Y Combinator playbook):

  1. Title — Company name, logo, one-liner
  2. Problem — What pain are you solving? Who feels it?
  3. Solution — Your product, simply explained
  4. Why now — Timing is critical. Why couldn't this exist 5 years ago?
  5. Market size — TAM, SAM, SOM. Be credible, not delusional.
  6. Product — Demo, screenshots, key features
  7. Traction — Revenue, users, retention, growth — real data
  8. Business model — How do you make money? Unit economics
  9. Competition — Competitive landscape and your moat
  10. Team — Why you? Relevant experience and passion
  11. Financials — 3-5 year projection, key assumptions
  12. Ask — How much, what for, expected milestones

Pitch deck rules:

  • One idea per slide
  • Maximum 15 words per slide (except financials)
  • Show, don't tell — use screenshots and data
  • Practice 10 times minimum
  • Know your numbers cold

Team Building

First Hires

The first 5-10 hires define your company's DNA. Choose carefully.

Hiring order for a typical startup:

  1. Co-founder — Complementary skills, aligned values, shared grit
  2. Engineer #1 — Technical co-founder or first hire. Full-stack preferred.
  3. Designer — If product is consumer-facing. First impression matters.
  4. Growth/Marketing — After PMF, to accelerate what's working
  5. Sales — For B2B, after product is ready for demos
  6. Operations — When admin overwhelms the founders
  7. Customer success — When churn becomes visible

What to look for in early hires:

  • Resourcefulness over experience: Can they figure things out without clear instructions?
  • Ownership mentality: Do they act like founders?
  • Speed: Do they ship, or do they discuss?
  • Culture add, not culture fit: Do they bring something new?

Culture

Culture is not ping-pong tables and beer fridges. Culture is what happens when no one is watching.

How to build culture intentionally:

  • Write down your values early (before you have employees)
  • Hire and fire based on values
  • Communicate the mission repeatedly
  • Model the behavior you want to see
  • Create rituals (standups, retrospectives, all-hands)

Warning signs of culture problems:

  • People hide mistakes
  • Blame replaces problem-solving
  • Politics replaces direct communication
  • People talk about what's "not my job"
  • Turnover spikes after 6-12 months

Equity

RoleTypical Equity (Early Stage)Vesting
Co-founder10-50% (split among 2-3)4-year, 1-year cliff
First engineer5-10%4-year, 1-year cliff
Early employee (1-10)1-5%4-year, 1-year cliff
Growth hire (10-30)0.5-2%4-year, 1-year cliff
Later employee0.1-0.5%4-year, 1-year cliff

Key terms:

  • Cliff: First 12 months before any equity vests. Protects against hires who don't work out.
  • Vesting: Equity earned over time (usually 4 years).
  • Option pool: Pre-allocated shares for future hires (usually 10-20%).

Rule: Don't give away equity too early to advisors or friends. It depletes the pool and complicates future fundraising.


Common Mistakes

  1. Premature scaling. The #1 startup killer. You raise money, hire a team, buy ads — all before achieving product-market fit. You run out of runway and never had the product ready.

    Prevention: Don't scale user acquisition before retention is proven. Don't hire a sales team before you can sell manually. Don't raise money to solve a product problem.

  2. Vanity metrics. Total registered users, app downloads, page views, press mentions. These make you feel good but don't tell you if you're building something people want.

    Prevention: Track cohort retention, paid conversion, revenue per user, and NPS. If these are flat while vanity metrics grow, you have a problem.

  3. Founder-market fit gaps. Building something for a market you don't understand deeply. You can't outsource domain expertise to customer interviews.

    Prevention: Ask honestly: "Do I have 10 years of insider knowledge about this problem?" If not, partner with someone who does.

  4. Building too much before talking to customers. Six months of silent development followed by launch day silence.

    Prevention: Talk to 10-20 potential customers before writing a line of code. Sell the solution before building it. Validate the problem, not your idea.

  5. Ignoring unit economics. Raising money while losing money on every customer, hoping to "figure it out later."

    Prevention: Know your CAC (Customer Acquisition Cost), LTV (Lifetime Value), payback period, and gross margin. If LTV < 3× CAC, fix the economics before scaling.

  6. Founder conflicts. Unresolved disagreements between co-founders that paralyze decision-making.

    Prevention: Have honest conversations early. Write a co-founder agreement. Vest equity. Establish decision-making rules. Disagree and commit.

  7. Raising too much or too little. Too much money creates waste and complacency. Too little forces death marches.

    Prevention: Raise 18-24 months of runway. Know exactly what milestones the money buys. Raise when you don't need it (you have leverage).

  8. Building features nobody asked for. Falling in love with your solution instead of the problem.

    Prevention: Every feature request goes through: (1) How many customers asked? (2) Does it improve retention/acquisition? (3) Can we test it with an MVP first?

  9. Slow decision-making. Startups die by a thousand slow decisions. Speed of decision = speed of learning.

    Prevention: 70% of the information is enough to decide. Move fast, correct course. A wrong decision is better than no decision.

  10. Neglecting personal health and relationships. Founders burn out, marriages strain, health deteriorates.

    Prevention: This is a marathon, not a sprint. Sleep 7+ hours. Exercise. Maintain relationships. A burnt-out founder builds nothing.


"The only thing that matters is getting to product-market fit." — Marc Andreessen

"Startups don't starve — they drown. Usually in their own bullshit." — Paul Buchheit

Frequently asked questions

What does the Startup Strategy AI skill do?

A comprehensive skill for building and scaling startups — covering lean methodology, product-market fit, growth frameworks, fundraising strategy, team building, and common pitfalls that kill young companies.

Why use Startup Strategy on TypingMind?

Because you install it once and use it with any model. Startup Strategy is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Startup Strategy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/business/startup-strategy. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Startup Strategy?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Startup Strategy?

As many as you like. As long as a model supports skills, you can use Startup Strategy with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Startup Strategy AI skill free?

Yes. It is published on GitHub by cosmicstack-labs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇