LAER Model: Land, Adopt, Expand, Renew, With Stage Gates (2026)

Every LAER diagram tells you the four stages. None of them tells you what has to be true before an account is allowed to move between them.

That is the whole problem. A contract gets signed, so the account moves to Adopt. Onboarding finishes, so it is called adopted. Usage looks healthy, so somebody adds it to an expansion list. Renewal arrives, so the team starts building a value story.

Every one of those transitions is defensible on a diagram, and every one of them can be wrong.

A usable LAER model needs a layer the four boxes do not have:

Someone accountable for the stage. Evidence that the work of the stage actually happened. A condition that decides when the account moves. That is the difference between LAER as a picture and LAER as an operating model.

First, which LAER do you mean

Two unrelated frameworks share this acronym, and search traffic for the term is split roughly between them.

LAER in customer success is Land, Adopt, Expand, Renew. It describes the commercial lifecycle of a recurring-revenue customer. That is this article.

LAER in sales training is Listen, Acknowledge, Explore, Respond. It is an objection-handling technique used inside a single conversation. Different origin, different purpose, no relationship to the first.

If you came for objection handling, this is not it.

What the LAER model is

LAER was developed by TSIA, the Technology and Services Industry Association, for technology companies shifting toward subscription and as-a-service economics. TSIA’s own description is that Land, Adopt, Expand and Renew “defined customer success in the SaaS era.”

The four motions:

Land. Win the initial commercial relationship.
Adopt. Get the customer using the solution and receiving value from it.
Expand. Grow spend as new use cases, capacity or products become relevant.
Renew. Preserve the recurring commitment.

The word that matters is connected. LAER is not four departmental programmes running in parallel. Weak Land creates adoption problems. Weak Adopt undermines expansion. Expansion that is sold but never embedded creates renewal risk. Thin value evidence makes renewal a negotiation instead of a confirmation.

Which is why the useful implementation is not four columns on a lifecycle dashboard. It is a chain of evidence.

The LAER stage-gate model

This is the operating version. The stages are TSIA’s. The gates are the layer this article adds.

The question this table forces is not which box is this account in. It is what has to become true before this customer deserves to move into the next motion.

1. Land: the contract is not the output

The obvious definition of Land is win the customer. Commercially that is right. Operationally it is incomplete.

The output of Land is not Closed Won. It is a customer the post-sale team knows how to make successful.

The Land gate

Land is complete when the post-sale owner can answer five questions without reconstructing the sales cycle.

What did they buy? The actual contracted scope.

Why did they buy it? The business or operational problem behind the purchase.

What does success mean? A customer outcome, not product activation.

Who owns that outcome? The stakeholder who cares whether it happens.

What are we measuring against? A baseline, prior process or defensible starting point.

If the contract is signed and those answers are missing, the deal has closed but the customer has not been landed. That gap becomes expensive at renewal, when someone is asked to prove improvement against a starting point nobody recorded. Capturing that starting point is the single cheapest thing you can do in the entire lifecycle, and it is covered properly in the value realization framework.

The first failure happens in the handoff

Sales optimised for getting the customer to say yes. Customer Success has to turn that yes into a result. Connected jobs, not identical ones.

So a handoff should transfer evidence, not introduce two people. What has to survive it:

The test is not whether a document exists. It is whether the Adopt owner understands the purchase without asking Sales to reconstruct it.

2. Adopt: onboarding complete does not mean adopted

This is where LAER goes vague fastest. Implementation finishes, users log in, training happens, the project turns green, and the company declares the customer adopted.

But product activity answers are they using it. The customer bought because they expected something to improve. Those are different questions, and a customer can use a product constantly while producing nothing that defends another year of spend.

The adoption ladder

Account created, then first report generated, then a report every week, then reporting is simply how the team works, then the time spent preparing reports materially falls.

The first steps prove activity. Only the last one proves the adoption mattered.

The Adopt gate

Four things, all of them evidenced.

Core behaviour. The action that actually creates value is happening, not generic login activity.

Repetition. It has happened enough times to look like a workflow rather than an experiment.

Relevant breadth. Enough of the intended population is participating for the use case to function.

First meaningful outcome. Something the customer bought the product to change has started changing.

That outcome does not have to be full ROI. It does have to be more than seventy-three users logged in this month. How to measure the usage half of this belongs to your product adoption KPI; what this gate owns is the decision about whether Adopt has earned the right to end.

Every expansion creates adoption debt

