A release earns Tier 1 status by scoring high on three inputs — how many users it reaches, how much revenue it touches, and how much it differentiates you from competitors — weighed against the coordination cost of a full launch. Score each factor 0–3, total the first three into an Impact Score, and match that score against fixed thresholds instead of letting the loudest stakeholder set the tier.
Quick answer: Score every release on reach, revenue, and strategic differentiation (0–3 each), sum them into an Impact Score out of 9, then match: 7–9 is Tier 1, 4–6 is Tier 2, 0–3 is Tier 3. Effort is a fourth factor that adjusts the edges — it's a gate, not a fifth vote toward a bigger launch.
Why "Everything Is Tier 1" Keeps Happening
Tier inflation happens because tiers usually get assigned in a negotiation, not a calculation. Whoever escalates loudest, or has the most executive face-time, tends to win the argument. Without a rubric applied before the debate starts, every stakeholder has a plausible-sounding reason their feature deserves the full go-to-market machine.
The incentives are real, not imagined:
- Sales wants a campaign and a slide to point to in the next deal cycle.
- Marketing wants a launch that justifies the quarter's content calendar.
- Engineering leadership wants recognition for six months of hard work.
- Executives want a story for the board deck.
None of these people are wrong to want those things. They're just optimizing for their own function, not for a shared definition of impact.
Product Marketing Alliance's ongoing research into launch practice has repeatedly flagged tier inflation — teams treating a majority of releases as flagship-worthy — as one of the most common complaints among product marketers. There's rarely an agreed scoring model sitting upstream of the argument.
This article assumes you already have tier definitions in place — what a Tier 1 actually includes in terms of channels, sales enablement, and PR, versus a Tier 2 or Tier 3. If you haven't nailed that down yet, start with our launch tiers framework before layering a scoring model on top of it.
The harder, more political problem — and the one this piece solves — is deciding which releases qualify for each tier once the tiers themselves are defined. Getting that wrong cuts both ways:
- Over-tier a release and you burn scarce sales and marketing attention on something that can't repay it.
- Under-tier a release and a genuinely high-impact launch gets the coordination of an afterthought.
Nielsen's long-running research on new product launches has found that the large majority miss their first-year commercial targets, and a mismatched launch tier is a quiet contributor to that gap. For the fuller launch-planning picture this rubric sits inside, see our complete guide to GTM launch.
The Four-Factor Scoring Rubric: Reach, Revenue, Differentiation, and Effort
The rubric scores every release on four factors: reach (how many users it touches), revenue (what it moves financially), strategic differentiation (whether the competitive story changes), and effort (what the launch costs to coordinate). The first three sum into an Impact Score; effort is a gate, not a fifth point in the total.
This structure borrows deliberately from RICE, the scoring framework Intercom's Sean McBride popularized for prioritization: separate the size of the opportunity from the cost of pursuing it, so a team can't inflate a score just by working harder on the case for it. Tiering is the same move, one level up — applied to launch investment instead of build investment.
Reach: How Many Users Actually Touch This
Reach asks a blunt question: what share of your active base will actually encounter this release? Not "who asked for it" — who experiences it once it ships.
| Score | Reach definition |
|---|---|
| 0 | Under 5% of active accounts, or a rarely used surface |
| 1 | 5–20% of active accounts, or a single customer segment |
| 2 | 20–50% of active accounts, or a core workflow for one plan tier |
| 3 | Over 50% of active accounts, or the first-run path every new user hits |
A feature buried three menus deep for a niche workflow scores low here even if the people who use it love it. That's intentional — reach measures breadth, not intensity.
Revenue: What Line Item Actually Moves
Revenue asks what the release does to money — new, retained, or unblocked. This is the factor stakeholders most often try to game with anecdote ("every enterprise call asks for this") instead of evidence.
| Score | Revenue definition |
|---|---|
| 0 | No measurable line item; doesn't touch pricing, packaging, or a renewal |
| 1 | Protects or adds revenue worth under 5% of ARR |
| 2 | Tied to a packaging tier, worth 5–15% of ARR, or unblocks a stalled deal cohort |
| 3 | Gates net-new ARR above 15%, a strategic logo, or an actual pricing change |
Retention counts here too, not just new bookings. A release that prevents churn in a shrinking cohort should score on the ARR it protects, not just the ARR it adds — see our growth and retention guide for how to size revenue at risk rather than only revenue gained.
If the release changes what customers pay or unlocks a new packaging tier, that's an automatic floor of 2. Our pricing and monetization guide covers how to connect a feature to willingness to pay before you score it.
Strategic Differentiation: Does the Competitive Story Change?
Differentiation asks whether this release gives you something to say that competitors can't say back. Geoffrey Moore's Crossing the Chasm framed this as the gap between a "generic" product and a "whole product" — the difference between matching a category and defining one. That's the same gap this factor scores.
| Score | Differentiation definition |
|---|---|
| 0 | Matches an existing competitor capability; no new claim |
| 1 | Minor improvement to a capability you already had |
| 2 | Closes a named gap versus one or two competitors; supports an existing narrative |
| 3 | Category-defining; opens a new analyst or press conversation competitors can't match within two quarters |
Teresa Torres's opportunity-scoring work is a useful gut check here: differentiation should trace back to a specific, validated customer opportunity, not an internal opinion about what sounds impressive. If nobody can name the competitor gap or the analyst reaction this closes, it's probably a 0 or a 1, not a 3.
Effort: The Gate, Not a Fourth Vote
Effort measures the coordination cost of the launch itself — not the engineering build, but the GTM lift: enablement, docs, comms, press.
| Score | Effort definition |
|---|---|
| 0 | Ships behind a flag or in release notes; no GTM lift needed |
| 1 | One team, under two weeks of launch coordination |
| 2 | Cross-functional prep — docs, enablement, changelog — over two to six weeks |
| 3 | Company-wide moment: executive comms, analyst or press briefings, over six weeks of prep |
Basecamp's Shape Up, written by Ryan Singer, popularized the idea of fixing an "appetite" — a time budget decided before scoping starts — rather than letting scope dictate cost after the fact. Effort scoring borrows that discipline: decide what a release is worth spending on before someone with a big personality argues for more.
Turning Scores Into a Tier Decision: Thresholds That Resolve Fights
Add the reach, revenue, and differentiation scores into a single Impact Score out of nine, then match it against fixed bands. Effort doesn't get added to the total; instead, it can pull a borderline release down a tier when coordination cost outweighs marginal impact, or let a cheap release ride along a tier higher for free.
| Impact Score (Reach + Revenue + Differentiation) | Default tier | Effort override |
|---|---|---|
| 7–9 | Tier 1 | If Effort = 3 and no single factor scored a 3, pause — a company-wide moment needs at least one standout dimension, not three solid-but-unremarkable ones |
| 4–6 | Tier 2 | If Effort = 0–1, layer in cheap Tier 1 channels (a customer email, a changelog highlight) without running a full campaign |
| 0–3 | Tier 3 | If Effort = 0, ship with standard release notes; there's nothing left to debate |
Two rules make the borderline cases resolve instead of re-litigate:
- Never argue the total — argue a factor. If a release lands at a 6 and someone insists it deserves Tier 1, the answer isn't "round up." It's: which specific factor was scored too conservatively, and what evidence supports raising it?
- Effort caps ambition, it doesn't create it. A Tier 3 release doesn't become Tier 1 because it happens to be cheap to ship widely. Low effort can add a channel or two; it can't manufacture reach, revenue, or differentiation that isn't there.
Once a release has a tier, feed that decision back into sequencing rather than treating it as a separate GTM conversation. Tier 1 releases typically need to anchor a roadmap window so the launch doesn't get squeezed into whatever slot happens to be open; our roadmapping guide covers how to protect that runway once the tier is set.
Worked Example: When the Loudest Stakeholder's Feature Scores Tier 3
Here's the scenario this rubric exists for. A VP of Sales is pushing hard for a "branded PDF export" feature — enterprise customers can put their own logo on exported reports. He wants a press release, a homepage banner, and an executive quote in the launch email.
The PM runs it through the rubric instead of arguing on vibes:
| Factor | Score | Why |
|---|---|---|
| Reach | 1 | Roughly 8% of active accounts use exports, and only on the top plan tier |
| Revenue | 1 | Pulling the last two quarters of closed-won deals, none were contingent on this specific capability |
| Differentiation | 1 | Two named competitors already ship white-labeled exports; this closes parity, it doesn't open new ground |
| Effort | 1 | One team, roughly a week of design and engineering polish |
| Impact Score | 3 | Tier 3 |
The VP's instinct isn't dishonest — "every enterprise call asks for this" is probably true, and the feature is genuinely worth shipping. But asked-for and high-impact are different questions, and the rubric is built to tell them apart.
The resolution looks like this:
- Reach stays low because export usage is concentrated in one plan tier, not the base.
- Revenue stays low because no deal data supports the claim that it's currently blocking pipeline.
- Differentiation stays low because it's parity, not a new story.
- The feature still ships — with release notes, a changelog entry, and a one-line addition to the sales talk track. No press release, no exec quote.
This is the mental shift the whole rubric is built around: tier is an earned score, not a stakeholder's volume. A VP arguing loudly for Tier 1 isn't evidence of Tier 1 impact — it's evidence that someone cares, which is a different (and useful, but separate) signal.
Handling Borderline Cases and Political Pressure
Borderline cases get resolved by re-examining the underlying factor scores, not by negotiating the total. If a stakeholder disputes a Tier 3 verdict, the process should ask them to argue a specific factor upward with evidence — a named deal, a usage number, a competitor announcement — rather than reopening the tier debate itself.
A few operating rules keep this from becoming a new political battleground of its own:
- Anyone can dispute a factor score, but only with evidence. "I think this is more important" doesn't move a number. "Here are the three deals in Salesforce citing this as a blocker" does.
- Re-score on a fixed cadence, not whenever someone complains. Quarterly, or whenever a release's scope changes materially — not every time a stakeholder feels overlooked.
- Someone owns the rubric. In most orgs that's a product operations function, maintaining the scoring bands and the historical record of what scored what. Our product operations guide covers how that ownership typically gets structured alongside other cross-functional processes.
- Document the score, not just the tier. A Tier 3 decision with no visible math behind it looks exactly like politics, even when it isn't. Showing the four numbers is what makes the call defensible.
The goal isn't to remove judgment from tiering — it's to make the judgment visible and consistent, so the same kind of release gets the same kind of tier whether it's championed by a VP or a first-year PM.
Where the Rubric Actually Lives
When someone revisits a Tier 3 call next quarter, or a new PM inherits the process, the reference point is the same criteria and the same math, not a fresh negotiation. That's the difference between a tier decision that holds up and one that gets re-litigated every launch cycle.
Key Takeaways
- Score reach, revenue, and differentiation from 0–3 each, sum them into an Impact Score out of nine, and match fixed bands: 7–9 is Tier 1, 4–6 is Tier 2, 0–3 is Tier 3.
- Effort is a gate, not a fifth point. It can pull a borderline release down a tier when coordination cost outweighs impact, or add a cheap channel to a lower-tier release — it never manufactures impact that isn't there.
- Borderline disputes get resolved factor by factor, with evidence, not by rounding the total up because someone is unhappy with the tier.
- Revenue should count retained ARR at risk, not just new bookings — a churn-preventing release can score as high as one that drives net-new deals.
- A loud stakeholder is a signal of care, not impact. The worked example shows how a genuinely popular, sales-championed feature can still score Tier 3 once reach, revenue, and differentiation are measured instead of assumed.
- Document the score alongside the tier. A visible rubric is what makes a Tier 3 call defensible instead of political.
Frequently Asked Questions
How many launch tiers should a product organization use?
Most teams settle on three — Tier 1, 2, and 3 — because a fourth tier tends to blur into an adjacent one and adds coordination overhead without adding decision clarity. If your organization is large enough that Tier 3 covers hundreds of releases a year, consider splitting it into a formal Tier 3 and an unscored "no launch process" bucket rather than adding a Tier 4.
Who should own the tier scoring decision?
The PM proposes the score using the rubric, but a product operations function (or a designated GTM lead where no formal ops role exists) should own the rubric itself — the bands, the thresholds, and the historical record — so scoring stays consistent across PMs and product lines rather than drifting team by team.
What happens when leadership wants a Tier 2 release treated as Tier 1?
Ask leadership which specific factor they'd score higher and why — usually revenue or differentiation — and re-score with that evidence. If the evidence holds up, the release genuinely was under-scored and the tier changes; if it doesn't, the rubric gives you language to hold the line without it becoming personal.
How often should a release be re-scored?
Re-score when the release's scope changes materially — a feature that shrinks from a platform capability to a single workflow tweak, for instance — or on a fixed quarterly cadence for anything still in planning. Re-scoring on demand, every time a stakeholder pushes back, defeats the purpose of having fixed thresholds.
Can a low-effort release ever justify a Tier 1 launch?
Only if it also earns a high Impact Score on its own merits — effort can add a cheap channel to a release that already scored well, but it can't substitute for reach, revenue, or differentiation. A release that's merely inexpensive to ship widely isn't automatically worth a company-wide moment; it's worth exactly what its impact score says it's worth.