5 Finance Quick Wins That Boost EBITDA Before Exit

The EBITDA you present in a confidential information memorandum is not the EBITDA that survives diligence. Every sponsor who has run more than a handful of processes knows this. The gap between reported, adjusted, and pro forma EBITDA is where value is won or lost — and it is almost always a function of how well the finance function anticipated buyer scrutiny.

What follows is a playbook we use when we have roughly 60 to 180 days before a process begins. These are not cosmetic adjustments. Each of them is defensible in front of a competent quality-of-earnings provider, and each of them materially shifts the enterprise value bridge when executed properly.

1. Revenue recognition cleanup — and why recurring revenue quality matters more than growth

Before you optimize anything, reconcile what you actually have. In most mid-market companies we work with, revenue is booked on a blend of policies that accrued over time: cash-basis remnants from early-stage accounting, invoice-date recognition for services that should be ratable, and one-time implementation fees commingled with subscription revenue. None of this is fraud. All of it will show up in a QoE report as a risk.

The single most impactful move is to separate recurring from non-recurring revenue at the ledger level, not just in a footnote. Buyers pay a multiple on recurring revenue that is two to three times the multiple on project or one-time revenue. If $4M of what you are calling ARR is actually implementation fees, professional services, or variable consumption overages, you are leaving a material amount of enterprise value on the table simply because the categorization is not clean.

Specifically:

• Move implementation and onboarding fees to a distinct revenue category. If they are truly ratable over a contract life, book them ratably. If they are one-time, call them one-time.
• Separate consumption-based overages from committed minimums. The committed portion is recurring; the variable overage is not, and buyers will model it differently.
• For multi-year contracts, disclose the weighted average remaining life. A three-year recurring contract at $500K/year is worth more than three one-year contracts that happen to have renewed.

The goal here is not to inflate anything. It is to make sure that when a buyer's QoE provider rebuilds your revenue from source documents, they arrive at the same numbers you have been reporting internally — and that the quality of that revenue is visible without them having to dig.

2. Expense reclassification — the capitalizable costs hiding in OpEx

This is the most common and most defensible EBITDA lift we see. In many founder-led and lower-middle-market companies, engineering salaries, consulting fees for multi-year platform builds, and software development costs are expensed as incurred. GAAP allows — and in many cases requires — capitalization of internal-use software development costs once the project passes the application development stage, per ASC 350-40.

A 25-person engineering team where 60% of time is spent on new feature development (not maintenance or bug fixes) can yield seven-figure capitalizable costs annually. That does not "create" EBITDA out of nothing; it moves spend that was genuinely investment below the EBITDA line, where buyers expect to see it.

The same logic applies to:

• Implementation costs for ERP or new platform rollouts
• Consulting fees tied to a specific capitalizable project
• Leasehold improvements expensed as repairs
• Internally developed intangibles — brand, processes, trained workforce is not capitalizable, but documented processes tied to a specific implementation often are

The discipline here is documentation. Do not attempt this the month before a process. You need time-tracking data, project charters, and a capitalization policy that has been consistently applied for at least two quarters before buyers start asking questions. Anything that looks like a late-stage reclassification done to dress up a deal will get unwound in diligence.

3. Working capital normalization and the enterprise value bridge

Working capital does not show up in EBITDA, but it absolutely shows up in the cash-free, debt-free bridge to equity value. And in mid-market deals, the negotiation around the working capital peg routinely moves $2M to $5M of equity value between buyer and seller. Yet most sellers approach the peg as an afterthought, often with numbers their controller generated the week before signing.

Start normalizing now:

• Build a 24-month trailing view of net working capital, not 12. A single year smooths over seasonality; two years lets you and your advisor argue a cycle-adjusted peg rather than a point-in-time snapshot.
• Identify what is genuinely operational working capital versus items that belong in the cash or debt-like buckets. Deferred revenue from annual prepaid contracts is a classic fight — buyers try to treat it as debt; sellers argue it is ordinary course working capital. The answer depends on the business, but you need the analysis done before the LOI, not after.
• Scrub AR aging. Any receivable over 120 days is a discussion. Either reserve for it properly (which reduces working capital but removes a diligence risk) or collect it.
• Review AP timing. Companies that consistently stretch payables to 75+ days have a working capital profile that will normalize adversely post-close. Buyers know this and will argue for a higher peg.

