A business should not add back every unusual project expense when unusual projects consume money every year. The project names may change, but the operating requirement can remain. Removing all of those costs from EBITDA describes a business that never needs to repair its systems or adapt its operations.

This is an easy mistake for a founder to make in good faith. Last year involved a scheduling system replacement. This year involved a warehouse reconfiguration. Neither project is expected to repeat, so both look exceptional when examined invoice by invoice. The problem becomes visible only when someone reads across the years.

Test the spending category

An invoice proves that a cost occurred. It does not prove that the cost sits outside the normal economics of the business. For that, the unit of analysis needs to move from the individual engagement to the operating need it served.

Consider a company that repeatedly hires outside specialists because its internal team cannot handle systems changes. Each consultant may have a defined end date. Yet if the company needs outside help for a different systems problem each year, a continuing expense exists even without a continuing contract.

That does not make every project cost recurring. A discrete expense caused by an exceptional event may support an adjustment. But project completion is weak evidence on its own. The stronger evidence is that the underlying need has ended, without another expense taking its place or necessary work being deferred.

Keep a normal expense allowance

Consider an illustrative business reporting EBITDA of 800,000 dollars after expensing 180,000 dollars of special projects. The founder proposes adding back the full amount, producing adjusted EBITDA of 980,000 dollars. All of the projects are complete, and none carries the same name as a project in the next annual budget.

A review finds comparable operating project expenses of 110,000, 125,000 and 120,000 dollars in the three preceding years. Management also expects roughly 120,000 dollars of similar work next year. If that evidence supports a normal annual allowance of 120,000 dollars, the potential adjustment is 60,000 dollars, not 180,000. Adjusted EBITDA would then be 860,000 dollars, subject to support for treating the excess as exceptional.

The allowance is not automatically a historical average. A larger operation may need more support, while a completed investment may genuinely reduce future work. The estimate should reflect the current business and the work required to sustain it. Historical spending is evidence, not a formula that substitutes for judgment.

Check the accounting before doing this arithmetic. Only costs that reduced reported EBITDA belong in this expense adjustment. A capitalized implementation cost cannot be added back as though it were an operating expense, and depreciation is already excluded from EBITDA. Continuing capital expenditure still matters to cash conversion, but it belongs in a separate analysis.

Look for the replacement cost

Some projects end because the work moves elsewhere. A consultant leaves, but an employee takes over system administration. An implementation contract closes, but the software subscription and support agreement begin. An adjustment that removes the old expense without recognizing the necessary replacement overstates the earnings available to an owner.

There is another version of the same problem: the founder absorbs the work. The invoice disappears because the founder spends Friday fixing data or coordinating vendors. That may reduce cash expense today, but it does not establish that a buyer can operate the business at the claimed cost. The replacement capacity needs to be identified and priced.

Keep this analysis separate from buyer integration savings. A buyer might already have the required team, but that is a potential benefit of its ownership rather than proof of standalone EBITDA. This distinction belongs in the operating work behind exit preparation, before an adjustment schedule becomes a negotiation document.

Review the project ledger this week

Ask your controller or outside accountant for three years of expenses coded to special projects, implementation and similar accounts. Include relevant costs buried in professional fees. Review them with the person responsible for delivering the work, not finance alone.

  • Group expenses by the operating need served rather than vendor name.
  • Confirm which amounts reduced EBITDA and which were capitalized.
  • Identify replacement spending, including employee time and ongoing support.
  • Compare the proposed adjustment with the next twelve months of planned work.

For each proposed add back, record the evidence that the need has ended and assign an owner to check it. Put the schedule into the monthly reporting pack. When a replacement expense appears, revise the adjustment rather than giving the new project another exceptional label.