Two Jobs One Word

How everything ends up on one plate

Now watch what happens to that one hire in a real company. A good product person sits at a natural crossroads. They talk to customers. They talk to engineering. They know what is being built, why, and when it will land. That makes them the most convenient person in the company to ask about almost anything. And in a young company, convenient wins, because there is no one else to ask. So they become the roadmap owner, and then also the launch owner, and then also the pricing owner, and then also the person sales pings when a competitor comes up in a deal.

Here is the important bit. Each of those things, on its own, looks reasonable to hand over. Nobody sat down and decided "let's overload one person." It happened one favor at a time. A launch here. A pricing question there. A battle card because the deal was hot and someone needed it by Friday. Every handoff made sense in the moment. The problem is never one item. The problem is the pile.

And a conscientious person will try to carry the pile, because that is what conscientious people do. That is exactly what makes this so hard to spot. The work doesn't get dropped loudly. It gets done at sixty percent, late, or last. Which is a different failure, and a sneakier one.

Why one discipline always starves

Here is the nasty part. When one person carries both disciplines, one of them starves. And it is almost always the same one.

Product Management wins the fight for attention, every time, because its work has alarms attached. Sprints have deadlines. Engineers are waiting. Things break loudly when the roadmap slips. Product Marketing's work has no such alarm. Vague positioning doesn't page anyone at 2am. Thin messaging doesn't fail a build. So when both live in one overloaded inbox, the urgent inward work crowds out the important outward work. Not through neglect. Through gravity.

Think of it like asking your best chef to also run the dining room on a Saturday night. They might be able to. But every minute they spend seating tables is a minute the kitchen runs without them, and something in the back is starting to burn. It is not that they don't care about the food. It is that the room in front of them is on fire and the oven is merely getting slowly worse.

The leak: where it actually costs you

And because the half that starves is the outward half, the damage lands exactly where you can least afford it: in go-to-market. The stuff that falls through the cracks is not random. It clusters, and it clusters at the moment you are trying to win a deal.

Watch what leaks when the market-facing work has no real owner. The salesperson can't crisply say why you beat the competitor, so the deal drags and slips to the incumbent. The launch goes out as a changelog note instead of a moment, so a genuinely good feature lands with a shrug and nobody in the market notices. Pricing gets set on gut feel and cost-plus, so you leave money on the table on every contract, quietly, forever. The one-pager the account exec needed never quite existed, so they built their own from memory in the deal, and got the message subtly wrong. Win and loss reasons never get gathered (CRM hygiene), so nobody actually knows why the big deals are dying.

None of these show up on the product roadmap. None of them break a build. That is exactly why they are dangerous. They leak straight out of the commercial side of the house, where every drip is revenue, and they leak silently.

And here is the real issue. A product-strong company with this problem often looks completely healthy from the inside. The product is good. Retention is fine. Existing customers are happy. So when deals are lost, leadership reads it as a sales problem, or throws more roadmap at it, because "product" feels like the answer. It isn't. The product was never the issue. The market's understanding of the product was. That is a Product Marketing gap wearing a Product Management costume, and it gets misdiagnosed almost every time.

Why it gets more expensive as you grow

You might think this is a small-company problem you will grow out of. It is the opposite.

When a company is young, the product mostly sells itself to a narrow, similar set of buyers. The founder does the positioning by instinct in every sales call. The gap is there, but it is tiny, so nobody notices. Then the company grows up. It moves upmarket. Deals get bigger and more competitive. Buyers get more sophisticated and start asking harder questions about why you, not them. This is exactly the moment the market-facing work stops being optional and becomes the difference between winning and losing the deals that matter most. And it is exactly the moment your overloaded product person has the least time to do it, because the roadmap has grown too.

So the gap doesn't shrink as you scale. It widens. A company that looked perfectly healthy can be quietly losing its best, biggest, most competitive deals a year later, with a product team working flat out the whole time. Everyone is busy. Everyone is doing their best. And the deals still leak, because the work that would have won them was never truly anyone's job.

For European companies this bites harder still. You are not selling into one big, uniform market. You are selling across languages, buying cultures, competitive sets and regulatory quirks that change from one country to the next. That is more positioning work, not less, and more of the low-hype, proof-led messaging that European buyers actually respond to. It is precisely the kind of nuanced, market-by-market work that dies first when it is squeezed into the corner of an overloaded week.

The question nobody asks: not "both," but "which first"

Here is where the small-company reality bites, and where honest advice diverges from the textbook.

At two or three million ARR, you cannot afford a Product Manager and a Product Marketer. The textbook answer (hire both and let them specialize) is a luxury you don't have. So the demarcation stops being an org chart and becomes something more useful: a diagnostic for spending your one scarce hire well.

Ask what is actually breaking. If engineering is building the wrong things, priorities are a mess, and there is no discipline behind what ships, you need Product Management first. Full stop. No amount of beautiful positioning saves a product that's being built by guesswork. But if the product is genuinely good, retention is healthy, and you are still losing deals you should win because the market doesn't understand why you're different, you may need Product Marketing first, even before a "classic" Product Manager. That is the case most European founders miss, because "we need a product person" almost always translates, by default, to a Product Manager, and everyone assumes the marketing half will simply happen on its own. It won't. It never does.

The default hire is not the wrong hire. It is just the unexamined hire. Decide on purpose.

So what should you actually do?

You don't need a re-org. You need to make four decisions.

1.  Name the two jobs, even if one person does both for now. Write down what is Product Management and what is Product Marketing. Just seeing the two lists on paper shows you how much market-facing work has been living, unowned, inside a role that was never scoped for it.

2.  Run the "own it or support it" test on every activity. For each item, decide whether the function owns it or merely supports it. This one question kills most turf confusion before it becomes a fight, and it stops your one hire from silently signing up for everything.

3.  Diagnose the real constraint, then sequence. Building the wrong thing points to Product Management first. Building the right thing that the market doesn't understand points to Product Marketing first. Hire against the gap that is actually costing you money, not the one that is easiest to picture.

4.  When the second hire arrives, protect the line. The moment you can afford both, defend the demarcation. Left alone, the urgent inward work will always eat the important outward work. That is gravity, and you have to build against it on purpose.

"Product" was never one job. The companies that scale cleanly are the ones that admit that early (that draw the line between building the thing and selling the thing) and then hire against the gap that's actually leaking, not the one that's easiest to imagine. None of this is complicated, and that's the good news. The work falling through the cracks is only invisible while it stays hidden inside one overloaded role. Draw the line on purpose, and the empty chair stops being a guess. It becomes a decision and a decision is just money waiting to be collected.