Measuring Customer Journey Metrics and KPIs by Stage

A skill from the The Five-Stage Customer Journey Framework method.

Pick customer journey metrics for each of the five stages, define them precisely, and track the conversions between stages to find leaks.

Pick customer journey metrics for each of the five stages, define them precisely, and track the conversions between stages to find leaks.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

FieldValue
DifficultyIntermediate
Time to LearnA day to define, longer to instrument
OutcomeA one-page scorecard with one defined primary metric per stage, the conversions between stages and an owner for each number.
PrerequisitesStage definitions, access to analytics, CRM and billing data, agreement on who owns each stage
Part ofThe Five-Stage Customer Journey Framework

Overview

Customer journey metrics tell you how each stage of the five-stage customer journey framework is performing and where customers are lost between stages. Without them, the framework stays a diagram. With too many of them, it turns into a dashboard nobody reads. This skill produces a short scorecard: one primary metric per stage, the conversion rate across each transition, and a few supporting measures that explain movement in the primary ones.

Most companies already measure the first three stages well because the data sits in ad platforms, web analytics and the CRM. Retention and advocacy are often measured loosely or not at all, even though the economics favor them. A Harvard Business Review summary of retention research notes that acquiring a customer can cost five to 25 times as much as retaining one. A scorecard that gives each stage equal weight corrects the habit of watching only the easy numbers.

Precision matters more than the choice of metric. A churn rate that one team calculates monthly by logo and another quarterly by revenue will produce arguments instead of decisions. The scorecard therefore includes written definitions, data sources and owners for each number.

Use this skill when setting up journey measurement for the first time, when stage owners disagree about what is working, or when a blended number such as revenue moves and nobody can say which stage caused it.

How It Works

The scorecard has three layers. The top layer is one primary metric per stage, chosen because it reflects whether the stage is doing its job for the customer. The middle layer is the conversion between adjacent stages, which is where most leaks show up. The bottom layer holds diagnostic measures that explain changes in the first two, and those are looked at only when a primary number moves.

Primary metrics differ by business, but the pattern is consistent. Awareness is measured by qualified reach, such as branded search or new visitors from the target segment. Consideration is measured by engaged evaluation, such as trial starts, demo requests or comparison-page visits that lead to a next step. Purchase is measured by conversion to paying customer and time to decide. Retention is measured by churn or renewal rate and by adoption of the capability customers bought for. Advocacy is measured by referral rate, review volume or Net Promoter Score.

Net Promoter Score has a precise definition worth following exactly. Bain asks how likely customers are to recommend you on a zero-to-ten scale and computes the percentage of promoters, who answer 9 or 10, minus the percentage of detractors, who answer 0 to 6. Treat it as a signal of advocacy potential and pair it with a behavioral measure, such as actual referrals, so the scorecard does not rely on stated intent alone.

For purchase and retention, customer effort is often a better diagnostic than satisfaction. Research published in Harvard Business Review argued that companies earn more loyalty by reducing the effort customers spend than by trying to delight them. Measuring how hard it is to buy, set up or get help gives the retention owner something concrete to fix.

The scorecard is read as a chain. A drop in purchase conversion might start in consideration, where the wrong prospects are entering. A rise in churn might trace back to a promise made in awareness. Reading the stages together, rather than in separate team reports, is what turns measurement into diagnosis.

Step-by-Step Guide

Step 1: Write the entry and exit event for each stage

Define exactly what moves a customer into and out of each stage in terms your systems can record, such as "first visit from the target segment" or "first paid invoice". Without these events, stage metrics cannot be calculated consistently. Agree them with every stage owner before choosing metrics. Write them at the top of the scorecard.

Step 2: Choose one primary metric per stage

For each stage, pick the single number that best shows whether the stage is doing its job for the customer. Prefer measures of customer progress, such as trial starts, over measures of company activity, such as emails sent. If two metrics seem equally good, pick the one you can measure reliably today. Record why you chose it.

Step 3: Add the transition conversions

Calculate the share of customers who move from each stage to the next within a defined window, for example from trial start to paid within a set number of days. These conversions are where leaks show up most clearly. Pick windows that fit your sales cycle rather than a default from a tool.

Step 4: Write definitions, sources and owners

For every metric, write the formula, the data source, the refresh frequency and the person who owns it. Include edge cases, such as how paused subscriptions or downgrades count toward churn. Share the definitions with finance and every stage owner. A metric without a written definition will be calculated differently by the next person who touches it.

Step 5: Add a few diagnostic measures

Under each primary metric, list a small number of measures you would check if it moved, such as page speed for consideration or time to first value for retention. Customer effort measures belong here for purchase and retention. Keep the diagnostic list short; it is for investigation, not for weekly reporting.

Step 6: Set baselines before targets

Collect a few periods of data for each metric before setting targets. Targets set without a baseline are guesses, and guesses create pressure to game the number. Once you know the normal range, set targets as improvements over your own baseline rather than borrowed industry figures.

Step 7: Review the chain on a fixed cadence

Review the scorecard monthly or quarterly with every stage owner in the room. Start with the transitions, find the biggest drop and trace it back through the diagnostic measures. Assign one action per significant change with an owner and a date. Retire metrics nobody has used in a decision for a few review cycles.

Best Practices

  • Measure customer progress, not team activity. Emails sent and calls made show effort. Trial starts and renewals show whether customers moved.
  • Weight retention and advocacy equally. They are harder to measure and easier to ignore. Put them on the same page as acquisition so gaps are visible.
  • Pair stated and behavioral signals. A survey score says what customers intend. Referrals and renewals show what they did.
  • Keep one owner per number. Shared ownership means no one investigates when a number falls.
  • Segment before you average. A blended churn rate can hide a healthy segment and a failing one. Split by segment when a number moves.
  • Change definitions rarely and visibly. When a definition changes, note the date and restate history, or trends will mislead.

Common Mistakes

  • Tracking too many metrics per stage: A long list spreads attention thin and hides the signal. Keep one primary metric per stage and move the rest to diagnostics.
  • Measuring only the first three stages: Acquisition data is easy to collect, so dashboards fill up with it. Add retention and advocacy even if the first version is rough.
  • Using undefined metrics: Two teams calculating churn differently will argue instead of acting. Write the formula and data source for every number.
  • Borrowing industry benchmarks as targets: Published benchmarks rarely match your segment or definitions. Set targets from your own baseline.
  • Reading stages in isolation: A purchase problem can start in consideration. Review the whole chain together.

References

  • Examples: Worked examples and scenarios
  • FAQ: Frequently asked questions
  • Parent Method: The Five-Stage Customer Journey Framework

Sources


Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.

Install this skill

Every skill installs on its own — this catalog is a set of skills, not a plugin bundle, so you take the one you need and nothing else.

Claude Code

.claude/skills/measuring-journey-stage-kpis
npx skills add gethamster/skills --skill measuring-journey-stage-kpis --agent claude-code --yes

Cursor

.agents/skills/measuring-journey-stage-kpis
npx skills add gethamster/skills --skill measuring-journey-stage-kpis --agent cursor --yes

Codex

.agents/skills/measuring-journey-stage-kpis
npx skills add gethamster/skills --skill measuring-journey-stage-kpis --agent codex --yes

Antigravity

.agents/skills/measuring-journey-stage-kpis
npx skills add gethamster/skills --skill measuring-journey-stage-kpis --agent antigravity --yes

Or browse the skills and pick interactively:

npx skills add gethamster/skills

Source: gethamster/skills on GitHub, MIT licensed.