Why Software Is Part of Your Means of Production

You own your machines. You rent the system that quotes, schedules and invoices for them. What that costs in EBITDA and tax, and when renting is right.

An owner signs a 10-year note for a new machining center. The same month, the owner signs a 1-year subscription that renews itself, for the system that schedules the machine. Nobody at the machine builder can raise the payment in year 3 or switch the spindle off. The software works the other way. NetSuite's standard agreement, for one, renews for 1 year at a time unless the customer gives written notice at least 30 days before it expires (Oracle NetSuite agreement).

Both are means of production. In plain economic terms, that means capital goods: the buildings, machines, tooling and software a business uses to make what it sells. The system that quotes, schedules, tracks and invoices belongs on that list; when it goes down, the floor follows. A shop would never let a machine builder reprice its machines every year or retire them on the builder's schedule. Most shops let their software vendors do both. This post runs a machine's arithmetic on that system, including where the comparison fails.

Software is capital

The national accounts already treat it that way. In its 1999 comprehensive revision, the Bureau of Economic Analysis "recognized business and government expenditures for computer software as capital formation" (BEA), whether prepackaged, custom or built in-house. US private software investment reached $751.3 billion in 2025 (BEA via FRED), about 45% the size of all equipment investment (FRED).

Manufacturers put far less into it. On our sums from BEA's detailed industry estimates, manufacturing invested about 17.5 cents in software per dollar of equipment in 2025, against about 45 cents economy-wide. Fabricated metal products, the job-shop sector, invested about 8 cents: $1.18 billion against $15.5 billion (BEA detailed estimates). Treat those ratios as indicative, because BEA rates this industry detail well below its aggregates in quality (BEA). Shops treat machines as capital and software as overhead. Some owners reject the split: "I don't lease machines ... I see no reason to lease an ERP system." (owner on Practical Machinist, 2023).

The research supports a narrower claim than the idea that software simply pays. Studies of large US firms find computer investment paid off at up to 5 times its first-year effect over 5 to 7 years, once firms reorganized around it (Brynjolfsson and Hitt), and the gains have gone mostly to larger firms (Lashkari, Bauer and Boussard). No study compares owned and rented systems at manufacturers of 20 to 200 people, so this post argues from contracts, accounting and arithmetic, not from a productivity promise.

Renting moves the capital onto the vendor's books

A rented system is still capital; it sits on the vendor's books. National accounts guidance, as summarized in a UN expert group paper, treats a cloud subscription as a service the user buys, with the asset recorded by the provider (UN Advisory Expert Group). You buy the machine's output by the month, at a price the vendor sets.

Economics predicts what that price does. In Shapiro and Varian's lock-in framework, a supplier's profit from a locked-in customer equals the customer's cost of switching, and lock-in built from accumulated data strengthens over time (course notes summarizing Information Rules). A machine gets cheaper to walk away from as it ages; an ERP holding years of your jobs, routings and costs gets harder to leave. Procurement-vendor data points the same way: Vertice, which does not explain its method, measured SaaS price inflation at 16.4% in June 2026, its highest reading (Vertice).

The contracts show the mechanism. Oracle's NetSuite agreement says "Pricing for subsequent renewal Estimate/Order Forms shall be set at then current Oracle pricing, unless otherwise agreed to by the parties." (Oracle). A buyer-side advisor puts the default uplift near 10% where no cap was signed (Redress Compliance); a cap signed up front avoids the worst of it (Vendr, procurement vendor). Microsoft raised Business Central Premium 10% at renewals from November 2025 (Microsoft) and ends Dynamics GP's tax updates and support on December 31, 2029 (Microsoft Learn): retirement on the vendor's schedule. The detail is in Why NetSuite Is Eating at Your Margins and Why Microsoft Dynamics Is Eating at Your Margins.

Owning a license is not owning the code either. Perpetual ERP licensees still pay about 20% to 22% of the license a year in maintenance (BE-terna, Microsoft reseller; Redress Compliance, advisor) and still face sunsets like GP's. The line that matters runs between owning the code and the data and licensing someone else's.

How the 2 show up in your numbers

