When to make your first product hire, and what to have in place first

Make your first product hire when the hours you spend on day-to-day product work cost the company more than they return, usually after you have signs of product-market fit. Before that hire starts, have three things written down: the North Star, the decisions already made and why, and the outcomes the team is working toward. A new hire cannot inherit what lives only in your head.

When is the right time to hire a first product manager?

The right time is when product work starts to crowd out work only the founder can do. First Round's advice from Saumil Mehta frames it as opportunity cost: log your tactical product time for two or three weeks, list what you missed, and weigh the cost of those misses.

Mehta adds other signals. The volume of decisions, feedback, and data starts to overwhelm the founders. The product grows more screens, user roles, and integrations. He also expects AI to push the first hire earlier, because engineering and design now produce work faster than one person can direct it.

NEA's guide to the first product hire sets a stricter bar: product-market fit, an engineering team of more than seven people, and a founder who is ready to share control of the roadmap. The two views agree on one point. Hiring before you have found product-market fit yourself usually backfires.

What should a founder have in place before the hire?

A founder should have the reasons behind the product written down, not only the backlog. A product hire who gets a task list and no reasons will either ask you about every call or quietly make different ones.

Write down at least these four things:

• The North Star. One metric the product aims at, and why that one.
• The decisions so far. What you chose, what you did not choose, and why. Include the calls you would not want reopened.
• The outcomes in flight. What result each current piece of work is meant to move.
• What you still own. Vision and strategy usually stay with the founder. Say so out loud, so the hire knows which calls are theirs.

This is the same record you would want for an agent. People and agents both do better work when they can read why the work exists.

What does a first product hire actually do?

A first product hire turns the founder's direction into a working rhythm. NEA describes the job as balancing growth against stability, building testing habits, setting the team's cadence, and filling gaps in design and data.

That is why both sources say to hire a builder. NEA's advice is direct: "find a builder, not a maintainer." Someone who has only run an established product may struggle when there is no process to run yet.

Can AI do the product work until then?

AI can carry much of the routine product work, but a person still makes every judgment call. Choosing what to build, what to drop, and what risk to accept stays with the founder until there is a product hire, and then with both of them.

Here is what the W agents do today for a founder without a product hire:

• Wizard by Ask The W tests an idea against the market and the numbers. It shows a verdict, who could buy, who already competes, monthly revenue against your goal, and what could make the idea fail. It then turns the chosen idea into a project plan.
• Way by Ask The W keeps the decisions, outcomes, next moves, and North Star. Each decision records what was picked, why, and the options not chosen. When an outcome's last move is marked done, Way asks whether it worked. If the answer is no, the decision comes back with the other options.
• Workspace by Ask The W writes project documents from the project's own record. Its Hiring kit writes a role scorecard, a job description, an interview loop, a take-home task, and offer and leveling notes. The scorecard lists the outcomes the hire has to produce, not a skill list.

None of this makes the hire for you. It means that when the hire starts, the record they read on day one already exists. For how Ask The W handles product management work before the first hire, see AI product manager.

What should the first week look like?

The first week should be reading, not shipping. Give the new hire the North Star, the decision record, and the open outcomes, and ask them to find three decisions they would question.

Their questions tell you two things. First, whether your record is clear enough to hand over. Second, whether they think like a builder. A good first product hire will challenge a decision with evidence, not just with a different taste.

Then agree on the line between their calls and yours. Write that down too. It becomes the first decision they inherit.