Customer Lifecycle Map Template

A lifecycle map is the written agreement behind every lifecycle stage, workflow and report in your CRM. This template gives you one block to fill in per stage, so the definitions, triggers, owners and metrics sit in one place instead of in five people’s heads. There’s a worked example near the end you can copy from.

Print or save as PDF

How to use this template

Fill it in away from the CRM. Start with plain-English definitions, then work out which data and events would let the system detect each stage. Only at the end should you look at how your platform implements it; otherwise the tool’s default stages end up defining your business instead of the other way around.

A few ground rules make the map far more useful:

• One record, one stage. If a contact could reasonably sit in two stages at once, the definitions overlap. Tighten them.
• Entry and exit must be observable. “Shows buying intent” can’t be automated. “Requested a demo” or “viewed pricing page twice in 7 days” can.
• Every stage has an owner. Not a team in general. A named role who is accountable for records sitting in that stage.
• Name what happens when things go backward. Lost deals, canceled subscriptions and lapsed buyers need a defined destination.

Most B2B maps land on five to eight stages. Ecommerce maps tend to be fewer and based on order behavior. If you have more than ten, some are probably sub-statuses that belong in a separate property, like HubSpot’s lead status alongside its lifecycle stage. The guide to customer lifecycle mapping covers how to choose stages in more depth.

Part 1: Map overview

Fill this in once for the whole map.

• Business model: B2B sales-led, B2B product-led, ecommerce, subscription, services, or a mix.
• Primary record: the object the lifecycle is tracked on (contact, company, customer profile, account).
• Stage property: the field that stores the stage, and its internal name.
• Can stages move backward? Yes, no, or only specific moves (list them).
• Systems that can change the stage: CRM workflows, integrations, manual edits by which roles.
• Map owner: the person who approves changes to definitions.
• Last reviewed: date.

Part 2: Stage block (copy once per stage)

• Stage name: the label people will see.
• Internal value: the exact value stored in the CRM.
• Definition: one or two sentences a new hire would understand.
• Entry criteria: the specific condition or event that moves a record into this stage. Include the data source.
• Exit criteria: every way a record can leave this stage, and where it goes for each.
• Maximum expected time in stage: after how long a record here is considered stuck.
• Key events tracked: the events or behaviors that matter while someone is in this stage (form submissions, orders, meetings, logins, replies, email engagement).
• Required data: the properties that must be filled for a record to be useful at this stage.
• Owner: the role accountable for records in this stage.
• Handoff: who receives the record on exit, how they’re notified, and the expected response time.
• Automation in this stage: workflows, flows or sequences that run while a record is here, including what they send and what they update.
• Suppressions: who should not receive this stage’s communication (existing customers, open deals, unsubscribed, competitors).
• Metrics: volume entering per month, conversion to next stage, median time in stage, and any stage-specific measure.
• Reports that depend on this stage: dashboard or report names.
• Known gaps: anything you can’t detect yet, and what data or integration would fix it.

Part 3: Transition list

Listing transitions separately catches the moves the stage blocks miss. Write one line per allowed move.

• From → To: for example Opportunity → Customer.
• Trigger: the event or rule (deal marked closed won, first order paid).
• Set by: workflow name, integration, or manual edit by which role.
• Side effects: what else should happen (owner change, onboarding flow starts, nurture stops).

Then list the moves that must never happen, such as Customer → Lead because someone filled out a newsletter form. Those become your guard rules.

Part 4: Worked example

This is a filled-in block for a B2B software company with a sales-led motion. The stage is “Sales Qualified Lead”.

• Stage name: Sales Qualified Lead (SQL).
• Internal value: salesqualifiedlead.
• Definition: A lead that a sales rep has spoken to and confirmed has a relevant use case, a budget owner involved, and a decision expected within six months.
• Entry criteria: Rep sets the “Qualification outcome” property to “Qualified” after a discovery call logged as a meeting. A workflow then sets the lifecycle stage. Reps do not edit the lifecycle stage directly.
• Exit criteria: (1) Deal created in the New Business pipeline → Opportunity. (2) Qualification outcome changed to “Not now” → back to Marketing Qualified Lead with lead status “Nurture”. (3) Qualification outcome “Disqualified” → Other, with a disqualification reason required.
• Maximum expected time in stage: 14 days. After that, the owner gets a task and the record appears on the stale SQL report.
• Key events tracked: meeting held, meeting no-show, pricing page views, reply to rep email, second contact from the same company engaging.
• Required data: contact owner, company, company size band, use case, qualification outcome, qualification date.
• Owner: Account executive assigned on qualification.
• Handoff: The SDR who ran discovery assigns an AE using the territory rules; the AE gets an email and a task due within one business day.
• Automation in this stage: Marketing nurture emails stop on entry. A task is created for the AE. If no deal exists after 14 days, a reminder task is created and the sales manager is notified at 21 days.
• Suppressions: Excluded from all marketing campaigns except event invitations the AE explicitly adds them to.
• Metrics: SQLs created per month; SQL → Opportunity conversion rate; median days from SQL to deal creation; share of SQLs reverting to nurture.
• Reports that depend on this stage: “Pipeline funnel by source” dashboard, monthly board pack.
• Known gaps: Meetings booked on reps’ personal calendar links aren’t logged, so some discovery calls never trigger qualification. Fix: connect all reps’ calendars and require the meeting outcome field.

Notice how specific the entry rule is. It names the property that triggers the change, who sets it, and what the system does next. That’s what lets you build the automation later without another round of meetings.

Part 5: Lifecycle map review checklist

Before you build anything from the map, check it:

1. Every stage has both entry and exit criteria filled in.
2. No two stages can be true for the same record at the same time.
3. Every exit criterion points to a named destination stage.
4. Each entry criterion can be detected from data the CRM actually receives today, or the gap is listed.
5. Each stage has one owning role.
6. Backward moves are listed and deliberate.
7. Marketing suppressions are defined for every stage where sales or service owns the relationship.
8. At least one metric per stage can be reported from the CRM without spreadsheets.
9. Sales, marketing and customer success leads have each read and agreed the definitions.
10. A review date is set (quarterly works for most teams).

When the map is agreed, each “Automation in this stage” line becomes a requirement. The CRM automation requirements template is the next step.