$0→1 Squad

Idea to first dollar. 34 agents. No pitch decks, no co-founders, no delusion.

The Problem

You have the idea. You might even have a prototype. What you don't have is confidence that anyone will pay for it.

So you do what feels productive — you refine the UI, add features, research competitors, rewrite the landing page. You stay in build mode because building feels like progress. Selling feels like exposure.

Then one of two things happens: you launch to silence, or you never launch at all.

The gap isn't knowledge. You've read Hormozi, you know about validation, you understand PMF intellectually. The gap is sequencing — knowing that "find 10 people who'd pay" comes before "pick a tech stack," and having something that enforces that order when your instincts tell you to just start coding.

Most founders discover their idea was wrong after building. This is a system that makes you discover it before.

Quick Start

squads install l0z4n0/zero-to-one
/v1 venture

That's it. The Venture Chief asks 5 questions, figures out where you are, and routes you to the right phase.

How To Use — Manual

"I have no idea what to build"

/v1 venture → Phase 0: DISCOVER

The Idea Miner (Paul Graham) maps your skills × interests × market gaps. The Contrarian Lens (Peter Thiel) kills ideas that lack a secret. The AI Scout (Karpathy) finds where AI creates unfair advantage.

"I have an idea but don't know if anyone will pay"

/v1 goto phase-1

Market Validator (Hormozi) runs the starving crowd test. Demand Tester designs a pre-sell experiment. You get a GO/NO-GO before writing a single line of code.

"I built something but nobody's buying"

/v1 goto phase-4

Offer Engineer (Hormozi) rebuilds your offer using the Value Equation. If the perceived value isn't 10x the price, the offer isn't done. Then Launch Strategist (Brunson) runs a 7-day sprint.

"I need to launch this week"

/v1 launch

7-day launch sprint: landing copy, email sequence, Reddit post, DM outreach, demo prep, launch day checklist, post-launch metrics review.

"Should I quit my job for this?"

/v1 runway-calc

Runway Calculator gives you the math — business runway, personal runway, break-even timeline, three scenarios weighted by probability. Math, not hope.

"I'm not sure this decision is right"

/v1 pre-mortem "describe the decision"

Pre-Mortem (Munger) inverts: "What would guarantee failure?" Then Kairo Business scans for cognitive biases contaminating your analysis.

"Do we actually have product-market fit?"

/v1 pmf

PMF Detector (Sean Ellis) runs the 40% test: "How would you feel if you could no longer use this product?" Segments your users, finds your north star segment, and builds the roadmap to improve your score. No scaling until this gate passes.

"Where is our funnel leaking?"

/v1 aarrr

Growth Engineer (Dave McClure) audits all 5 AARRR stages: Acquisition, Activation, Retention, Revenue, Referral. Finds the biggest leak, designs an experiment to plug it. Max 3 experiments at a time — focus beats breadth.

"My growth is linear — I need compounding"

/v1 flywheel

Flywheel Architect (Jeff Bezos) maps your business for self-reinforcing loops. Each customer should make the next one cheaper. Also runs Working Backwards (write the press release before building) and classifies your decisions as Type 1 (slow down) or Type 2 (speed up).

"Should I build this feature or kill it?"

/v1 working-backwards "describe the feature"

Write the internal press release from the customer's perspective. If it doesn't excite you after 3 iterations, kill it. Working Backwards never fails. Skills-forward always fails.

The 10 Phases

DISCOVER → VALIDATE → ARCHITECT → MODEL → OFFER
    ↓                                        ↓
  GROW ← SUSTAIN ← ITERATE ← LAUNCH ← BUILD

Cross-cutting (available at any phase): Pre-Mortem (Munger), Kairo Business (bias detection), Copy Engine (Halbert), Research Engine, Analytics Engineer, Legal Minimum, Runway Calculator, Demo Strategist, Growth Engineer (McClure), Flywheel Architect (Bezos).

What Makes This Different

The mechanism: Each phase has a gate. The gate requires specific outputs — a TAM calculation, not a guess. A unit economics model, not a feeling. A pre-mortem that stress-tests your idea against documented failure patterns. If the numbers don't work, the system tells you before your bank account does.

• You can't skip to building. Phase gates block you from architecture (Phase 5) until you've validated demand (Phase 1). This isn't rigidity — 70% of failed startups built something nobody wanted.
• Two agents exist solely to find your blind spots. Kairo (based on Kahneman's bias work) and Pre-Mortem (based on Munger's inversion) review every major decision for confirmation bias, sunk cost fallacy, and overconfidence. The things that kill solo projects are the things you can't see yourself.
• Your progress survives between sessions. Founder profile, phase state, decisions, artifacts — all persisted. Come back in a week and pick up exactly where you stopped.
• Runway math includes your rent. The calculator models personal burn, not just business burn. Three scenarios, probability-weighted. You get "you have 7.2 months before this gets uncomfortable," not a hockey-stick projection.
• PMF is a gate, not a guess. The PMF Detector (Sean Ellis) runs the 40% "very disappointed" test, segments your users, and blocks scaling until fit is measured — not assumed. Most founders scale on revenue vibes. Revenue with high churn is a treadmill.
• Growth is diagnosed, not hacked. The Growth Engineer (Dave McClure) decomposes your business into 5 AARRR stages, finds the biggest leak, and designs experiments with hypotheses, metrics, and kill criteria. No "growth hacking" — growth engineering.
• Flywheels replace treadmills. The Flywheel Architect (Bezos) designs self-reinforcing loops where each customer makes the next one cheaper. Also gates major decisions as Type 1 (irreversible — slow down) or Type 2 (reversible — speed up).
• 30+ embedded frameworks with 50+ supporting heuristics, anti-patterns, and case studies. Not summaries — full protocols with steps, scoring templates, and edge cases. The Hormozi Value Equation alone is 120 lines of executable logic. Each agent averages 500+ lines of structured methodology — not a paragraph of instructions with "act as an expert."
• Every agent thinks in named frameworks. You get "run the MAGIC formula for offer naming" — not "brainstorm some name ideas."

Value Equation

Who This Is For

• You're a developer or prompt engineer who can build anything but keeps building things nobody buys
• You have runway pressure — 6-12 months, maybe less — and can't afford a 4-month detour into the wrong product
• You've read the books (Hormozi, Blank, Ries) but haven't turned that knowledge into a repeatable sequence
• You're working solo or with one co-founder and need a system that replaces the team you don't have

Who This Is NOT For

• Teams larger than 2-3 people — this is calibrated for the solo founder's decision space
• Existing businesses looking to scale — this is zero-to-one, not optimization
• People looking for motivation or mindset content — this is an execution system, not a coach
• Founders building non-AI products — the agents and frameworks assume you're building with AI

<details> <summary>All 35 Skills</summary> </details> <details> <summary>All 13 Workflows</summary> </details> <details> <summary>Vocabulary</summary> </details>

Confidence System

· · · · ·

Forged by l0z4n0 — squads.sh

First forged: 2026-03-19 | v1.1.0: 2026-03-19

"The best time to validate was before you started building. The second best time is now."

<!-- If you found this, you read the whole README. That's the kind of founder who makes it. --> <!-- v1.1.0: Ellis taught us to measure. McClure taught us to diagnose. Bezos taught us to compound. The flywheel spins. -->