How I Went From Sales to Product Management

You move from sales to product management by converting customer exposure into product evidence: own a metric, ship something small, and document decisions the way a product manager does. Sales gives you the single hardest thing to teach a PM — hundreds of real conversations about why people buy, hesitate and leave. What it does not give you is the discipline of saying no to a customer, and that is the gap interviewers probe.

This is how the move went for me, what actually transferred, and what I had to unlearn.

What sales gave me that PMs usually lack

Volume of customer contact. In an account-management year at Just Eat I spoke to more customers than most product managers speak to in five. That produces pattern recognition you cannot get from a research readout: which objections recur, which reasons for leaving are the real ones, and the difference between what a customer says in a survey and what they say when a renewal is on the table.

Comfort with rejection. Product work is mostly having your idea disproved, and salespeople are unusually well trained for that. The second half of a bad discovery call is where the useful information sits, and people who have never been told no professionally tend to leave early.

Commercial instinct. Sales teaches you what things are worth, why deals stall on price versus trust, and how to read a buying process. A large share of PMs learn that late, if at all — and it is the skill that separates a roadmap from a business plan.

What I had to unlearn

Solving for the customer in front of you. In sales, the loudest account gets the attention and that is correct behaviour. In product, that instinct produces a roadmap made of one-off requests from your three noisiest customers and a product that serves none of them well.

Closing instead of investigating. A sales conversation is designed to converge. A discovery conversation is designed to diverge — you want the messy answer, not the yes. I had to consciously stop steering.

Treating a feature as a concession. It is easy, after years of unblocking deals, to see the roadmap as a set of things you can give away to win business. Occasionally that is right. Usually it is how a product loses its shape.

The five steps that actually made the move

• Owned a metric nobody else owned — churn reasons on my accounts — and reported it weekly until it became the product team's input.
• Turned customer patterns into written briefs: the problem, the evidence, the size, the options. Product managers noticed the briefs before they noticed me.
• Shipped something small myself. Internal tooling first, then real products. Building removes the abstraction between wanting a thing and understanding what it costs.
• Moved internally rather than applying out. The first product job is far easier to get at a company that already trusts your judgement.
• Kept the sales access. Even as a PM I stayed on customer calls, because giving that up is what makes product managers slow.

Where it ended up

From account management into product roles at Just Eat and Sage, then founding and running product at Wocal, and now building AI products for founders and running fractional product leadership. The commercial grounding never stopped mattering — in AI product work especially, where the deciding question is usually 'does this cost less than the value it creates?' rather than 'can the model do it?'.

If you are making the same move: your customer exposure is the asset. Convert it into written evidence, own a number, and ship one real thing. That combination is what gets you interviewed, and it is a stronger case than most internal candidates can make.