Session
I Spent Two Years Building the Median. Novelty Is Scarce, The Median Is Free.
Ask a hundred AI-native teams to build the same product and they build the same product. On most of your stack, differentiation is arithmetically impossible. I learned this by losing.
I shipped an AI code review tool. Anyone could bolt a model onto a diff and get review comments, and that is what I did, along with a hundred other teams that year. First-time users were impressed. The praise flattered me into under-investing in the one layer the median could not reach, the part that understood the repository. By mid-2024 the competition had pulled ahead. Their model was no better than mine. I had spent my time on solved plumbing and left the unsolved understanding half-built.
The trap is not building the wrong thing. It is that the commodity part works well enough to hide the fact you never built the moat.
Why it happens. A model does not deliberate. It reaches for the highest-probability continuation drawn from a corpus every competitor also trained on, and the highest-probability continuation is the canonical answer the field already agreed on. Where a problem is solved, every AI-native team receives the same median on the same morning. Thinking harder there produces the same output more slowly.
The split. Roughly 60 to 80 percent of a product stack is solved territory: retrieval plumbing, evaluation scaffolding, integration surfaces, the diagram, the compliance matrix. Retrieve it, ship it, move on. The residual 20 percent is your customer's specific reality, unposed at internet scale, unretrievable from any model. That is the only ground where effort still moves the needle.
A diagnostic you run this week. Take your last three product decisions. For each, ask whether every AI-native competitor would have arrived at the same answer. If yes, and it cost you more than a day, you spent your novelty budget in the commodity zone.
The last third is the operational consequence. Spine and Leaf is the shape I now build in: one immutable Spine holding the customer's problem in their own language, which is the unposed 20 percent, and seven Leaves that are the solved 60 to 80 percent, authored by agents from the Spine alone and never from each other. Deliberation concentrates in one file. Retrieval concentrates in the rest. I will show a shipped open-source product built this way, with 56 features each traced to a commitment and a named passing test.
The claim is falsifiable and I will say how. If a hundred AI-native teams do not converge, the argument is weaker than I think it is. Come and tell me.
Hariprasad Sudharshan
Product Leader AI, who still writes code
Dallas, Texas, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top