The Hidden Tax Penalty of Offshore Dev — and How AI Changes the Math

For years, the playbook was simple: hire a development team in India, Eastern Europe, or Southeast Asia, build your SaaS product at a fraction of US labor costs, and deduct the R&D expense immediately. It was efficient. It was common. And as of 2022, it carries a tax penalty that most founders still don't fully understand.

The culprit is Section 174 of the Internal Revenue Code, rewritten by the Tax Cuts and Jobs Act (TCJA) of 2017 with changes that took effect for tax years beginning after December 31, 2021. The change was technical. The impact is enormous — especially for early-stage SaaS companies that depend on offshore engineering.

What Changed with Section 174

Before 2022, companies could immediately expense their research and experimental (R&E) expenditures in the year they were incurred. A dollar spent on software development was a dollar deducted from taxable income that same year.

The TCJA changed this. Starting in 2022, all Section 174 costs must be capitalized and amortized — spread out over multiple years rather than deducted immediately:

Read that again. If you spend $1 million on an offshore development team, you can only deduct approximately $33,000 in the first year. The same $1 million spent on a domestic team yields a $100,000 first-year deduction — three times more.

The Cash Flow Trap

This isn't just an accounting nuance. For early-stage SaaS companies, the impact is felt directly in cash flow and taxable income:

This creates a paradox: the company has no cash (it was spent on development), but the IRS treats it as if the company has income. Early-stage SaaS companies operating at thin margins or burning through runway can face unexpected tax liabilities that threaten their survival.

The problem compounds year over year. Each year's offshore R&D spend creates a new 15-year amortization schedule. By year three, the company is juggling multiple overlapping amortization timelines, each contributing only a fraction of the actual expense to the current year's deductions.

Why Offshore Development Gets Hit Hardest

The distinction between 5-year and 15-year amortization is based on where the research is performed, not where the company is incorporated. This means:

• A US company with developers in Bangalore — those salaries and contractor costs are foreign R&D, amortized over 15 years.
• A US company with developers in Austin — those same costs are domestic R&D, amortized over 5 years.
• Mixed teams — costs must be allocated between domestic and foreign based on where the work is performed. This adds compliance complexity and often results in a significant portion falling into the 15-year bucket.

For a typical early-stage SaaS company that built its product on the back of a 10–20 person offshore team, the majority of R&D costs now face the worst possible tax treatment.

Side-by-Side: Offshore vs. Domestic R&D Tax Impact

Consider two identical SaaS companies, each spending $500,000 annually on software development. One uses an offshore team; the other uses a domestic team. Here's how the tax deductions compare over 5 years:

By year 5, the domestic company has deducted $500,000 more in R&D expenses than the offshore company — on the same level of annual spend. At a 21% corporate tax rate, that's $105,000 in additional tax paid by the offshore-dependent company over just 5 years.

How AI-Powered Development Changes Everything

This is where the math gets interesting. The rise of AI-assisted software development — tools like GitHub Copilot, Claude, Cursor, and other AI coding assistants — is fundamentally reshaping what a development team can look like.

The key insight: AI doesn't just make developers faster. It makes smaller teams viable.

The New Playbook: AI-First, Domestic-First

For early-stage SaaS companies, the optimal development strategy has shifted. The old playbook of large offshore teams is no longer the default winner when you factor in the full economic picture:

The cost difference between the two approaches is often negligible — sometimes the AI-augmented domestic team is actually cheaper in total loaded cost. But the tax treatment difference is dramatic: 3x faster deductions, significantly better cash flow, and none of the compliance complexity of allocating costs between domestic and foreign buckets.

What This Means for Indian SaaS Founders

This is where the conversation gets nuanced — and where Soft Equities sees opportunity that others miss.

The Section 174 penalty applies to US companies offshoring development. It does not apply the same way to Indian companies building products in India for the Indian or global market. The distinction matters enormously:

