Hypotize wordmarkOpen the app

PIE framework · Free calculator

PIE prioritization: guide, calculator, and product formula

Score Potential, Importance, and Ease for conversion opportunities. Compare the documented average with Hypotize's 1–10 implementation and the multiplicative variant often repeated online.

What it is and where it came from

A relative ranking tool, not an automatic decision

PIE is attributed to WiderFunnel founder Chris Goward for prioritizing conversion-optimization opportunities. Published worked examples average Potential, Importance, and Ease to produce a score out of 10; multiplication is a variant rather than a uniquely canonical rule.

Source: Segment experimentation guide: PIE attribution and worked example

Dimensions

What each letter must make explicit

Potential

How much improvement appears possible on the page, flow, or experience.

Guardrail: Use research and current performance to identify room for improvement.

Importance

The value and volume of users affected by the opportunity.

Guardrail: Define the audience and why this touchpoint matters to the business.

Ease

Relative cost and complexity of implementing and measuring the change.

Guardrail: Count dependencies and analysis work, not only build time.

Formula disclosure

Documented method and Hypotize method

Source method

(Potential + Importance + Ease) ÷ 3

Hypotize

(Potential + Importance + Ease) ÷ 3

The documented average and Hypotize both return a 1–10 score. The multiplicative variant returns 1–1000. A product and an average do not always preserve the same ranking, so a record should store which method produced the number.

Deterministic · No account required

Compare both calculations

Inputs stay in this browser. Nothing is sent to Hypotize by this calculator.

Documented source units

1 = little room, 10 = large room

1 = low-value audience, 10 = critical

1 = difficult, 10 = easy

Documented average

7

Hypotize input scale

Hypotize input, 1–10

Hypotize input, 1–10

Hypotize input, 1–10

Hypotize score

7

Multiplicative variant using these inputs: 336

Worked example

One experiment, reproducible arithmetic

A pricing-page opportunity scored Potential 8, Importance 7, and Ease 6 returns 7.00 by both the documented average and Hypotize. The multiplicative variant returns 336 and should be labeled as a different method.

Decision rules

When to use PIE, and when not to

Use it when

  • You are prioritizing page or funnel optimization opportunities.
  • Traffic value and room for improvement matter separately.
  • A shared 1–10 rubric is sufficient for relative ranking.

Do not let it decide when

  • You are comparing projects rather than conversion opportunities.
  • Reach and effort need explicit real-world units.
  • Potential cannot be grounded in research or current performance.

Common input failures

  • Low-performing pages can look high-potential even when demand is weak.
  • Importance can double-count traffic and business value.
  • Ease estimates often omit analytics and QA work.

Product behavior

Exactly what Hypotize does

Hypotize calculates the arithmetic mean of Potential, Importance, and Ease and keeps the result on a 1–10 scale. It stores PIE as the framework and the resulting priority score. The current MCP connector has no dedicated PIE vote tool, so a connected client cannot claim it scored PIE through a parallel operation.

A score is one field in the experiment record. It does not execute a test, prove a hypothesis, or replace owner, state, evidence, outcome, learning, and next step.

Choose the right lens

The same pricing experiment in three rubrics

FrameworkExample inputsHypotize resultBest question
ICE8, 6, 77.00What is impactful, evidenced, and easy?
PIE8, 7, 67.00Which conversion opportunity matters?
RICE8, 7, 6, 3112.00How much impact per unit of effort?

Keep the context

A score is useful when its reasoning survives

Read the experiment memory guideReview MCP boundariesICE guideRICE guideOpen the web app

Reviewed 29 August 2026. Source links identify the documented method; product behavior is derived from the current Hypotize framework configuration and calculator implementation.