
Before a company gets from zero to one, there is a phase most founders skip: minus one to one, where an idea is validated or killed before it becomes a company. A venture studio treats that phase as the real work, sequencing risk so the hardest questions, whether anyone wants this and whether this operator can win it, are answered before anyone writes production code. This is how that de-risking actually happens.
The famous framing is zero to one: build something new. But a vertical AI company has a phase before that, the minus-one-to-one phase, where there is no product, no company, sometimes only a domain expert with a conviction. Most founders rush through it, incorporating and building on the strength of an unvalidated belief, and most of the failures trace back to that rush. A venture studio does the opposite. It spends real time and money in the minus-one-to-one phase deliberately, killing most ideas cheaply so the ones that survive are built on something. This is the operator-to-operator account of how a studio de-risks a vertical AI company before it exists.
What minus one to one means, and why it is skipped
Zero to one assumes you already know what to build. Minus one to one is the phase before that certainty exists, when the questions are still open: is this a real problem, do the people who have it want a solution badly enough to pay, is this the right operator to build it, and can it actually be built with defensible advantage. The venture studio model treats these as the entrepreneur's real first job, systematically de-risking the idea before committing a company to it, a framing developed well in Product-Led Alliance's account of how venture studios sequence risk before they build.
Founders skip this phase for a human reason: building is more satisfying than validating. Writing code feels like progress, while customer interviews and demand tests feel like delay. So the default path is to incorporate, build the thing, and then discover whether anyone wanted it, which is the most expensive possible order to learn in. The studio inverts it because it has watched the build-first path fail enough times to know that the cheap questions have to come first. The philosophy behind that discipline runs through the gAI Ventures manifesto.
Sequencing risk: retire the cheap, fatal risks first
The heart of the minus-one-to-one playbook is sequencing. Every new company carries several kinds of risk, and they are not equal in cost to test or in consequence if ignored. The studio orders them so the cheapest and most fatal are retired first.
| Risk | What it asks | How the studio tests it before building | Why it comes first or last |
|---|---|---|---|
| Demand risk | Do people want this enough to pay? | Customer discovery, letters of intent, pre-sales, demand tests | First, cheapest to test and most fatal to miss |
| Founder-market-fit risk | Is this the right operator for this problem? | Assess the operator's domain edge, access, and credibility | First, no team fixes the wrong founder |
| Market risk | Is the segment large and reachable? | Bottom-up sizing, reachable-channel analysis | Early, shapes whether the outcome can be big |
| Technical feasibility risk | Can it be built with an edge? | Rapid prototyping, technical spikes, data-access checks | Middle, after demand is credible |
| Go-to-market risk | Can it be sold repeatably? | Early pipeline tests, channel experiments | Middle to late, once there is something to sell |
| Execution risk | Can this team ship and scale it? | Assembling the founding team, milestone plan | Last, addressed by how the company is built |
The logic is that demand and founder-market fit are cheap to test and lethal to get wrong, so they go first. There is no point building a defensible product for a problem no one will pay to solve, or pairing a brilliant playbook with an operator who has no real edge in the domain. Only once those clear does it make sense to spend on technical feasibility and go-to-market. Studios evaluate hundreds of ideas a year against this kind of sequence and kill roughly 85 percent early, which is not failure but the point: concentrating capital and talent on the few that survive, a discipline described in this overview of what a venture studio is and how it works. The general mechanics are described in Entrepreneur's account of the venture studio way from idea to company.
Why the hardest questions get answered before any code
The counterintuitive rule of the minus-one-to-one phase is that coding starts last, not first. By the time a studio commits engineers to a build, it has often already spent real money, commonly in the 50,000 to 250,000 dollar range, killing or de-risking the idea, so the build begins against validated demand rather than a hope. This is the reverse of the first-time-founder pattern, where the code comes first and the validation, if it happens, comes after the money is spent.
For vertical AI specifically, this ordering matters more, not less. A vertical AI company's advantage rests on domain depth, proprietary data access, and workflow fit, and those are exactly the things that have to be validated before the build, because they cannot be bolted on afterward. Testing whether a regulated buyer will share the data that powers the model, or whether the workflow the product must slot into will actually accommodate it, is minus-one-to-one work. Get it wrong and the most elegant model is unusable. The reasons vertical depth beats general-purpose AI in these markets are laid out in why vertical AI beats horizontal AI in the enterprise, and the theses gAI co-founds against are set out in the gAI Ventures vertical AI investment theses.
What changes when the studio also brings the team
Validation answers whether to build. It does not build. The gap that sinks many domain experts is the one between a validated idea and a shipped product, because the operator who validated the thesis often cannot execute the engineering alone and then loses months searching for a technical co-founder. A studio that carries the minus-one-to-one work into the build closes that gap by supplying the team on the other side of validation. What that day-zero team looks like, and why it beats the co-founder search, is covered in getting a team on day zero to build your vertical AI company with a technical venture builder.
This is how gAI Ventures runs the phase. It co-founds vertical AI companies with expert operators in financial services, enterprise productivity, and commerce, across San Francisco and Bangalore, and it starts with a focused four-week validation sprint that does the demand and founder-market-fit work before committing to a build. When an idea clears the sprint, it places an institutional technical cofounder and a founding engineering team on the problem, and contributes capital at incorporation and against milestones, so the operator moves from a validated thesis straight into building with a real team rather than restarting the search for one. The people who do that building are named on the gAI Ventures team page, and the companies that have come through the process are visible in the gAI Ventures portfolio. More on how gAI approaches building from minus one is on the gAI Ventures blog, and the operating premise runs through everything at gAI Ventures. This is educational content about the venture studio model, not investment advice or an offer of any kind.
Frequently asked questions
- What does minus one to one mean for a startup?
- It is the phase before zero to one, when there is no product and often no company, only an idea or a domain expert with a conviction. The work of this phase is validating or killing the idea: testing whether the problem is real, whether people will pay to solve it, whether this is the right operator, and whether it can be built with a defensible edge. Zero to one assumes you already know what to build. Minus one to one is where you earn that certainty, and skipping it is why many first-time attempts fail expensively.
- How does a venture studio de-risk an idea before building it?
- By sequencing risk and testing the cheapest, most fatal risks first. It runs customer discovery and demand tests before writing code, assesses whether the operator has a real edge in the domain, sizes the market from the bottom up, and only then spends on technical feasibility and go-to-market. Studios evaluate many ideas and kill most of them early, concentrating capital on the few that survive, and often invest significant money de-risking a single idea before a founder is even matched to it. The result is that the build begins against validated demand.
- Why should validation come before writing code?
- Because code is the most expensive way to learn whether anyone wants what you are building. Writing it first feels like progress but commits time and money before the fatal questions are answered, so a team can build something excellent for a problem no one will pay to solve. Testing demand and founder-market fit is cheap by comparison and answers the questions that actually kill companies. For vertical AI it matters even more, because data access and workflow fit have to be validated up front, since they cannot be added after the model is built.
- What is founder-market fit and why does a studio test it early?
- Founder-market fit is whether a specific operator has a real, hard-to-copy edge in the problem they want to solve: deep domain knowledge, credibility with buyers, and access others lack. A studio tests it early because no team, playbook, or capital fixes the wrong founder for a problem. A brilliant execution engine paired with an operator who has no genuine edge in the domain still loses to someone who does. In vertical AI, where the advantage is domain depth, founder-market fit is often the difference between a defensible company and a generic one.
- How long does the validation phase take with gAI Ventures?
- gAI Ventures runs it as a focused four-week validation sprint that does the demand and founder-market-fit work before committing to a build. If the idea clears the sprint, gAI places a technical cofounder and a founding engineering team and contributes capital at incorporation and against milestones, so the operator goes from a validated thesis into building with a real team. The compressed timeline is deliberate: the point of the minus-one-to-one phase is to answer the hardest questions quickly and cheaply, then move fast on the ideas that survive.
End of article · #005