Owning and renting land in different places on your financial statements, which is where a buyer looks. Under GAAP's internal-use software rules, ASC 350-40, a company capitalizes the cost of developing a build and typically amortizes it "straight-line over three to five years" (Cohen & Co, accounting firm), below EBITDA. A subscription is a service contract unless you can take possession of the software and run it elsewhere (ASC 350-40-15-4A, per Deloitte), so its fees reduce EBITDA dollar for dollar. Even a capitalized implementation is amortized in the same line, with "no positive impact (i.e., not an addback) to key financial reporting metrics such as EBITDA." (PwC).

FASB's ASU 2025-06 changes when capitalization starts and is "effective for all entities for annual periods beginning after December 15, 2027" (Deloitte's summary of the FASB update), so a calendar-year private manufacturer applies it in 2028, or earlier by choice. Many manufacturers this size keep tax-basis statements and simply expense a build, so ask your CPA whether yours counts as capitalized.

Renting a subscriptionOwning code you hold
GAAP treatmentService contractInternal-use software under ASC 350-40
Effect on EBITDAFee and implementation both reduce itAmortization sits below it; hosting and support reduce it
Federal tax in 2026Fees deducted as paidDomestic development generally deducted in the year paid
Balance sheetNothing beyond prepaids and capitalized implementationAn intangible asset at amortized cost
At saleMoves only as the contract's assignment terms allowMoves with the business

Buyers price on adjusted EBITDA. GF Data recorded lower middle-market manufacturing deals at 6.6x EBITDA in 2025, 7.2x in the first quarter of 2026 and 5.9x for deals of $10 million to $25 million (GF Data via Iconic, M&A advisor; Mercer Capital). At those multiples, every recurring dollar of software cost takes $5.90 to $7.20 off the sale price.

That argument has a limit. Part of owning's EBITDA gain is only where the cost sits, and diligence teams normalize aggressive capitalization (CapEQ, UK-focused transaction advisor); in 1 case, capitalized development proved to be recurring maintenance and the price was renegotiated (Withum). We found no source that quantifies a premium for proprietary systems at small manufacturers. A buyer credits a lower recurring cost, if the upkeep really is lower than the rent and documented.

Tax: what changed in 2025, and what did not

In July 2025, P.L. 119-21 added Section 174A, which allows a deduction for "any domestic research or experimental expenditures" and says "any amount paid or incurred in connection with the development of any software shall be treated as" one (26 U.S.C. 174A). It covers tax years beginning after December 31, 2024, and a business may elect instead to amortize over 60 months or more. From 2022 to 2024, the same costs had to be amortized over 5 years (EY), a penalty on building that is now gone. When an outside firm writes the code, who takes the deduction turns on who bears the financial risk and holds the rights under IRS Notice 2023-63, and accounting firms disagree on edge cases (BDO; RSM).

Bought software follows other rules. Section 179 covers off-the-shelf software only (26 U.S.C. 179), with a 2026 limit of $2,560,000 (Journal of Accountancy), and 100% bonus depreciation was restored permanently for property acquired after January 19, 2025 (Wiss, accounting firm). Subscription fees are deducted as paid, since subscriptions "are usually treated as services, not purchased software" (Section179.org, equipment-finance information site).

The tax difference is mostly timing. Both paths deduct the same dollars; owning puts them in the year you pay for the build. For S corporations and partnerships, what that is worth depends on the owners' rates and on your state's rules. This is not tax advice. Talk to your CPA.

Where the machine analogy breaks

The analogy holds on control: nobody can reprice, restrict or switch off a machine you own, or code you own. It breaks in 4 places.

TestMachineSoftware
Useful life (BEA)24 years for metalworking machinery in fabricated metal3 years prepackaged, 5 years custom
Upkeep a year2% to 3% of replacement value as a target, 3% to 5% average (ReliaMag, vendor guide)15% to 25% of the build cost (CodeStringers, software vendor)
ResaleA used-equipment market; lenders take it as collateralLittle value outside the firm (Richmond Fed review of Capitalism Without Capital)
Proof of ownershipPaying for itA signed IP assignment (Mondaq, law firm article)

Software is short-lived capital, and most of its upkeep is change rather than repair (UCI lecture notes): a machine you keep re-tooling. Both upkeep figures are rules of thumb, and a maintenance consultancy disputes the machine one (IDCON), but the gap is the point. One difference cuts the other way: a subscription bundles hosting, security patches and upgrades, so a fair comparison adds those costs to the owned side.

