Compensation Plan Design · Glossary

DNOB (Did Not Onboard) Status

DNOB, short for did not onboard, is a status flag for a deal that closed but where the customer never actually went live. The contract was signed and the commission was earned, but no value was ever delivered. It sits between a healthy deal and a cancellation, and how a comp plan treats it is a question most plans never answer.

What is DNOB status?

DNOB, short for did not onboard, is a status flag for a deal that closed but where the customer never actually went live. The contract was signed. The booking was recorded. The rep earned commission on it. And then the customer never implemented, never used the product, and in many cases never paid.

It is an awkward category because it does not fit the two states a comp plan usually recognizes. The deal did not fail to close, so it is not lost. The customer did not cancel a working relationship, so it is not straightforwardly churn. It closed and then quietly went nowhere.

This matters specifically for bookings-based plans, which pay when the contract is signed rather than when the customer pays. Under a bookings model, a DNOB deal has already been paid on. The company has an expense and no revenue, which is precisely the risk a bookings model accepts in exchange for paying reps quickly.

DNOB compared to the states around it

DNOBChurnCancellationWhat happenedClosed, but the customer never went liveCustomer used the product, then leftContract was voided, often within a cancellation windowRevenue receivedOften noneSome, for a periodUsually noneRep effortFull. The deal was genuinely closed.FullFullTypical commission treatmentUndefined in most plans, which is the problemUsually keptUsually clawed backWhat it signalsA qualification or expectation problem at the point of saleA product or success problemA commercial or legal problem

The fourth row is the important one. Most plans have a rule for cancellations, which is the clawback, and most plans have no rule at all for DNOB. So it gets handled case by case, which means it gets handled inconsistently, which means it generates disputes.

What a plan should say about DNOB

There is no single right answer, and the choice is a genuine trade-off rather than a best practice. What is not defensible is having no answer at all.

Treat it as a clawback. Commission is recovered because no revenue materialized. Simple and consistent with how cancellations are handled, but it punishes the rep for something that may have been entirely outside their control, such as an implementation failure or a change of sponsor.

Pay on collections instead of bookings. The problem largely disappears, because commission is not paid until the customer pays. This is the structural fix, and it is a real plan design decision with real consequences for rep cash flow. See bookings vs collections.

Use a milestone payout. Pay part of the commission at signature and the rest at go-live. The rep is rewarded for closing, and the company does not pay in full for a customer that never onboarded. This is the middle path, and for businesses where onboarding is a real risk it is usually the right one.

Pay it anyway, deliberately. A legitimate choice if the company judges that onboarding is not the rep's responsibility. The point is to make it a stated policy rather than an accident.

What this means?

For Finance, DNOB is a commission expense with no matching revenue, and if it is not tracked it is invisible. A DNOB rate that is quietly rising is telling you something important about qualification, and it will show up in the commission expense line long before anyone connects it to the sales motion.

For RevOps, the pattern is the diagnostic. A single DNOB deal is bad luck. A cluster of them, particularly around one rep, one segment, or one product, is a signal that something is being sold that cannot be delivered, or being sold to someone who was never going to implement it.

How Visdum handles DNOB

Visdum can flag a closed deal as DNOB and apply the plan's stated treatment to it, whether that is recovering the commission, withholding a milestone that was contingent on go-live, or paying it in full as a deliberate policy. The point is that the treatment is defined in the plan and applied consistently, rather than being decided one deal at a time by whoever happens to be asked.

Because the adjustment carries its reason, a rep whose payout changes because of a DNOB sees why on their commission statement, rather than encountering an unexplained deduction. And because DNOB is a tracked status rather than an informal note, the pattern is visible: Finance can see the commission expense attached to deals that never onboarded, and RevOps can see whether that number is growing.

Take a self-guided product tour to see this in action, or read how to build a SaaS sales compensation plan.

Calculate your OTE in 30 seconds

Enter your base, quota, and commission rate. Get your projected OTE plus earnings at common attainment scenarios.

Open the OTE calculator →

Frequently asked questions

What does DNOB mean?

DNOB stands for did not onboard. It is a status flag for a deal that closed but where the customer never actually went live. The contract was signed and commission was earned, but the product was never implemented and often never paid for. It sits awkwardly between a healthy deal and a cancellation.

How is DNOB different from churn?

Churn means a customer used the product and then left, so revenue was received for a period. A DNOB customer never went live at all, so there is often no revenue whatsoever. Churn signals a product or success problem. DNOB usually signals a qualification or expectation problem at the point of sale.

Should commission be clawed back on a DNOB deal?

There is no single right answer, but there should be a stated one. Options include recovering the commission, moving to a collections-based model so it is never paid early, splitting payment across a milestone at signature and another at go-live, or paying in full as deliberate policy. What is indefensible is having no rule at all.

Why does DNOB matter on a bookings-based plan?

Because a bookings-based plan pays when the contract is signed rather than when the customer pays. Under that model, a DNOB deal has already been paid on, which leaves the company with a commission expense and no revenue. That is the precise risk a bookings model accepts in exchange for paying reps quickly.

How can DNOB commission risk be reduced?

The structural fix is a milestone payout: pay part of the commission at signature and the rest at go-live. The rep is still rewarded for closing, but the company does not pay in full for a customer who never onboarded. Moving to collections-based commission removes the risk entirely, at some cost to rep cash flow.

What does a rising DNOB rate indicate?

Usually a qualification problem. A single deal that never onboards is bad luck. A cluster of them, especially around one rep, one segment, or one product, suggests something is being sold that cannot be delivered, or sold to buyers who were never going to implement it. Finance sees it first, in the commission expense line.