In 2000, starting a software company meant raising millions for servers and licenses before a single customer saw anything. Today a founder can put a working product in front of customers within days. The hard part hasn’t disappeared. It has moved, to getting noticed, earning trust, and keeping customers who can switch in an afternoon.
Every playbook founders use was written for a world where building was the expensive, slow part. The lean startup existed to stop teams from spending a year building something nobody wanted. Venture capital existed partly to pay for engineers. Moats were often just the head start of having built something hard.
When a competent founder with coding agents can build most of that in weeks, those assumptions break. Not all at once, and not equally everywhere, but enough that a founder starting today needs a different map.
I start things. I’ve felt the difference between building a product over quarters and building one over a weekend, and I’ve also felt how little the weekend version matters if nobody knows it exists or trusts it with their data. This is the founder’s side of the same shift the rest of this site describes.
The ideaBuilding is no longer the moat. Learning from customers faster than anyone, reaching them before anyone else, and earning a kind of trust a weekend clone can’t fake: that’s where a founder’s time now goes.
Pick an era. Dollar figures for 2000–2010 are from investors at the time; the rest are my estimates, and they vary a lot by product.
Steve Blank and Eric Ries gave founders one loop: build something small, measure how customers respond, learn, repeat. For twenty years “build” was the long leg. Now it’s the short one. Blank himself put it plainly this year: the 2024 playbook doesn’t work in 2026, and development is becoming parallel rather than sequential.
Arc length is time. Build shrinks dramatically. Measuring and learning from real customers shrinks much less, because customers don’t speed up.
The loop is no longer limited by how fast you can build. It’s limited by how fast you can get honest answers from customers.
That’s why the conversations still matter most. In Blank’s own Stanford class this spring, eight teams spoke with 978 potential customers, beneficiaries and regulators. Agents can research a market in an afternoon; they can’t tell you whether a buyer will actually change how they work.
The flip side of building fast is that everyone else can too. A feature that once gave you a year of lead now gives you weeks, sometimes days, before someone ships the same thing with two more features and half the price.
Illustrative. Drag the slider to move forward in time and watch lookalikes appear around you in each era.
The one-person company is real. Solo founding has roughly doubled over a decade, and a solo-built product, Base44, sold for $80 million. Anthropic’s CEO has put high odds on a one-person billion-dollar company arriving soon.
But the data also says something quieter: building the first version got dramatically cheaper; scaling a company didn’t. Recruiting, selling to enterprises, covering many domains under growth pressure, and earning trust are still people problems. The question for a solo founder isn’t whether AI is enough to start. It’s who to add first.
Switch between a typical early SaaS team and the one I’d build now. The engineering work doesn’t vanish; it moves into the founder’s workflow and the agents.
Posting on social media is free and instant for everyone. That’s exactly why it’s hard to be heard. Software is heading the same way: when anyone can ship a polished product, the product alone stops getting attention. The founders who win already have an audience, a community, a partner channel, or a place inside the tools customers use every day.
This shifts where a founder spends the first year. Less on building, which agents now carry; much more on distribution, from day one. Building an audience in public, owning one channel deeply, getting found in AI search, and partnering with whoever already has the customer’s attention are no longer “later” work.
A buyer looking at ten products that do the same thing has a new question: which of these was built last weekend, and which will still be here, secure and supported, in three years? Trust used to come mostly from being a known vendor. Now it has to be built on purpose, in layers.
From the foundation up. Tap a layer for what it means in practice.
When a rival can copy your product, add personalization and charge half, customers become fickle. The old defenses weaken: features, code, shallow integrations. Others get stronger. Here’s how I’d rate them, then and now.
My judgment, informed by the founders and investors cited below. The hollow marker is 2016; the solid one is today.
The common thread: the strongest defenses are the ones that get better with time and can’t be generated. A product that learns each customer’s patterns, becomes where their work actually lives, and is backed by people they trust gets harder to leave every month. A feature list gets easier to copy every month.
A one-person unicorn is possible; it will also be rare. Teams still attract most of the funding. Code that was fast to write can be slow to secure and maintain, which YC’s own partners warned about as AI-written codebases took over their batches. Blank rethought his class so students would build businesses “rather than AI slop.” And in regulated markets, the time it takes to earn a buyer’s trust hasn’t shrunk at all. Speed of building is a real advantage. It just isn’t the one that decides who wins.