The theory behind Product Printer
Software is no longer a craft. It's a technique.
For seventy years software was built like furniture in a workshop — one artisan, one piece, everything from scratch. That era just ended. When writing code becomes cheap, the value moves to the plan, the parts and the line. So we build like a factory.
From craft to technique
The cost of writing code collapsed
AI agents now write most of the code. The expensive middle of every software project — typing the implementation — became the cheap part almost overnight. What used to take a team a quarter takes a supervised production line a week.
Most software is a solved problem
Sign-in, billing, multi-tenancy, languages, monitoring: every business application needs them, and none of them deserves to be reinvented. They are standard parts — catalogue items, not design work.
What stays scarce is the problem itself
Understanding a bike shop, a rental fleet, a care service — and specifying the right thing to build. That is where humans belong. Everything downstream of a good specification can be industrialised.
A craft becomes a technique the moment its steps can be written down, repeated and checked. Software just crossed that line — and once something is a technique, a factory beats a workshop.
The factory floor
Nine elements turn software development into a production line. Together they are the Product Printer software factory.
01
Blueprints
Every vertical starts with a blueprint: the scoped MVP, the design spec, the data model — drawn once with an industry champion, then reused for every business that follows in that vertical.
02
Standard parts — blocks
Reference implementations of the solved problems: authentication, billing, tenancy, languages, monitoring. Built once, hardened in production, injected into every new product instead of rebuilt.
03
Guidelines
Where no part exists, a method does. Guidelines are our prompt reference library: they encode how a feature gets manufactured — the patterns, prompts and checks our agents follow.
04
Glue
The honest name for project-specific work: connecting standard parts to one business's reality. Engineered, not improvised — but the only part of a product that is built one-off.
05
Worksteps
The work orders of the line. Every product is built in phases; every phase is a list of worksteps; every workstep derives from a block, a guideline or an individual requirement — and is picked up by an agent and delivered as a pull request.
06
Quality gates
Nothing reaches production without passing the line's checks: linting, tests, build, end-to-end runs and a security review on every single change. Machines check the machines; humans check the judgement.
07
On the ground
A factory is not offshore. A forward-deployed engineer stands in the champion's business, sees the real shop floor, and feeds reality back into the line before it hardens into software.
08
After-sales service
A product is never finished. Change requests, monitoring, uptime, updates: the line keeps running after delivery, because operating the software is the product.
09
Quartier management
We don't run a single production line — we run the quartier: a portfolio of vertical platforms sharing infrastructure, parts and lessons. Every product we ship makes the next one cheaper.
The workshop era was beautiful. The factory era is affordable.
— Cut the noise.
Come with your problem →