If you are the one signing the check for a custom software project, at some point your CFO or your CPA is going to ask how it should be recorded. Is custom software a capital expense (CapEx) or an operating expense (OpEx)?
The honest answer is that it can be either, and on most projects it is both. Which bucket a given invoice lands in depends on what the software is for, how long it will be used, and which phase of the work the invoice covers. This article walks through the factors in plain language so the conversation with your accountant is short. It is not accounting advice. The rules have specifics that depend on your situation, and your CPA should make the final call.
The difference, in one paragraph each
A capital expense buys or improves a long-lived asset. Think a building, a piece of equipment, or a system the business will run on for years. The cost goes on the balance sheet and is expensed over the asset’s useful life instead of all at once.
An operating expense is the ongoing cost of running the business. Rent, payroll, utilities, subscriptions. It hits the income statement in the period it is incurred.
Custom software sits awkwardly between the two. It is clearly an asset. It is also built by people over time and kept alive by more people over more time. That is why the answer is usually a split rather than a single label.
Five factors that decide it
1. What the software is for
The rules differ depending on whether the software is for internal use or is a product you intend to sell or license to others. Internal-use software, which describes most of what we build for middle-market operators, generally has the more straightforward treatment. Software you plan to sell has a stricter set of rules about when costs can be capitalized. If you are building a product, tell your CPA early, because the answer changes.
2. How long it will be used
This is the biggest factor. Software you expect to run the business on for years looks like a capital asset. Software built for a short-lived purpose, such as a one-season campaign tool, looks like an operating expense. Most custom systems we build are the first kind. A scheduling platform, a customer portal, or an operations system is meant to last, and that is the case for capitalizing the build.
3. What it costs
Every company has a capitalization threshold, a dollar amount below which purchases are simply expensed because tracking them as assets is not worth the effort. A custom system is almost always above that line. A small enhancement to it might not be.
4. How much is built versus bought
Software written specifically for your business is a stronger candidate for capitalization than an off-the-shelf tool with a subscription and some configuration. A SaaS subscription is nearly always OpEx. A system your team designed and owns is closer to a building you had constructed.
5. What it does for the business
Software that opens a new market, replaces a core process, or changes how the company operates has the profile of a capital investment. A minor efficiency tweak looks more like an operating cost. This factor rarely decides things on its own, but it shapes the conversation with your accountant.
The phase of the work matters as much as the software
Here is the part that surprises most owners. Even on a single project that clearly qualifies as a capital asset, not every invoice is treated the same way. The accounting generally follows the phase of work:
- Planning and evaluation. Deciding what to build, whether to build it, and how. These costs are often expensed as incurred. Our VDP Sprint and System Evaluation live here.
- Design and development. Building the thing. This is where costs are most often capitalized, once the project has been approved and is likely to be completed.
- Post-launch maintenance and support. Keeping it running, fixing bugs, small updates. Nearly always expensed. Hosting is the same.
- Major enhancements. A new module or a significant expansion may be treated like new development. Routine upkeep is not.
This is one reason we structure engagements the way we do. A fixed-fee planning step, then a build under its own statement of work billed in installments tied to milestones, then maintenance and hosting as separate monthly items. Each SOW and each invoice maps cleanly to a phase. Your bookkeeper does not have to guess which part of a lump-sum bill was planning and which was construction.
R&D tax credits: worth asking about
Custom software development can qualify for research and development tax credits in some cases, particularly when the work involves solving technical problems where the outcome was uncertain at the start. Not every project qualifies and the documentation requirements are real. The rules around how development costs are deducted have also shifted in recent years. Raise it with your CPA before the project starts, not after, because the records you keep during the build are what make a claim defensible. We can provide timesheets, milestone documentation, and technical write-ups if your accountant asks for them.
What this means when you are budgeting
A few practical implications for the owner or CFO deciding whether to go ahead:
- The build cost is likely to spread across several years on the income statement rather than land in one. That changes how the project looks against this year’s numbers.
- The ongoing costs are real and recurring. Most of the lifetime cost of software comes after launch. Plan for maintenance, support, and hosting as operating line items from day one. Ours are described on the Managed Hosting & Support page.
- If you are PE-backed, your sponsor likely has a view on capitalization policy. Ask before the first invoice.
- Whatever the treatment, the value has to beat the fee. Accounting changes when the cost shows up, not whether it was worth paying.
The typical budgets by type of project are on our pricing page, along with how we structure payment. That page plus this article should give your CPA everything needed to set the treatment before you sign anything.
The first step
Talk to your CPA with the five factors and the phase breakdown in hand. Then, if the project is worth doing, the first step with us is a 30-minute intro call and a Deep Dive, followed by a fixed-fee VDP Sprint or System Evaluation that gives you a real scope and a real cost to take back to your accountant. Start here.
Frogslayer does not provide accounting or tax advice. Confirm the treatment of any software cost with your CPA.