The discipline

Startup Engineering

The technical discipline of getting from 0 → 1 without letting your commitments outrun your evidence.

From 0 to 1 through five loops: Problem, Solution, Product, Market, Fit0PROBLEMSOLUTIONPRODUCTMARKETFIT1

First principle

Learn faster than you burn.

Traditional engineering optimizes for scale, reliability and longevity — the right priorities for a company that already knows what it’s building. A startup between idea and product-market fit doesn’t know yet. Its scarcest resource isn’t engineering capacity; it’s runway.

So startup engineering has a different first priority: learn faster than you burn. Every technical choice — what to build, what to buy, what to postpone — should purchase the next piece of evidence as cheaply and as reversibly as possible. Three rules follow:

  1. 01Evidence before architecture. Don’t solve scaling problems before validating the product.
  2. 02Stay reversible. Avoid large technical commitments while uncertainty is high.
  3. 03Build only what the current stage has earned. A prototype, an MVP and a scalable platform are different things.

The framework

The Five Loops.

0 → Problem → Solution → Product → Market → Fit → 1. Each loop asks one question, and each loop changes which technical decisions are the right ones.

Is the problem real and worth money?

What this stage has earned: Manual delivery

  • Should software be built yet — or should the service be delivered by hand first?
  • What is the riskiest technical assumption in the idea?
  • Could AI make the idea obsolete before it ships?

Read the decisions in this loop, explained for founders →

The build progression

Each loop earns the next build.

The loops imply a progression. You don’t build the final system first — you build the cheapest thing that answers the current loop’s question, and let the evidence earn the next stage:

  1. 01Manual delivery. Proof the problem is worth money — before any software exists.
  2. 02Disposable prototype. Proof the solution creates value — built to be thrown away.
  3. 03Launchable MVP. Proof strangers can receive the value without you in the room.
  4. 04Observable product. Proof it survives the real world — measured, monitored, supportable.
  5. 05Repeatable system. Proof the value repeats without founder heroics. That's 1.

Most expensive startup engineering mistakes are stage mistakes: building the Market loop’s platform while still inside the Problem loop, or shipping the Solution loop’s prototype to the Product loop’s strangers. The framework exists to catch those mistakes before they’re paid for.

Quick reference

One question per loop.

Problem

Is the problem real and worth money?

Earned build: Manual delivery.

Solution

Does this solution actually create value?

Earned build: Disposable prototype.

Product

Can strangers reliably receive the value?

Earned build: Launchable MVP.

Market

Will customers adopt it in the real world?

Earned build: Observable product.

Fit

Does the value repeat without founder heroics?

Earned build: Repeatable system.

The book walks every loop decision by decision — Startup Engineering for Non-Technical Founders.

Not sure which loop you’re in?

That’s usually the first thing worth establishing. Bring your current situation and we’ll locate it together.