AI Made Building Faster. It Did Not Make Enterprises Buy Faster.

AI Made Building Faster. It Did Not Make Enterprises Buy Faster. Curiosities September 9, 2026 12 min /curiosities/the-speed-of-trust/ A friend running an enterprise software startup at $1.5M ARR keeps hearing the same thing from Series A investors, come back at $3M. The number stuck with me, so I went digging. What I found is a mismatch. AI made building software dramatically faster. It did not make enterprises buy software faster, and we are quietly pricing startups as if it had.

I was talking to a friend recently who is the CEO of an enterprise software startup. He had a bit of a slow start, but things are working now. Customers are buying. Revenue is growing. He is at around $1.5M ARR. He has raised a seed round and is now starting to test the waters for a Series A.

The feedback he keeps hearing is surprisingly consistent: come back when you are at least at $3M ARR.

Hmm. That number stuck with me. Not because $3M is impossible, but because I started wondering where the expectation came from. Why has $3M become some kind of magic number for a Series A? Is that reasonable for an enterprise B2B company? Has something fundamentally changed in how enterprises buy software that I somehow missed?

So I started digging. And the more I thought about it, the more I realized there may be a very simple mismatch underneath all of this. AI has dramatically compressed how fast software can be built. It has not equivalently compressed how fast enterprises buy software. And I wonder if we are starting to confuse the two.

Today, a small team can build an astonishing amount of software. A founder can have an idea on Monday and a surprisingly good prototype by Friday. Five engineers can potentially accomplish what required 15 or 20 a few years ago. Products improve faster. Experiments happen faster. The cost of building and iterating is collapsing. Amazing.

Now go sell that product to a Fortune 500 company.

• Find the champion. Run discovery. Demo it.
• Meet their boss. Meet IT. Meet security.
• Run a proof of concept. Fill out the security questionnaire.
• Architecture review. Legal review. Procurement. Vendor onboarding. Budget approval.
• MSA. DPA. Maybe another security review, because somebody discovered another questionnaire.
• Then the executive sponsor goes on vacation. Then procurement tells you the person approving new vendors is also on vacation. Then the quarter ends.

None of this is an exaggeration, and the data says it is getting longer, not shorter. B2B sales cycles ran roughly 38% longer in 2024 than in 2021, and deals above $100K in annual contract value typically take six to nine months or more to close.¹ On the buyer's side, IT and security leaders now report spending about nine working weeks a year on vendor security reviews and risk assessments, up from seven the year before.² That is the customer's clock, and it is ticking slower while ours ticks faster.

Your AI coding assistant may have become 10X faster. The customer's organization did not. That is the mismatch. We are applying software velocity to organizational velocity, and the two operate on very different clocks.

Take a B2B enterprise company selling at $100K ACV. To reach $3M ARR, it needs roughly 30 enterprise customers. At $50K ACV, 60 customers. At $250K ACV, 12.

Is that possible before a Series A? Of course. Some companies will blow through those numbers. If you enter a hot market, the budget already exists, the pain is urgent, your ACVs are high, the founders have strong relationships, and customers can deploy quickly, $3M can happen remarkably fast. There will always be exceptional companies.

The problem begins when an exceptional outcome becomes a universal expectation. Because underneath that expectation seems to be an assumption: if startups can build much faster, they should also generate revenue much faster. That sounds logical. But enterprise revenue is not produced only by the startup. Revenue is produced by two organizations moving together. You control the speed of one. You barely control the speed of the other.

This becomes even more obvious when you are creating a new enterprise category. If you are replacing an existing product, you may move faster. The buyer understands the category. Someone already owns the problem. Budget probably exists. There may literally be a line item waiting for you.

But some of the most interesting startups are not replacing something. They are introducing something new. Now you have to explain why this problem matters, who owns it, where the budget comes from, how value should be measured, and why a large enterprise should trust a 12-person startup with an important workflow. And perhaps hardest of all: why should the organization change how it already works?

That is not primarily a software problem. It is an organizational problem. Organizations have latency. AI has not eliminated that.

Interestingly, the number is not arbitrary. Silicon Valley Bank's data on US B2B software companies puts the median ARR at Series A at about $1.3M in 2021 and nearly $3M in 2024.³ CRV's 2026 benchmarks land in the same neighborhood, a $2.5M median in 2025, roughly 75% higher than four years earlier, with a "competitive" range of $2M to $5M.⁴ A survey of 52 venture funds published this spring puts the B2B SaaS median at $3M, up from $1M in 2021.⁵ So investors are not making the benchmark up.

But there is a statistical trap hiding here. We observe the companies that successfully raised a Series A. We calculate their median revenue. Then that median gradually becomes the requirement for raising a Series A. Those are two very different things.

Imagine observing that the median Olympic finalist runs extraordinarily fast. That is useful information. But then imagine saying: anyone who cannot already run that fast should not receive professional coaching. Now you have changed the meaning of the statistic.

The same thing can happen in venture. Investors become more selective. They fund companies with higher revenue. Next year's Series A dataset therefore contains companies with higher revenue. We measure those companies. The benchmark rises again. Investors then point to the new benchmark as evidence that companies need even stronger numbers. The SVB data even shows the mechanism at work: ARR at Series A has risen faster at the lower quartile than at the upper quartile, which is exactly what you would expect if the floor is being raised rather than the ceiling.³