This is the idea the four-box diagram hides, and it is the most expensive one to miss.

The standard picture runs LAND → ADOPT → EXPAND → RENEW, one pass, one direction. Now take a customer who has genuinely adopted one workflow, and expand them into another department, another module, another region, another hundred seats.

Commercially that is an Expand event. Operationally you have just created a second Adopt problem. The new scope did not become valuable because the customer signed for it. Somebody still has to adopt it.

So the lifecycle actually behaves like this:

Every expansion creates adoption debt. The customer now owes another adoption cycle, and the vendor owes another value-delivery cycle.

Ignore that debt and this year’s expansion becomes next year’s shelfware. Then renewal arrives and the account looks strangely unhealthy despite having grown. It is not strange. The expansion was sold. It was never adopted.

This is the single strongest argument against running LAER as a one-way waterfall, and it is why the stage-gate version lets accounts move backward.

3. Expand: healthy does not mean ready to buy

Strong usage, low support volume, high NPS, a CSM who likes them. So the account lands on an expansion list.

But satisfaction is not buying need. A perfectly healthy account may have nothing else worth purchasing.

Expansion requires pressure: a seat ceiling approaching, a second department appearing, usage exceeding the plan, a new workflow emerging, repeated interest in functionality outside the contract, consumption limits starting to bind.

The question is not is this customer happy. It is has something changed that makes additional scope rational.

The Expand gate

A specific motion. What exactly could they buy?
A customer-side need. What changed that makes it useful?
A buyer path. Who can authorise it?
Timing. Why now rather than in six months?

Missing any of those and you have an account worth watching, not a qualified opportunity. Scoring and staging those opportunities properly is its own job, handled in the expansion pipeline model.

Expansion should send the account backward

When an expansion closes, do not park the account in Expand until renewal. Send the new scope back into Adopt.

The original relationship may be mature. The new scope is not. A product fully adopted in Finance tells you nothing about Operations, who have just bought access and are effectively a new adoption cohort needing activation, repetition, workflow integration and their own first outcome.

Which gives a principle worth writing on the wall:

Expansion revenue is not realised until the expansion is adopted.

4. Renew: confirm value, do not discover it

Renew is where the first three stages present their bill.

Weak Land and nobody remembers the original outcome. Weak Adopt and usage exists but no business result was documented. Bad Expand and extra product sits unused on the contract. Then renewal arrives and a CSM has thirty days to explain twelve months.

That gets called a renewal problem. It is usually accumulated LAER debt.

The Renew gate

By the time an active renewal motion starts, the team already knows the renewal date, what has actually changed for the customer, what evidence supports it, what could still prevent renewal, who has authority, and what procurement, legal or budget steps remain.

Running that motion is a discipline of its own, covered in SaaS renewal management. What LAER owns is the upstream question: why does this account arrive at renewal prepared or unprepared?

Does every customer have to Expand before Renew?

No, and treating LAER as a mandatory sequence is the most common over-reading of it.

One customer runs Land → Adopt → Renew. Another runs Land → Adopt → Expand → Re-adopt → Renew. Another cycles through Expand and Re-adopt twice. Another renews before an expansion that comes later.

The letters name commercial motions that matter. They do not require every account to pass through every box exactly once. The operating question stays the same: what evidence exists now, and what motion does that evidence justify?

Who owns each motion

The customer sees one relationship. Internally, several teams touch it.

There is no universal ownership map, and that is fine. The failure is not choosing a different map. It is having an ambiguous one, where nobody knows the point at which accountability changes hands.

The LAER metrics that matter

The common mistake is hanging every available SaaS metric off the framework, which produces a reporting catalogue rather than an operating model.

One outcome metric per stage, plus a small number of leading indicators.

The test for anything else: would this metric change a decision? If not, it does not belong on the operating dashboard.

A worked example

A B2B reporting platform. The customer buys 80 seats because producing their weekly management report takes the operations team about five hours.

Land. Expected outcome: reduce weekly reporting time. Starting state: five hours per cycle. Operations owns the workflow; Finance approved the purchase. Outcome, starting state, stakeholder, scope and implementation owner are all captured, so the account can move.

Adopt. Implementation finishes and users start building reports. Over time the reporting workflow becomes habitual and preparation time begins falling. The evidence that matters is not that 65 of 80 seats are active. That shows adoption. The drop in reporting effort is what shows value.

Expand. A second business unit starts requesting access. That is a signal, not yet an opportunity. The team establishes which group, which workflow, why the current package is insufficient, who owns budget and when rollout has to happen. Now it qualifies, and the deal closes.

