Customer journey definition and implementation in HubSpot
Last updated: 2026-11-10 · Reviewed by Noah Charak, Managing Director
A customer journey definition is the written model of how a buyer becomes a customer and stays one: the lifecycle stages contacts and accounts move through, the lead statuses reps work, the stages of the deal pipeline, the entry and exit criteria for each, and the handoffs and SLAs between marketing, sales and customer success. Checkpoint GTM defines that model with your teams in interviews and workshops, then builds it into HubSpot: properties, lifecycle automation, pipelines, routing and reporting on stage-to-stage conversion. Most broken funnels have one field doing the work of three and no agreed way out of any stage. We separate them, write the definitions down and make the CRM enforce them.
- 80+implementations
- 100+B2B companies
- PlatinumHubSpot Partner
What does a customer journey definition cover?
Six parts, agreed with the teams that own them. Together they become the reference every report and automation in the CRM follows.
Lifecycle stages
From subscriber and lead through MQL, SQL and opportunity to customer and advocate, for contacts and for accounts. Each stage gets a one-sentence definition and one owning team. See the lifecycle stage model.
Lead status
What a rep is doing with a record right now: new, attempting, connected, qualified or disqualified. A separate field from lifecycle stage, so a to-do never shows up as a funnel stage.
Deal stages
A pipeline named for what the buyer does and what the seller does next, such as Educate, Discover, Value, Setup and Closed Won, instead of qualified, proposal, closed. Read the five-stage model.
Entry and exit criteria
Every stage is entered on an observable event and left forward, back to nurture or disqualified, with a reason code. Required fields per stage mean a record cannot move without the data the next owner needs.
Handoffs and SLAs
Marketing to SDR, SDR to AE, AE to customer success: who accepts the record, within what window, and what happens when nobody does. See the sales and marketing SLA.
Onboarding and the customer stages
What customer success inherits after closed won: kickoff, onboarding, renewal and expansion, with a named owner and a clean handover from the buying committee. See the onboarding plan.
How does the journey get built into HubSpot?
| Part of the journey | Agreed in the workshops | Built in HubSpot | Reported as |
|---|---|---|---|
| Lifecycle stages | Stage definitions, entry triggers, one owner per stage, recycle and disqualification reasons | Lifecycle stage property, workflows that set stages from events, and a guardrail so Customer is set only by a closed won deal | Stage-to-stage conversion by cohort month, recycle rate |
| Lead status | Status values and the action each one asks of the rep | Lead status property, task queues and a disqualification reason picklist | Time to first touch, disqualification reasons |
| Deal pipeline | Deal stages with one-sentence definitions, entry and exit criteria and an owner each | Pipelines and deal stages, required fields per stage, stale-deal alerts | Stage conversion, median days in stage, win rate by stage reached |
| Handoffs and SLAs | Who accepts each handoff, within what window, and the escalation path | Routing and assignment rules, SLA tasks and alerts, handoff fields | SLA adherence and response time per team |
| Customer onboarding | The Setup stage and the handover from sales to customer success | Onboarding pipeline or tickets, kickoff tasks, a customer success owner property | Time to kickoff, onboarding milestones reached |
Why define the journey before building it in HubSpot?
Most CRMs we inherit were configured before anyone agreed what the stages mean. Marketing reports MQLs that sales never accepted, deals sit in proposal for months, and closed won means contract signed for one rep and kickoff scheduled for another. More automation on top of that only makes the disagreement faster.
So we start with the people, not the portal: interviews with marketing, sales, customer success and, where ARR and invoicing depend on CRM data, finance. Then workshops where the teams agree the stages, the criteria and the handoffs in writing. HubSpot is configured after that, to enforce what was agreed.
Checkpoint is a HubSpot Platinum Partner with 80+ implementations, so the definition is written with the build in mind. Every stage maps to a property, every criterion to a required field or a workflow, and every handoff to a report somebody reviews.
Customer journey work fits when
- Marketing and sales disagree on what an MQL is, and the funnel numbers depend on who you ask
- Your pipeline has stages nobody can define in one sentence, and deals stall without a recorded reason
- Leads go untouched or get routed by hand, and nobody owns the handoff to sales or customer success
- You are implementing, rebuilding or consolidating HubSpot across teams or business units and want the process designed first
When is customer journey work the wrong first step?
A journey definition needs a sales motion to describe. Start somewhere else when:
- You are still in founder-led sales. If the ICP and the motion still change every month, there is no stable journey to write down yet. The GTM Kickstarter is the better starting point.
- You are leaving another CRM. The journey still gets designed first, but it belongs inside a CRM migration, so the new stages and the data mapping are planned together.
- Only one workflow is broken. If the stages are agreed and a single routing rule or report is wrong, a HubSpot optimisation sprint fixes it faster.
- You want a template switched on. A default picklist is a starting point, not a model. If HubSpot's standard stages are all you need, you do not need a project for that.
How does a customer journey project run?
Five steps. Your teams are in the room for the first two, because the definitions have to be theirs.
- Discovery: interviews with marketing, sales, customer success and finance where it matters, plus an audit of the current portal: stages, properties, pipelines, workflows and data quality. Interviews run in English, German, Italian, French or Spanish.
- Journey workshops: the teams agree the lifecycle stages, lead statuses, deal stages, entry and exit criteria and handoffs. The output is a written journey document that each team signs off.
- Build in HubSpot: properties, lifecycle and lead status automation, pipelines with required fields, routing and SLA tasks, and a migration map from old values to new ones.
- Review and go-live: each team reviews the build and tests it on real records before cutover, and reporting switches to the new model on a set date.
- Training and reporting: each team is trained on the transitions it owns, and dashboards report stage-to-stage conversion, days in stage and SLA adherence.
Customer journey work runs as a fixed-scope project within our published €15K–€90K range, excl. VAT, or as part of a HubSpot implementation. We scope every engagement before quoting. See all our prices.
Questions about customer journey definition and implementation
What is a customer journey definition?
It is the written model of how a buyer becomes a customer and stays one. It names the lifecycle stages of contacts and accounts, the lead statuses reps work, the stages of the deal pipeline, the entry and exit criteria for each, and who owns each handoff between marketing, sales and customer success. Every report and automation in the CRM should follow it.
What is the difference between lifecycle stage, lead status and deal stage?
Lifecycle stage describes where the relationship with a contact or account is, from subscriber to customer. Lead status describes what a rep is doing with a record right now, such as attempting or connected. Deal stage describes where one specific buying process is. Many broken funnels put all three into one field, which makes the conversion rates meaningless. We keep them as three separate fields.
How do you implement the customer journey in HubSpot?
We map each definition to HubSpot: lifecycle stage and lead status properties, workflows that move records on observable events, pipelines with required fields per deal stage, routing and SLA tasks for each handoff, and dashboards on stage conversion and days in stage. Old values are mapped to new ones with a set cutover date, so history stays reportable.
How long does it take?
Rebuilding a pipeline against agreed stage definitions typically takes four to six weeks on a HubSpot portal. A full journey across marketing, sales and customer success is scoped after discovery, because the number of teams, pipelines and business units drives the timeline.
Who needs to be involved from our side?
An owner from each team that touches the journey: marketing, sales or SDR, customer success, and finance if ARR or invoicing depends on CRM data. They join the discovery interviews and the workshops where the stages and handoffs are agreed, so the definitions are theirs and not ours.
Do we need to migrate our CRM first?
No. Most journey projects happen inside an existing HubSpot portal. If you are moving from another CRM, the journey is designed as part of the migration, so the new stages and the data mapping are planned together.
How much does it cost?
It runs as a fixed-scope project within our published €15K–€90K range, excl. VAT. The price depends on the number of teams, pipelines and integrations involved, and we scope every engagement before quoting. See all our prices.
Which CRMs and languages do you work in?
HubSpot and Salesforce. Checkpoint GTM is a HubSpot Platinum Partner and Salesforce Advanced Administrator, based in Berlin, and delivers in English, German, Italian, French and Spanish.
How we think about the customer journey
A five-stage B2B SaaS customer journey
Educate, Discover, Value, Setup, Closed Won: deal stages named for buyer behaviour and seller action, and why Value is the stage most teams skip.
Where revenue leaks: the handoffs nobody owns
The inbound lead that waits days for a first touch and the closed won deal that sits in a rep's head. Name an owner for each.
The sales-to-CS handover
Why the first renewal starts slipping at kickoff, and why the fix is an artifact, not a meeting.
Lifecycle Stage Model skill
Define every stage from subscriber to advocate with entry rules, owners and recycle paths, so funnel numbers mean one thing.
Pipeline Stage Definitions skill
Define deal stages by what the buyer has done, with exit evidence, required fields and stall rules.
HubSpot implementation
The full portal build the journey usually sits inside: setup, migration, integrations, reporting and training.
Want one customer journey every team agrees on?
Tell us how leads, deals and customers move through your CRM today, and where the numbers stop matching. We will tell you honestly whether to start with the journey definition, a HubSpot rebuild or something smaller.
Book a call