All frameworks and cheat sheets

Flowchart

Should this feature move to a higher tier?

Flowchart for deciding whether a feature should move to a higher tier: three yes or no questions, one side step, ending in a follow-up 30 days after launch.
Run every feature on your list through the same three questions
Download PNGRead the full guide

A decision path for pricing teams weighing a packaging change. After interviewing current users of a feature, it asks whether the feature is a reason they bought, whether they know what they would do without it, and whether most would buy the higher tier at its planned price, then says when to keep the feature, when to move it for new customers only and when to move it with notice. It follows the leaders, fillers and killers idea from Monetizing Innovation. Koji runs the interviews and the price test behind each answer.

Where this appears

What's in this flowchart

Start: You plan to move a feature up a tier

  1. Interview current users of it. 20 to 30 people who used it in the last 90 days.
  2. Is it a reason they bought the lower tier?
    • No: go to 3.
    • Yes: Keep it where it is. Moving a leader breaks the tier. Fence on something else.
  3. Do they know what they would do without it?
    • Yes: go to 4.
    • No: Probe the workaround. Ask what they used before it existed and what that cost them. Then go to 4.
  4. Would most buy the higher tier at its price?
    • Yes: go to 5.
    • No: Move it for new customers only. Keep current customers on their plan and test again in six months.
  5. Move it, with 60 days of notice. Say plainly what they keep and name a person to contact.
  6. Finish: Interview again 30 days after launch.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/should-this-feature-move-tiers-flowchart"><img src="https://www.koji.so/visuals/should-this-feature-move-tiers-flowchart/should-this-feature-move-tiers-flowchart.png" alt="Flowchart for deciding whether a feature should move to a higher tier: three yes or no questions, one side step, ending in a follow-up 30 days after launch." width="1200" height="1541" /></a>
<p>Source: <a href="https://www.koji.so/visuals/should-this-feature-move-tiers-flowchart">Should this feature move to a higher tier?</a>, Koji</p>

Related

Question bank for packaging change interviews in three sections: how they use the feature today, what the plan is worth to them, and how the change would land.

Packaging change interview questions

Comparison table of four ways to research a packaging change: AI interviews, a MaxDiff survey, a conjoint study and calls by your own team.

Ways to research a packaging change, compared

Bar chart comparing software companies a year earlier and in 2026: hybrid pricing rose from 25% to 37%, and offering several pricing models from 21% to 29%.

Hybrid pricing at software companies, 2025 to 2026