Postman Rewrote Its Homepage for Agents. Sourcegraph's Didn't Last.

3 October 2026 10:19 Will & Brian

Postman rewrote its homepage this week to speak to AI agents first: the first button now installs Postman for your agent. Sourcegraph had already gone agents-first, then put up an even harder line for about a day and took it back. Brian reads the pages like letters and asks who they are addressed to now; Will says what the growth team in that room was thinking.

Sources

Transcript

Click a time to jump there. Times are approximate.

Postman rewrote its homepage in the last couple of days, and the first sentence on it is now addressed to AI agents. Postman is the API tool, the one for testing an endpoint before you ship it. Sourcegraph, which indexes whole codebases so you can search them, went the same way about two weeks ago and kept it. Then yesterday morning it had a harder version of that page up, and by this morning the harder one was gone. So that is one decision, made twice in a fortnight, and one of the two is still working out how loudly to say it. What I want to argue about, once you've heard the pages, is who they stopped talking to.
You read homepages the way other people read novels, so read me Postman. Before and after, and tell me what moved.
Here is how I read one. A homepage is a letter, and the hero is the salutation, the Dear-whoever line at the top: who it is to, and what you want from them. Before, the page's title, the words in your browser tab, said world's leading API platform, sign up for free. That was still there yesterday. That's from our page monitor, by the way, The Beat's own tool: it checks a set of company pages every day and records what changed, and everything I say about a before comes from it. This morning the title and the hero are the same five words: "API engineering for your agents". Under it, go faster from development to production with higher accuracy and fewer tokens. Fewer tokens. That is a cost line, written for whoever pays an agent's bill. And the first button is not sign up. It is install for your agents, with an npm install command beside it. So the tab went from sign up free to Dear agent, install me.
Hang on. The sign-up button isn't the first button? On Postman? What else moved?
Most of the letter. The monitor flagged the page yesterday because its stored text grew by about two thirds in a day, so this was not one headline, it was a lot of new text underneath it. High up on the page sits the Context Graph, Postman's map of your whole API estate, with one line of evidence: an agent working from one checkout finds about a hundred and thirty of your services, and with the graph nearly four times as many. Their number, their product doing the counting, but notice the shape. The demo is an agent failing without them. And then, near the bottom, trusted by over forty million developers, their own count. It is the P.S. One more thing. The footer tells machine readers that a clean markdown version of the page exists. The letter comes in an edition meant for the agent.
The forty million are in the P.S. Right, let me be the growth team, and I am inventing this room: Postman has said nothing we can find about why the page changed. Picture the growth team's room. The forty million do not read the homepage, they open the app. The Dear line is for whoever you have not got, and in the last couple of weeks the company shipped three products for exactly that reader, all of them about agents and APIs, the last one a day or two before the page moved. The CEO's line on that launch was that a business whose agents cannot see or securely reach its APIs becomes irrelevant. Vendor words, but that is the pitch. So the room says: we own the map of the whole estate, and a new reader needs a map more than any person ever did. Lead with the asset, rent it to the new reader, and the old address still works on the pricing page, where the free plan for individuals still is. I think I would have won that room.
Good case, and I will come back to that free plan. Yours is the company that could not decide how hard to say it.
Sourcegraph. It indexes a whole codebase so a person, or now an agent, can find anything in it. The decision to write to agents was made months ago, in public: earlier this year its big release post called the platform the shared intelligence layer for developers and AI agents. The homepage caught up about two weeks ago, by our monitor. The hero became the context layer for your entire codebase, with agents named first in the line under it, and that hero is still live. Then yesterday morning the monitor caught a harder version of the same page. Same hero, but the problem section rewritten, and its new line was, "Codebases have outgrown the people who built them." Followed by a promise that your senior engineers would stop being the human search index. By this morning it was gone.
Gone how? Back to the old page, or on to a third one?
Back, word for word, this morning, and still back tonight. So it lived about a day, as far as our monitor can tell. Was it a test, a staged launch somebody pulled, a deploy that went out early? Nobody outside Sourcegraph can know, they have published nothing about it, and I am not going to pretend. What I can say is what was on each page. The one they kept says context layer, agents and developers. The one that lasted a day said the codebase has outgrown the people who built it.
Say that sentence again slowly, because I think it is the whole story. Codebases have outgrown the people who built them. The developer is not the reader of that line. The developer is the thing that got outgrown.
And the one they kept still has the developer in it. Second, but in. Here is why Sourcegraph can write to the agent without flinching. The pricing page has one plan. Enterprise, starting at sixteen thousand dollars a year, with an annual contract as the minimum. There is no individual on that page to lose. Nobody at Sourcegraph is missing a sign-up button: the button on that hero is get a demo.
Which brings me to Coder, the third one, briefly, through its pricing page. Coder sells enterprises self-hosted development environments and, since last month, a coding agent of its own to run on the same infrastructure. As of yesterday morning its Premium tier carries a badge reading includes AI governance. Until last month, AI governance, the controls on what an agent may do and what it costs, was an add-on, a separate per-user licence bought on top of Premium, in Coder's own docs. A release a month ago said to present it as included, the pricing page caught up as of yesterday, and there is no public price on the plan or on what the add-on used to cost. So governance is the floor at Coder now, not the upsell, and Coder's own beta number is the case for that: nearly seventy percent of its agent workloads came in through the API, not from someone chatting with an agent. Their number, from a beta. But if seven in ten of the jobs come in through the API, the policy about what they may do is not an extra.
So that is three. One wrote the agent in and kept it, one wrote it in, tried it harder, and the harder page came down, one made the agent's rules part of the base price. Argue with me. Is writing your front page to the agent the right trade?
Two problems, and the second is the one I care about. First, sameness. Both companies now use the same two words about themselves. Sourcegraph's hero says context layer. Postman's CEO, introducing the Context Graph API, called it a shared context layer for the systems that already do the work. Same fortnight, same noun. April Dunford, the positioning writer, has a line about AI features sold as positioning. "Who cares? Nobody cares. Everybody's got one of those." Second-hand, from a write-up of a podcast. If every devtool's Dear line says for your agents, none of them is positioned. Second, and this is mine: who stopped being addressed. At Postman it is the individual who opens the app to test one endpoint, the forty million. That person got the old title's promise, sign up for free, and now gets a desktop install button and a line near the footer. And since the spring the free plan is one user. One. No team, where before a few people could work together for free. Postman's own docs say so. So the letter did not just change who it is to. The free plan got smaller in the same year the salutation changed. Not a connection I can prove. Not one I will ignore.
Every devtool that sells to teams should write the agent in by the end of... no. Strike that. Postman can write Dear agent because it owns the map, and Sourcegraph can because it owns the index, and an agent needs a map or an index more than any person ever did. If you own nothing the agent needs, for your agents on your homepage is Dunford's sentence with your logo on it. On the free plan I have no answer. One user is one user. But the Coder page is the strongest thing on the table and it's on my side. If seven in ten jobs come through the API, the person who signs is a platform or security lead, and for your agents is how you tell that person you have thought about what theirs will do. That reader is addressed more, not less.
Then say that. Write to the platform lead. Whatever happened in Sourcegraph's room, and I do not know, the letter still up this morning is the softer one. The page that gets kept is the one that knows whose name goes after Dear.

Will and Brian are fictional hosts voiced with ElevenLabs, and the music is made with ElevenLabs; the episode was researched and written by AI agents and fact-checked against the sources above. ElevenLabs is a company this site covers; it is a tool the site pays for, not a sponsor.

transcript as markdown mp3 all episodes