The goal is not to manipulate the peg — it is to defend a peg that reflects how the business actually operates in a normal cycle, not a snapshot on a specific closing date.

4. Add-back documentation that survives buyer scrutiny

Every management presentation we have ever seen has a slide titled "Adjusted EBITDA" with eight to fifteen add-backs totaling 15–40% of reported EBITDA. In almost every case, 30–50% of those add-backs get haircut in diligence — not because they are fabricated, but because they are not documented.

A defensible add-back has three things: a clear category, contemporaneous support, and a reason it will not recur under new ownership. "CEO travel" is not an add-back unless you can document which specific trips, why they were non-recurring, and why the go-forward CEO — who will almost certainly travel — will not incur similar costs. "Legal fees" is not an add-back unless you can point to a specific matter (an M&A transaction, a one-off litigation) that has concluded.

Categories that typically survive:

• Transaction costs — legal, accounting, advisory fees tied specifically to the current or a prior process. These are the easiest add-backs to defend if you have invoices.
• Owner compensation above market — if the CEO-owner earns $800K in total comp and the buyer will replace them with a professional CEO at $400K, the delta is defensible. Get a comp benchmark from a reputable source before the process starts.
• One-time legal matters — litigation that has settled, with documented settlement and legal spend.
• Non-recurring customer concessions — documented by customer, reason, and whether the issue has been resolved.
• Owner-related expenses that will not continue — a leased vehicle, a personal travel pattern, a family member on payroll.

Categories that routinely get haircut:

• "Rebranding" or "website refresh" expenses — buyers argue these are ongoing marketing investments
• System implementations — usually treated as ordinary course for a company at your scale
• Management bonuses tied to the transaction — sometimes defensible, often not, depending on how they are structured
• "Growth investment" add-backs for hires that stayed — if the salesperson is still on the payroll, the cost is recurring

Build your add-back schedule as a living document starting 12 months before a process. Every add-back should have a supporting file: the invoice, the board resolution, the comp study, the settlement agreement. When the QoE team arrives, you hand them a binder, not a spreadsheet.

5. Run-rate EBITDA with a defensible methodology

Run-rate — or "annualized" or "pro forma" — EBITDA is where the most equity value is captured and the most credibility is lost. Done correctly, it lets a buyer see the earnings power of a business that has acquired a new customer, opened a new location, or closed a cost action that is not yet reflected in trailing numbers. Done poorly, it looks like wishful thinking and gets ignored.

The methodology matters more than the number. A defensible run-rate adjustment has:

• Timing certainty — the event has already occurred or is contractually committed. A signed enterprise contract with a defined start date can be run-rated. A "likely to close" pipeline opportunity cannot.
• Quantification tied to evidence — a cost action of $1.2M annually should tie to specific employees terminated with documented severance, or a specific contract cancelled with a termination letter.
• A clear annualization approach — if you are annualizing a customer that started in Q3, you need to show that their consumption pattern in the two quarters you have data for supports the annualized number.
• No double-counting — if you have added back the cost of a position that was eliminated, you cannot also run-rate the revenue of a new hire who is covering the work.

A useful test: if the run-rate adjustment is more than 15% of reported LTM EBITDA, expect buyers to discount it heavily or demand an earn-out structure that ties purchase price to actual future performance. The cleanest processes we have seen keep run-rate adjustments modest and rigorously documented, preserving credibility for the adjustments that really matter.

The bridge, not the number

Sponsors and buyers do not pay on a single EBITDA number. They pay on the bridge — reported, adjusted, pro forma, run-rate — and they pay a premium when every step of that bridge is defensible without having to be argued. The work above is not about inflating anything. It is about making sure that when a buyer's diligence team rebuilds your numbers from source, they arrive at the same place you did, with the same story.

We typically start this work six to twelve months before a process. If you are closer to a transaction than that, there is still meaningful value to capture — particularly in add-back documentation and working capital normalization — but the revenue recognition and capitalization work requires runway to avoid looking opportunistic.

If you want to walk through where your bridge is vulnerable, we run exit readiness engagements specifically for this window, and our FP&A and performance management work builds the operating cadence that makes the diligence phase far less painful.