Everyone Is a Builder Now

July 6, 2026 6 min read

Product management is dead. Design is dead. Engineering is dead.

Except none of that is true, and anyone who tells you they pointed an agent at a prompt and it farted out a billion-dollar company is selling something. What is actually happening is more interesting: the three jobs are collapsing into one.

Call it the product builder. A person who holds the whole picture, from "what should this even do?" to "it shipped, it feels right, and customers love it," and refuses to hand any part of that off to someone else's queue.

The bottleneck moved

For most of software's history, the bottleneck was making the thing. Writing the code, cutting the pixels, wiring the backend. So we organized around production: specialists, handoffs, tickets, a PM to decide, a designer to draw, an engineer to build, and a game of telephone in between.

Agents broke that model. Coding agents make anyone an engineer and make great engineers 10x. Design tools are catching up fast. Production is no longer the scarce thing.

Here is what did not get cheaper: knowing what to build and why. Taste. Judgment. The courage to ship something opinionated instead of something safe. When you can build anything in an afternoon, the constraint moves from "can we make it?" to "should we, and is this the version worth shipping?" That is a product question, and it is now everyone's job.

This is the gap. Call it the infinite monkeys problem: point an agent at an open-ended prompt and it will confidently build something, just not always toward where your company is actually trying to go. AI-powered teams are shipping faster than they can think, which means they are shipping blind. Decisions get ignored. The same question gets answered five different ways by five different agents. Speed was never the problem. Judgment is.

What a product builder actually believes

The role is new, but the standard is old. A product builder runs on a few convictions:

Care. The difference between a beloved product and generic output is that someone sweated the small things. Agents will hand you plausible. Care is what makes it right.

Context over cleverness. The best decision is the one made with the full picture: the customer, the constraint, the business model, the thing you decided last month and forgot. Cleverness without context just ships the wrong thing faster.

Shipping over signaling. No performance of work. No decks about the work instead of the work. You are measured by what reaches a user and how it lands, not by how busy you looked getting there.

Breadth becomes depth. The more ground you cover, the sharper your judgment gets. Time in the field, across disciplines, across customers, is not a detour from the craft. It is the craft.

Us. Nobody builds a whole product alone, agents included. The job is to hold the picture and bring the room with you.

The job takes two shapes

We are hiring product builders, and we have learned that the disciplines blend but the best people still have a center of gravity. So we are hiring for two shapes of the same role.

The first is engineering-centered. A long tenure writing real software, paired with genuine taste for how a thing should feel to use. This is the person who owns entire features end to end, product definition through implementation, and cannot leave something alone until it is right. They use Claude and Cursor as a collaborator, not autocomplete, and they build a product that agents themselves use.

The second is forward-deployed. A product-and-people builder who goes into our biggest customers, wires Brief into their real context, wins the skeptics, and drives a measurable step-change in how they build. Think of a PM crossed with a management consultant who loves to prototype. The hard part, and the whole point, is change management: moving an organization off habits it has held for years without breaking trust. Breadth in the field becomes depth in our roadmap.

The unified role makes sense to start, but the taste required to build developer tools is not the taste required to build consumer apps. Over the next few years the product builder will bifurcate and specialize again: more engineering-oriented product people, more product-oriented engineers, each needing something different from the agents that support them. These two shapes are the leading edge of that split.

Two shapes, one conviction: hold the whole thing, and make the call.

Why this matters beyond us

We are building Brief because Product was the one corner of this shift with no tools. Coding has Claude Code and Cursor. Design has its new stack. Product had strategy-dot-md and bots that turn Slack messages into Jira tickets. So teams building at agent speed had no navigator, and it showed.

Brief is that navigator. It aggregates the business context, decisions, customer research, work pipeline, team knowledge, and makes it legible to both people and their agents. It matters because most of what agents burn tokens on is rediscovery: hook up a Notion MCP and every new session your agent crawls the same docs again, chewing through context just to relearn where your strategy lives. We call those dumb tokens. Brief calls that data once, shapes it, and hands the agent a tight book report that costs a few percent of its context window instead of a chunk of it.

The results are measurable. In our own dark factory, two agents ran the same open-ended prompts, one with Brief and one without. With Brief, the agent reached the right solution about 95% of the time. Without it, roughly 46%. Same model, same prompt. The only difference was whether it knew what the company was actually trying to build. AI ships. Brief navigates.

But the tool is downstream of the belief. The belief is that the future of building software belongs to people who can hold product, design, and engineering in one head and have the taste to know when it is right. Everyone is becoming a builder. The only question is whether you build with judgment or just build fast.

We would rather build with judgment. If that sounds like you, we are hiring for both shapes of the role.