Cisco uses the LAER model—Land, Adopt, Expand, Renew—to describe a customer lifecycle in which value is created after the initial sale, not completed by it. The current 820-605 Customer Success Manager exam explicitly expects candidates to work across adoption, renewal, and expansion, while Cisco’s current training material still describes the CSM’s responsibilities across the LAER lifecycle.
The model is easy to memorize and easy to misuse. Real customers do not move through four clean boxes once. They can be adopting one use case, expanding another, and approaching renewal for a third entitlement at the same time. The useful way to apply LAER is as an operating loop with handoffs, evidence, ownership, and recovery paths.
That means each stage should answer three questions: What decision is being made? What evidence supports it? Who owns the next action? When those answers are missing, lifecycle language becomes presentation vocabulary instead of an operating discipline.
Land should preserve the assumptions that justified the purchase
The Land stage is commonly treated as the sales phase, but customer success depends on what survives the handoff. Discovery conversations contain crucial information: why the customer is changing, which stakeholders care, which risks were accepted, what capabilities were promised, how value will be judged, and what timing constraints influenced the decision.
A poor handoff loses that context. The post-sale team then asks the customer to repeat discovery, interprets the purchase through product configuration rather than business intent, and may build a success plan around assumptions that sales never validated. Trust erodes before adoption has even started.
The handoff should therefore behave like versioned state. The account baseline, intended outcomes, success criteria, stakeholders, purchased solution, known constraints, and unresolved questions should be explicit. If any of those change, the change should be visible rather than silently replacing the original story.
Adopt is where the value hypothesis is tested
Adoption is not synonymous with implementation. Implementation can make a capability technically available while adoption asks whether the intended users and processes actually use it in the way required to produce value. A customer can complete deployment and remain stuck in the Adopt stage because usage is shallow, barriers persist, or the solution does not fit the operating workflow.
This stage needs both quantitative and qualitative evidence. Telemetry can show what is being used, by whom, and how often. Conversations can reveal why usage is low or why a high-usage metric is misleading. Process observation can identify workarounds that dashboards cannot see.
A disciplined adoption motion resembles the logic in technology-adoption planning: define the intended behavior, identify barriers, assign owners, change the relevant conditions, and then check whether behavior changed. Training may be appropriate for a knowledge barrier; it is useless for an integration defect or a policy conflict.
Promotion from adoption should be evidence-based
Teams often move to expansion because a calendar says the account is mature or because a commercial opportunity exists. A safer promotion criterion is evidence that the customer has realized enough value in the current scope to make a new scope credible.
This does not require perfect adoption. It requires clarity. The team should know which outcomes were achieved, which remain open, which barriers are understood, and whether the proposed expansion solves a real adjacent problem. The decision to expand should have a reason that would still make sense if no sales target existed.
That logic also protects capacity. Expanding a customer that has unresolved adoption problems can multiply the number of unused capabilities and make the eventual renewal conversation harder. Expansion is not progress if it increases contractual scope faster than realized value.
Expand should create a new success hypothesis, not copy the old one
An expansion motion changes the system. New users, new sites, new products, or new use cases introduce different stakeholders, risks, technical dependencies, and measures. The old success plan provides useful history, but it should not be copied mechanically.
Suppose a customer successfully adopts a collaboration capability in headquarters and wants to expand it to frontline locations. The original outcome may have been meeting efficiency for knowledge workers. The new environment may care more about shift communication, device constraints, network quality, or training logistics. The product family is related, but the value hypothesis is different.
A strong CSM treats expansion as a mini-Land-and-Adopt cycle: validate the new outcome, confirm stakeholders and constraints, define use cases, establish measures, and watch the new adoption behavior. LAER is cyclical precisely because each expansion can restart part of the lifecycle.
Renewal is a lifecycle result, not a late-stage rescue
Renewal risk accumulates long before a renewal date. Weak adoption, unresolved quality problems, sponsor turnover, ambiguous value, and poor stakeholder coverage can exist for months. Waiting until the commercial window opens converts a customer-success problem into a negotiation problem.
The current Cisco certification structure also distinguishes the CSM role from the 700-805 Renewals Manager track. The roles can collaborate, but the CSM’s most valuable contribution to renewal is credible evidence: what outcomes were expected, what changed, what remains at risk, and which stakeholders recognize the value.
Renewal therefore needs a rollback mindset. If the account is drifting, the team should know what intervention is possible before the deadline. That might mean narrowing scope, resolving a barrier, rebuilding executive sponsorship, correcting a success metric, or making an explicit decision that a use case no longer deserves investment.
Observability matters at every stage
Lifecycle management fails when teams collect activity but cannot observe state. A long list of meetings, training sessions, cases, and campaigns does not reveal whether the customer is progressing. Observability means having signals tied to the decisions of each stage.
During Land, the important signals are clarity of outcome, stakeholder alignment, and handoff completeness. During Adopt, the signals include use-case activation, behavior, barriers, sentiment, and operational results. During Expand, the team needs evidence that a new problem exists and that the customer can absorb the additional scope. During Renew, the focus is value evidence, risk, sponsorship, commercial readiness, and unresolved commitments.
The signals should also have owners. A dashboard can show declining usage, but someone must decide whether it is normal seasonality, a technical defect, a process change, or true disengagement. Data without interpretation creates the appearance of control.
Rollback in customer success means reversing bad assumptions
Software teams think of rollback as restoring a previous version after a failed release. Customer-success teams need an equivalent concept. When an assumption proves wrong, the team should be able to return to a workable state rather than defending the original plan.
A rollout may be too broad. A KPI may not represent value. A stakeholder may no longer own the process. A planned expansion may have been premature. The recovery action could be reducing scope, redefining a use case, changing the adoption motion, or rebuilding the success plan around a different business condition.
This is why a living success plan is more useful than a static presentation. It preserves the current state of the value hypothesis and makes change explicit. The organization can explain not only what it is doing now but why the plan changed.
Ownership prevents lifecycle gaps
LAER has natural seams where work can disappear: sales to customer success, implementation to adoption, adoption to expansion, customer success to renewals. Every seam needs an explicit handoff. The receiving team needs the context required to continue the customer story rather than start a new one.
RACI-style ownership is useful when it remains tied to decisions. Who owns the success plan? Who resolves a technical barrier? Who can approve a change in outcome? Who validates value? Who owns the renewal motion? Who decides whether an expansion opportunity is mature enough to pursue?
The answers vary by organization, but ambiguity is itself a risk. The larger the account and the more functions involved, the more important it becomes to distinguish participation from accountability.
The lifecycle is healthy when value survives the handoffs
The best LAER implementations do not feel like four departments passing an account downstream. They feel like one value model being refined as the relationship evolves. The original business outcome remains visible, evidence accumulates, barriers are recorded, decisions have owners, and expansion or renewal uses the history rather than replacing it.
For 820-605 candidates, that is the durable mental model. Land captures the intent. Adopt tests whether the solution changes behavior. Expand extends value only where evidence supports it. Renew confirms that the relationship still deserves continuation. Each stage can expose a bad assumption and send the team back to revise the plan.
Cisco’s broader customer-success ecosystem is built around this lifecycle logic. Memorizing LAER is useful for the exam; operating it requires something harder: traceable decisions, honest evidence, clear ownership, and the willingness to correct course before a weak assumption becomes a renewal crisis.
A lifecycle model is most useful when it remains intelligible after personnel changes. Accounts often lose sponsors, CSMs rotate, technical owners move teams, and commercial responsibilities shift. If the lifecycle exists mainly in individual memory, each transition resets the relationship and forces the customer to reconstruct context.
The operating record should therefore preserve decisions, evidence, barriers, stakeholder roles, and the current value hypothesis. A new owner should be able to see why the account is in a particular lifecycle state, which commitments remain open, and what evidence is needed for the next decision. This continuity is part of customer trust because it shows that the provider’s process is larger than any one relationship holder.
