What "0 to 1 as sole PM" actually looks like
No design lead, no research team, and a small engineering team. The honest version of what building from scratch actually involves.
5 min read
Most writing about 0 to 1 product work makes it sound like a specific kind of adventure. Blank slate, endless possibility, the thrill of building something from nothing. That framing is not wrong but it leaves out most of what the job actually involves.
Here is the more accurate version.
You are the only one holding the context
On a larger team there are people whose job is to remember things. A product designer who knows why a decision was made six months ago. A researcher who documented what customers said in the last round of interviews. A product ops person who maintains the source of truth.
When you are the sole PM there is no one else. Every decision, every trade-off, every piece of customer feedback that shaped the current direction lives in your head or in whatever system you have built to get it out of your head. If you do not write it down it does not exist. If you leave, it leaves with you.
This sounds manageable until you are three months in, the team has grown, and you are trying to explain to a new engineer why the data model looks the way it does. The real discipline of sole PM work is treating documentation as a core deliverable, not an afterthought.
Discovery does not stop when you start building
The temptation in early stage product work is to treat discovery and delivery as sequential. You figure out what to build, then you build it. In practice they run in parallel and they have to.
Customers will tell you things during development that change what you are building. Engineers will surface constraints that make the original approach unworkable. The market will shift. A competitor will ship something that makes your planned feature less interesting.
The teams that handle this well are the ones where the PM is still talking to customers during active development, still updating the direction based on what they learn, and still communicating those updates clearly to engineering without blowing up the sprint every time something changes.
Your relationship with engineering is everything
Without a designer, a researcher, or a product ops function, the PM to engineering relationship carries more weight than it would on a larger team. There is less buffer. Decisions get made in conversation rather than in structured review processes. Trust matters more because the feedback loops are tighter.
The mistake is treating engineering as a delivery function rather than a thinking partner. The engineers building your product early on will see things you do not see. They will have opinions about the product that are worth hearing. A sole PM who runs a tight requirements process and keeps engineering at arm’s length is leaving a lot of value on the table.
The isolation is real
There is nobody to pressure test your thinking with before you take it to the team. No peer PM to gut check a prioritisation call or push back on a direction that might be wrong. You are making consequential decisions with incomplete information and no one in your immediate orbit who does the same job.
Some people find this energising. Others find it quietly exhausting. Most find it both at different points. The useful habit is building external feedback loops deliberately. A mentor, a peer network, a former colleague who will give you an honest read. The absence of internal peer pressure does not mean you should stop seeking it.
What actually makes it work
Not speed. Not having the right framework. The thing that makes sole PM work sustainable is being honest about what you do not know and building a team culture where that honesty is normal.
You will make calls with incomplete information. Some of them will be wrong. The teams that recover well from wrong calls are the ones where the PM modelled intellectual honesty from the start. Where changing direction based on new information was treated as good judgement rather than a failure of planning.
That is available to you regardless of team size. It is just more visible when you are the only PM in the room.
By Curtis Blunden
12 March 2026