• An Indian SaaS company incorporated in India is subject to Indian tax law, not Section 174. India's tax treatment of R&D expenses remains favorable, with options for immediate deduction and additional weighted deductions under certain schemes.
• An Indian founder building a US-incorporated company with a development team in India is subject to Section 174's 15-year foreign amortization. This is a critical structural decision that affects the company's tax position from day one.
• AI changes the calculus for both models. Indian founders leveraging AI can build with smaller teams, reducing total R&D spend regardless of jurisdiction. And if they choose a US entity structure, AI makes it feasible to have a small US-based development presence that keeps costs in the favorable 5-year bucket.

R&D Tax Credit: A Partial Offset

The R&D tax credit (Section 41) still exists and can partially offset the pain of Section 174 amortization. Key points:

• The credit applies to qualified research expenses (QREs) — which can include wages, supplies, and contract research related to software development.
• Startups can apply the credit against payroll taxes — up to $500,000 per year for companies with less than $5 million in gross receipts and fewer than 5 years of revenue. This is valuable for pre-revenue or early-revenue SaaS companies.
• The credit does not eliminate the amortization requirement — you still must capitalize and amortize the costs. The credit is a separate calculation that reduces tax owed, but the deduction timing disadvantage of offshore R&D remains.
• Foreign-performed research has limitations — contract research performed outside the US generally receives a reduced credit rate (65% of the otherwise allowable amount for funded research). Another reason domestic R&D gets better treatment.

Will Congress Fix This?

There has been bipartisan support for restoring immediate expensing of R&D costs. The American Innovation and Jobs Act and similar bills have been introduced in multiple sessions of Congress. However, as of early 2026:

• No retroactive fix has been enacted. Multiple bills have stalled due to broader legislative gridlock and disagreements over offsetting revenue.
• The domestic/foreign distinction may persist even if immediate expensing is restored. Some proposals would restore expensing only for domestic R&D, leaving the 15-year foreign amortization in place as a policy tool to incentivize onshoring.
• Companies should not plan on a legislative fix. The prudent approach is to structure around the current law and treat any future change as upside.

This legislative uncertainty makes the AI-powered domestic development model even more attractive: it works under current law and any likely future scenarios.

Practical Steps for SaaS Founders

If you're building a SaaS company and evaluating your development strategy in light of Section 174, here's what we recommend discussing with your tax advisor:

• Audit your R&D cost allocation. Understand exactly how much of your development spend falls into the domestic vs. foreign bucket. Many founders are surprised by the split when they look closely.
• Model the tax impact. Run a 5-year projection comparing your current structure against an AI-augmented domestic team. Include the amortization schedules, R&D credits, and cash flow impact.
• Evaluate AI tooling seriously. This is no longer a productivity nice-to-have. AI coding tools directly affect your tax position by changing the size and location of your development team.
• Consider entity structure carefully. For international founders, the choice of US vs. foreign incorporation has significant Section 174 implications. Get advice before you incorporate, not after.
• Claim the R&D credit. Many early-stage SaaS companies leave the payroll tax offset on the table. It won't fix the amortization problem, but it helps.
• Document everything. The IRS requires clear documentation of where R&D activities are performed. Sloppy recordkeeping can result in the IRS reclassifying domestic costs as foreign — pushing them into the 15-year bucket.

How Soft Equities Thinks About This

As a micro PE firm that acquires and invests in early-stage SaaS companies, Section 174 is a critical factor in how we evaluate deals:

• We assess every target company's R&D cost structure as part of due diligence — not just the total spend, but where the work is performed and how it's classified.
• Post-acquisition, we help portfolio companies restructure development teams around AI-first workflows that reduce headcount, shift costs to favorable amortization buckets, and improve cash flow.
• Our CTO-for-equity service is specifically designed to help early-stage companies make this transition — building lean, AI-augmented engineering organizations led by executives who understand both the technical and tax implications.
• For Indian SaaS founders, we help navigate the entity structure decision and build development strategies that optimize for both US and Indian tax treatment.