The foundry journal
Why we build in a foundry, not a studio of silos
Method 5 min read
The default shape of a venture builder is a collection: four or five products, each with its own stack, its own habits, its own way of deciding what to build next. The products may share a holding company, but they share little else. Every new venture starts from zero.
We chose a different shape. The Collective Foundry is one facility — one path that every venture walks: discover a problem worth solving, define the venture, design the experience, build the intelligent system, assure its quality, launch it, and feed what the market says back into the next cycle.
The departments are permanent; the products passing through them change. That distinction matters more than it sounds. When the capability lives in the foundry rather than in any single product team, the second venture starts faster than the first, and the fifth starts faster than the fourth. Nothing is relearned from scratch.
It also changes what a product is. Startup Suite, Engyn, LoopLift and EngynQA are not four unrelated bets — they are four traversals of the same system, and each one left the system better: sharper research instincts, reusable engineering foundations, a quality bar that is now infrastructure rather than aspiration.
The most practical consequence is honesty about focus. A foundry forces one question at every stage gate: is this still a problem worth the next department’s time? Ventures that pass keep moving. Ideas that stall do so early, before they consume years.
The empty bays in our portfolio hall are not decoration. They are the point. A collection is finished when its founders run out of ideas; a foundry is never finished, because the system that produces ventures outlives every venture it produces.