Re-adopt. The account does not proceed to Renew. The second business unit is new adoption debt: it has to activate, repeat the core workflow, make it operational and reach its own first outcome. Only then has the commercial expansion become a customer expansion.

Renew. The motion opens with the original desired outcome, current outcome evidence, adoption history, expansion history, stakeholder ownership, known risk and commercial timing already in place. Renewal reviews evidence rather than creating it.

Five ways LAER breaks

Land means contract signed. The transaction completes but the customer outcome never reaches CS, so Adopt begins without a destination. Fix: outcome, owner and starting state become Land-gate requirements.

Adopt means onboarding complete. Implementation tasks turn green and the customer is declared adopted, confusing project completion with behavioural change. Fix: require repeated core behaviour and a first meaningful outcome.

Expand means healthy account. CS exports the top health scores and Sales calls them expansion targets, mistaking satisfaction for buying need. Fix: require need, scope, buyer and timing.

Expansion closes and nobody re-adopts it. New seats appear on the contract with no owner for their adoption, and expansion ARR becomes unused scope. Fix: every material expansion opens a new Adopt motion.

Renew begins when the meeting is booked. Evidence collection starts after commercial negotiation has, so twelve months get reconstructed under deadline. Fix: value and risk evidence accumulate through Land, Adopt and Expand.

A 30-day implementation

Week 1: reconstruct real accounts. Take a handful of recently renewed and churned customers and rebuild what was sold, what adoption looked like, whether expansion happened, whether it was adopted, and what evidence existed at renewal. Do not design anything yet. Find where information disappeared.

Week 2: define the gates. For each stage, fix an owner, the required evidence and the exit condition. Keep mandatory evidence small. Eighteen required fields per stage guarantees the system gets ignored.

Week 3: classify live accounts. Take twenty and ask which motion should dominate each. Then have someone else answer independently. If the two disagree regularly, the gate definitions are too subjective. Fix the definitions, not the people.

Week 4: automate facts, not judgment. Automate observable events: contract signed, milestone completed, core usage changed, new team activated, usage limit reached, champion changed, renewal window opened. Let those trigger review. Do not let them draw conclusions. A seat limit can indicate an expansion opportunity; it does not prove one.

How to audit your LAER model

Six questions it should survive.

Can every active account be assigned a dominant current motion? If not, the lifecycle is not operational.

Does every motion have one accountable owner? Contributors can be many. Accountability cannot.

Is movement based on evidence? “Feels healthy” is not an exit condition.

Can the next owner see why the account moved? A transition without evidence is a reset.

Can accounts repeat a stage? They should, because expansion keeps creating adoption cycles.

Can a lost renewal be traced backward? Did it begin in Land, in Adopt, in unrealised expansion, or in the renewal process itself? If you cannot tell, LAER is categorising work without teaching the organisation anything.

Is LAER still current in 2026?

Yes, with two developments worth knowing.

APLAER is TSIA’s extension of the model, adding Analyze and Place ahead of Land, Adopt, Expand and Renew, bringing customer analysis and resource allocation into the lifecycle upstream of acquisition.

DARE is newer and more significant. Published by TSIA in November 2025, the DARE Progressive Growth Model runs Design → Activate → Realize → Evolve and is aimed at AI and outcome-oriented engagements. TSIA describes it as “a services-intensive framework built to deliver guaranteed outcomes and continuous value realization,” and their argument for it is one line worth sitting with:

“AI value isn’t unlocked by adoption; it’s unlocked by integration.”

That is a direct challenge to the assumption underneath LAER, which treats adoption as a reliable proxy for value. Where a provider is contracted to produce a measurable business result rather than to drive software consumption, that proxy stops holding.

None of this makes LAER obsolete.

For most B2B SaaS teams asking how to run acquisition, adoption, expansion and renewal, LAER remains the right starting framework. The stage gates above matter more than which acronym you put above them.

Where GainTrace fits

Every gate in this article depends on evidence existing at the moment someone needs to make a decision. That is the part that fails in practice, and it fails quietly.

The evidence a LAER gate needs sits across CRM, product usage, billing and support. Assembling it by hand is why teams reconstruct value stories at renewal instead of reading them. GainTrace keeps those account signals current and visible, so a gate decision starts from evidence rather than from someone’s memory of the last call.

It does not decide whether an account should move. That judgment is yours, and it should be.