How to Build a Why-Now Your PDM Will Accept

Ask a partner why an account is worth co-selling right now and the answer usually describes the partner. We are focused on this vertical this quarter. We have capacity opening in March. This is our target segment. Our new specialisation covers it.

Every one of those is a fact about the partner’s plan. None of them is a reason the account is ready. And a partner manager reads the difference immediately, because she is not evaluating your quarter — she is deciding whether spending her hours on this account is likelier to produce a closed deal than spending them on someone else’s.

The test: would this still be true if you did not exist?

A why-now is valid if it survives your removal from the situation.

“They are migrating a workload off a platform whose support ends this year” is true whether or not your company exists. “We are targeting manufacturing this quarter” evaporates the moment you do.

That single test resolves most of the confusion. It is worth applying literally, in writing, before a submission goes anywhere — and it disqualifies a surprising share of what partners currently put forward as timing.

Four things that are not a why-now

Fit.The most common substitution. “They are exactly our ICP” explains why they are on your list; it says nothing about the calendar. An account that has been a perfect fit for three years is evidence that fit does not create timing.

Intent data alone. Someone at the company read something about a category. That is weak, ambiguous, and available to every competitor with the same subscription. It can support a why-now. It cannot be one.

Your capacity or quota. Real constraints, and entirely yours. Presenting them as account timing is the tell that no account timing was found.

Funding rounds, absent a mechanism.“They raised a Series B” is used constantly and means little on its own. Money is not an initiative. What the money is being spent on can be — but that requires the next sentence, and most submissions do not have one.

Four things that are

A dated forcing function. A contract renewal, a support end-of-life, a compliance deadline, a data-residency requirement with a date attached. These are the strongest kind, because they carry their own urgency and the customer already knows it.

A visible commitment of resources. Roles posted against a specific workload. A team being stood up. A migration disclosed in a job description, a conference talk, or a public case study. Companies do not staff for things they have decided against.

A structural change. A new CTO or VP of Engineering, an acquisition creating two estates to reconcile, a market entry requiring infrastructure in a new region. New decision-makers re-examine inherited architecture; that is a window, and it closes.

A stakeholder who said so. The strongest and the most under-used. If a named person at the account has told you they are looking at this, that is not inference — it is testimony. It should be the first line of the submission, and it frequently is not mentioned at all.

The shape a good one takes

A why-now that works has three parts and fits in two sentences: the observable fact, the source that makes it checkable, and the consequence that makes it urgent.

They have posted four roles in eight weeks against a data platform they are visibly moving off, and the engineering lead who owns it replied to us confirming the timeline is this fiscal year.

Fact, source, consequence. It is checkable, it would be true without you, and it tells a partner manager exactly what she is being asked to support. Compare it with “strong fit, actively evaluating modernisation” — which asserts everything and evidences nothing.

Why-nows decay, and that is the point

A real why-now has a shelf life. A support deadline passes. A new CTO stops being new. A hiring burst finishes and the team is built.

Partners treat this as a problem. It is the most useful property the signal has. Decay is what makes a why-now a reason to act rather than a permanent description — and it is why a qualification written six weeks ago and never revisited is often worse than none, because it looks like evidence while describing a window that has closed.

Which has a practical implication: a why-now should carry the date it was observed. Anything else invites a submission built on a fact that stopped being true.

Write it before you reach out, not before you submit

The sequencing matters more than it appears. Most partners construct the why-now at submission time, working backwards from a conversation that already happened. That is reconstruction, and it produces the vague, assertive language partner managers have learned to discount.

Written before outreach, the why-now does something different. It becomes the reason the message is worth sending at all, which makes the outreach better. It is checkable later against what actually happened. And it forces a real refusal: if you cannot write a why-now that survives the counterfactual test, the correct action is to exclude the account and record why — not to send anyway and hope the conversation produces one.

A qualification system that never refuses anything is not qualifying. The excluded accounts, with their written reasons, are the evidence that the included ones mean something.

What it is worth downstream

The immediate payoff is a submission a partner manager can champion without doing your homework. The compounding payoff is that she learns your submissions are reliable, which changes how the next one is read — and that reputation survives her rotating out, because the next person reaches the same conclusion from the same evidence.

There is now a measurable version of this too. Partner Central returns an opportunity quality score and its trend on shared opportunities. A partner whose why-nows are genuine and dated will see that trend behave differently from one whose submissions assert timing. That is a slow feedback loop, and it is the only honest one available.