Eventually the benchmark stops describing the stage. It starts redefining the stage.

Maybe that is actually what has happened. Seed rounds became larger: the median seed deal on Carta went from $2.6M in early 2021 to $3.7M by mid 2022, and sits around $4M today.⁶⁷ AI made teams dramatically more productive. Starting companies became cheaper. Beautiful products became easier to build. So naturally investors started expecting more.

At seed, founders are increasingly expected to prove that the product works, that customers care, that customers will pay, that customers stay, that the market is large, that there is some repeatability, that the economics look reasonable, and ideally that revenue is already moving quickly.

Which means the old model, seed to find something that works, Series A to figure out how to scale it, is quietly becoming: seed to find it, build it, sell it, prove it, retain it, and demonstrate the beginnings of repeatability. Series A to show me the machine.

The graduation numbers reflect it. Among startups that raised a seed round in 2018, 25% to 30% closed a Series A within two years. For the 2022 seed cohort, that figure was about 17%.⁸ The median time from seed to Series A has stretched to 2.2 years.⁹

At which point I have a slightly provocative question. What risk exactly is the Series A investor underwriting? Venture capital historically earned extraordinary returns because it accepted extraordinary uncertainty. If every uncertainty has to disappear before the next investor arrives, the risk has not disappeared. It has simply moved upstream. To seed investors. To angels. And increasingly, to founders.

I do not think VCs literally believe enterprise software works like consumer software. They know procurement exists. They know security reviews take time. Many of them have built enterprise companies themselves. But I do wonder whether some consumer-style expectations about speed of evidence have leaked into enterprise investing.

A consumer startup can launch something and potentially get 100,000 users. Within weeks it can measure activation, retention, conversion, engagement, cohorts, and pricing. Change something tonight. Observe another thousand users tomorrow. The feedback loops can be extraordinarily fast.

Enterprise is different. Your experimental unit might be one company, and that experiment might take three months. What you learn from it is about security, integrations, organizational politics, procurement, workflow changes, economic value, executive sponsorship, deployment complexity, and renewal behavior. The enterprise startup is not necessarily learning slowly. It is learning deeply. B2C frequently learns through volume. Enterprise often learns through depth. And unfortunately, you cannot A/B test JPMorgan overnight.

Imagine two startups.

Company A has $3M ARR. Four huge customers. The founder personally knew all four executives. One customer represents almost half the revenue. Nobody is quite sure whether the sales motion is repeatable.

Company B has $800K ARR. Fifteen customers, and they keep buying for roughly the same reason. Customers are expanding. Implementations are getting easier. Sales cycles are shortening. Different customers describe the problem using almost identical language. Early retention is excellent. And the company is starting to close customers without the founder personally driving every deal.

Which company is more ready for a Series A? The spreadsheet says Company A. I am not sure. Because a Series A should not simply answer "how much revenue have you accumulated?" It should answer: have you learned enough that adding capital could accelerate something real?

None of this means investors should lower their standards. Quite the opposite. Ask harder questions.

• Is the same pain appearing repeatedly? Are customers actually using the product? Are they expanding?
• Are implementations becoming easier? Are sales cycles getting shorter? Is the buyer becoming obvious?
• Is pricing stabilizing? Are customers getting measurable economic outcomes?
• Can someone besides the founder sell it?
• Do customers care enough to fight through their own procurement organization to get it?
• Is customer #20 likely to be easier than customer #2?
• And yes: what is your ARR?

Revenue matters enormously. It is one of the strongest signals a business can produce. But ARR should be evidence. It should not become theology.

This is the part I find most interesting. AI was supposed to make startups more ambitious. But there is a risk that we take AI's productivity gains and use them to make venture capital more conservative. Build faster. Use fewer engineers. Spend less. Generate revenue earlier. Prove retention. Prove efficiency. Prove repeatability. Then come back for a Series A.

That may be a perfectly rational investment strategy. But perhaps we should acknowledge what actually changed. We moved a lot of venture risk earlier in the company lifecycle. And maybe that is okay. Markets change. Round definitions change. Capital becomes more selective. But we should not turn that into a new law of startup physics: good enterprise companies reach $3M ARR before Series A. Some will. Some exceptional companies will not.

Because there are really two clocks running inside every enterprise startup. The first is the startup's clock. AI is making that clock move incredibly fast. The second is the customer's clock. That clock still runs on budgets, security reviews, procurement, legal, organizational politics, trust, and human beings. And enterprise founders live in the gap between those two clocks.

AI compressed how fast software can be built. It did not equivalently compress how fast enterprises buy software. That may be the part we are forgetting when we decide what a Series A company should look like. Because enterprise revenue ultimately does not move at the speed of code.

It moves at the speed of trust.

If you are a founder living in that gap right now, or an investor who has said "come back at $3M" this year, I am curious: have you ever watched a company with the better machine lose the round to the company with the bigger number?

The $1.5M and $3M figures at the top are from a private conversation and are rounded. Benchmark figures are as published by the sources above through mid 2026; different datasets define "Series A" and "ARR" slightly differently, so treat them as direction, not decimals. Nothing here is investment advice.