The PMM's first 90 days: how to earn your seat at the table before you know the product

Two weeks into the new job, there's a battle card.

Also a draft message house, a competitor teardown, and the skeleton of a positioning deck. Real work, all of it, produced before anyone talked to a buyer.

Call it credible fiction. Work that's well-made, confidently formatted, and quietly wrong, because it was built on an inherited view of the customer rather than a firsthand one.

That's the expensive part. Nobody rejects credible fiction, because it looks finished and it's hard to argue with. People adopt it, and then it's the company's story for a year.

---

Salt before ice

The pressure to produce is legitimate. Leadership wants to see what you're working on, the backlog of neglected work is real, and starting a new job is uncomfortable in a way that making things relieves.

And there's something we all have in week one and never get back. It isn't energy. It's ignorance.

Right now we can see the water everyone else is swimming in. The jargon still sounds like jargon, and the category claim still sounds like a claim rather than a fact.

In two months all of it sounds normal, and we've lost the only view of the company a buyer shares.

You salt a driveway before the ice, not after. Same bag, same twenty minutes.

Do it Tuesday night and nobody falls. Do it Wednesday morning and you're out there with a shovel, chipping at something that's already set.

The listening window works the same way. The work is identical in month one and month six. The value isn't.

---

The listening tour

The first month has one job. Build a first-principles read of the market, the buyers, and the internal politics before you're too embedded to see any of it.

Run the same conversation with everyone who touches go-to-market. The same questions every time, so the answers can be compared:

• What's the hardest part of your job you think product marketing could help with?
• When we've beaten a competitor, what was actually true?
• If you were rewriting the homepage, what would you change first?
• What do customers think we do, and what do they actually care about?
• What's the problem everyone knows about and nobody has named?

Run those with your VP or the CEO, three to five AEs, a couple of CSMs, the strongest product manager, and a marketing peer. Twelve to fifteen conversations.

Tag the themes as you go. Notice where two functions contradict each other about the same buyer, because that contradiction is the most valuable thing anyone will hand you all quarter.

Sit on a dozen sales calls, minimum. Listen for the words buyers use for their own problem, which objections repeat, and which part of the pitch makes someone lean in.

Live call language is primary source material. Everything else is a derivative of it.

Pull the last six months of deals and run a win/loss analysis retrospective with sales ops. CRM data is always imperfect and patterns still emerge.

If a lot of losses are logged as price, dig into those specifically. Price is the proxy answer. Underneath it usually sits positioning, differentiation, or sales execution.

Then read what already exists. Customer Slack channels, support tickets, G2 reviews for you and for your competitors, call transcripts if you have them.

By day thirty you should be able to say who the ICP actually is versus who the company believes it is, and which single project would move something real.

Don't publish any of it yet.

---

A testable position

Month two turns notes into a point of view. Most of us skip it and go straight from listening to building, which is how we end up with a beautifully made answer to a question nobody asked.

Write a positioning hypothesis. Hypothesis is the operative word.

What's the most defensible, differentiating story this company can tell right now? What customer outcome sits at the center of it, and what did you actually hear that supports it?

Then show it to two or three people and ask where it breaks. A rough document at day 35 that draws pushback is exactly right. A polished one at day 70 is late.

Write an internal narrative document alongside it. Prose, a few pages, no deck. Here's the buyer, here's their problem, here's what else they're considering, here's where we fit and why that matters.

Built on their language, not ours.

Then test the ICP against the pipeline. Most companies carry an official ICP from a whiteboard at some off-site, alongside an empirical one made of the customers who actually renew and expand.

Those two rarely match, and the gap between them is worth more than either document alone.

Audit the enablement inventory while you're in there. What exists, when was it last updated, and is anyone opening it?

The temptation is to fix everything. Resist it. The audit exists to find the one thing that, if it existed and was good, would most change win rate or ramp time.

That's your first project. Agree on it with your manager before month three starts, and if they see a different biggest gap, that disagreement is worth more than the agreement would have been.

---

The first artifact

Month three is execution, deliberately narrow. One thing, done well.

Pick it on three tests. It solves a pain multiple people named unprompted, it uses buyer language from the listening tour, and it has an outcome you can actually track.

The usual candidates are a battle card for the competitor reps mention constantly, a one-pager rebuilt on customer language, a discovery framework for sales, or a landing page variant that tests the core message.

Get two reps and a CSM to review it before it ships. Their feedback improves the work. Their fingerprints on it are what make it get used.

Then ship it with context, because a Slack post isn't a launch. Twenty minutes, live, with four things covered. What you heard from customers, what hypothesis this is testing, how to use it, and how you'll know whether it worked.

That session isn't optional. The artifact is the mechanism and the session is the conversion.

Two weeks later, go back and ask. Did anything move on the deals where it got used?

What came back, and what would you change?

That loop is the difference between shipping work and running a program.

---

The mistakes worth naming

Three habits cost new PMMs the most, and all three feel responsible at the time.

We absorb the internal pitch and repeat it outward. Feature names, framework jargon, the category claim.

Most of it was written to settle an internal argument, and buyers have never once responded to it. The job is translation, and transcription is what we hand in.

We run new research before finding the voice-of-customer research already sitting in the building. There are almost always interviews, recordings, and reviews nobody has synthesized into anything.

We usually have better data than we think. It's just scattered and unlabeled.

We take the internal competitive story at face value. It gets shaped by whatever was won and lost recently, usually against one competitor, often under strange circumstances.

The rep who lost three deals to them is the loudest voice in the room, and every deal where competition never came up goes unmentioned.

---

The first PMM

If you're the first product marketer this company has ever had, everything above holds and three more things become true.

You'll be asked to define the job. Leadership hired a PMM because something hurts, and they often can't name what product marketing is.

Write the scope and the boundaries down with your manager in the first month. The role is inherently political and the ambiguity never resolves on its own.

The GTM alignment problem is probably severe. Sales pitches inconsistently, launches don't move anything, and the website reads like an internal FAQ.

Map that gap explicitly in your first ninety days. Closing part of it is usually the most visible early win available to you.

And start with sales enablement, even though positioning is the strategic foundation and should logically come first. Your credibility comes from solving the loudest named pain in the room.

Build one excellent enablement deliverable, then spend the goodwill on the positioning work that should have come first.

---

At day ninety, you've shipped one thing that's in use, you can name the ICP and defend it against pipeline data, and one AE trusts your judgment enough to call you before a hard meeting.

You don't need it right yet. You need to know what the next ninety days have to be.

The ice is coming either way. Salt now.

---

What to do next

If you've just landed and the pressure to produce is already stacking up, the most useful thing you can buy is an outside read of the buyer. That's what a positioning audit is, and it starts with the customer conversations nobody has time for.

If that's where you are, start here. The first conversation is free.

---