Planned Journey Framework Stages: Latent, Evaluation, Buying

A skill from the Planned Journey Framework: Map High-Stakes Purchases method.

Define the planned journey framework stages for your category: latent, evaluation and buying, with entry signals, buyer behaviors and exit criteria.

Define the planned journey framework stages for your category: latent, evaluation and buying, with entry signals, buyer behaviors and exit criteria.

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 few hours, plus a round of buyer validation
OutcomeYou have a one-page definition of the latent, evaluation and buying stages for your category, with the signals that mark each boundary, that research and marketing teams can use without reinterpreting it.
PrerequisitesAccess to recent buyers or interview transcripts, a clear product category, basic familiarity with consideration sets
Part ofPlanned Journey Framework

Overview

The planned journey framework stages are the latent, evaluation and buying stages of a long, deliberate purchase. This skill turns those three labels into definitions specific to your category, so that every later piece of work, from consideration tracking to touchpoint scoring, sorts buyers into stages the same way. Without shared definitions, one team's "evaluation" is another team's "late latent," and cross-stage comparisons stop meaning anything.

The labels come from SKIM. In the Quirk's article that sets out the planned journey, Alex Xiaoguang Zhu describes viewing the planned journey, a long and research-heavy purchase, through latent, evaluation and buying stages, and says the key is to identify distinctive stages and connect the dots across them. The article gives no fixed definition of where each stage starts and ends. That is deliberate work for each category, and it is what this skill covers. The background and the comparison with other journey models are on the Planned Journey Framework page.

A useful stage definition describes what the buyer does. "Requested a quote" is a buyer behavior. "Became a marketing qualified lead" is a seller label that may or may not match a change in the buyer's state. Definitions also need observable signals, so that a survey question, an analytics event or a sales note can place a buyer in a stage with reasonable confidence.

The output is a short stage definition document: for each stage, the entry signal, the buyer's dominant behaviors and questions, the information sources they lean on, and the exit signal. It also lists the triggers that move buyers from latent to evaluation, because those triggers are the first thing downstream work needs. This is the foundation for customer decision journey mapping in any category where people deliberate over the purchase.

How It Works

Each stage is defined by a change in the buyer's state. The latent stage is the period before any intention to buy. A SKIM expert Q&A describes it as the stage "where customers are not actively looking for any information but in a passive receiving information mode." Buyers in it still absorb advertising, product experiences and other people's opinions, which is why familiar brands often dominate the first consideration set.

The move from latent to evaluation happens when the buyer forms an intention. The same Q&A describes buyers entering a consideration stage once they form an intention to purchase. Something usually causes that intention: a lease ending, a life event, a failing product, a price change, a recommendation. An article written with Ehrenberg-Bass professor Jenni Romaniuk and published on her site defines category entry points as the moments when someone mentally enters a category, and listing them is a practical way to name the triggers for your category.

The evaluation stage is active and deliberate. SKIM's description of deliberate decisions, in which consumers are more conscious of their choices and pay attention to stimuli that match their needs (SKIM habitual-deliberate loop), fits this stage well. Buyers search, compare, read reviews, ask friends, visit showrooms or book demos, and the set of brands they seriously consider changes as they learn (Consideration set).

The buying stage begins when the buyer is choosing among specific offers rather than brands in general: pricing a particular configuration, negotiating, arranging finance, comparing where to buy. It ends with the purchase or with an exit, such as a postponement back into latent.

Boundaries are rarely clean. Buyers can move back from evaluation to latent when a trigger fades, or skip quickly through evaluation when a trusted recommendation settles the choice. Define the typical path, then note the common loops so later analysis does not treat them as errors.

Step-by-Step Guide

Step 1: Gather buyer evidence

Collect accounts of recent purchases in your category from recent buyers, buyers who chose a competitor and people who started looking and stopped. Interview transcripts are best, supported by any survey or behavioral data you have. Ask buyers to walk through the purchase from the first moment they thought about it, anchored to dates and events, which limits memory drift. Include people outside your customer base, or the definitions will describe only journeys you won.

Step 2: Find the latent-to-evaluation triggers