Finance Accounting, invoicing, payroll. Usually the part that works.
Planning ERP and MES: orders, routings, inventory, schedule.
The handoff layer Spreadsheets, paper travelers, email threads, whiteboards. Where the floor and the system actually meet.
The floor Machines, operators, inspection, shipping.
Figure. Most replacements swap the planning layer and leave the handoff layer untouched. The handoff layer is where the data is lost, and it is the layer a new system inherits unchanged.

A worked example: $100,000 against the rent it replaces

Take a 100-person manufacturer with GAAP books paying $60,000 a year for an ERP-class subscription, inside vendor and consultant ranges of $54,000 to $62,000 (VendorBenchmark citing a Cetec example; Ultra Consultants). The alternative is a $100,000 build done in the US: $90,000 capitalized over 5 years, $10,000 expensed, and all of it deducted in year 1 under Section 174A at a blended 25% tax rate. Upkeep and hosting are set at $24,000 a year. That is an assumption. Replace it with your own number, because it decides the answer. Rent is held flat with no implementation fee, which favors renting.

YearRent, cashOwn, cashOwning's EBITDA advantageOwning's after-tax cash advantageCumulative
1$60,000$124,000$26,000($48,000)($48,000)
2$60,000$24,000$36,000$27,000($21,000)
3$60,000$24,000$36,000$27,000$6,000
4$60,000$24,000$36,000$27,000$33,000
5$60,000$24,000$36,000$27,000$60,000
Total$300,000$220,000$170,000$60,000

Owning costs $48,000 more after tax in year 1, breaks even around month 33, and is $60,000 ahead after 5 years, with the system still running and the code still the shop's. The $36,000 of steady-state EBITDA is worth $212,400 to $259,200 at 5.9x to 7.2x, or about $105,600 at 6.6x if a buyer deducts a $20,000-a-year reserve for a rebuild every 5 years. The sensitivities decide the argument:

  • Break-even near $44,000. The build plus 5 years of upkeep is $220,000, so owning wins only if it removes more than about $44,000 a year of rent. At $30,000, renting wins by $52,500 after tax.
  • Upkeep. At $40,000 a year, the 2 paths tie.
  • Abandonment. Replace the system in year 2 and $72,000 is written off, where a subscription could have been dropped at renewal.
  • Escalator. At 5% a year on the rent, owning's lead grows to about $83,600.
  • Tax-basis books. Expense the build and year-1 EBITDA under owning carries $124,000 of cost against $60,000.

Against the 2 big products, the line sorts cleanly. Our model prices NetSuite from third-party estimates, since Oracle publishes no price list; on it, a 50-person shop's NetSuite run cost after year 1 is $103,000 to $134,000 a year, far above the line. A lean 50-person Business Central deployment costs $221,598 over 5 years, against $254,000 to $278,000 for an owned system on the same upkeep assumption plus packaged accounting (QuickBooks costs from Brady Martz, accounting firm), so renting that one wins. The NetSuite and Dynamics posts show the models.

When renting is the right call

Much of a manufacturer's software is the same at every company. The general ledger, payroll and tax filing change with outside rules, and a vendor that updates them once for thousands of customers does it cheaper than any 1 shop. Microsoft moved GP's end of support to December 31, 2029 precisely so customers could finish a year of payroll and tax filings (Microsoft). Renting also buys what equipment lessees lease for: 55% of them cite "protection from equipment obsolescence" (Equipment Leasing and Finance Foundation). Rent when:

  • It is the ledger, payroll, tax filing, email or the office suite.
  • The rent an owned system would remove is under about $44,000 a year, as with a lean Business Central setup.
  • Cash is tight. In the example, the build puts you $48,000 behind after tax in year 1.
  • You expect to sell within 2 to 3 years to a buyer with its own platform. The example breaks even around month 33, and some private equity buyers replace any custom system.
  • Your bench is thin. If only 1 developer could maintain the code, rent until that changes.

The bench binds hardest. A software developer's median US pay was $135,980 in May 2025 (BLS), so owning works only if an outside firm builds and maintains the system for a fraction of a hire, and the shop holds the code so that firm can be replaced. Owners name the risk themselves: "If you get hit by a truck ... then the ERP stops working" (Practical Machinist).

