For most of my career, capital was one of the scarcest inputs in building a software company. Software took armies of engineers, months of runway, and a plan credible enough to convince someone to fund it before a single customer ever saw the product. That friction was painful, but it imposed discipline. Founders had to choose.
AI is removing much of that constraint. A single developer with a coding assistant can now build in a weekend what a seed-funded team of six might have spent a quarter building in 2024. As the cost of turning an idea into working software collapses, building stops being the hard part. The scarce resource becomes judgment: knowing what is worth building in the first place. How do you get that judgment? Not by predicting the future. You get it by doing one experiment at a time, and proving it works before you scale.
Find the problem before you scale it
One of my favorite examples started as a cluttered little app called Burbn. In 2010, Kevin Systrom and Mike Krieger had built a location check-in product packed with features: plans, points, photos. Users mostly ignored them. But when Systrom and Krieger looked at what people actually did, one behavior stood out: they posted photos. So they did something that becomes harder as companies get larger and better funded. They threw almost everything away. They rebuilt the product around that single behavior, renamed it Instagram, and signed up 25,000 people on launch day.
Slack has a similar origin story. Stewart Butterfield's team spent years building an online game called Glitch that never found a large enough audience. But the team loved the internal communication tool they had built to work on it. They shut down the game and followed the signal. Neither company predicted the future. They got there one experiment at a time, by watching what people actually did and having the humility to admit which experiment had worked.
That is the approach I keep coming back to when I talk with founders today. Start with the narrowest painful problem you can find, ideally work customers hate doing or that consumes an unreasonable amount of their week, and solve it completely. Run small experiments. Kill the ones that fail. Follow the ones customers pull out of your hands. Don't build a sprawling system before you know which piece anyone actually wants. This matters even more in AI because nobody can see that far ahead. When the technology itself changes every few months, long-range product certainty is mostly fiction. The advantage goes to teams that can learn and adapt faster.
When an experiment fails, the explanation I hear most often is that customers just don't get it. My answer to founders is always the same: customers are voting with their wallets, and you are voting with your instinct. When the two disagree, I side with the wallets every time. If a product needs customers to "get it" before they will pay, it usually has not found its problem yet.
Treat the journey as a series of experiments
See your startup as a series of experiments, not a single bet. Most of them will fail, which is why resilience and grit matter as much as the idea. Every experiment, even a failed one, sharpens your judgment, as long as you are honest about why it failed. It is also why experience on a prior startup counts for so much: you already know the drill, how long things really take, and what it feels like when an experiment dies. No wonder investors write checks most readily to founders who have already been on the journey. Harvard research on venture-backed companies found that founders with a prior success went on to succeed about 30% of the time, against roughly 20% for first-time founders.
What investors generally will not do is pay for the search. Venture capital funds a company that has found something, not the experimentation it takes to find it. That part is yours to figure out. Switching to a completely different experiment, the pivot, is not a failure. Burbn and Glitch were both abandoned experiments before they became Instagram and Slack. Twitter began as a side project inside Odeo, a podcasting company, and Shopify began as Snowdevil, an online snowboard store. The Startup Genome research found that startups that pivoted once or twice raised 2.5 times more money and were 52% less likely to scale prematurely than those that never pivoted or pivoted constantly. And AI has made pivoting cheaper than it has ever been, so you can keep running new experiments until you've found your niche.
Small teams, outsized outcomes
And when a small team does lock onto the right problem, the results can be extraordinary. Instagram had roughly 13 employees when Facebook agreed to buy it for $1 billion in 2012. WhatsApp had around 55 when Facebook bought it for $19 billion two years later. Mailchimp never took venture capital, grew for two decades on customer revenue, and sold to Intuit for $12 billion in 2021. Atlassian ran for eight years without outside funding before raising, and Zoho built a global software business without ever raising external capital. These companies did not win by having the largest payroll. They found something people cared about intensely, stayed focused on it, and resisted diluting that focus.
AI should make this kind of company more common. The amount of labor required to build software, operate a business, and serve a customer is falling. A company that once needed 100 people may need 20. One that needed 20 may need five. It is already happening: Lovable crossed $100 million in annual recurring revenue eight months in, with 45 full-time employees. But that does not mean scale is obsolete.
When scale is the moat
Some of the greatest companies of my lifetime were built by going big deliberately. Amazon started with books, then spent years pouring money into warehouses, logistics, and eventually AWS. Uber raised tens of billions of dollars and subsidized rides city by city to create networks dense enough that a car would reliably appear within minutes. It lost money for more than a decade while it scaled, posting its first full-year operating profit in 2023. Facebook raced from campus to campus because a social network has little value unless the people you know are already on it.
In each case, scale was not vanity. Scale was the moat.
Network effects, logistics density, capital-intensive infrastructure, and winner-take-most markets can reward whoever gets big first. When the underlying economics have that shape, capital is fuel.
Fund math is not company math
The mistake is assuming every business has that shape, and the venture industry increasingly has incentives to do exactly that. As funds get larger, they have to write larger checks and pursue larger outcomes for the economics of the fund to work. A billion-dollar fund cannot generate a great return through a portfolio of companies selling for a few hundred million dollars each. It needs outliers. That logic makes perfect sense for the fund. It does not necessarily make sense for the company.
Many businesses are naturally excellent niches: focused products serving specific customers extremely well, with strong margins and durable economics at modest scale. Put a megafund's growth expectations on one of those businesses and you can destroy what made it attractive in the first place. The company hires ahead of demand, enters adjacent markets before owning its core one, and trades a durable niche for a fragile attempt at dominance. (There are funding models built for exactly these companies, and they deserve more attention than they get.)
Scaling before you have earned it
The wreckage from that mistake is instructive. Webvan went public in 1999 promising rapid grocery delivery, then committed enormous sums to automated warehouses and national expansion before proving that the economics worked in a single market. It was bankrupt by 2001. Juicero raised around $120 million to build an internet-connected juicer that cost hundreds of dollars, only for reporters to demonstrate that its proprietary juice packs could be squeezed effectively by hand. Then there was Quibi: two of the most accomplished executives in media, roughly $1.75 billion in funding, a Super Bowl ad, and a roster of Hollywood stars. It shut down about six months after launch, never having answered the most basic product question: why would consumers pay for short-form video on their phones when enormous quantities of it were already available elsewhere for free?
These companies had different problems, but they shared a failure of sequencing. They scaled before they had earned the right to scale. They are not outliers. A 2011 Startup Genome study of more than 3,200 high-growth startups found that 74% of the high-growth internet startups that failed did so because they scaled prematurely, and that startups that scaled properly grew about 20 times faster. Capital allowed them to execute assumptions that should still have been experiments.
Good reasons and bad reasons to raise
That leads to a rule that should always have been obvious: raise money when you know what the money is for. A good reason to raise is that you have an engine that works and needs fuel: a distribution channel that converts profitably, a product customers want faster than you can deliver it, infrastructure that genuinely requires upfront investment, or a market in which scale itself creates defensibility. A bad reason is that a fund is eager to invest, a competitor just announced a round, or a larger number feels like validation. Paul Graham's default alive test is a useful check here: on the cash you already have and your current growth, would you reach profitability? If the answer is yes, you are raising to accelerate, not to survive.
Money raised before you have found the right problem is expensive in ways that are easy to miss. It dilutes ownership. It creates a valuation you now have to grow into. More subtly, it changes behavior. A large bank balance creates pressure to hire, launch, expand, and "put the money to work" when what the company may actually need is six more months of inexpensive learning. AI strengthens the case for restraint. If a tiny team can build and test a product cheaply, much of the early learning that once required venture capital no longer does. Raise to accelerate discovery only when discovery itself is expensive, and expect to fund most of that search yourself. Otherwise, raise to accelerate something that has already been discovered.
What does "proven" actually mean? Think in cohorts, not averages. Define your ideal customer profile narrowly, then watch how each cohort of those customers behaves over time. As one experienced operator put it to me, seven numbers tell you whether you have an engine: customer acquisition cost (CAC), lifetime value (LTV), gross revenue retention (GRR), net revenue retention (NRR), gross margin (GM), EBITDA, and net income (NI). Your financials are the microscope. If you cannot explain what drives each of these, and which levers move them, more capital will not create scale. It will just amplify whatever is broken. Earn the right to each stage, whether $1 million, $5 million, $10 million, or $25 million in revenue, with cohort data that shows the economics hold.
To see how each of these numbers breaks down into the KPIs and drivers you can actually move, explore our free Metric Tree: every core startup metric, laid out by industry, with definitions, formulas, and stage benchmarks.
The path to that proof depends on who you sell to. Enterprise software often does require upfront investment, but the early work can be run as paid projects with a handful of customers, learning what the product must be before building it at scale. Mid-market and SMB products have no such cushion. They need product-level thinking from day one, because no individual customer is large enough to fund the discovery.
What still counts as a moat
AI changes the nature of defensibility, too. When software becomes cheap to build, it also becomes cheap to imitate. A large engineering team and a long feature list are weaker moats when a competitor can reproduce much of your interface in weeks. What remains difficult to copy is everything accumulated around the software: proprietary data, deep understanding of a particular customer or industry, integration into critical workflows, distribution, trust, and becoming a system of record that customers are reluctant to remove. Advantages like these come from depth, not breadth.
Generic AI products face another problem: incumbents already own the customer. Every established software product can add AI to workflows their customers already use. For many buyers, "good enough and already integrated" will beat "slightly better but new." That leaves startups with an opening, but often a narrower one: understand a specific customer or workflow so deeply that a horizontal incumbent cannot justify matching you.
You can see the market moving this way. One of the fastest-growing roles in AI is the forward deployed engineer, a model Palantir made famous: an engineer who works alongside the customer, learns their workflows and pain points firsthand, and builds against what they find. It is the same discipline as watching what Burbn's users actually did, only now embedded inside the customer's business. And the AI products winning real budgets are the ones integrated most deeply into a customer's workflows and data, which is exactly what makes them hard to rip out.
The economics of AI make choosing correctly even more important. Traditional SaaS could add users at relatively low marginal software cost. AI products often incur meaningful inference costs every time customers use them. Scale the wrong product and you do not merely waste salaries and marketing dollars. You can also accumulate a large usage bill proving that people do not value what you built.
Earn the next problem
None of this means companies should stay small forever. A niche is a beachhead, not a ceiling. Amazon started with books. Great companies keep expanding, but the best expansions are earned. Own one problem. Let that ownership generate data, trust, distribution, and insight. Then follow those advantages into the next problem. Capital should follow demand rather than attempt to manufacture it.
The winners of the AI era will treat capital as scarce even when it is abundant, and measure what each dollar of burn buys. They will run more experiments, keep teams smaller for longer, kill bad ideas faster, and raise serious money only when they can explain precisely what proven engine that money will accelerate. They will pursue scale when scale creates an advantage, not because scale itself looks like success.
For investors, that means accepting an uncomfortable truth: not every great company is a venture company. For founders, the lesson is simpler. AI can build almost anything you ask it to build. The hard part is deciding what to ask AI for.
Prove it first. Stay small until customers start pulling the product out of your hands, then, and only then, pour on the fuel.If you are weighing whether it is time to raise, or what the money would actually accelerate, book a 30-minute consultation. We will look at your numbers together and tell you plainly whether you have an engine ready for fuel.
References
- Instagram's launch: From 0 to $1 Billion in Two Years: Instagram's Rose-Tinted Ride to Glory, TechCrunch, 2012
- Facebook's acquisition of Instagram: Facebook to Buy Instagram for $1 Billion, KQED / Associated Press, 2012
- Facebook's acquisition of WhatsApp: Facebook Will Buy WhatsApp Message Service for $19 Billion, NPR, 2014
- Intuit's acquisition of Mailchimp: Intuit Confirms $12B Deal to Buy Mailchimp, TechCrunch, 2021
- Atlassian's bootstrapped years: Q&A: Mike Cannon-Brookes on Bootstrapping Atlassian, iTnews
- Zoho's funding history: Zoho Reports Profits of Rs. 1,918 Crore for FY21, OfficeChai, 2021
- Lovable's growth and headcount: Eight Months In, Swedish Unicorn Lovable Crosses the $100M ARR Milestone, TechCrunch, 2025
- Slack's origin in Glitch: Glitch (video game), Wikipedia
- Twitter's origin in Odeo: The Real History of Twitter Isn't So Short and Sweet, NBC News, 2011
- Shopify's origin as Snowdevil: Five Interesting Facts You Probably Didn't Know About Shopify, BrainStation
- Uber's first full-year profit: Uber Posts First Annual Profit as a Public Company, CBS News, 2024
- Webvan's collapse: Webvan, Wikipedia
- Juicero: Juicero CEO Says Luxury Juicer Is "Much More" Than Juice, NPR, 2017
- Quibi's shutdown: Short-Video App Quibi Shutting Down Just Months After Launch, PBS NewsHour, 2020
- Premature scaling: The Startup Genome Compass, Steve Blank, summarizing the Startup Genome Report Extra on Premature Scaling, 2011
- Pivoting: Lessons Learned From the Startup Genome Project, Global Venturing, 2011
- Repeat founders: Performance Persistence in Entrepreneurship and Venture Capital, Gompers, Kovner, Lerner and Scharfstein, Harvard Law School Forum on Corporate Governance, 2010
- Default alive: Default Alive or Default Dead?, Paul Graham, 2015
- Forward deployed engineers: Forward Deployed Engineer Is AI's Hottest Job, The New Stack
