You're paying for Claude, GitHub Copilot, Cursor, and maybe a ChatGPT Plus subscription on top of that. Individually, each one looks like a rounding error on your monthly statement. Add them up across a year, though, and a small dev shop or solo founder can easily be spending $1,500-$6,000 annually on AI coding tools alone. So when tax season rolls around, a fair question comes up: are these subscriptions just another software expense, or do they trigger the kind of multi-year amortization rules that make software developers groan?
The good news is that for the vast majority of developers, the answer is simple. The confusing part is knowing when it stops being simple — and that's exactly where AI coding tools have started tripping people up.
The Short Answer: Most AI Coding Subscriptions Are Fully Deductible Now
If you're paying a monthly or annual fee for Claude, GitHub Copilot, Cursor, ChatGPT Plus/Team, or a similar coding assistant, and you're using it the way most developers do — to write code faster, debug, or generate boilerplate for client work or your own product — that cost is generally deductible in full, in the year you pay it. It falls under Internal Revenue Code Section 162, the "ordinary and necessary business expense" rule that covers everything from your laptop to your coworking desk.
There's no special AI carve-out that makes these subscriptions harder to deduct than, say, a project management tool or a code editor license. The IRS doesn't care that the tool has "AI" in its marketing copy. It cares about what the expense was for and whether it's ordinary and necessary for the type of work you do.
Where it gets more complicated is a different part of the tax code entirely: Section 174, which governs research and experimental (R&E) expenditures. And this is the part that catches developers off guard, because Section 174 isn't about the tool — it's about what you're doing with it.
Section 162 vs. Section 174: Same Tool, Different Tax Treatment
Here's the distinction that actually matters, and it has nothing to do with which AI product you're using:
Section 162 (immediate deduction) covers routine, day-to-day use of software — running your existing product, fixing bugs, doing client billing work, writing marketing copy, or using Copilot to speed through a normal feature ticket. If the work is largely routine and doesn't involve resolving genuine technical uncertainty, it's an ordinary operating expense.
Section 174 (research and experimental expenditures) covers costs tied to developing something new or resolving real technical uncertainty — building a new product from scratch, architecting a novel system, fine-tuning a model, or running extended experiments to figure out whether an approach is even technically feasible. If a contractor or engineer is doing genuine R&D-style development work, the labor and associated costs tied to that work can fall under Section 174, not the subscription fee itself.
The key thing to understand: the subscription itself almost never changes category. Your Cursor or Copilot license is a tool, like a hammer. What changes category is the work — specifically, wages, contractor payments, and directly attributable costs tied to genuine research and development activity. A no-code automation subscription (think Zapier or Make) is squarely Section 162 even if you use it while building something experimental, because the subscription itself isn't "computer use" research spending — it's a SaaS tool.
For most solo developers and small dev shops, this means: your AI coding subscriptions are deductible expenses, full stop. Section 174 becomes relevant mainly if you're paying engineers or contractors to do substantial new product development — and even then, the rules recently got a lot friendlier.
The 2025 Rule Change That Actually Helps You
If you've heard horror stories about software companies being forced to amortize development costs over five years starting in 2022, that was real — and it hit small software businesses hard. Congress reversed course with the One Big Beautiful Bill Act (OBBBA): for tax years beginning after December 31, 2024, domestic research and experimental expenses are immediately deductible again, not spread out over five years. Foreign R&E costs — say, a contractor based overseas doing your fine-tuning work — still have to be amortized, currently over 15 years.
That single geography-based distinction is worth remembering if you work with international contractors: identical development work is either fully deductible this year or stretched across 15 years, purely based on where the person doing it is located.
A Practical Breakdown for Small Dev Shops
Here's how the common categories typically shake out:
| What you're paying for | Typical treatment | Why |
|---|---|---|
| Claude Pro/Team, ChatGPT Plus/Team | Section 162 — deduct in full | Ordinary business software subscription |
| GitHub Copilot, Cursor | Section 162 — deduct in full | Developer tooling subscription, not R&D spend itself |
| Cloud hosting for a live, deployed app | Section 162 — deduct in full | Production use, not experimentation |
| Cloud compute used to train or fine-tune a proprietary model | Often Section 174 | Genuine technical experimentation |
| Contractor wages building a brand-new product from scratch | Often Section 174 | Labor tied to resolving real technical uncertainty |
| Zapier, Make, Airtable, and similar no-code platforms | Section 162 — deduct in full | Subscription service, not a qualifying R&D expenditure |
| A one-off purchased software license (not a subscription) | May qualify for Section 179 expensing | Purchased property, not recurring service |
Note the pattern: almost everything a solo developer or small team pays for monthly lands in the simple, fully-deductible bucket. Section 174 only becomes a real consideration once you're paying real money for people — employees or contractors — to build something genuinely new, or running meaningful compute spend specifically for R&D-style experimentation rather than running your live product.
When Mixed Use Actually Matters
If you're a small agency or dev shop that both maintains client products (routine, Section 162) and builds custom AI features or new systems from scratch (potentially Section 174), the IRS generally expects you to make a reasonable allocation rather than lump everything into one "Software" line. A defensible approach:
- Track the same tool (say, your cloud compute bill) with separate cost tags for "production/maintenance" versus "development/experimentation."
- Keep contractor invoices or time logs that describe what was actually built, so you can substantiate the split if asked.
- Don't try to force subscription-based tools like Copilot or Zapier into Section 174 — they're categorically service subscriptions, not qualifying research expenditures, even if you happen to use them while doing R&D work.
If your entire business is client services with no in-house product development, you likely don't need to think about Section 174 at all — everything is ordinary and necessary Section 162 expense.
Keep the Paper Trail Simple but Real
Whatever category your AI tool spending falls into, the IRS wants to see that the expense was ordinary, necessary, and business-related — not that you've built an elaborate tax shelter. A few habits go a long way:
- Keep invoices and receipts for every subscription, even the $20/month ones. They add up, and auditors have flagged missing documentation on small recurring charges before.
- Note the business purpose if a tool has any personal use crossover — if you use ChatGPT Plus for both client code and personal projects, only the business-use portion is deductible.
- Separate development spend from production spend at the time you incur it, not months later when you're reconstructing memory at tax time. Provider dashboards (OpenAI usage pages, AWS cost tags, Anthropic console) often purge granular historical data, so tag as you go.
This is really just an extension of good bookkeeping discipline, not a new burden. If you're already tracking business expenses in a structured way — separate accounts or categories for hosting, tooling, contractor payments — adding a couple of new lines for "AI subscriptions" and, if relevant, "R&D compute" is a small lift with real payoff at filing time.
Common Mistakes to Avoid
- Lumping everything into one "Software" or "Tools" expense category. It's nearly impossible to reconstruct an accurate Section 162/174 split at year-end if every subscription and cloud bill lives in one undifferentiated bucket.
- Assuming a tool's category is fixed by its name. "AI" in the product name doesn't determine tax treatment — what you're doing with it does.
- Treating subscription platforms as R&D expenditures. No-code and automation subscriptions don't qualify as computer-use research costs for R&D credit purposes, regardless of how experimental the project is.
- Missing the domestic-vs-foreign distinction on contractor work. Paying an overseas contractor for genuine development work can mean 15-year amortization instead of an immediate deduction — worth knowing before you hire, not after.
Keep Your Finances Organized from Day One
Sorting out which AI subscriptions are simple write-offs and which development costs need special tax treatment is a lot easier when your books are clean and categorized as you go, rather than reconstructed from memory in April. Beancount.io offers plain-text accounting that's transparent, version-controlled, and easy to tag by project or expense category — so splitting "production tooling" from "R&D compute" is a matter of a clear chart of accounts, not a scramble through twelve months of credit card statements. Get started for free and see why developers are switching to plain-text accounting for exactly this kind of clarity.