Nobody can draw your lead lifecycle

Here's a test you can run in five minutes. Walk up to three people on your marketing team and ask each of them to draw your lead lifecycle on a whiteboard. From first touch to closed deal. Every stage, every transition, every handoff.

Compare the three drawings. They won't match.

One person will show five stages. Another will show seven. The criteria for moving from one stage to the next will be different in each version. The point where marketing hands to sales will be in a different place. The definition of MQL will be subtly (or dramatically) different. One person will include stages the others forgot existed. Another will describe transitions that the other two didn't know happened.

Three people on the same team, working in the same platform, on the same leads, with three different understandings of how the system works.

This isn't a knowledge problem. It's a design problem. The lifecycle was never clearly defined in a way that everyone understands, or it was defined once and has drifted so far from the original design that the documentation (if it exists) no longer reflects reality.

Either way, the result is the same: the most fundamental process in your marketing operation, the one that every campaign, every score, every report, and every sales handoff depends on, exists differently in different people's heads. And nobody notices because everybody assumes everyone else understands it the same way they do.

Why the lifecycle drifts

Lead lifecycles don't start unclear. They start as a clean model. Someone designs it during the platform implementation. Stages are defined. Transitions are documented. Criteria are established. The model makes sense on paper and in the platform.

Then reality starts reshaping it.

A campaign needs a stage that doesn't exist, so someone creates one. A new product line requires a different qualification path, so someone adds a branch. Sales complains that leads are arriving too early, so someone tightens the MQL criteria without updating the documentation. A new rep joins and interprets the stages differently because nobody walked them through the model. A platform upgrade changes how lifecycle transitions are triggered and nobody checks whether the new behavior matches the intended design.

Each change is small. Each one makes sense in isolation. Over two or three years, the cumulative effect is a lifecycle that no longer resembles the one that was designed. The platform enforces whatever the current configuration dictates, which may be the result of dozens of undocumented modifications by multiple people with different understandings of the original intent.

The lifecycle didn't break. It evolved without anyone guiding the evolution. And now nobody can describe it accurately because the "it" that exists is different from the "it" that was designed, and different from the "it" that each team member carries in their head.

What a misunderstood lifecycle costs

When the team doesn't share a clear understanding of the lifecycle, every process built on top of it is unreliable.

Scoring loses meaning. The scoring model is supposed to align with lifecycle stages. A lead scores up, hits a threshold, transitions to MQL. But if different people have different understandings of what MQL means, the threshold is arbitrary. Some leads that hit MQL aren't actually qualified under any consistent definition. Others that are genuinely ready for sales sit below the threshold because the scoring criteria don't match the lifecycle criteria. The model produces numbers. The numbers don't mean what anyone thinks they mean.

Reporting becomes fiction. Lifecycle-based reports show conversion rates between stages: lead to MQL, MQL to SQL, SQL to opportunity. These numbers are only meaningful if the stages are applied consistently. If three people apply MQL criteria differently, the MQL number is three different numbers blended together. The conversion rate from MQL to SQL is calculated on a denominator that includes leads from three different definitions of "qualified." The report shows a precise percentage. The precision is false.

Sales handoffs fail. The handoff from marketing to sales depends on both teams agreeing on what "ready for sales" means. If marketing's definition of MQL doesn't match sales' expectation of what they'll receive, every handoff is a disappointment. Sales receives leads they don't consider qualified. Marketing reports leads as handed off that sales never accepts. Both teams point to their own metrics as evidence that the other team is the problem. The lifecycle gap between them is the actual problem, and neither team can see it because they're each operating from their own version.

Nurture programmes miss. Nurture sequences are typically designed for specific lifecycle stages. A lead at the awareness stage gets educational content. A lead at the consideration stage gets comparison content. A lead at the decision stage gets case studies and demo invitations. But if the lifecycle stages aren't clearly defined and consistently applied, leads end up in the wrong nurture. The decision-stage lead receives awareness content. The awareness-stage lead gets pushed toward a demo they're not ready for. The nurture is doing exactly what it was designed to do for the wrong people.

The whiteboard test reveals everything

The whiteboard test isn't a trick. It's a diagnostic. The degree to which the three drawings differ is a direct measure of how much operational risk the lifecycle is creating.

If the drawings are nearly identical, the lifecycle is understood. It may still need improvement, but the team shares a common mental model and can have productive conversations about how to make it better.

If the drawings are moderately different (different numbers of stages, slightly different criteria), the lifecycle has drifted and needs realignment. The original design probably exists somewhere but hasn't been reviewed or communicated in a while. This is fixable with a half-day workshop and updated documentation.

If the drawings are dramatically different (different stage names, different transitions, fundamental disagreement about where the sales handoff happens), the lifecycle needs to be redesigned. Not tweaked. Redesigned from current business requirements with input from both marketing and sales, documented clearly, configured in the platform to match the design, and communicated to everyone who touches it.

The severity of the mismatch determines the size of the fix. But the test itself takes five minutes and reveals a problem that most teams don't know they have until something breaks visibly enough to force the investigation.

How to fix it

The fix is a single exercise with four steps. It doesn't require new tools or a consulting engagement. It requires a room, a whiteboard, and the willingness to admit that the lifecycle isn't what anyone thinks it is.

Step one: map what actually exists. Not what was designed. Not what the documentation says. What the platform actually does right now. Pull the lifecycle configuration from the MAP and the CRM. Trace every stage, every transition trigger, every automation that moves a lead from one stage to another. Document the current state honestly, including the stages nobody remembers adding and the transitions nobody can explain.

Step two: define what should exist. With marketing and sales in the same room, define the lifecycle from scratch based on current business requirements. What stages does a lead pass through from first touch to closed deal? What criteria trigger each transition? Where does the handoff from marketing to sales happen, and what does "qualified" mean in specific, measurable terms both teams agree on?

Step three: reconcile the gap. Compare the current state (what the platform does) with the desired state (what the team just defined). Identify every discrepancy: stages that exist in the platform but not in the new model, transitions that fire on the wrong criteria, automations that move leads based on outdated logic. Each discrepancy is a configuration change that needs to be made.

Step four: document and communicate. Write down the agreed lifecycle model in a shared document that anyone on the team can access. Include the stage definitions, the transition criteria, and a visual diagram that matches the whiteboard drawing the team just agreed on. Then communicate it: walk the team through it, walk new hires through it, and review it every six months to ensure it still matches how the business operates.

The entire exercise takes one to two days. The result is a lifecycle that everyone understands, that the platform enforces consistently, and that produces reliable data for scoring, reporting, and sales handoffs. The cost of not doing it is measured in months of unreliable data, misaligned teams, and lost deals that nobody connects to the lifecycle gap because nobody knew the gap existed.

The lifecycle is the foundation

Every article on this blog about scoring, nurturing, reporting, AI governance, and sales alignment assumes that the lifecycle underneath them is solid. When it isn't, none of those things work properly regardless of how much effort goes into them.

The lifecycle is the most boring, most fundamental, and most impactful piece of infrastructure in your marketing operation. It doesn't produce a campaign. It doesn't generate a pipeline number. It doesn't appear in a QBR deck. But every campaign, every pipeline number, and every QBR metric depends on it being defined clearly, applied consistently, and understood by everyone who touches it.

Run the whiteboard test. If the drawings don't match, you've found the problem that's silently undermining everything else. Fix it first. Everything downstream gets better when the foundation is solid.