Read the accounts for the moment each buyer started actively looking and what caused it. Group the causes into a short list of triggers, using the category entry point idea as a guide to name the situations that bring people into the category (category entry points). Note which triggers are predictable, such as a contract end date, and which are not, such as a breakdown. This list becomes the entry signal for evaluation.

Step 3: Describe the latent stage

Write what buyers were exposed to and what they already believed before the trigger. List the brands they already had in mind and where those impressions came from. Keep in mind SKIM's point that latent buyers are receiving information passively (SKIM Q&A), so the evidence will come from recall of ads, conversations and past experience rather than from searches. Record the signal that someone is in this stage, such as owning an aging product without looking at replacements.

Step 4: Describe the evaluation stage

List the dominant behaviors, questions and information sources during active research, and the brands that entered or left consideration. Define the exit: the point where the buyer has a short list of specific offers. Write the exit as an observable event, such as a request for a quote or a test drive of a named model. Check that two people reading your definition would place the same buyer in the same stage.

Step 5: Describe the buying stage

Describe the final choice among offers: price, terms, availability, trust in the seller and the last reassurance the buyer needs. Name the exit events, both purchase and postponement. Note which objections appeared only at this stage, since they are often invisible in evaluation research. Record where the purchase happens, because channel choice is part of the buying stage in many categories.

Step 6: Write the stage definition document

Put the three stages side by side in one table: entry signal, behaviors, questions, sources, exit signal. Add the trigger list and the common loops, such as returns from evaluation to latent. Keep it to one page so teams actually use it. Store it where research, marketing and sales can all find it.

Step 7: Validate with buyers and front-line staff

Show the definitions to a few recent buyers and ask whether they recognize their own path. Show them to sales or service staff and ask which buyers they meet do not fit. Adjust wording until both groups agree the stages describe real behavior. Set a date to revisit the definitions when the category changes.

Best Practices

  • Define stages by buyer behavior and state. Seller labels such as lead status can sit alongside the definitions but should not replace them, because they change with internal process rather than with the buyer.
  • Make every boundary observable. A stage that can only be identified by asking the buyer how they feel is hard to measure at scale, so pair each definition with at least one survey question or data event.
  • Include lost and stalled buyers in the evidence. They show the exits that customer-only samples never reveal.
  • Keep the definitions category-specific. The same three labels describe very different behavior for a car, a pension and a laptop, and the Quirk's article frames the stages as something to identify for each journey (Quirk's).
  • Record loops as part of the model. Returns from evaluation to latent are common in long purchases, and treating them as noise hides a real stall point.

Common Mistakes

  • Copying your sales pipeline stages: Pipeline stages reflect internal hand-offs. Start from the buyer's account and map the pipeline to it afterward, noting where they disagree.
  • Treating latent as unaware: Latent buyers are not shopping, but they are forming impressions that shape their first consideration set. Define what they already believe as well as what they are not doing.
  • Vague exit criteria: "Ready to buy" cannot be measured. Name the event that ends each stage, such as a quote request or a signed offer.
  • Defining stages once and never revisiting: Categories change as channels and products change. Revisit the definitions when a new trigger or information source appears in buyer accounts.
  • Relying on recall alone: Retrospective accounts of long decisions drift, a known problem called recall bias. Anchor interviews to dated events and cross-check with behavioral data where you have it.

References

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/defining-latent-evaluation-buying-stages
npx skills add gethamster/skills --skill defining-latent-evaluation-buying-stages --agent claude-code --yes

Cursor

.agents/skills/defining-latent-evaluation-buying-stages
npx skills add gethamster/skills --skill defining-latent-evaluation-buying-stages --agent cursor --yes

Codex

.agents/skills/defining-latent-evaluation-buying-stages
npx skills add gethamster/skills --skill defining-latent-evaluation-buying-stages --agent codex --yes

Antigravity

.agents/skills/defining-latent-evaluation-buying-stages
npx skills add gethamster/skills --skill defining-latent-evaluation-buying-stages --agent antigravity --yes

Or browse the skills and pick interactively:

npx skills add gethamster/skills

Source: gethamster/skills on GitHub, MIT licensed.