Software CapEx vs OpEx: How Outsourcing Engagements Impact Your Balance Sheet

A CTO walks into a budget meeting with a solid case. Scope is defined, the architecture holds up, and the timeline is realistic. Six weeks later the project still has no funding, and nobody involved can explain precisely what went wrong.

The technical argument was never the weak point. What sank the request was an accounting question that never made it onto the whiteboard.

Michael McAuliffe, Senior Client Partner at Euvic US, has spent decades advising technology and tech-enabled firms on how to plan, source, and manage global engineering capacity.

This is the conversation that should happen between the CTO and the CFO before the first line of code is ever written."

Michael McAuliffe

Senior Client Partner

Two Buckets, Two Very Different Outcomes

Every dollar spent building software lands in one of two places. Operating expense hits the income statement in the period it is incurred. Capital expense goes onto the balance sheet as an asset and gets amortized across its useful life. For a company measured on EBITDA, that difference is far from cosmetic.

Software built by an internal team is treated as an operating expense. It hits EBITDA directly, dollar for dollar."

Michael McAuliffe

Senior Client Partner

Move two million dollars of engineering spend from operating expense into a capitalized asset and reported EBITDA improves by that full amount in the period, even though the cash leaving the business is identical.

Apply an earnings multiple and the effect on stated enterprise value compounds quickly. Buyers, lenders, and sponsors all anchor to adjusted EBITDA, which is why classification surfaces in every serious diligence process.

Our guide to technical due diligence for investors covers the wider set of questions asked in the same room.

What the Accounting Rules Actually Say

The conventional shorthand holds that internal work is expensed and outside work is capitalized. Reality is more specific. US GAAP governs internal-use software under ASC 350-40, and capitalization turns on the nature of the work, not who employed the engineer.

Preliminary evaluation and post-implementation support get expensed. Development activity on software probable to be completed and used as intended can be capitalized, whether the payroll is internal or the cost is external.

So the reason internal builds so often end up fully expensed has little to do with the rules themselves.

In-house engineers move between feature development, maintenance, and production support inside the same week, and untangling that into a defensible capitalization schedule requires time tracking most teams never maintain. An outside engagement scoped as a defined project produces that documentation as a byproduct: statements of work, acceptance criteria, and milestone invoices create a clean cost boundary auditors can follow.

End-to-End Services: See How We Can Help You Get Better Results.

6000+ Polish software developers and IT experts are ready to level up your business

Learn About Our Services

What Changes Under ASU 2025-06

FASB issued Accounting Standards Update 2025-06 in September 2025, removing the project-stage model from ASC 350-40 entirely.

In its place sits a principles-based test built around management authorization and funding, together with whether significant development uncertainty remains. Grant Thornton and Forvis Mazars both cover the shift in detail.

FASB has indicated that more software development costs may end up expensed under the revised guidance, because the development-uncertainty test can push the capitalization start date later than the old model did.

Effective dates run to annual reporting periods beginning after December 15, 2027, putting calendar-year companies at 2028, with early adoption permitted. Deloitte covers the scope of the amendments in full.

Engagement Structure Decides More Than Location

Rate cards absorb most of the attention in outsourcing conversations, which is part of why our comparisons of developer hourly rates by country get read as often as they do. How the engagement is structured carries more weight on the financial side.

Time and materials billing produces a stream of hours with no natural boundary between qualifying development work and everything else. Deliverable-based contracts produce discrete, documented units of work with acceptance attached to each one.

The car doesn't make money sitting on the lot. It only earns when it's out driving around, and it doesn't matter where it goes as long as the meter runs."

Michael McAuliffe

Senior Client Partner

A vendor billing by the hour has no particular reason to care whether a delivery slips from March to June. A partner working against defined outcomes carries that delay as a real problem, because payment attaches to the deliverable.

The Build Still Has to Earn Its Keep

Accounting treatment improves how a build reads on paper. It does not make the build worth making.

Most outsourced software projects don't fail because of bad code. They fail before anyone writes a line of code."

Michael McAuliffe

Senior Client Partner

Michael's 15-point risk assessment for choosing software partners scores exactly that territory, and only five of the fifteen items are technical. Euvic built the Product Solutions Manager role to hold delivery against a stated business result rather than a feature list, the same discipline behind Position Green reaching a 1000% growth rate.

Before the Next Build Gets Proposed

Four moves worth making while classification is still changeable:

• Bring the CFO into the scoping conversation, not the approval conversation.
• Ask your accounting advisors how your current capitalization policy performs under ASU 2025-06, and whether early adoption serves you.
• Compare a time-and-materials arrangement against a deliverable-based statement of work on documentation quality, not on rate alone.
• Where an acquisition, refinancing, or raise sits within eighteen months, treat classification as a board-level topic. Quality of earnings reviewers certainly will.

Structure Your Next Build Around a Defined Outcome

A software build shapes your product roadmap and your financial statements at the same time. Book a consultation with the Euvic US team to scope your next build as a defined, deliverable-based project.

Learn more about Euvic US and our 6,000+ person organization with 100+ specialized teams at a 92% client retention rate. Review our case studies to see how our engineering teams have supported companies such as FIAT, GM, and Samsung.