AI moved the build line less than owners now hear. Coding tools speed up well-defined tasks (Peng et al.), but a trial of experienced developers in mature codebases found they took 19% longer, a result its authors now mark out of date (METR). AI lowers the cost of a first version, not the cost of owning one. The famous ownership stories, such as SpaceX's in-house ERP, come from large firms with dozens of engineers; we found no documented case of a 20 to 200 person US manufacturer that built its core quote-to-invoice system and published measured results.

So rent what is the same at every company, and own what decides how your shop wins work: quoting, routing, scheduling, job costing and traceability.

Is your system production equipment?

Answer with the invoices and the contract in front of you.

  1. Does it run the floor? If quotes, schedules or shipments stop when it is down, yes.
  2. What does it cost per year, all in? Subscription, add-ons, support and admin time, from the invoices.
  3. What did it cost 3 years ago? The difference is your escalator.
  4. Who can change it, and how fast? A ticket and someone else's quote means you rent the right to change your own process.
  5. What happens at renewal? Find the notice window, the pricing clause and any cap.
  6. Can you export everything? Including the reports, workflows and logic, not only the records.
  7. Who owns the code if you paid for it? Look for a signed IP assignment.
  8. Who could maintain it if your developer or reseller left? If nobody, rent, or fix the bench first.

If it runs the floor, costs more than your own break-even, and the vendor sets the price, you are renting production equipment.

Questions we get

Does owning the system raise my EBITDA?

Not by itself. Hosting and support still reduce EBITDA, and a quality-of-earnings review normalizes aggressive capitalization (CapEQ). Owning lowers the recurring cost a buyer multiplies, if the upkeep is genuinely lower than the rent and documented.

Can I deduct a custom build in the year I pay for it?

Generally yes for domestic development under Section 174A, or over 60 months or more by election (26 U.S.C. 174A). Section 179 covers off-the-shelf software only. If you hoped to claim 2022 to 2024 build costs, the small-business amended-return window closed July 6, 2026 (Cherry Bekaert). Ask your CPA what remains.

Does a custom system qualify for the R&D credit?

Possibly, and the facts decide. Administrative software, such as financial management and HR, must pass a high threshold of innovation test; production-process software is exempt from that test but must still meet the 4-part test (The Tax Adviser). Scheduling, routing and quality software are stronger candidates than quoting and invoicing. If an outside firm builds it, you may generally count 65% of qualifying payments when the agreement predates the work, you bear the cost even if the research fails, and you hold rights to the results (CPA Practice Advisor). Bring the contract to your CPA.

If I paid a developer to build it, do I own the code?

Only if a signed writing says so. Without one, a contractor keeps the copyright in code it writes, and a work-for-hire clause alone may not transfer software (Mondaq). Get a signed assignment of the code and its copyright, and keep a current copy of the code and the data. Those rights also bear on who takes the deduction and the credit.

What happens to the system when I sell the business?

Owned code moves with the business without anyone's consent. A subscription in an asset deal moves by assignment, and the vendor's consent right becomes bargaining power at closing (C. Wilson Law). An asset buyer amortizes acquired custom software over 15 years under Section 197 (CBIZ). None of that raises the price, which is set on earnings, and some buyers replace custom systems with their own.

Is a software subscription treated like an equipment lease?

No. Under ASC 842, an operating lease puts a right-of-use asset and a liability on the balance sheet (Moss Adams). A subscription is a service contract: off the balance sheet, expensed as you go, and nothing in hand when it ends.

What's next

Pull 12 months of software invoices and list every subscription next to what it runs, in 2 columns: what is the same at every company (ledger, payroll, email) and what runs your floor (quoting, routing, scheduling, job costing, shipping). Total the floor column, project it 5 years at your contracts' escalator, and set it against a build plus your own upkeep number. How much does a custom ERP cost? walks through that arithmetic, and manufacturing data sovereignty tests whether your data is really yours.

If the floor column clears the line, write to Kol with the list. KoldOps builds a system the shop owns, live in under 6 months for under $100,000, and the code and the data stay with the shop. GatorStep, a marine manufacturer, moved off Microsoft and Odoo onto one system in 2.5 months, has been live since August 2026, and holds its development environment. If it does not, keep renting, and take the list to your next renewal.