Hire a product manager when selling time beats building time
Former LocBox founder and Square product chief Saumil Mehta says the answer is in your calendar, not in a headcount rule.
First Round · When Should You Stop Clinging to Product and Hire Your First PM? Advice From a Founder and CPOSaumil Mehta, who sold his startup LocBox to Square and later led product there, offers founders a test for letting go. As he puts it: "Hire your first PM once the marginal hour you spend on product work is worth less than the same hour you might spend on go-to-market or company building." By go-to-market he means getting customers to buy, through selling and marketing, along with hiring and other work that builds the company.
The test matters because founders should keep control of product direction, but the daily product chores compete for the same finite hours. Mehta argues that once planning, triage, and feedback summaries crowd out customer and company work, the equation flips.
To run the test, he says to track your days for two or three weeks. Write down hands-on product chores like choosing details inside a feature, leading planning for the next stretch of engineering work, and reviewing usage numbers, then average the hours per week.
Add a rough percentage to the logged hours to cover time lost switching in and out of product work.
In those same weeks, keep a second list of valuable work you skipped for lack of time, such as, for example, a sales conversation you postponed, a key hire you did not start, or outreach to customers you never made. Add any high priority work you handed to others that might have gone better if you had done it yourself. The two lists are then compared.
Set the logged product hours against the skipped company work and ask what that gap cost the business. That is the opportunity cost. The log might tell you to wait, or show you are already overdue. Either way, Mehta says, the comparison helps you make a more intentional choice about hiring.
Questions people ask
What counts as tactical product work versus product strategy a founder should keep?
Tactical work is the recurring execution of building, such as prioritizing features, planning engineering work, triaging bugs, and turning customer feedback into specifications. Strategy is the bigger choice of which customers to serve, what problem to solve, and why you will win. Mehta argues founders should keep the strategy reins even after they hand off the tactical load.
How many hours of product work means I should hire?
There is no fixed number, because it depends on what else needs you. The signal is when 10 to 15 hours a week of tactical work plus switching time is crowding out selling, hiring, or fundraising. If those company building tasks would create more value than the product tasks, that is the flip point.
What does a first product manager actually do day to day?
A first product manager synthesizes inputs from customers, engineers, designers, and data, then makes prioritization calls under uncertainty. In practice that means running planning, writing clear requirements, analyzing usage, and saying no to lower value requests. The goal is to keep engineering and design moving without the founder in every decision.