Who is a builder?
A builder is anyone turning evidence into product change. Not a job title. A role.
PMs are builders. Engineers are builders. Designers, founders, support leads who pattern-match across tickets, growth folks running experiments — all builders. The common thread: they author intent. They decide what's worth building, why, and what "done" looks like.
The word is deliberate. It collapses a debate that's getting noisy.
Why not "PM"
For decades, the answer to "who owns the spec?" was "the PM." That worked when implementation was the bottleneck — the PM filled the gap between business intent and engineering capacity.
AI coding agents removed the implementation bottleneck. The new bottleneck is upstream: who can describe what to build precisely enough that the agent doesn't guess? That person isn't necessarily the PM. Often it's the engineer closest to the user. Sometimes it's the founder. Sometimes it's a designer who saw the friction firsthand.
Tying the work to "PM" misnames it. The work is intent authorship, and anyone with evidence and judgment can do it.
Why not "engineer"
The counter-position — "engineers should own specs because they're the ones using the agents" — has the same problem in reverse. Engineers writing specs is fine. Engineers being the only people writing specs concentrates authorship in the layer least connected to user evidence.
The honest answer is that intent authorship is a craft, not a role. The person who should write a given spec is the person who has the evidence, the judgment, and the time. Pathmode names that person a builder.
Builder vs. operator, maker, creator
The word "builder" was chosen over alternatives for specific reasons:
- Operator — too business-y, suggests running things rather than making them
- Maker — too craft-y, suggests solo work and physical artifacts
- Creator — taken by the creator economy, suggests audience-facing content
- Builder — neutral, durable, role-agnostic, and already the word the audience uses
If you ship things people use, you're a builder. The tool you reach for matters less than the discipline you bring — and the discipline is intent engineering.