The quarterly review starts the way it always does. The number is hit, missed, or comes in close. The room moves to commentary, pipeline coverage, and what the next quarter looks like.
One person at the table is doing the math in their head. They know what hitting the number costs the company in places the booking line doesn’t show. They don’t raise it. The agenda doesn’t have a slot for it.
The question that doesn’t get asked: Did this revenue strengthen the business?
It rarely gets asked. When it surfaces, it gets deflected. A redirect to next quarter’s pipeline. A short “margins held.” A “we’re looking into it” means we aren’t. Each person moves quickly past the question.
That gap, between the revenue you report and the revenue that strengthens the business, is where most companies quietly lose enterprise value.
The Gate
Picture a gate. A defined opening with four sides. Each side is one of the dimensions of good revenue.
A deal that fits the gate has four faces of its own, each aligned with one of the four sides. The deal goes through without forcing anything. A deal that doesn’t fit is too big, the wrong shape, or it requires the gate to be reshaped before it can pass.
Three things matter about how the gate behaves.
First, its dimensions are the four economic tests that determine whether a booked deal is the deal the company wanted to book.
Second, forcing a deal through has a cost, and that cost is not paid in the quarter in which the deal closes. It shows up in engineering, in support sized for one customer’s instance, in commitments to a custom path, and in renewal expectations that the account team cannot say no to. Each cost lands months or quarters later, on operating lines that nobody traces back to the original close.
Third, the gate can be reshaped on purpose, for one deal at a time. Named in the deal review. Ring-fenced so the next deal is evaluated against the original gate, not the exception. The reshape is a one-time admission, not a recalibration of the standard. Without the ring-fence, the exception becomes the precedent, and the gate has been reshaped without anyone deciding to.
The Sides of the Gate
| Side of the gate | Fits the gate | Forces the gate |
| Margin | Holds or improves margin. The deal pays its own way. | Discounted to close. The deal borrows margin from the rest of the book. |
| LTV | Expansion path visible at six months. Renewal disposition strong. | Support-intensive from go-live. Expansion path unclear or absent. |
| CAC | In line with the segment. Payback inside the target window. | Two to three times the core. Payback stretches beyond the planning horizon. |
| EBITDA | Positive at booking. Holds positive at twelve months. | Marginal or negative. Operating cost absorbs what the top line produced. |
Most deals fall into one of four shapes against the gate.
ICP customer, list-price or modest discount, margin holds, LTV strong, CAC inside the window. The four faces of the deal line up with the four sides of the gate. Most reviews barely discuss these deals because they didn’t create heat.
The deal that fits inside the gate but doesn’t fill the four sides. Maybe it closed on a discount nobody would defend in writing. Maybe it’s the wrong segment for the motion. The booking is real. The renewal economics never recover. The deeper damage is in the comp-plan signal. Sales sees that this kind of deal got approved. The next pipeline review, the same shape shows up in three more places. The wrong shape becomes the trained shape.
The strategic logo. The math does not work on its own. The company decides to reshape the gate for this one deal, naming the trade in the deal review and ring-fencing it so the next deal is evaluated against the original gate. This is the only category that should produce a value-eroding deal on purpose. When it gets named and ring-fenced, it works as intended. When it goes through quietly as if it were a clean fit, it is forced fit.
A composite scene drawn from how this usually plays out. The numbers are indicative.
A $400,000 enterprise logo the company has been chasing for three quarters. Strategic territory. Recognizable name. The sales lead is pushing hard. To close, the customer asks for three bespoke features and an integration that isn’t on the roadmap.
In the deal review, the customer success lead raises a concern. The bespoke features will run heavy on support. The team has seen the pattern with two other accounts. The point gets noted. The deal goes through anyway, because the logo matters this quarter and the support cost shows up on someone else’s line.
The deal closes at quarter-end. Product commits two engineering sprints, roughly two months of work, pulled from the existing roadmap. Two committed items get pushed to the next half to make room.
Then the cost begins to surface.
Revenue recognition. Contract terms tie portions of the booked ACV to feature delivery. Part of the revenue that hit the quarter is now spread across the next two quarters. The forecast for next quarter starts with a small hole that has to be filled.
Implementation. Takes four months instead of two. The bespoke features have edge cases that surface during deployment. Implementation services were not separately priced for this customer, because the discount to close consumed the implementation buffer.
Support load. In the first six months post-go-live, escalations on this account run roughly three times the cohort average. The bespoke features behave differently from the core product, and support engineers learn this customer’s instance separately. The CS lead’s flag from the deal review was right. Nobody references it.
Renewal year. The customer asks for two more bespoke features and references the precedent from year one. The account team cannot say no without putting the renewal at risk. Engineering commits another sprint. The customer’s instance drifts further from the core product.
Expansion. The CS lead pitches the standard expansion module on a renewal call. The customer says “our instance doesn’t work that way. Can you build it for us the way you built the integration.” The expansion motion that works for the rest of the book stops working for this account.
Precedent. The next big enterprise prospect hears about the bespoke build through industry conversation. They ask for the same. The deal review references the prior approval. The cost of the original deal arrived in four operating lines over four quarters, and nobody traced it back to the original close.
The lesson is not that the deal was wrong. It might have been the right deal. The lesson is that the company forced it through the gate without naming that it was forcing it.
CompaniesLook at Economics.
The Question is When, and Who has Authority
Most companies already have something in place. Some have a deal desk. Others have a final VP sign-off above a dollar threshold. Larger organizations have pricing committees and segment exception reviews. Smaller ones rely on the CRO and the CFO having a conversation before close. The variation scales with company size and deal complexity.
Example #1
A Series B SaaS, around $20 million in ARR. Founder-CEO still in every major deal. The mechanism is the CEO saying yes or no. It works when the CEO’s economic instincts are calibrated. It falls down when the CEO is the person most attached to the logo, because the logo is going in the next investor deck. The same person is making the economic call and the narrative call. The narrative usually wins.
Example #2
A growth-stage SaaS, $80 to $150 million in ARR. The mechanism is a standing pre-close conversation between the CRO and the CFO on any deal above a threshold. It works when both have authority and both push back. It falls down when the CRO is carrying the quarter and the CFO is treated as advisory, which is most of the time. The conversation happens. The deal still goes through.
Example #3
A late-stage or public company, $300 million ARR and up. The mechanism is a deal desk with a pricing committee for exceptions above thresholds. It works when deal desk reports to Finance and has authority to hold a deal. It falls down when deal desk reports to Sales, which is more common than the org chart admits, and “hold” means “delay by a day so we can find a way to approve.”
The mechanism scales with the company. The authority does not. Authority is a function of org design and tenure. In most companies, the mechanism is real and the authority is decorative.
Timing matters as much as authority. When the fit-the-gate conversation happens in the QBR after close, the only available move is to write it up. When it happens at proposal, deal desk, or contract review, there is still time to say no, restructure, or name the reshape deliberately.
Deliberate Reshape, Ring-fenced
Deliberate reshape is not a permanent change to the gate. It is a one-time decision to admit a specific deal that does not fit, made openly, named in the deal review, and ring-fenced so the next deal is evaluated against the original gate.
The ring-fence is the discipline. Without it, the exception becomes the precedent. The next strategic deal references the prior approval. The deal review treats the exception as the new norm. The gate has been reshaped without anyone deciding to reshape it.
The audit question is not whether the gate is the right shape. It is whether the current shape was chosen for each deal it admitted, or whether it drifted there.
The Test You Can Run on a Sunday
You do not need a methodology to start. You need the question and a single page.
Pull the last four quarters. Take the top ten bookings from each. For each deal, ask: did this fit the gate the company said it had? If it did, on which sides and at what cost? If it didn’t, was the reshape deliberate or accidental?
Four data points to gather:
- Gross margin twelve months in.
- Lifetime value signal six months in. Renewal disposition, expansion pattern, support intensity.
- All-in customer acquisition cost against the deal.
- EBITDA contribution at booking and at twelve months.
A note on CAC. This test uses fully-loaded CAC (sales plus marketing spend, allocated at the segment level) measured against the gross-margin-adjusted contribution. This is the investor view, the same definition the published benchmarks use. Marketing-attributed CAC is useful for channel decisions. It is not the right lens for reading whether a deal fit the gate.
Lay the answers out on a single sheet. Look at it.
What the test looks like in practice.
| Deal | ACV | GM (12mo) | LTV signal (6mo) | Blended CAC payback | EBITDA at 12mo | Shape |
| 01 | $180K | 68% | Strong, expansion underway | 14 months | Positive | Clean fit |
| 02 | $220K | 65% | Strong, renewal locked | 16 months | Positive | Clean fit |
| 03 | $55K | 78% | Strong, expansion underway | 11 months | Positive | Clean fit. Smallest ACV, strongest economics |
| 04 | $190K | 45% | Uncertain | 34 months | Marginally negative | Forced fit. Margin side compressed |
| 05 | $160K | 48% | Weak, support-intensive | 38 months | Negative | Forced fit. LTV side compressed |
| 06 | $210K | 44% | Uncertain | 36 months | Marginally negative | Forced fit. Margin side compressed |
| 07 | $140K | 47% | Weak, no expansion path | 40 months | Negative | Wrong shape. Doesn’t fill the four sides |
| 08 | $250K | 58% | Strategic logo, market signal | 24 months | Neutral | Deliberate reshape. Named and ring-fenced |
| 09 | $90K | 52% | Segment experiment | 28 months | Marginally negative | Forced fit. CAC side compressed |
| 10 | $110K | 50% | Segment experiment | 30 months | Negative | Forced fit. CAC side compressed |
Three deals fit the gate. The smallest, at a fraction of the ACV of the others, has the strongest economics. Shape is not a function of deal size.
Five deals forced the gate. Different sides compressed in each. Margin in some, CAC in others, LTV in a couple. Each is real revenue, and each is operating drag the financials will not show until the cost has compounded across quarters.
One deal was a deliberate reshape. The math did not work on its own. The positioning value did. Named in the deal review. Ring-fenced.
One deal was the wrong shape. The booking went through but the four sides were not there. Should have moved through deal desk and been declined. It was approved because the mechanism was real and the authority was decorative.
Three deals carried most of the year’s enterprise value. Six contributed nominal revenue and active drag. The tenth was the deliberate reshape, taken on purpose.
That is the test. You can run it on a Sunday with a spreadsheet and the last four quarters of bookings.
Published benchmarks show top-quartile B2B SaaS companies recover CAC in under sixteen months. Bottom-quartile players take nearly four years. The spread is real. Composition is one of several drivers, alongside product-market fit, geographic pacing, and capital structure. All of them are downstream of whether the company is choosing what goes through the gate.
The Next Board Meeting
The next board meeting opens with the usual questions. Did we hit the growth rate? Did the quarter come in as forecast? How does the next half look?
Someone in the room asks a different first question. Not “what was the ACV.” Not “did we hit the number.” Something closer to: what shape was the revenue we booked? Did it fit the gate, or did it force the gate?
That question changes the operating cadence within two quarters. The QBR question follows the board question. The deal review follows the QBR. The comp plan follows the deal review.
The only change needed to start is the first question in the room. Everything else follows from it.
If the last four quarters of bookings reads as composition rather than just volume, the next conversation worth having is whether the operating cadence is positioned to enforce the shape of the gate, or just to report on the shape that arrived. That conversation is worth having before the next quarter starts.
The architectural concepts and methodology behind this argument are the proprietary work of Marketing Affects.
Source: Top-quartile and bottom-quartile CAC payback benchmarks drawn from publicly available SaaS economics research.