One human, one studio: what the venture-studio paper gets right, and what it can't see yet

A developer running a one-person venture studio since January reports building eight products and managing a thirteen-project portfolio using AI agents rather than employees, with four launches planned by the end of October. The account responds to a Technovation paper by Viglialoro, Sansone, Ughetto, Landoni and Lukeš that analyzed 1,006 venture studios and argued their advantage lies in codifying founder expertise into repeatable organizational capability. In the solo setup, that codification lives in machine-readable files and rules rather than people, shifting the scarce resource from headcount to human judgment and replacing trust with artifact verification.

A paper came out in Technovation last month that I would have loved to read in January. Viglialoro, Sansone, Ughetto, Landoni and Lukeš mapped 1,006 venture studios, studied twelve of them up close, and asked a simple question: how does an organisation turn one person's entrepreneurial experience into a repeatable capability for creating several start-ups at once? Their answer, in one line: a studio converts individual founder expertise into organisationally codified human capital. The moat is not any single venture. The moat is the institutionalised learning, the standardised process that runs in parallel across ventures. I have been running a studio since January where that "organisation" is one human and a set of AI agents. Eight products built, four launching by the end of October, thirteen projects in the portfolio. No employees. I am not an academic and I am not an expert on venture studios, so take what follows as field notes from eight months, not as theory. But the paper describes, from the outside, something I have been living from the inside, and the differences are instructive. In a classic studio, the codification lives in people. Founders-in-residence, a shared product team, a playbook that partners carry from venture to venture. The learning is institutional because the same humans apply it again. In a one-human studio, that option does not exist. If the learning is not written down in a form a machine can act on, it is gone by the next project. So everything that would be a habit in a team became a file: The paper says studios extend "entrepreneurial agency and cognition from individuals to organisations". Here the cognition moved from me to a repository. The agents supply the labour. The repository supplies the memory. I supply the judgment. 1. Parallelism is bounded by attention, not headcount. A studio with forty people can run six ventures because it can staff six teams. I can run thirteen projects because agents do not need to be staffed, but I can only decide for one or two at a time. The scarce resource inverted. The old studio rations builders. This one rations judgment. 2. The cost structure is not a smaller version of theirs. In March I had burned about two hundred euros. Today the spend is model plans and a handful of small servers. That is not a cheaper studio. It is a different object: the marginal cost of building one more product is close to zero, so the portfolio can be wider than any rational human studio would allow, and the selection happens after building, not before. "Build fast, list the pain points, park the proper solution for later" was a personal habit. It is now the operating model. 3. Learning compounds differently. In a human studio, learning compounds through people who stay. Here it compounds through rules. Every failure that reached me became a check that runs on every project after it. An agent that declared a bug fixed when it had only opened the fix became a rule that nothing counts as fixed until someone has seen it work in production. Tests that looked green while quietly ignoring problems became a rule that green is not the same as clean. None of it lives in anyone's head. None of it depends on anyone remembering. The next project inherits every lesson the day it starts. 4. Verification replaces trust. A studio partner trusts a founder-in-residence after a few ventures together. I cannot trust an agent that way, and I learned not to. In early September we discovered that several checks that were green did not prove the products worked, and the fleet sweep found one product in eight actually ship-ready. The answer was not better agents. It was a promise-versus-product page that only turns green when both QA legs pass on the released commit. The old world verifies people. This one verifies artifacts. 5. The studio itself is one of the products. Half of what got built this year is not a product for customers. It is the tick fabric that wakes workers, the bus that routes events, the task-worker that drains the queue, the deploy QA, the secrets plane. A classic studio has an operations team. This one has an operations product that had to be built before the first customer product could be trusted. That is the real "first venture". The paper's contribution is a framework for the human studio. I think the agentic version is at least as frameworkable, for a reason the paper hints at: the mechanism is codification, and codification is what agents are good at consuming. Eight months in, the shape looks like five layers. I offer it as a hypothesis, not a result. Every layer is text, which means every layer can be copied into a second studio in an afternoon. That is the part I find hard to argue against: the framework is not a description of the studio, it is the studio. This is where I stop pretending to know. The paper's studios are made of relationships, and the relationships are the part I have not automated and do not want to. The interesting studio is probably not mine and not the classic one. It is a booster network of experienced operators, the people who open doors and tell you the standard is wrong, plugged into an execution layer that never sleeps and never forgets a rule. The paper says studios reduce early-stage uncertainty and hand over validated, investment-ready ventures. An agentic studio can make the "validated" part nearly free. The "investment-ready" part still needs people who have done it before. I would rather test that with those people than write about it. If you run a studio and want to compare notes, or you have a founder with an idea and no technical team, the lunch is on me. Eight months of field notes, thirteen projects, one human. Everything in this article that sounds like a rule was a mistake first.