When Buyers Become Builders
This is the largest founder unlock in history
We keep meeting founders who never planned to start companies. They were the ones fielding discovery calls, sitting through demos, and always ending up back in the same Excel workbook that needed to be opened in safe mode.
They spent years in the loop: evaluating tools that almost worked, filing tickets that went nowhere, explaining their workflow to product managers who didn’t get it. Then the tools to build got easy enough to use that explaining the problem became harder than building the fix.
They didn’t set out to start a company. They just stopped being customers. We call them Buyer-Builders.
This gets pattern-matched to “contrarian bet on outsiders.” It’s not. The physics haven’t changed. Scarcity still wins. Execution is still everything. The bottleneck inside execution just moved, and these founders happen to be standing on the other side of it.
“Ideas are cheap. Execution is everything.”
This was never wrong. It was a specific instance of a more general rule: the scarce input determines who wins. In software, execution means converting customer demand into dollars.
For twenty years, that meant technical ability.
Building was slow, expensive, and specialized. So “execution” came to mean engineering velocity. That wasn’t the definition. It was the constraint.
Ilya Sutskever said recently that Silicon Valley now has more companies than ideas. He’s describing what happens when the constraint lifts. The scarce input is now the part you cannot autocomplete: knowing what should exist, and knowing it with enough specificity that you can ship something a buyer will actually pay for.
Knowing what to build means knowing what is broken, what drives adoption, and what “yes” looks like. It’s knowing the difference between a vitamin and a painkiller. A buyer-builder does not discover that in interviews. They already lived it.
At pre-seed, the asymmetry has flipped. A buyer-builder with strong demand can find technical help to scale. A build-only team trying to generate demand is competing against buyers who might just do it themselves. That’s where the alpha is.
“Do things that don’t scale.”
Still true. Buyer-builders already did.
Paul Graham wrote that advice for founders starting from zero. It is a recipe for acquiring market truth the hard way.
Buyer-builders have already been doing it, just under a different title. They recruited users manually because they spent years at the same conferences, in the same group chats, on the same job sites. They paid attention to early customers because those customers were their coworkers, their clients, and the people who called them when something broke. They built by hand before automating because they were the manual workflow. They were the duct tape.
This is why their go-to-market can look unfair. It is not marketing genius. It is proximity.
This is why their product conviction can look irrational. They cannot turn off the voice in their head because the problems are not hypothetical. When someone like that finally gets the ability to build, they do not need a brainstorm. They need a weekend.
“The best team wins.”
Still true. The definition of “best” moved.
For a long time, the best team was the team that could move fastest, and “fast” mostly meant code output. In a lot of markets now, the limiting factor is not typing speed. It is time-to-truth: the time it takes to learn the unwritten rules of the industry you are trying to sell into. Those rules are stubborn. AI compresses the learning curve for software. It does not compress the learning curve for industries.
Buyer-builders get to traction before needing permission because they already have distribution. A decade of conferences, group chats, former colleagues, and knowing which buyers are real, which ones are tire-kickers, which ones can approve a pilot, and which ones only forward emails.
At some point the domain expert hits the wall, because the wall is real. Security, reliability, architecture, and scaling do not show up in a demo. That is where a professional builder becomes leverage instead of a leap of faith.
The old pattern was a domain person showing up with a napkin and asking a builder to spend a hundred hours on spec. The builder had no way to price the risk because the market was unproven. The new pattern is a domain person showing up with something jury-rigged, ugly, and undeniably alive. It has users. It has revenue. That is a very different starting point for a serious engineer.
This is not ideological. It is practical. The partnership works because both sides bring the scarce input at the right time.
The Pattern
Over the last fifteen months, we have made five investments. Every one followed the same arc. Every one came from one of three industry buckets: regulated, physical, or services. That is not a portfolio. That is a sample. But the pattern has been consistent enough that we are treating it as a thesis.
The buyer-builder’s founder journey
It starts with pain. Not market research, not customer discovery interviews, but years inside a broken workflow. The buyer-builder knows where it breaks because they were the person everyone called when it did.
Then a prototype. Not clean, not correct, but concrete enough that users show up anyway. The tools got cheap enough that the person with the problem stopped writing requirements docs and started building. They duct-taped something together over a weekend because they couldn’t stop thinking about it.
Then pull. Usage appears. Revenue appears. The prototype shouldn’t be holding together, and yet it is. This is proof that “yes” exists before anyone asked for permission.
Then professionalize. The duct tape starts to fail under its own success. Security, reliability, architecture, and scaling collect their debts. That’s the handoff point. The company stops being “a clever build” and starts being a real system.
This is the moment we see the most asymmetric potential to invest: at the earliest stage of commercialization when pull exists, but the system doesn’t yet.
Where the edge appears
The buyer-builder edge shows up wherever the hard part was never the interface.
In the regulated economy, the verbs are approve, report, and enforce. The budget hides in compliance labor, audit readiness, fines avoided, and the fear of being the person who signed off on the wrong thing.
In the physical economy, the verbs are build, make, and send. The budget hides in rework, delays, coordination failure, and the quiet tax of waiting on someone.
In the services economy, the verbs are engage, advise, and deploy. The budget hides in utilization, churn, training time, and the operational drag that turns skilled labor into human middleware.
This is where we see the largest addressable markets: buyer-builders are not selling against software budgets. They are selling against all of OpEx.
What This Means for the Market
Capital is concentrating at the top of the distribution. This is not a new paradigm or a story about haves versus have-nots. It is a massive concentration onto the place where the old definition of execution is still the most legible. The largest rounds are going to companies where technical moats and access to immense capital still determine outcomes. That version of execution still wins at scale.
Below that line, the distribution of winners in vertical software is not going to be random. But it is not legible if you are still applying the old definition of execution. The founders who will win these markets are not optimizing for code velocity. They are optimizing for workflow truth, early pull, and credible access to buyers.
What This Means for Underwriting
For investors, the risk shifts. It used to be execution risk. Now it is adoption risk.
We look for founders who lived the problem, built something ugly that works, and have pull they did not pay for. We look for the compliance officer who got tired of the workaround, the ops lead who finally snapped, the account manager who knew exactly which workflow was bleeding money. We look for the moment when the buyer became the builder.
Daring Ventures backs Buyer-Builders. We keep meeting them in the places where real work happens. We are raising Fund I.
🤞🤞