SkillsAdd

smithery/samarv

internal-startup-incubation

A framework for launching and scaling a high-growth "New-Co" within a mature organization.

Installation

$ npx skills add smithery/samarv --skill internal-startup-incubation
View on skills.sh ↗ Website ↗

Summary

  • A framework for launching and scaling a high-growth "New-Co" within a mature organization.
  • Use this when you need to pivot a legacy business to catch a market wave (like AI), leverage proprietary assets for a new product line, or protect a high-speed innovation project from corporate "immune system" drag.

Also in this package

Other skills from smithery/samarv · top by installs.

npx skills add smithery/samarv
wrong-but-not-confused-clarity-framework 0 working-backwards-product-development 0 workflow-tracing-product-expansion 0 word-of-mouth-growth-engine 0 winning-tactic-to-strategy 0 what-if-innovation-framework 0 walk-the-store-quality-review 0 unifying-concept-product-expansion 0 understand-identify-execute-framework 0 systems-thinking-product-tradeoffs 0

Browse all from smithery/samarv

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,244 B
  • docs SUMMARY.md 341 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Internal Startup Incubation

To achieve radical growth—like Handshake AI’s jump from $0 to $50M ARR in four months—you cannot treat a new venture as a "side project" or a feature set. You must disrupt your own organization by building a "New-Co" that operates with the speed of an early-stage startup while leveraging the "unfair advantages" of the parent company.

The "New-Co" Framework

1. Identify and Weaponize the Unfair Advantage

Do not build a commodity product. Identify the one proprietary asset your mature company has that a standalone startup cannot easily replicate.

  • Access to Audience: Handshake leveraged its network of 500k PhDs and 3M Master's students. While competitors spent tens of millions on LinkedIn ads (high CAC), Handshake had zero CAC and established trust.
  • Data Moats: Identify "human data" or proprietary signals that AI labs or new markets crave.
  • Institutional Trust: Use existing enterprise relationships (e.g., Fortune 500 partnerships) to bypass initial sales hurdles.

2. Enforce Structural Isolation

A mature company's "immune system" (processes, slow cadences, risk aversion) will kill a high-growth venture.

  • Founder-Led Execution: The CEO/Founder must spend 80%+ of their time on the New-Co. Do not delegate this to a "Head of Innovation."
  • Separate Everything: Establish a separate engineering team, design team, finance, and recruiting.
  • Physical Separation: Sit in a different part of the office or a separate building to foster a distinct culture.
  • Custom Compensation: Create separate equity or incentive structures based on New-Co milestones, not legacy company KPIs.

3. Recruit the "A-Player" Internal Parachute

Identify the most entrepreneurial "beasts" in the legacy organization and move them.

  • The Pitch: Offer them the chance to work on the "fastest-growing business in Silicon Valley" within the safety of the parent firm.
  • Zero-Responsibility Rule: Once moved, they must have zero legacy responsibilities. Do not allow them to "consult" for their old teams.
  • Entrepreneurial Profile: Prioritize staff/principal engineers and product leads who have founded companies before or thrive in ambiguity.

4. Implement a High-Rigor Operating Cadence

Replace "corporate" planning with "founder mode" metrics.

  • Metrics-Based Rigor: Move from quarterly planning to a weekly and monthly operating cadence.
  • 24/7 Expectation: Be transparent during hiring/transferring that this is an early-stage environment (weekends and late nights) distinct from the 9-to-5 legacy business.
  • Flat Hierarchy: The person most capable of driving an initiative is the DRI (Directly Responsible Individual), regardless of their title in the legacy org.

5. The "Leave Nothing to Chance" Mindset

In a market with "unlimited demand," execution is the only bottleneck.

  • Check Data Six Times: In high-stakes fields like AI training, quality is the primary moat. Erroding trust with early frontier customers is fatal.
  • Customer Proximity: Get on the plane. Talk to the researchers/customers directly to understand their evolving hypotheses (e.g., shifting from generalist data to expert trajectory data).

Examples

Example 1: Turning a Marketplace into a Training Lab

  • Context: A talent marketplace (Handshake) realizes AI labs need expert data.
  • Input: 500k PhD users.
  • Application: Instead of just "matching" them to jobs, create a separate platform (Handshake AI) where they are paid $150/hr to "break" models and provide reasoning steps.
  • Output: $50M ARR in 4 months by serving 7 of the top AI labs.

Example 2: Data-Led Pivot for a Legacy SaaS

  • Context: A legacy legal-tech company has a decade of proprietary court filings.
  • Input: 10 years of proprietary legal outcomes.
  • Application: Isolate 5 top engineers to build an "AI Litigator" New-Co. Move the CEO to lead it 4 days a week.
  • Output: A high-margin predictive tool that outpaces the core SaaS growth by leveraging the data moat.

Common Pitfalls

  • Shared Resources: Using the legacy "shared services" (Marketing, Legal, HR) for the New-Co. They will prioritize the $200M business over the $0 business every time, causing fatal delays.
  • The "No" Culture: Allowing legacy managers to veto New-Co priorities because it "interferes with the roadmap." The New-Co must have its own roadmap.
  • Scaling Before Quality: In expert domains (like PhD-level biology or math), one bad batch of data can ruin a customer relationship. "Move fast and break things" applies to features, not the core data quality.
  • Half-Measures: Keeping the CEO focused on the legacy business. If the leader isn't in the trenches, the team won't adopt the necessary "2:00 AM" startup intensity.