The SaaS Customer Success Metric That Predicts Churn

The most impor­tant SaaS cus­tomer suc­cess met­ric is not the one your CS team reports on every Mon­day. It is not logins, NPS, time-in-app, tick­et vol­ume, or health score col­or. It is the per­cent­age of cus­tomers who actu­al­ly achieved the out­come you sold them — mea­sured 90 days after they start­ed using your prod­uct. Almost no SaaS com­pa­ny between $5M and $15M ARR mea­sures this direct­ly, which is exact­ly why most reten­tion dash­boards are con­fi­dent­ly wrong.

This arti­cle gives you the for­mu­la, the math, and a 3‑step play­book to instru­ment it. By the end, you will know which met­ric to put at the top of your CS review, why it mat­ters more than NPS, and how it ties direct­ly to net rev­enue reten­tion, LTV, and the mul­ti­ple a buy­er will even­tu­al­ly pay for the com­pa­ny.

What “Customer Success” Actually Measures (And What It Doesn’t)

Cus­tomer suc­cess has two def­i­n­i­tions. One of them is use­ful. The oth­er is a van­i­ty met­ric dressed up in CSM head­count.

Use­ful def­i­n­i­tion: Did the cus­tomer get the result you promised them when they bought the prod­uct?

Van­i­ty def­i­n­i­tion: Are the cus­tomer’s users active in the prod­uct?

Activ­i­ty is a lead­ing indi­ca­tor of noth­ing in par­tic­u­lar. A cus­tomer can log in every day and still churn at renew­al because the dash­board nev­er moved the num­ber that jus­ti­fied the pur­chase order. Con­verse­ly, a cus­tomer can log in once a week and renew with­out hes­i­ta­tion because the prod­uct is qui­et­ly deliv­er­ing the out­come that was promised. Activ­i­ty cor­re­lates with out­comes only in prod­ucts where activ­i­ty is the out­come (Slack, Fig­ma, Notion). For every­thing else — sales tools, ops tools, finance tools, mar­ket­ing tools, ver­ti­cal SaaS — activ­i­ty is a proxy. And prox­ies break.

The right SaaS cus­tomer suc­cess met­ric mea­sures the out­come, not the proxy. That met­ric is Out­come Achieve­ment Rate (OAR).

The Headline Metric: Outcome Achievement Rate (OAR)

