Hands-on

·

5 min read

Zero to one vs. one to many: what each phase of product development needs

Finding out what to build and building it a million times are two different jobs. This note covers what each phase needs, where projects lose time at the handover, and how I work across both.

Aerial view of a road winding in tight, regular curves through a green mountain forest

In short

Zero to one asks what to build. One to many asks how to build it reliably in large numbers. Projects lose most time at the handover between the two.

01 Zero to one

Short loops, prototypes and a clear decision: build, change direction or stop.

02 One to many

Tooling, suppliers, certification and roadmaps across releases.

03 My role

I lead the early phase and stay on as a partner into series.

Most product work falls into one of two phases, and they ask for different habits, tools and people. Zero to one is about finding out whether something should exist at all. One to many is about making it exist reliably, at cost, in large numbers, for years. I have worked in both. I do my best work at the start, and that work draws on what I learned in series production.

Each phase asks a different question

In zero to one, the open question is what to build. Every assumption is still cheap to change, and the fastest way to learn is to make something people can hold, tap or argue about. Speed matters more than polish here. Time spent refining the wrong idea is the main waste in this phase.

In one to many, the question shifts to how to build it well, again and again. The product is mostly decided. What remains is hard and unglamorous: tolerances, suppliers, certification, software releases that must not break devices in the field, and a cost target that leaves room for margin. In this phase a quick fix can be the most expensive decision of the year.

What zero to one needs

A good zero-to-one phase is short and focused. In practice that means:

  • A sharp problem statement and a few hypotheses that are allowed to fail.

  • Conversations with users and buyers early, before the concept feels finished.

  • Prototypes at the right fidelity: a clickable flow for an app, a foam model or a works-like rig for hardware, sometimes both side by side.

  • A rough business case from the first week, so everyone knows which price, volume and cost would justify continuing.

  • A clear decision at the end: build, change direction or stop.

Stopping is a valid result. A concept that ends after four weeks of testing has saved a company far more than it cost.

What one to many needs

Once a product moves towards series, other skills carry the project:

  • Design for manufacture and assembly, CMF choices that suppliers can actually hold, and drawings that leave little room for interpretation.

  • Specifications that engineering, firmware, app teams and suppliers read the same way.

  • Roadmaps that sequence features across hardware generations and software releases.

  • Variants and product families, so one platform can serve several markets.

  • Patience with certification, testing and the long tail of small decisions.

Here the job is mostly to protect the good ideas through tooling, testing and certification.

Where projects lose time

The most costly moment is usually the handover between the two phases. A concept arrives in development without a cost logic, without a view on tooling, or with an app that assumes features the hardware cannot deliver. Development rebuilds half of it, and the original intent gets lost on the way.

The reverse happens too. Teams with a strong series mindset bring production rigour into the early phase and slow it down with detail before the basic question is answered.

Both problems are avoided when someone who knows what the next phase will demand plans the current one with that in mind.

How I work across both

My strength is zero to one. I like the phase where the brief is still blurry. A prototype built in a few days can change the conversation, and strategy, design and the business case are still worked out together.

That work is grounded in years of in-house product development for energy hardware, including the Wattpilot Flex EV charger at Fronius and its app. I know what it takes to get a product through tooling, supplier reviews and series production, and how roadmaps and requirements keep hardware and software aligned over several releases. So when I sketch an early concept, I already think about the part that comes off the tool and the app update that ships two years later.

For clients this means one person who can open the question quickly and still hand over something development can build on. I usually lead the early phase and stay involved as a partner once the product moves into series, so the intent survives the handover.

Which phase are you in?

  • If the main open question is whether customers want it or will pay for it, you are in zero to one.

  • If the main open questions are cost, quality, schedule and certification, you are in one to many.

  • If you are unsure, you are probably still in zero to one. Treat it that way for a few more weeks.

Knowing the phase sets the pace, the team and the kind of prototype that makes sense. Get it wrong and you either bury an open question in detail or rush a product that needs rigour.

Aerial view of a braided glacial river splitting into many channels across dark sand
Aerial view of dry sandy ground with scattered shrubs on the left and dense conifer forest on the right

Create a free website with Framer, the website builder loved by startups, designers and agencies.