Every venture in our portfolio started the same way: someone walked in with a problem they understood better than we did, and a rough sense of what a solution might look like.
What happens between that first conversation and a live product with real users is the part most founders never see from the outside. Here is roughly how it goes.
Week one: we try to break the idea
Before any code gets written, we spend time trying to find the reason the idea will not work. Not because we want to talk founders out of building — because an idea that survives real scrutiny early is worth far more time than one that gets built first and questioned later.
The founders who get the most out of this stage are the ones who already know their problem is real, because they have lived inside it. Domain expertise is worth more here than a polished business plan.
Weeks two to four: a working prototype, not a deck
We do not build slide decks. We build the smallest working version of the product that a real user could actually use, even if it is held together with manual processes behind the scenes. Getting something real in front of users early surfaces problems no amount of planning would have caught.
The middle stretch: validate, then rebuild what needs rebuilding
Almost every venture we have shipped has had at least one significant rebuild once real usage data came in. This is normal, not a sign of a failed first attempt. The first version's job is to teach us what the second version needs to be.
- Watch what users actually do, not what they say they will do in an interview.
- Rebuild the parts that do not hold up under real usage, and leave the parts that do.
- Resist the urge to add features before the core loop is working reliably.
Scale: the studio steps back, the founder steps forward
By the time a venture is ready to scale, our role shifts from hands-on building to support — infrastructure, advisory, and access to the studio's network, while the founder and their team take the lead on running the business day to day.
Our job is to make ourselves less necessary over time, not more.
Zero to hero is not a straight line, and it does not happen on a fixed schedule. But the pattern above has held, roughly, across every venture we have taken from a first conversation to something real.