Out­come Achieve­ment Rate = (# of cus­tomers who achieved the promised out­come with­in 90 days) / (Total # of cus­tomers who start­ed using the prod­uct 90+ days ago)

Three pieces mat­ter, and all three are oper­a­tional deci­sions, not mea­sure­ment deci­sions:

1. Promised out­come. What spe­cif­ic result did your sales motion com­mit to? “Increase qual­i­fied pipeline by 30% in 90 days.” “Reduce close-the-books from 8 days to 4 days.” “Cut cus­tomer sup­port tick­ets by 25%.” If the promise is fuzzy, OAR can­not exist.
2. Achieve­ment thresh­old. Did the cus­tomer hit the promised num­ber, or close enough to count? Define this once and apply it con­sis­tent­ly.
3. Mea­sure­ment win­dow. 90 days from go-live is the right default. Long enough to see real impact, short enough to pre­dict renew­al behav­ior, short enough to act on.

Once you fix those three def­i­n­i­tions, OAR is a sin­gle num­ber you can put on the wall and trend month-over-month.

Why the 90-Day Window Is Non-Negotiable

Renew­al deci­sions are made well before the renew­al date. By month 6 of a 12-month con­tract, the cus­tomer’s view of whether the prod­uct worked is most­ly locked in. By month 9, the bud­get­ing com­mit­tee has already short­list­ed what gets renewed and what gets cut. If you wait until month 11 to find out the cus­tomer did­n’t get the out­come, you are man­ag­ing a death spi­ral, not reten­tion.

90 days gives you 9 months to fix what’s bro­ken before it shows up as churn.

Why Standard SaaS Customer Success Metrics Fall Short

Most CS dash­boards are stacks of met­rics that all mea­sure adja­cent things. They feel com­pre­hen­sive. They are not.

Here is how the com­mon met­rics fail when you ask them to pre­dict renew­al:

Met­ric	What It Actu­al­ly Mea­sures	Why It Fails as a Renew­al Pre­dic­tor
Logins / DAU / MAU	Whether users open the prod­uct	Many cus­tomers log in reli­gious­ly and still don’t get val­ue
Fea­ture adop­tion	Whether users touched spe­cif­ic fea­tures	Adop­tion ≠ out­come; you can adopt the fea­ture and still miss the result
NPS	How users feel right now	Mood-dri­ven; uncor­re­lat­ed with renew­al in B2B
CSAT after sup­port tick­ets	Qual­i­ty of sup­port inter­ac­tions	Mea­sures CS team per­for­mance, not prod­uct out­come
Health score (com­pos­ite)	A weight­ed aver­age of the above	Garbage in, garbage out — most health scores hide the real sig­nal
Time-to-val­ue	How fast onboard­ing com­pletes	Onboard­ing fin­ish­ing ≠ cus­tomer win­ning
QBR sen­ti­ment	Whether the QBR call went well	Cus­tomers are polite; polite­ness is not a met­ric

None of these met­rics tell you whether the cus­tomer got what they paid for. OAR does.

This is not a take­down of those met­rics. They are use­ful for diag­nos­ing why OAR is low. But none of them belong at the top of the dash­board. OAR does.

How OAR Drives the Metrics Investors Actually Care About

OAR is upstream of every reten­tion met­ric a sophis­ti­cat­ed investor or acquir­er cares about. The chain looks like this:

OAR → Gross Rev­enue Reten­tion → Net Rev­enue Reten­tion → LTV → Val­u­a­tion Mul­ti­ple

Each link in the chain is most­ly mechan­i­cal. If OAR is high, cus­tomers stay (GRR holds), cus­tomers expand (NRR climbs), LTV com­pounds, and the LTV/CAC ratio that dri­ves your val­u­a­tion mul­ti­ple stays healthy. If OAR is low, the chain col­laps­es one link at a time, but it always col­laps­es.

The Math: How a 10-Point OAR Improvement Compounds

Take a SaaS com­pa­ny at $10M ARR with these base­line met­rics:

• Aver­age rev­enue per cus­tomer: $50K/year
• Gross month­ly churn: 1.5% (≈ 16.6% annu­al)
• Net rev­enue reten­tion: 105%
• Gross mar­gin: 78%

That com­pa­ny’s LTV (using the stan­dard for­mu­la LTV = ARPC × Gross Mar­gin / Annu­al Churn) lands at rough­ly $235K per cus­tomer.

Now sup­pose OAR improves from 50% to 60%. Cus­tomers who hit their out­come churn at maybe 5% annu­al­ly. Cus­tomers who don’t churn at 30%+. Mov­ing 10 per­cent­age points of the cus­tomer base from the high-churn buck­et to the low-churn buck­et drops the blend­ed annu­al churn from ~16.6% to rough­ly ~14%. Re-run­ning the LTV math:

New LTV ≈ $50K × 0.78 / 0.14 = $279K per cus­tomer

That is a ~$43K LTV improve­ment per cus­tomer from a 10-point OAR move. With a 200-cus­tomer base, that’s rough­ly $8.7M in new­ly-cre­at­ed LTV — and the com­pa­ny has­n’t acquired a sin­gle new cus­tomer to earn it. Improv­ing OAR is the sin­gle high­est-lever­age move avail­able to most $5M–$15M ARR SaaS com­pa­nies, because it con­verts cus­tomers you’ve already paid for into cus­tomers who actu­al­ly pay back.

This is why churn is the silent killer: small move­ments in reten­tion com­pound into very large move­ments in enter­prise val­ue. Out­come Achieve­ment Rate is the oper­a­tional lever you actu­al­ly pull to move reten­tion.

Worked Example: Two SaaS Companies, Identical NRR, Very Different Futures

To see why OAR is upstream of every reten­tion met­ric, com­pare two com­pa­nies with iden­ti­cal NRR today.

Com­pa­ny A

• ARR: $10M
• NRR: 105%
• OAR (mea­sured): 30%
• Cus­tomer base: 200, aver­age $50K
• Expan­sion dri­ven by: a small group of pow­er users buy­ing more seats; the rest are flat or declin­ing

Com­pa­ny B

• ARR: $10M
• NRR: 105%
• OAR (mea­sured): 70%
• Cus­tomer base: 200, aver­age $50K
• Expan­sion dri­ven by: most cus­tomers see­ing the out­come and nat­u­ral­ly buy­ing more

On a fundraise deck, both com­pa­nies show 105% NRR. A casu­al investor would call it a tie. Now project three years for­ward.

Com­pa­ny A’s path: The 70% of cus­tomers who did­n’t hit their out­come churn at 25–30% annu­al­ly. Expan­sion from the 30% who did achieve their out­come even­tu­al­ly slows because the pow­er-user pool shrinks as the base shrinks. By Year 3, NRR has dropped to ~85%, gross churn is up, and the com­pa­ny is fight­ing just to stay flat. The board adds a CRO. The CRO does­n’t fix it because the prob­lem isn’t sales — the prob­lem is that 70% of cus­tomers nev­er got val­ue.

Com­pa­ny B’s path: The 70% who hit their out­come churn at ~5% and expand reli­ably. The 30% who did­n’t get the out­come become the focus of CS work; OAR climbs from 70% to 80%. NRR holds at 105% and creeps high­er as expan­sion picks up. By Year 3, ARR is ~$12M with­out hero­ics ($10M com­pound­ing at 105% reach­es $11.6M; push­ing NRR up anoth­er point or two from ris­ing OAR adds the rest). The Rule of 40 num­ber is healthy. The com­pa­ny is fund­able on bet­ter terms than it could get today.

Same start­ing NRR. Dif­fer­ent OAR. Wild­ly dif­fer­ent three-year out­comes. This is why OAR belongs at the top of the SaaS cus­tomer suc­cess met­ric stack — it is the lead­ing indi­ca­tor of every lag­ging met­ric an investor actu­al­ly cares about.

How to Instrument OAR (3‑Step Playbook)

Most SaaS com­pa­nies do not mea­sure OAR not because it is hard, but because the oper­a­tional def­i­n­i­tions have nev­er been writ­ten down. Here is the play­book to fix that in 30 days.

Step 1: Define the Promised Outcome — Per ICP, Not Company-Wide

Com­pa­ny-wide out­come def­i­n­i­tions are too vague to be mea­sur­able. The promise that clos­es a $200K enter­prise deal is not the same as the promise that clos­es a $20K SMB deal. Define the out­come per ICP seg­ment.

A typ­i­cal $5M–$15M ARR SaaS com­pa­ny has 2–4 real ICP seg­ments. For each seg­ment, write down on one page:

• Who they are (seg­ment def­i­n­i­tion)
• What they bought the prod­uct to accom­plish (the promise)
• How that promise is mea­sured (the met­ric and the thresh­old)
• Where the data lives (their sys­tem, your prod­uct, a sur­vey, a CSM-col­lect­ed num­ber)

If the promise is “increase qual­i­fied pipeline,” the met­ric is qual­i­fied pipeline dol­lars and the thresh­old is +30% with­in 90 days. If the promise is “reduce close-the-books time,” the met­ric is days-to-close and the thresh­old is a 50% reduc­tion. Force the speci­fici­ty. Vague­ness here is the most com­mon rea­son OAR does­n’t get mea­sured.

Step 2: Capture the Baseline at Signup

You can­not mea­sure improve­ment with­out a base­line. Cap­ture the cus­tomer’s start­ing num­ber for the out­come met­ric with­in the first 7 days of go-live. This is a CSM respon­si­bil­i­ty but it is a sales oblig­a­tion: the AE knows the prospec­t’s pain num­ber from dis­cov­ery, and that num­ber must be car­ried for­ward into the imple­men­ta­tion hand­off.

A sim­ple base­line cap­ture form has 4 fields:

1. ICP seg­ment
2. Promised out­come met­ric
3. Start­ing val­ue (today)
4. Thresh­old to count as achieved (e.g., +30%, ‑50%, or an absolute tar­get)

If you can­not fill in those four fields for every new cus­tomer, your sales motion is sell­ing a fuzzy promise. That is a deal-qual­i­ty prob­lem upstream of CS.

Step 3: Measure at Day 90 and Mark the Outcome

At day 90, cap­ture the cur­rent val­ue of the out­come met­ric and com­pare to the base­line. Mark the cus­tomer as Achieved or Not Achieved. Roll up across the cohort to get OAR.

The out­put is a sin­gle per­cent­age you can trend month over month, seg­ment by seg­ment.

The full instru­men­ta­tion looks like this:

Step	Own­er	Out­put	Cadence
Define promised out­come per ICP	Sales + CS lead­er­ship	One-page out­come spec per seg­ment	Once, then revis­it­ed quar­ter­ly
Cap­ture base­line at signup	AE → CSM hand­off	4‑field base­line record per cus­tomer	Every new cus­tomer, week 1
Mea­sure at day 90	CSM	Achieved / Not Achieved flag	Every cus­tomer, day 90
Roll up cohort OAR	Ops / Ana­lyt­ics	Sin­gle % per ICP seg­ment	Month­ly, with trend

This is the entire sys­tem. It does not require a Cus­tomer Suc­cess Plat­form, a new head­count, or a six-month inte­gra­tion project. It requires the dis­ci­pline to write down what you sold and check whether the cus­tomer got it.

The SaaS Customer Success Metric Stack

OAR sits at the top, but it does not stand alone. The full stack a $5M–$15M ARR SaaS com­pa­ny should run, in pri­or­i­ty order:

Tier	Met­ric	What It Tells You	Why It Sits Here
1 (Head­line)	Out­come Achieve­ment Rate (OAR)	Did cus­tomers get what we sold them?	Lead­ing indi­ca­tor of all reten­tion math
2 (Reten­tion)	Gross Rev­enue Reten­tion	How much rev­enue stayed	Direct bot­tom-line con­se­quence of OAR
2 (Reten­tion)	Net Rev­enue Reten­tion	How much expand­ed vs. churned	The sin­gle most-watched SaaS met­ric by investors
2 (Reten­tion)	Logo reten­tion rate	How many cus­tomers stayed	San­i­ty check on rev­enue reten­tion
3 (Diag­nos­tic)	Time-to-first-val­ue	How fast onboard­ing deliv­ers a result	Short­er TTFV → high­er OAR
3 (Diag­nos­tic)	Fea­ture adop­tion (key fea­tures only)	Whether the cus­tomer is using the parts that dri­ve the out­come	Pre­dicts OAR mid-cohort
3 (Diag­nos­tic)	Cus­tomer-report­ed sat­is­fac­tion (NPS / CSAT)	How cus­tomers feel	Use­ful when tri­an­gu­lat­ed with OAR
4 (Activ­i­ty)	Logins / DAU / MAU	Whether users open the prod­uct	Use­ful only as a lead­ing “aban­don­ment” alert

Tier 1 is the met­ric you put at the top of the CS review. Tier 2 is what the board sees. Tier 3 is what the CS team uses to diag­nose why Tier 1 moves. Tier 4 is what most com­pa­nies put at the top of the dash­board, which is exact­ly the wrong order.

Common Mistakes That Kill OAR (And the Fix)

These are the pat­terns that show up repeat­ed­ly when a $5M–$15M ARR com­pa­ny final­ly mea­sures OAR for the first time and finds it embar­rass­ing­ly low.

Mis­take 1: Sell­ing out­side the ICP. The sin­gle largest dri­ver of low OAR is bad-fit cus­tomers. The prod­uct can­not deliv­er the out­come because the cus­tomer’s real­i­ty does­n’t match what the prod­uct was built for. Fix at the source: tight­en ICP qual­i­fi­ca­tion before the cus­tomer ever signs. Low OAR is often a sales prob­lem, not a CS prob­lem.

Mis­take 2: Aspi­ra­tional promis­es in the pitch. Sales says “you’ll cut sales cycle by 40%.” The prod­uct can do 20%. OAR is math­e­mat­i­cal­ly capped at the gap between the promise and what the prod­uct can deliv­er. Fix: pres­sure-test out­come claims against the achiev­able dis­tri­b­u­tion from exist­ing cus­tomers, and rewrite the pitch to match real­i­ty.

Mis­take 3: Out­comes that aren’t mea­sur­able. “Improve sales pro­duc­tiv­i­ty” is not a mea­sur­able promise. “Add 15% to qual­i­fied pipeline with­in 90 days” is. Vague promis­es pro­duce vague OAR — usu­al­ly opti­misti­cal­ly vague, which is worse than admit­ting the met­ric isn’t being mea­sured.

Mis­take 4: Mea­sur­ing too late. Mea­sur­ing out­come achieve­ment at month 9 is autop­sy work, not met­ric work. Move to day 90. Any­thing lat­er is too late to influ­ence renew­al.

Mis­take 5: Report­ing OAR com­pa­ny-wide instead of by seg­ment. Aggre­gate OAR hides the truth. The same com­pa­ny often has 75% OAR in one ICP seg­ment and 25% in anoth­er. The aggre­gate looks like 50% and prompts no action. Seg­ment OAR by ICP, chan­nel, con­tract size, and indus­try. There are always sig­nif­i­cant vari­ances; pre­tend­ing oth­er­wise is mal­prac­tice. (This is the same lens applied to every oth­er met­ric — seg­ment every­thing.)

Mis­take 6: Treat­ing low OAR as a CS per­for­mance issue. Low OAR is almost nev­er a CS team prob­lem. It is upstream — wrong cus­tomer, wrong promise, wrong prod­uct fit, or wrong prod­uct-mar­ket fit alto­geth­er. Hold­ing the CS team account­able for fix­ing OAR with­out giv­ing them author­i­ty to push back on sales and prod­uct is a set­up for fail­ure.

OAR vs. Other SaaS Customer Success Metrics: Which Belongs Where

OAR replaces noth­ing — it sits on top.

Met­ric	Keep It?	Where It Sits
OAR	Yes	Head­line met­ric
Gross Rev­enue Reten­tion	Yes	Board met­ric
Net Rev­enue Reten­tion	Yes	Board met­ric
Logo reten­tion	Yes	Board san­i­ty check
NPS	Yes	Diag­nos­tic
CSAT	Yes	Diag­nos­tic, sup­port qual­i­ty
Health score	Option­al	Only if it weights toward out­come data
Logins / DAU	Yes	Activ­i­ty / aban­don­ment alert
Fea­ture adop­tion	Yes (key fea­tures)	Diag­nos­tic
Cus­tomer effort score	Option­al	Onboard­ing diag­nos­tic

The mis­take is not hav­ing too many met­rics. The mis­take is hav­ing no hier­ar­chy among them. Once OAR is the head­line, every oth­er met­ric stops being a com­peti­tor for atten­tion and starts being a diag­nos­tic tool.

How OAR Connects to Net Revenue Retention

A com­mon ques­tion: “We already mea­sure NRR. Why add anoth­er met­ric?”

NRR is a lag­ging indi­ca­tor. It tells you what hap­pened over the last 12 months. By the time low NRR shows up in the dash­board, the cus­tomers who did­n’t get val­ue have already left or down­grad­ed. OAR is the lead­ing indi­ca­tor that tells you 9–12 months in advance whether NRR is about to drop.

Com­pa­nies that mea­sure both can see the ten­sion ear­ly. OAR drops to 45% in Q1, but NRR is still 108% because the con­tracts writ­ten at the high­er OAR peri­od are still in their ini­tial term. By Q3, those low-OAR cus­tomers are com­ing up for renew­al, and NRR cracks. Com­pa­nies that mea­sure only NRR notice the prob­lem in Q3. Com­pa­nies that mea­sure both noticed it in Q1 and had two quar­ters to fix it.

How to Put OAR on the Wall in 30 Days

If you are start­ing from zero, here is the min­i­mum work to get OAR into the next CS review:

• Week 1: Sales and CS lead­er­ship write the one-page out­come spec for each ICP seg­ment. Two ICPs is fine to start.
• Week 2: CSMs go back to the last 90 days of new cus­tomers and recon­struct the base­line out­come num­ber from the deal notes. Imper­fect data is fine — the goal is a start­ing OAR num­ber, not aca­d­e­m­ic pre­ci­sion.
• Week 3: Mark each of those cus­tomers as Achieved or Not Achieved at their day-90 mark. Roll up by ICP seg­ment. This is your first OAR.
• Week 4: Put the num­ber on the CS review slide. Decide what to do about the seg­ments that came in below 50%.

You will not love the first num­ber. That is nor­mal. The point of putting it on the wall is that every­one now sees it and deci­sions start mov­ing in its direc­tion.

---

FAQ: SaaS Customer Success Metrics

What is the most important customer success metric for B2B SaaS?

Out­come Achieve­ment Rate (OAR) — the per­cent­age of cus­tomers who hit the out­come you sold them with­in 90 days of going live. Every oth­er cus­tomer suc­cess met­ric is either a diag­nos­tic tool to explain OAR or a lag­ging con­se­quence of it.

What’s a good OAR target?

Above 70% is healthy for a typ­i­cal $5M–$15M ARR B2B SaaS com­pa­ny. 50–70% is the real­is­tic start­ing point for most com­pa­nies that begin mea­sur­ing it. Below 50% indi­cates a struc­tur­al mis­match — usu­al­ly ICP drift, a sales motion that over­promis­es, or a prod­uct that has­n’t reached full prod­uct-mar­ket fit for the seg­ment.

How is OAR different from NPS?

NPS mea­sures how cus­tomers feel right now. OAR mea­sures whether cus­tomers got the out­come they paid for. NPS can be high while OAR is low (cus­tomers like the team but the prod­uct isn’t mov­ing the num­ber). NPS can be low while OAR is high (the prod­uct works but the sup­port expe­ri­ence is rough). Both are use­ful, but OAR is the pre­dic­tor of renew­al; NPS is a mood check.

How is OAR different from a customer health score?

A health score is a com­pos­ite of inputs (logins, fea­ture use, NPS, sup­port tick­ets, CSM gut feel). OAR is a sin­gle bina­ry mea­sure­ment (did the cus­tomer hit the promised out­come, yes or no). Health scores are diag­nos­tic. OAR is the actu­al answer to the ques­tion “is this work­ing?” Most health scores are wrong because they weight activ­i­ty inputs heav­i­ly and out­come inputs light­ly or not at all.

How does OAR relate to revenue retention?

OAR is the lead­ing indi­ca­tor. Gross rev­enue reten­tion and net rev­enue reten­tion are the lag­ging con­se­quences. A drop in OAR today shows up as a drop in reten­tion 9–12 months lat­er. The chain is: OAR → renew­al deci­sions → GRR → NRR → LTV.

Can a product-led growth company use OAR?

Yes, but the def­i­n­i­tions need trans­la­tion. In a PLG motion the “promised out­come” is what­ev­er the user signed up to accom­plish. Cap­ture it at signup (the acti­va­tion event), mea­sure it at day 30 or day 60 instead of day 90 (PLG cycles are faster), and seg­ment by use case rather than enter­prise ICP. The met­ric still works; the cadence shrinks.

Should sales own OAR or should customer success own it?

Cus­tomer suc­cess owns the mea­sure­ment. Sales owns the upstream input (the promise). Prod­uct owns the upstream input (the pro­duc­t’s abil­i­ty to deliv­er the promise). Hold­ing CS account­able for OAR while deny­ing them influ­ence over sales-stage qual­i­fi­ca­tion and prod­uct roadmap is the most com­mon rea­son OAR pro­grams fail.

How is OAR different from time-to-value?

Time-to-val­ue mea­sures how fast onboard­ing deliv­ers a first notice­able result. OAR mea­sures whether the cus­tomer hit the actu­al out­come with­in a defined win­dow. Fast TTV is a lead­ing indi­ca­tor of high OAR but does­n’t guar­an­tee it — a cus­tomer can see a fast first win and still miss the big­ger 90-day out­come.

What if the promised outcome is hard to measure (e.g., “better culture”)?

Then either the promise needs to change or the SaaS prod­uct is sold on aspi­ra­tion rather than result. Either way, the gap is a sales-and-posi­tion­ing prob­lem, not a mea­sure­ment prob­lem. Find the oper­a­tional met­ric the buy­er was secret­ly hop­ing would move (engage­ment sur­vey scores, reten­tion of key tal­ent, inter­nal NPS) and use that as the proxy for the promise. If no proxy exists, the deal prob­a­bly should­n’t have closed.

The Bottom Line

The right SaaS cus­tomer suc­cess met­ric is not a list of 15 indi­ca­tors with no hier­ar­chy. It is one head­line met­ric — Out­come Achieve­ment Rate — sup­port­ed by the reten­tion rate cal­cu­la­tions, LTV math, and diag­nos­tic met­rics that explain why OAR moved. Every oth­er CS met­ric is either upstream of OAR (sales fit, prod­uct fit) or down­stream of it (rev­enue reten­tion, expan­sion, val­u­a­tion mul­ti­ple).

Most com­pa­nies don’t mea­sure OAR because it forces them to write down what they actu­al­ly sold. Once you write it down and check whether the cus­tomer got it, the rest of reten­tion strat­e­gy becomes a series of oper­a­tional deci­sions instead of a series of dash­boards. That’s the whole point: mea­sure out­come, not activ­i­ty. Mea­sure trans­for­ma­tion, not usage. The renewals — and the val­u­a­tion mul­ti­ple — will fol­low.