CapEx vs OpEx in software development, modeled from your Jira

What counts as capitalizable software development

The CapEx versus OpEx question in software comes down to one thing: are you building a new asset, or are you running and maintaining one? Work that creates or substantially enhances software an organization intends to use over multiple periods is generally treated as a capital expenditure. Work that keeps the existing system alive — bug fixing, support, routine maintenance, planning, and research that does not result in a new asset — is generally operational expenditure.

In practice the line runs straight through your backlog. A team shipping a brand-new feature is doing capitalizable work. The same team firefighting a production defect the next morning is doing operational work. Most engineering organizations carry both kinds of work in the same sprint, on the same board, under the same people — which is exactly why the split is so hard to see.

Why the CapEx and OpEx split matters

Capitalized software development cost lands on the balance sheet and is amortized over time; operational cost hits the income statement now. That difference shapes reported margins, EBITDA, and how your finance team and board read the health of the business. When the split is guessed once a year from a few interviews, it is fragile and hard to defend. When it is grounded in the actual work delivered, the conversation gets a lot calmer.

• Finance gets a repeatable, transparent input instead of an annual estimate pulled together under deadline.
• Engineering leaders can show how investment in new development trends quarter over quarter.
• Boards and investors see a consistent methodology rather than a number that moves for unexplained reasons.

How Delimetrics models the split from Jira

You tell Delimetrics two things and it does the rest. First, mark which work is capitalizable using a custom field on your Jira issues — most teams already have a flag or can add one in minutes. Second, store a monthly cost per team. From there the model is deliberately simple and easy to explain to a CFO:

• Take each team's monthly cost, scaled to the period you are viewing.
• Calculate that team's capitalizable share: capitalizable tickets delivered divided by all tickets delivered in the period.
• CapEx equals period cost multiplied by the capitalizable share. The remainder is OpEx.

Because the calculation reads from Jira issues your teams already close, there is nothing new to instrument and no timesheets to chase. Connect Jira Cloud, point us at your team, work type, and capitalizable fields, and you have a CapEx versus OpEx view in minutes.