Everyone can build now. Nobody made more buyers.

The thread

In the third week of September a post on r/SaaS titled "AI made everyone a builder. It forgot to make more buyers." collected about two thousand upvotes and two hundred comments in a few days. The title is the whole argument, and the comments are founders agreeing with it from inside their own launch: the product took a weekend, the first hundred users took a quarter, and the second hundred have not arrived.

I would have filed it as a mood if the numbers had not landed the same month. Founder threads run hot and then cool; a study of a hundred thousand developers does not. When both point the same way in the same month, the mood is a measurement that has not been written down yet.

The numbers

Three economists, Leon Musolff at Wharton and Mert Demirer and Liyuan Yang at MIT, tracked over 100,000 developers on GitHub from 2022 to 2026 and matched them to tool usage. Knowledge at Wharton summarised the findings. Autocomplete raised coding activity by 40%. Adding agents that edit alongside the developer took the cumulative increase to 140%. Autonomous agents, working from a prompt, took it to 180%.

Then the funnel narrows. Projects rose about 50%. Releases rose about 30%. At the app store level the flood is visible: Apple App Store monthly releases went from roughly 30,000 to roughly 100,000 by April 2026. And the last line, the one that matters for anyone selling software: overall usage across the four major app stores remained flat or declined. In the article's words, AI is increasing the number of new applications, but not user adoption.

Read that as a supply chain. Code is cheap. Shipping is cheaper than it was. Being chosen costs exactly what it cost before, because the thing that chooses is a person with the same number of hours.

What moved

For twelve years I have watched developer platforms, JetBrains to CNCF projects, win on the same input: a claim a developer can test in ten minutes, and evidence that someone like them already did. That input did not get cheaper. Every step before it did.

So the constraint moved. It used to sit at "can we build this". It now sits at "will anyone spend an evaluation on it". A developer evaluating tools in 2026 has the same hours and an order of magnitude more candidates, and the first cut is brutal: the README, the first sentence of the homepage, the one comparison page, the answer an AI assistant gives when asked what to use. If those do not state who it is for and why it is different, the evaluation goes to the next tab, and the next tab is one of a hundred thousand.

This is why star counts stopped meaning what they meant. A repository can be generated. A thousand stars can be bought or farmed. What cannot be generated is a specific claim that turns out to be true in production. That is the whole of positioning, and it is now the scarce part.

What a seed or Series A founder should do

Not more building. Four things, in order, none of them a campaign.

1. One positioning statement your engineers will sign. Who it is for, what it replaces, why it is different, in words the team would say to a peer without wincing. If they wince, the statement is marketing and the market will treat it as such.
2. One channel, worked properly. The place your buyer already evaluates tools. For most developer products that is one of: a specific community, search, or the AI assistants that now write the shortlist. Pick one. Two half-worked channels produce nothing measurable.
3. A README that reads as the product's homepage. It is the page the developer reads first and the page the AI assistants quote. If it opens with install instructions and no claim, it has already lost the evaluation.
4. A measurement before and after. Unbranded AI answers, the comparison query, trial-to-paid, whatever the number is that your channel moves. Read it before the work and again after. Without the first read the second one is a story.

Everything else on the usual launch list is volume: more posts, more integrations, more features shipped. Volume was a way to be found when the supply was small. It is now a way to be one more entry in a feed that grew three times faster than the people reading it.

The uncomfortable part

The thread's title puts the blame on AI for not making buyers. That is not quite right. Buyers were never made by tooling; they were made by being convinced, one at a time, and that process was always the slow part. What AI did was remove the excuse. When building took a year, a launch could fail on execution and nobody had to ask whether the claim was clear. Now the build takes a weekend, and the only thing left to fail on is the claim.

If you run an open-source developer tool and the stars have stopped turning into users, the open-source go-to-market page walks the commercial motion. If the problem is earlier than that, the claim itself, the Growth Pilot is four weeks and $5,000: the claim written in week one, then two experiments that test it with your real users and channels, and a decision every Friday on what continues.