Software Developer Freelance Tax in 2026: The SE Tax, S-Corp, §174 R&D, QBI, and Home Office Playbook
1099-NEC vs W-2 — the worker classification fight
The first question for any freelance software developer: are you actually a freelancer, or has your client classified you as one to save payroll tax? The distinction matters because if the IRS reclassifies you as an employee, your client owes back FICA, Medicare, FUTA, and withholding, plus penalties. You potentially get an SS-8 ruling and a wave of revenue back into employee territory.
The legal standard. IRC §3121 defines employment for FICA purposes. Treas. Reg. §31.3121(d)-1 and a long line of revenue rulings (most Rev. Rul. 87-41) lay out the 20-factor common-law test, now consolidated into three groups: behavioral control, financial control, and the relationship of the parties.
Behavioral control. Does the client direct how you do the work? A true freelance developer chooses their own tech stack, sets their own hours, and decides the implementation approach. A worker told to attend the 9am standup, use the company’s GitHub Enterprise, and follow company coding standards starts looking like an employee.
Financial control. Do you have unreimbursed business expenses? Multiple clients? An opportunity for profit or loss? A freelancer with a registered business, their own equipment, multiple concurrent clients, and the ability to take on more work to earn more — that’s a freelancer. A developer paid hourly with no other clients, no business expenses, and an annual cap on hours — that’s an employee in disguise.
Relationship of the parties. Written contracts. Permanence of relationship. Whether the work is a key business function. A ‘freelance’ developer working 40 hours/week for 18 months on the client’s core product line is hard to defend as a contractor.
Why clients prefer 1099. Saves the client 7.65% employer FICA, FUTA (small), state unemployment, workers’ comp, benefits. The freelancer absorbs all of it through self-employment tax. For the client, $100K of W-2 wages costs ~$108K all-in. $100K of 1099 costs $100K flat.
Why some freelancers prefer W-2. Employer-side payroll tax not on you. Health insurance through the employer. 401(k) match. Workers’ comp coverage. Unemployment eligibility.
Reclassification consequences. The IRS Form SS-8 process lets workers request a classification ruling. If you get reclassified, the client gets a bill for back taxes. The client retaliates by not renewing the contract. You’re out of work. So most freelancers don’t pursue SS-8 unless the relationship is already ending.
Section 530 relief. Section 530 of the Revenue Act of 1978 provides safe harbor for businesses that treat workers as contractors based on reasonable basis and consistent treatment. Many businesses defend their 1099 classification under §530. It doesn’t help the worker, only the business.
Practical advice for freelance developers. Maintain real freelance characteristics — multiple clients ideally, your own equipment, set your own hours, work product oriented (the work, not time logs). Bill via invoice. Have a written contract that recites the freelance characteristics. Form an LLC or S-corp to add a layer of business identity.
Hybrid arrangements. Some freelance developers operate through staffing agencies that handle the 1099/W-2 distinction. The agency pays the developer as W-2 employee and bills the end client. The developer gets W-2 wages with FICA/Medicare withheld but loses business expense deductibility. Pros: simpler tax situation, employer-paid health benefits, 401(k) match in some cases. Cons: smaller take-home pay due to FICA, no business expense deductions, less control over engagement terms.
Hybrid arrangements have grown post-COVID as some companies refused to engage 1099 contractors. The cost: a 1099 contractor earning $150K typically nets more than a W-2 employee earning $150K after considering employer-side payroll tax, benefits cost, and business expense deductions. But the W-2 path has lower compliance burden and predictable cash flow.
Self-employment tax — the 15.3% that hurts
Self-employment tax under IRC §1401 is 15.3% on net SE earnings, with a wage-base cap on the Social Security portion. The Medicare portion has no cap. The 2026 figures (Rev. Proc. 2024-40 plus SSA announcements):
Social Security portion: 12.4% on net SE earnings up to $184,500 (2026 wage base). Maximum SS tax: $22,878.
Medicare portion: 2.9% on all net SE earnings, no cap.
Additional Medicare tax: 0.9% on net SE earnings + wages over $200,000 single / $250,000 MFJ. Reported on Form 8959.
Schedule SE Part I computation. Net earnings from SE = net Schedule C profit × 0.9235 (the 92.35% adjustment that compensates for the employer half being deductible on the corp side).
Example. Solo developer with $180,000 Schedule C net profit. Net SE earnings: $180,000 × 0.9235 = $166,230. Below the $176,100 SS wage base, so 12.4% on full $166,230 = $20,613 SS portion. Medicare: 2.9% on $166,230 = $4,821. Total SE tax: $25,434. Plus possible additional Medicare 0.9% if combined with spouse income pushes over threshold.
Half-SE deduction. IRC §164(f) allows deduction of half the SE tax as an adjustment to gross income on Schedule 1 line 15. Effectively, the employer-equivalent half (which a W-2 employer would pay) is deductible. Halves the federal income tax effect of SE tax.
$25,434 SE tax × 50% = $12,717 deductible. At a 24% bracket, federal tax savings: $3,052. Net SE tax after the offset: $25,434 – $3,052 = $22,382 effective.
Quarterly estimated tax. Self-employed developers don’t have withholding. The IRS requires quarterly payments to avoid §6654 underpayment penalty. 2026 due dates: April 15, June 15, September 15, January 15 (2027). Compute via Form 1040-ES.
Safe harbor. §6654(d) defines safe harbor as the lesser of (a) 90% of current-year tax or (b) 100% of prior-year tax (110% if prior-year AGI was over $150,000). Most freelance developers pay against the 100%/110% prior-year safe harbor for predictability.
Underpayment penalty rate. §6621 underpayment rate is 8% annual through 2026 (rising in recent years). Compounded daily. Form 2210 computes the penalty.
State analog. Most states have their own quarterly estimated payment regime for self-employed income. California, New York, Massachusetts, and others have aggressive estimated tax rules. Check state-specific safe harbors and due dates.
S-corp election — when freelance developers should consider it
The S-corp election for freelance developers is a math problem. Above a certain net profit level, the SE tax savings exceed the additional administrative costs.
Setup. Form an LLC (single-member or multi-member). File Form 2553 within 75 days of formation or beginning of tax year to elect S-corp tax treatment. The LLC continues to be the legal entity; the IRS treats it as an S-corp for tax purposes.
Once elected, the developer becomes a shareholder-employee. The S-corp pays W-2 wages to the developer + the IRS-required Social Security/Medicare on those wages. The remainder of S-corp profit flows through as a K-1 distribution, which is NOT subject to SE tax or FICA/Medicare.
Example. Solo developer, $180,000 net profit (before owner comp). Sole proprietor SE tax: $25,434 (from prior section).
S-corp election: $80,000 W-2 wages + $100,000 distribution. FICA/Medicare on wages: $80,000 × 15.3% = $12,240. Half is employee (paid through W-2 box 4 and 6), half is employer (paid by S-corp). Total payroll tax: $12,240.
Distribution piece: zero payroll tax. SE tax savings vs sole prop: $25,434 – $12,240 = $13,194 per year.
Subtract S-corp costs. Payroll service ($60/month = $720). Additional tax prep for Form 1120-S ($1,500-$2,500). State franchise tax (CA $800, others vary). Bookkeeping if you didn’t have it before. Total additional costs: $3,000-$5,000 per year.
Net S-corp annual benefit at $180K profit: approximately $9,000-$10,000.
Break-even. Below $80,000-$100,000 net profit, the administrative costs eat the SE tax savings. The break-even depends on the state (high franchise tax states push it higher) and the cost of the payroll/tax services.
Reasonable comp. IRC §3121 and the case law (Watson v. Commissioner, David E. Watson PC v. US — 8th Cir. 2012) require S-corp owner-employees to be paid market-rate compensation. For a solo software developer, RCReports or other reasonable-comp studies typically suggest $80K-$120K W-2 wages depending on experience, geography, and the corp’s revenue.
Setting wages too low. Common audit issue. IRS reclassifies distributions as wages, with retroactive employment tax + penalties. Document the reasonable comp determination with a written study.
Section 199A QBI interaction. S-corp wages help the QBI deduction calculation for high-income developers (above the SSTB threshold). For developers below the threshold, QBI is available without W-2 wage limitation. For developers above the threshold who are SSTBs, S-corp wages don’t help — the deduction phases out entirely.
Solo 401(k) capacity. Schedule C developer can contribute 20% of net SE income + $24,500 deferral = up to $70K total (2026). S-corp owner contributes 25% of W-2 wages + $24,500 deferral. At $80K wages, that’s $20K + $24,500 = $44,500. S-corp limits retirement plan capacity for owner-employees. Significant tradeoff.
Multi-shareholder S-corp considerations. Two developers forming an S-corp together: each gets W-2 wages proportional to services performed and ownership. Disproportionate compensation among shareholders triggers IRS scrutiny. K-1s issued to each shareholder. Distributions must follow ownership percentages.
S-corp owners are NOT eligible for unemployment insurance benefits in most states because they’re considered owners, not employees. So if a freelance developer S-corp’s work dries up, no UI claim. Sole props similarly excluded. W-2 employees of a third party have UI eligibility if laid off.
Section 199A QBI — SSTB analysis for software developers
The 20% qualified business income deduction under IRC §199A is one of the biggest benefits for self-employed developers. Up to 20% of net business income shaves off the top before federal income tax.
Income thresholds (2026, Rev. Proc. 2024-40). Below $241,950 single / $483,900 MFJ: full QBI deduction regardless of business type or W-2 wages. Above the threshold: SSTB rules kick in, and for non-SSTB businesses the W-2 wage and UBIA limitations apply.
SSTB definition. §199A(d)(2) lists ‘specified service trades or businesses’ where the QBI deduction phases out above the threshold and disappears entirely above $341,950 single / $683,900 MFJ. The SSTB list includes: health, law, accounting, actuarial science, performing arts, consulting, athletics, financial services, brokerage services, investment management, and any trade or business where the principal asset is the reputation or skill of one or more of its employees or owners.
Notice: ‘computer programming services’ is NOT specifically listed as an SSTB. The IRS’s intention in Treas. Reg. §1.199A-5(b)(2)(xiv) was to exclude software development from the SSTB list. Computer programming, software engineering, app development, and similar technical work are NOT SSTBs.
But: ‘consulting’ IS an SSTB. The Treasury Regulations define consulting broadly as ‘providing professional advice and counsel to clients to assist the client in achieving goals and solving problems.’ A freelance developer who frames the work as ‘consulting on architecture and providing recommendations’ could find themselves classified as an SSTB consultant. A developer who frames the work as ‘developing software’ is clearly non-SSTB.
The line. Building software for clients = non-SSTB (eligible for full QBI regardless of income). Advising clients on technology strategy without producing software = potentially SSTB consulting.
Mixed activities. Many freelance developers do both — they architect AND code. Treas. Reg. §1.199A-5(c) addresses mixed activities. If SSTB activities are less than 10% of gross receipts (or 5% if gross receipts exceed $25M), the entire business is treated as non-SSTB. So a developer who does 90%+ coding and 10% advisory is fully non-SSTB.
Practical positioning. Bill as ‘software development services’ on invoices. Document the work (code, software, libraries). Avoid pure ‘consulting’ contracts. Use a tax structure that separates pure-advisory work from development work if both are substantial.
QBI deduction calculation for non-SSTB developer above threshold. Limited to greater of: (a) 50% of W-2 wages paid by the QTB, or (b) 25% of W-2 wages + 2.5% of UBIA (unadjusted basis immediately after acquisition) of qualified property.
Solo developer above threshold with $300K QBI, no W-2 wages, $20K of laptops and equipment. 50% W-2 limit: $0. Alternative: 25% × $0 + 2.5% × $20K = $500. QBI deduction: lesser of $300K × 20% = $60K, or $500 = $500. Without W-2 wages or significant UBIA, the QBI deduction is essentially zero above the threshold.
Same developer S-corp electing with $80K W-2 wages: 50% × $80K = $40K. QBI = 20% × $220K (QBI is now $300K minus $80K wages) = $44K. Limited to $40K. Federal tax savings at 35% bracket: $14,000. S-corp election captures QBI deduction that would have been lost.
Below threshold. No W-2 limitation. Solo developer with $200K QBI below threshold gets full 20% × $200K = $40K deduction. No S-corp needed for QBI purposes at this income level.
Section 174 — mandatory capitalization of software development costs
Section 174 is the biggest unpleasant surprise in the post-TCJA tax rules for software developers. IRC §174 as amended by TCJA §13206 effective for tax years beginning after December 31, 2021, requires all specified research or experimental expenditures to be capitalized and amortized — no current expensing allowed.
Domestic R&E: amortized over 5 years (60 months), starting with the midpoint of the year incurred. So a $100K of domestic R&E in 2026 deducts $10K in 2026, $20K each in 2027-2030, and $10K in 2031.
Foreign R&E: amortized over 15 years.
Software development is specifically included. Notice 2023-63 from the IRS confirms that software development costs are §174 expenditures. This includes activities to develop software for own use or for sale/license, as well as activities to develop or improve software for use in the taxpayer’s business.
Specifically excluded from §174 (per Notice 2023-63). Software training. Maintenance after software is ready for intended use. Data conversion. Marketing of completed software. Customer acceptance testing of completed software. Cost of acquiring purchased software for own use (separate §197 amortization rules apply).
Practical scope for freelance developers. If you’re a freelance developer paid on contract by a client to write code, the §174 rules apply to YOU on the cost of producing the deliverable. Your own labor (in self-developed software for own use) is a §174 cost — but if you’re paid by a client for the work, your client is the one capitalizing your invoiced amount; you’re recognizing the receipt as ordinary income.
If you’re developing your own SaaS or product. ALL costs incurred in developing the software — your own labor time, contractor payments, infrastructure costs, software licenses used in development — must be capitalized. This includes the value of your own time, which creates the bizarre situation of having to capitalize phantom income (you ‘paid yourself’ to write code, even though no cash changed hands).
Reasonable treatment for solo founders. The IRS hasn’t definitively addressed how to value owner-developer time for §174. Common approaches: (a) capitalize only direct out-of-pocket costs and ignore owner time, treating the owner as a passive equity contributor; (b) capitalize a reasonable owner compensation amount and reduce Schedule C net profit by the same amount; (c) ignore §174 if you have no W-2 wages and the activity isn’t a trade or business yet (pre-revenue startup).
When does the activity become a trade or business? Section 174 applies to a trade or business. A pre-revenue solo dev working on a startup might be pre-trade-or-business under §195 (start-up expense rules). Once the trade or business begins (you have customers, you’re billing), §174 applies prospectively.
R&D credit interaction. §41 R&D credit remains available even with §174 capitalization. The credit math is the same, but the capitalization reduces the deduction. Many developers don’t claim §41 because they didn’t realize they qualify.
Net effect on a $200K freelance developer in 2026. Suppose $50K of revenue is from new software product development for own SaaS, $150K is from contract work. The $50K of self-developed software costs are subject to §174 capitalization, amortized over 5 years. Year 1 deduction: $50K / 5 × ½ = $5K. The other $45K of deduction sits on the balance sheet to be deducted over years 2-6.
Cash tax impact. Marginal rate 32% × ($45K not currently deductible) = $14,400 of additional current-year tax. Significant for a solo developer building product on the side.
Section 41 R&D credit. If the activity qualifies as R&D, the credit offsets income tax (or payroll tax for qualified small businesses under §41(h)) by approximately 6-10% of qualified research expenditures. For $50K of qualified research, credit might be $3,000-$5,000. Net tax cost: $14,400 – $5,000 = $9,400 still in deferral.
Method changes. To start applying §174 properly (which is mandatory starting 2022), file Form 3115. Most freelance developers transitioning had this method change in 2022. Going forward, the rules are baked in.
R&D credit under Section 41 — overlooked by most freelance developers
The Research and Experimentation Credit under IRC §41 is a federal income tax credit equal to a portion of qualified research expenditures. Most freelance developers don’t claim it. They should.
Qualifying activities. §41(d) requires four tests. The activity must be (a) intended to discover information that is technological in nature, (b) intended to be useful in the development of a new or improved business component, (c) substantially all activities constitute elements of a process of experimentation, and (d) the process of experimentation relates to a new or improved function, performance, reliability, or quality of a business component.
Translation. Did you write new code that solved a hard problem where the solution wasn’t obvious from the start? You probably qualify. Routine debugging, configuration, or applying existing techniques to new problems? Doesn’t qualify.
Qualifying expenditures. Qualified research expenses (QREs) include: (a) wages paid to employees engaged in qualified research, (b) supplies used in qualified research, (c) 65% of contractor payments for qualified research, and (d) certain rental/lease payments for computers used in qualified research.
Solo developer wages = your S-corp W-2 wages allocated to R&D activities. Sole-proprietor wages aren’t counted (you can’t pay W-2 wages to yourself as a sole prop), which is why S-corp election can access R&D credit value for solo developers.
Two credit calculation methods. Regular credit method: 20% of QREs exceeding a base amount (often produces low credit for new businesses with no historical base). Alternative Simplified Credit (ASC): 14% of QREs exceeding 50% of average QREs for the three preceding years. Most solo developers elect ASC.
Example. Solo S-corp developer, $80K W-2 wages, 70% time spent on qualifying R&D activities. QRE wages: $80K × 70% = $56K. Plus $2K of supplies. Plus $5K × 65% of contractor payments = $3,250. Total QRE: $61,250.
ASC credit. Year 1 with no prior years: 6% of QREs (the reduced rate for first-time claimants) = $3,675. Year 2+: 14% of QREs in excess of 50% of three-year average. As QREs grow, credit grows proportionally.
Payroll tax offset for QSBs. §41(h) permits qualified small businesses to apply the R&D credit against payroll tax (FICA/Medicare/SUTA) instead of income tax. Qualified small business means gross receipts under $5M in the credit year AND no gross receipts in any year more than 5 years before the credit year (essentially: small startup, less than 5 years old).
For a solo S-corp developer in early years, the payroll tax offset under §41(h) means the R&D credit reduces actual payroll tax payable, which is real cash flow benefit even when the developer has no income tax liability (pre-revenue).
Election timing. The R&D credit must be claimed on Form 6765 attached to the timely filed (with extensions) tax return. Amended returns to claim missed R&D credits — possible but more administrative work.
Documentation. The audit-ready documentation is the hardest part. The IRS expects records describing the technical uncertainty being addressed, the alternatives evaluated, the experimentation process, and the technical conclusions. Most freelance developers do this informally (commit messages, design documents, slack conversations) — formalizing it into a credit study takes effort.
Service providers. Specialty R&D credit firms (Strike Tax, Source Advisors, Acena Consulting, Engineered Tax Services) charge contingency fees (10%-30% of credit obtained) for credit studies. For solo developers with $50K+ of qualified research, the contingency fee is justified by the work involved.
Home office deduction for the WFH developer
Solo developers who work from home almost universally qualify for the home office deduction under IRC §280A. The ‘principal place of business’ test in §280A(c)(1)(A) is easy to meet for a developer with no other office.
Two methods. Simplified ($5/sq ft up to 300 sq ft, max $1,500). Regular method (Form 8829, actual costs × business-use percentage).
Simplified math. 200 sq ft office × $5 = $1,000. Max $1,500.
Regular method math. 200 sq ft office in 1,500 sq ft apartment = 13.3% business use. Annual costs: rent $30,000, utilities $2,400, internet $1,200, renters insurance $300 = $33,900. Business portion: $4,509. Significantly more than simplified.
Renters vs owners. Renters can deduct a portion of rent (not available under simplified method). For a renter in a high-rent area (San Francisco, NYC, Boston, Seattle), the regular method blows away simplified.
Owners can deduct mortgage interest (subject to SALT cap), property tax, depreciation, insurance, repairs. The SALT cap is $10,000 for the personal portion; the business portion of property tax is deductible as a business expense, not subject to SALT cap.
Exclusivity test. The home office must be used exclusively for business. Dedicated home office. Walk-in closet converted to an office. Garage converted to a workshop/office. NOT a kitchen table that gets cleaned off.
Regular use test. Consistent business use. A developer working from the home office 30+ hours/week clearly meets this.
S-corp owner home office. The S-corp can’t deduct the home office because the corp doesn’t own the home. Two workarounds. (1) Accountable plan reimbursement: the S-corp reimburses the owner for actual home office costs based on a written accountable plan. Deductible to corp, tax-free to owner. (2) Lease agreement: the owner leases office space to the S-corp at market rates. Owner reports rental income; rental income offset by home expenses. Net result similar to deduction.
Cell phone allocation. Cell phone (since TCJA removed cell phones from listed property) is deductible based on reasonable business-use percentage. A solo developer with 90% business use of cell phone: 90% of cell phone costs deductible.
Internet. Same allocation as home office, OR a reasonable allocation if internet is used for purposes beyond just the home office activity. A developer with a 13.3% home office allocation can deduct 13.3% of internet bill. But if business use is higher than residential use (the developer spends 60% of internet time on business work), a higher allocation can be justified.
Coworking space. If you rent a coworking space (WeWork, Industrious, local space), the rent is fully deductible as an office expense on Schedule C. Many developers use a hybrid: home office for some work + coworking for client meetings or focus days. Both can be deducted.
Coffee shop work. Coffee shop bills aren’t deductible as office rent. Coffee while working is questionable — generally not deductible. Lunch at a coffee shop where business calls happen — 50% meal deduction may apply under §274. Practical advice: don’t bother deducting coffee shop bills.
Equipment, software, and §179 expensing
Freelance developers buy equipment. Laptops, monitors, ergonomic chairs, mechanical keyboards, microphones for calls, ring lights, standing desks, server hardware, GPUs for ML work. All deductible.
Section 179 first. §179 2026 limit: $1,290,000 of §179 expense allowed, phase-out beginning at $3,210,000 of total §179-eligible purchases. For a solo developer buying $10K of equipment in a year, well within §179 limits. Full deduction year 1.
Listed property rules. Computers/laptops/cell phones since 2018 are NOT listed property under §280F (TCJA removed them). So no special substantiation requirement beyond ordinary business records.
Tablets, iPads, monitors, accessories. Same as computers — not listed property since 2018.
Higher-end equipment. GPUs for AI/ML development can run $2K-$10K each. Servers, network equipment, security devices — all §179 expensable.
Bonus depreciation as backup. §168(k) bonus depreciation: 60% in 2025, 40% in 2026, 20% in 2027, 0% in 2028. For amounts exceeding the §179 limit, bonus depreciation applies. Most freelance developers never exceed §179 cap.
Software. Off-the-shelf software (Adobe Creative Cloud, JetBrains, Office 365, ChatGPT Plus, Cursor, GitHub Copilot, AWS credits) is deductible as software subscription expense — no need for §179. Annual subscription billed and paid in the year is current-deductible.
Custom software developed for own use. §174 applies (5-year amortization). See prior section.
Books, courses, certifications. Continuing education to maintain or improve skills in current trade or business is deductible under §162. Tax-deductible: AWS certifications, online courses related to current work, technical books. Not deductible: courses that prepare you for a new trade (e.g., a developer taking a law school course).
Conference travel. Tech conferences (AWS re:Invent, Google Cloud Next, KubeCon, RailsConf) are deductible business expenses. Registration fees, airfare, hotel, 50% of meals under §274.
Mileage and travel between client sites. Standard mileage rate 2026: TBD by IRS but typically around $0.725/mile. Actual costs alternative.
Substantiation. §274(d) requires written records for travel, entertainment, gifts, and listed property. Vehicle log apps (MileIQ, Everlance) cover most cases. Conference receipts kept in folders by year.
Health insurance, retirement, and the benefits stack
Freelance developers lose employer-provided benefits. Have to replicate them — at deductible cost.
Self-employed health insurance deduction. IRC §162(l) allows full above-the-line deduction of health insurance premiums for the self-employed (and their family). The deduction can’t exceed net SE earnings.
Mechanics. Premiums paid by the sole proprietor go on Schedule 1 line 17. Premiums paid by S-corp on behalf of >2% owner-employee go on W-2 box 1 wages, then deducted by the owner on Schedule 1 line 17. Net result: same federal income tax outcome.
HSA contributions. High-deductible health plan + HSA. 2026 HSA contribution limit: $4,400 self / $8,750 family. Plus $1,000 catch-up if 55+. Above-the-line deduction on Form 8889. Distributions for qualified medical expenses are tax-free.
Long-term care insurance. §213(d)(1)(D) includes qualified LTC insurance. Premium deduction caps by age: $480 for under 40, $890 for 40-50, $1,790 for 50-60, $4,770 for 60-70, $5,960 for 70+.
Solo 401(k). The gold standard for solo developers. 2026 contribution limits: $23,500 employee deferral (or $32,500 if 50+) plus employer profit-sharing contribution of 20% of net SE income (Schedule C) or 25% of W-2 wages (S-corp), with total combined limit of $70,000 ($77,500 if 50+).
Schedule C math. $180K net profit, $25K SE tax. Net for retirement: $180K – half SE = $167K. 20% × $167K = $33,400 employer contribution. Plus $23,500 employee deferral. Total: $56,900. Well under $70K cap.
S-corp math. $80K wages. 25% × $80K = $20K employer contribution. Plus $23,500 employee deferral. Total: $43,500. Below Schedule C capacity.
SEP-IRA. Simpler than Solo 401(k). 20% of net SE income (Schedule C) or 25% of W-2 wages (S-corp). 2026 limit: $70K. No employee deferral component. Best for developers who want simple admin and don’t want to fund the deferral piece.
Roth 401(k) and Mega Backdoor Roth. Solo 401(k) plans with Roth provisions allow Roth deferrals. Mega Backdoor Roth strategy: after-tax contributions up to the $70K total limit, then in-plan conversion to Roth. Can place $46,500 of after-tax money into Roth annually for high-income developers. Plan documents must support the strategy.
Disability insurance. Premiums paid personally are non-deductible; benefits are tax-free. Premiums paid by S-corp and reported as W-2 wages: deductible to corp, taxable wages to owner (recovers as ordinary income if benefits ever paid).
Multi-state developers and digital nomads
Software developers are uniquely mobile. Working from anywhere, billing clients anywhere. The tax implications get messy fast.
State income tax nexus. Working from a state — even temporarily — can create income tax nexus. A developer living in Texas (no income tax) but spending 3 months a year in California has California income tax exposure during those 3 months.
Day-count rules. Most states use a day-count rule for non-resident taxation: if you spend X days physically in the state working, the income attributable to those days is taxable. New York, California, and others have aggressive enforcement. Day-count threshold varies (NY uses 14 days, some others 30 days).
Domicile vs residence. Domicile is your true home — where you intend to return. Residence is where you spend time. You can have multiple residences but only one domicile. State tax often hinges on domicile rules.
Moving away from a high-tax state. Establishing domicile in Texas, Florida, Nevada, Wyoming, South Dakota, Washington, Tennessee, New Hampshire (interest/dividends only) or Alaska (no income tax) requires more than just renting an apartment. The high-tax state will challenge the move. Documentation: new driver’s license, voter registration, vehicle registration, primary doctor, primary banking, family physician, kids’ schools.
Convenience-of-the-employer rule. New York, New Jersey, Pennsylvania, Connecticut, and a few others have a ‘convenience of the employer’ rule. A developer working remotely from out-of-state for an in-state employer may have their wages taxed by the employer’s state even though the work is done elsewhere. This was an enormous issue during COVID.
Foreign Earned Income Exclusion. §911 permits US citizens working abroad to exclude up to $130,000 in 2026 of foreign earned income from US tax. Tests: bona fide residence (full tax year in foreign country) or physical presence (330 days in any 12-month period). Plus housing exclusion for foreign housing costs above a base amount.
Self-employment tax abroad. The §911 FEIE doesn’t reduce SE tax. A solo developer in Portugal under FEIE excludes income from federal income tax but still owes SE tax on the full amount. Totalization Agreement with certain countries can shift SE tax to the foreign social security system.
Form 2555 for FEIE. Filed with the tax return. Documentation of residence/presence.
Foreign tax credit. §901 permits a credit for foreign income taxes paid. Alternative to FEIE in some cases (when foreign tax rate exceeds US rate, credit may produce better result than exclusion).
GILTI for US shareholders of foreign companies. Solo developers forming a foreign LLC or corp for tax planning need to worry about §951A GILTI inclusion. Complex. Almost always requires international tax specialist.
Year-end planning playbook for freelance developers
Move list for December.
1. Equipment purchases. Place equipment in service by December 31 for §179 deduction. Computer that’s 4 years old getting upgraded? Buy in December.
2. Make the most of Solo 401(k) deferrals. Employee deferral ($23,500) can be made by December 31. Employer profit-sharing can be made by the tax filing deadline (April 15 or extended October 15).
3. SEP-IRA setup. Establish and contribute by the tax filing deadline. No December 31 deadline.
4. Pay business expenses before year-end (cash method). All December expenses with deductions wanted in current year — pay before December 31.
5. Defer December billings if income is high. Send the December 28 invoice on January 2 instead. Cash-method deferral.
6. Accelerate January billings if income is low. Send the January 5 invoice on December 28 to recognize income in current year (helpful if current-year tax rate is lower than expected next year).
7. Charitable contributions. Cash, appreciated stock, or DAF (donor-advised fund) contributions by December 31. §170 deduction subject to AGI limits.
8. State and local tax planning. Pay state Q4 estimated taxes by December 31 (for cash-method states allowing prepayment deduction). Watch SALT cap interaction ($10K cap on personal SALT through 2025; TCJA expiration looming).
9. Health insurance / HSA contributions. Max HSA before year-end if employer-sponsored, or before tax filing deadline if individual HDHP.
10. Roth conversions. If income is unusually low in current year (between jobs, sabbatical), convert traditional IRA to Roth IRA at lower tax rate. Pay tax now at low rate; future growth tax-free in Roth.
11. R&D credit documentation. Compile QRE documentation by December 31. Easier to remember details when the year is fresh.
12. Section 199A planning. If income is near the QBI threshold ($241,950 single / $483,900 MFJ 2026), consider deferring income or accelerating deductions to stay below.
13. S-corp 2553 election. If considering S-corp for next year, file Form 2553 by March 15 of next year for January 1 effective date. Filing before year-end is also fine.
Estimated tax payments and the cash flow problem
Solo developers face a cash flow timing issue most W-2 employees don’t. No withholding means you have to budget for tax payments quarterly — and if you don’t, the penalties stack.
Quarterly estimated tax basics. §6654 requires quarterly payments to avoid an underpayment penalty. Due dates are April 15 (for Q1, covering income earned January-March), June 15 (Q2, April-May income), September 15 (Q3, June-August income), and January 15 of the following year (Q4, September-December income). Yes, the quarters are uneven months. That’s how Congress wrote it.
Compute via Form 1040-ES. The form has a worksheet to estimate annual federal income tax + SE tax based on projected income. Divide by 4. Send a check or pay online via IRS Direct Pay.
Safe harbor. §6654(d). The lesser of (a) 90% of current year tax, or (b) 100% of prior year tax (110% if prior year AGI was over $150,000). Pay enough quarterly to clear the safe harbor and no underpayment penalty applies, even if you owe a large April balance.
Most developers use the prior year safe harbor for predictability. Pay 25% of prior year tax each quarter. April balance is what’s owed beyond that. Eliminates the math of projecting current year income.
Underpayment penalty rate. The §6621 underpayment rate as of 2026 is 8% annual. Compounded daily. Form 2210 computes the actual penalty if you didn’t meet safe harbor. Penalty applies even if the late payment is made before April 15.
State analog. Most states with income tax have their own estimated payment schedule. California has Q1, Q2, Q3, Q4 with different percentages (30%, 40%, 0%, 30% in CA). Other states use 25% each quarter. Penalties for underpayment also apply.
Cash flow planning. Set up a separate savings account for tax money. As each invoice is paid, transfer 30-35% to the tax account immediately. Pay quarterly from that account. Never co-mingle tax money with operating cash.
Annualized income exception. Form 2210 Schedule AI lets you compute the underpayment based on income actually received in each quarter, instead of assuming income is earned evenly. Useful if a freelance developer has a big payment in Q4 that wasn’t anticipated — annualized method may eliminate the early-quarter penalty.
Withholding from W-2. If you have a side W-2 income, you can increase W-2 withholding to make up for SE tax. W-2 withholding is treated as paid evenly throughout the year regardless of when actually withheld — useful trick to retroactively cover Q1-Q3 underpayments via a December bonus with high withholding.
Bookkeeping basics for solo developers — what actually matters
Many freelance developers DIY their bookkeeping. QuickBooks Self-Employed, Wave, FreshBooks, or even a spreadsheet works at the solo level. Key categories matter.
Income categorization. All client payments hit revenue. Use one category for service revenue. Don’t separate by client unless useful for business reporting (income tax doesn’t care about per-client splits).
Expense categorization (Schedule C lines). Advertising (line 8) for marketing, website, business cards. Commissions and fees (line 10) for referral payments or finder’s fees. Contract labor (line 11) for payments to subcontractors. Depreciation (line 13) for equipment §179 and bonus depreciation. Insurance (line 15) for E&O, professional liability, general business liability. Legal and professional services (line 17) for CPA, attorney, accounting software. Office expense (line 18) for office supplies. Rent or lease — vehicles (line 20a) and other business property (line 20b). Repairs and maintenance (line 21). Supplies (line 22) for technical books, smaller equipment under $2,500. Taxes and licenses (line 23) for state filing fees, business license, sales tax. Travel (line 24a) for hotels, airfare. Meals (line 24b) at 50% deductible. Utilities (line 25) for office utilities (when you have a separate office, not home office which goes on Form 8829). Wages (line 26) for W-2 employees (zero for sole prop without payroll). Other expenses (line 27a) for things that don’t fit elsewhere.
Home office expense. Form 8829 attaches to Schedule C. Output flows to Schedule C line 30.
Self-employment health insurance. Schedule 1 line 17 (above the line deduction, not on Schedule C).
Half-SE deduction. Schedule 1 line 15 (above the line, not on Schedule C).
Solo 401(k) / SEP / SIMPLE contributions. Schedule 1 line 16 (above the line, not on Schedule C).
Misclassification mistakes. Personal expenses that get coded as business — a frequent audit issue. Personal meals coded as ‘meals and entertainment.’ Family vacations coded as ‘travel.’ Personal Netflix/Spotify subscriptions coded as ‘software subscriptions.’ Personal Amazon orders coded as ‘office supplies.’ These get reclassified on audit.
Mileage tracking. Use an app (MileIQ, Everlance, Stride). The 2026 standard mileage rate (set annually by IRS, not yet announced for 2026 as of this writing but typically $0.65-$0.70/mile). Multiply business miles × rate = deduction. Or use actual costs (depreciation, gas, repairs, insurance, registration) × business-use percentage — more complex but sometimes higher deduction for owners of expensive vehicles.
Bank statements vs accounting records. The IRS in audit asks for bank statements and ties them to the accounting records. Discrepancies trigger questions. Reconcile monthly. Don’t co-mingle business and personal accounts — open a dedicated business checking account at minimum.
When to upgrade to a professional. Solo developers typically hire a CPA for tax prep but DIY bookkeeping until revenue exceeds $250K-$500K. Above that, the time savings and tax planning value of a CPA-managed bookkeeping engagement (Bench, Pilot, BookkeeperLive, or a local CPA firm) typically justifies the cost ($300-$800/month).
State tax — California and New York digital service taxation
California and New York are the two states that hit freelance developers hardest. Both have aggressive income tax rates, both source service income to the state where the customer benefits, and both have specific nuances that catch developers off guard.
California source rules. Cal. Code Reg. §17951-4 sources income from personal services to the state where the services are performed. So a CA-resident developer working from home in CA: 100% CA source. A non-CA-resident developer performing services in CA (on-site work for a CA client): CA-source for the days worked in CA.
California convenience-of-the-employer interpretation. CA has historically not adopted the strict ‘convenience of the employer’ rule that New York uses. So a developer living in Texas working remotely for a CA company is generally not CA-taxed on services performed in TX. (Some practitioners have raised concerns about CA’s evolving stance — discuss with CA-specialist CPA.)
New York convenience-of-the-employer rule. New York applies the convenience-of-employer rule: if you work remotely for a NY-based employer (or your work location of choice is your home rather than the employer’s NY office because of convenience rather than necessity), NY taxes the wages as NY-source. This caught remote workers during COVID. Doesn’t typically apply to freelance contractors (you don’t have a ’employer’), but does apply to W-2 employees.
New York pass-through entity tax (PTET). NY allows an entity-level tax election under §164 SALT cap workaround framework. Pass-through entities (S-corps, partnerships, LLCs taxed as partnerships) can elect to pay state tax at the entity level. The entity-level tax is deductible on the federal return without SALT cap. Owners get a credit on their personal NY return. Net benefit: full federal deduction for state tax, bypassing the $10K SALT cap.
California PTET. California adopted a similar PTET. Same mechanic. Election made annually.
For S-corp developers in CA or NY: PTET election is usually beneficial. Saves $5K-$15K of federal tax per year at high income levels.
Sales tax on software services. Most states don’t tax pure software development services (custom programming is generally a service, not a product). But several states (Texas, Connecticut, New York, others) tax some software services under specific circumstances. Texas taxes ‘data processing services’ broadly, which can include some software development. Consultations with a state-tax specialist when crossing state lines.
Multi-state apportionment for S-corp. S-corp K-1 reporting allocates business income to states based on apportionment factors. A solo developer with clients in 10 states might face 10-state filings, but typically only states where the developer physically performs work create nexus. Phone or video calls from out-of-state don’t typically create nexus.
Workers’ comp and unemployment. State-specific. Sole prop generally exempt from workers’ comp for self (some states require if you have employees). S-corp owner-employees subject to workers’ comp (with a minimum premium of $300-$1,000/year typically).
Frequently Asked Questions
I made $180K freelancing in 2026. Will an S-corp election save me money next year, and what salary should I pay myself?
Yes, but the savings are smaller than the popular podcast advice suggests once you account for setup costs and lost retirement plan capacity. Let’s work the numbers. Sole prop at $180K. SE tax: $180K × 0.9235 = $166,230 net SE earnings. SS portion: 12.4% × $166,230 = $20,613 (below the $176,100 wage base, so no cap). Medicare: 2.9% × $166,230 = $4,821. Total SE tax: $25,434. Half-SE deduction reduces federal income tax by $25,434/2 × marginal rate (say 24%) = $3,052. Net SE cost: $22,382. S-corp election with $90K W-2 wages, $90K distribution. FICA on wages: $90K × 15.3% = $13,770 (half employee, half employer-paid by corp; corp gets deduction for employer half but you wear it economically). Distribution: zero payroll/SE tax. Total payroll cost: $13,770. Gross savings: $25,434 – $13,770 = $11,664. After-tax savings (since the half-SE deduction goes away too): roughly $10,000-$11,000. Subtract costs. Payroll service ($720/year). Tax prep increment ($1,500). State franchise tax (CA $800, NY MTA $25-300, others $0-$500). Workers’ comp ($300 minimum in some states). Total: $3,000-$5,000. Net S-corp benefit at $180K: $5,000-$8,000 per year. Worth it for most, marginal at this income level. Reasonable comp determination. RCReports or similar services price compensation for software developers based on geography, experience, business revenue, and time spent on operations vs strategy. For a solo S-corp developer in a mid-cost-of-living metro, $80K-$120K W-2 wages is typically defensible. Setting wages at $90K-$110K hits the sweet spot: enough to defend reasonable comp on audit, low enough to capture meaningful SE tax savings. Going too low (below $50K) on $180K of profit is the classic IRS audit trigger. The Watson case (Watson v. Commissioner, 8th Cir. 2012) is the cautionary tale — a CPA’s $24K W-2 with $200K distribution got 80% of the distribution reclassified as wages, with retroactive payroll tax + penalties. The QBI factor. At $180K of net profit, you’re below the §199A QBI threshold ($241,950 single / $483,900 MFJ 2026). Your QBI deduction is 20% × $180K = $36K regardless of S-corp status. So QBI isn’t a reason to S-corp at this income. Above the threshold, S-corp helps QBI because W-2 wages activate the 50% wage limitation. But you’re not there yet. Retirement plan capacity. The hidden cost of S-corp election. Schedule C: Solo 401(k) max contribution at $180K profit ≈ $33K profit-sharing + $23,500 deferral = $56,500. S-corp with $90K W-2: 25% × $90K = $22,500 profit-sharing + $23,500 deferral = $46,000. S-corp loses $10,500 of retirement plan room. If you’re maxing retirement contributions, the S-corp election’s net benefit is reduced by the lost retirement capacity (which is tax-deferred money that would have compounded). Some advisors argue the S-corp election only makes sense when your profit exceeds the Solo 401(k) cap and you can’t use the extra capacity anyway. Other factors. Multi-state work: S-corp election adds state corporate filings in each state you have nexus. Health insurance: S-corp slightly more complicated (premium on W-2, then deducted on Schedule 1). Banking: business account easier to maintain with S-corp because it forces separation. Legal liability: LLC provides limited liability regardless of tax treatment. Conclusion. At $180K profit, S-corp election saves approximately $5K-$8K net annually after costs and lost retirement capacity. Worth it for most freelancers at this income level. At $80K-$100K profit, the savings are marginal — probably break-even. At $250K+ profit, the savings grow meaningfully ($15K-$25K annually) and S-corp becomes obvious. How to elect. Form an LLC (or use existing LLC). File Form 2553 with the IRS by March 15 of the tax year you want S-corp treatment to begin (or within 75 days of formation for new LLCs). Set up payroll. Update bookkeeping. Maintain shareholder basis records. Comparison table for clarity. At $180K net profit. Sole prop: $25,434 SE tax, $0 corp filings, $0 payroll service, $0 franchise tax. S-corp ($90K wages): $13,770 FICA, $1,500 corp tax prep, $720 payroll, $800-$2,000 franchise/SUTA. Net cash difference: roughly $8,000-$10,000 favoring S-corp. Higher income brings bigger savings. At $300K profit: sole prop SE tax ~$30K (capped by SS wage base). S-corp with $130K wages: FICA ~$22K. Net savings $8K + QBI improvement potentially $20K. Total $28K/year. At $500K profit: SE tax stays near $30K (Medicare 2.9% + 0.9% additional Medicare keep growing but SS portion capped). S-corp at $150K wages: FICA $24K. Savings $6K on SE side but QBI improvement captures up to $30K-$40K. Total $35K-$45K/year. Don’t forget the QBI cliff. Just below the $241,950 single threshold (2026), full QBI deduction applies. Just above, the W-2 wage limit kicks in (for non-SSTB) or phase-out begins (for SSTB). Solo developer with no W-2 wages (sole prop) above threshold loses QBI deduction. S-corp with adequate wages preserves QBI deduction. Effect of state tax. Some states have entity-level tax options (PTET — pass-through entity tax) that S-corps can elect. PTET converts state SALT-capped personal tax into deductible federal corporate-level tax. In high-tax states (CA, NY, NJ, MA, MD, OR, MN), PTET election saves another $3K-$15K of federal tax. Sole props can’t access PTET. Another reason to S-corp at higher income. Watson v. Commissioner facts. Watson was a CPA with $24,000 W-2 wages and $200,000+ distributions from his firm. The 8th Circuit upheld the IRS reclassification of $93K of distributions to wages. The court relied on expert testimony that CPAs in the relevant market and experience level earned $94K. Lessons. (1) Document reasonable comp with market data. (2) RCReports or similar services. (3) Don’t pay yourself below 30%-40% of business profit, even if technically defensible. When NOT to S-corp. Pre-revenue startups (no income to save tax on). Owners with significant passive losses (S-corp losses subject to basis/at-risk/passive activity rules). Owners planning to sell the business within 5 years (S-corp basis tracking complications). Owners in states with high franchise tax that exceed SE tax savings. Owners who want max retirement plan capacity (Schedule C allows higher 401(k) contributions). Mid-year election. Form 2553 can be filed within 75 days of the start of the tax year for S-corp election to be retroactive. So a developer who decides on March 15, 2026 to elect S-corp for 2026 has until May 30 (75 days from January 1) to file Form 2553 effective January 1. Late elections beyond 75 days require Rev. Proc. 2013-30 relief — usually granted but adds complexity. Final advice. At $180K profit, S-corp election typically nets $7K-$10K/year of true savings. Worth doing. Document reasonable comp. Set up payroll correctly (most developers use Gusto, ADP, or Justworks). Maintain basis records. Don’t pay yourself too low — the IRS will reclassify.
I’m building a SaaS product on the side while doing freelance contracts. How does Section 174 affect me?
Section 174 is the elephant in the room for solo developers building products on the side. The post-TCJA rules require all specified research or experimental expenditures to be capitalized and amortized over 5 years (15 for foreign research). No current expensing. Software development costs are §174. Notice 2023-63 from the IRS confirmed this. Activities to develop software for sale, license, lease, or own use in your trade or business are §174 expenditures. For your situation. Two activities. (1) Freelance contracts: you’re paid by clients to write code. Your time and any out-of-pocket costs you incur to deliver to the client are part of your cost of providing the service. These costs are generally deductible as ordinary business expenses under §162 — not §174 expenditures from your perspective, because the deliverable is being purchased by the client. The client may have §174 capitalization on the side they pay you, but that’s their problem. (2) SaaS product development: you’re developing software for your own SaaS business (to sell to customers). The development costs ARE §174 expenditures. They must be capitalized. What counts as SaaS development cost? Time spent coding new features. Time spent on architecture and design. Time spent on testing. Payments to contractors for development work. AWS/Azure/GCP costs for development environments (production hosting is operational, not development). Software licenses used in development (your JetBrains license, GitHub Copilot, etc.). Your own time. The thorny question. If you don’t pay yourself a W-2 wage (you’re a sole prop or pre-revenue developer), how do you value your time for §174? The IRS hasn’t issued clear guidance for solo founders. Several positions are taken in practice. Position A: Ignore owner time. The argument: §174 capitalizes ‘expenditures.’ If you don’t pay yourself, you haven’t expended anything. Your own labor isn’t an expenditure in the literal sense. This position has appeal but is risky if audited — the IRS could reasonably argue that the value of your time should be capitalized. Position B: Capitalize a notional owner compensation. Establish a reasonable hourly rate for your labor (say $100-$150/hr based on market rates for your skills). Track hours spent on the SaaS. Capitalize the notional value to §174. Then reduce your Schedule C net profit by the same amount (effectively converting current SE-taxable income into capitalized R&D). This position is more defensible but creates a paperwork burden. Position C: Run the SaaS through an S-corp. Pay yourself W-2 wages from the S-corp. The W-2 wages allocable to R&D activities are §174 expenditures. This position is the cleanest for §174 compliance but adds S-corp administration costs. Pre-revenue startup status. If your SaaS hasn’t generated revenue yet, you may not even be in a trade or business with respect to that activity. §195 start-up expenses applies pre-trade-or-business. Costs incurred to investigate or create the active trade or business of the SaaS aren’t currently deductible — they’re capitalized as start-up costs and amortized over 180 months starting when the business begins. So pre-revenue, §174 might not even apply yet; start-up cost capitalization does. Once the SaaS becomes a trade or business (you have customers, you’re billing, the business is operating), §174 starts applying prospectively to ongoing development. R&D credit §41. The same activities subject to §174 capitalization may qualify for the R&D credit under §41. The credit doesn’t reduce the §174 capitalization amount, but it offsets income tax (or payroll tax for qualified small businesses under §41(h)) by 6%-14% of qualified research expenditures. For a solo developer with $50K of qualifying SaaS development costs, the §41 credit might be $3,000-$7,000. The payroll tax offset under §41(h) is available if your SaaS qualifies as a small business (under $5M gross receipts in the credit year, and no gross receipts in any year more than 5 years before the credit year — so a recent startup). Net effect on cash flow. Suppose you have $200K of freelance contract revenue (no §174 issue) and $50K of SaaS development costs (subject to §174). Year 1 deduction of the $50K: $50K / 5 × ½ (midpoint convention) = $5K. So $45K of the cost is pushed to future years (deductible in years 2-6). Marginal rate 32%: $14,400 of additional current-year tax. Offset by R&D credit (say $5K) = $9,400 net additional tax. Compared to pre-2022 rules. Pre-2022, you could’ve expensed the full $50K in year 1. $50K × 32% = $16K of current-year deduction. The §174 capitalization extracts $9,400 of cash flow over multiple years. Strategic responses. Some developers delay the SaaS launch until major development is complete (concentrating §174 capitalization in fewer years), then operate steady-state with less new development (less §174 capitalization going forward). Some developers contract out development to vendors (which the developer pays for) — the developer’s payments to contractors are §174 expenditures. The contractor recognizes income from the developer. Net effect: same §174 capitalization but moved to a different taxpayer. Legislative outlook. Multiple bills have been introduced to repeal or modify the §174 capitalization requirement, including the Build Back Better Act and various standalone bills. As of 2026, the rule remains in effect for software development. Bipartisan support exists for repeal but no enacted change yet. Stay tuned to legislative developments. Documentation. Track development time by activity. Track contractor payments by activity. Maintain a project tracking system that allows allocation of costs to the SaaS R&D bucket. Form 4562 reports §174 amortization. Consider engaging an R&D credit firm if you have significant qualifying R&D expenditures. Form 4562 reporting. §174 amortization is reported on Form 4562. The amortization begins in the month/half-year when the cost was incurred, using the half-year convention or the midpoint convention as specified in the regulations. Tracking individual cost items by year placed in service matters because each year’s costs start a new 5-year (or 15-year for foreign) amortization schedule. Section 174 versus Section 195 startup costs. Pre-revenue startups have an additional analysis. Section 195 covers investigatory and pre-operational costs (creating an active trade or business). Section 174 covers research and experimental costs once the trade or business exists. The trade or business begins when the activity is producing income — for a SaaS, when you first acquire a paying customer. Costs incurred before the SaaS has any revenue are §195 startup costs, amortized over 180 months. Costs after revenue starts are §174, amortized over 60 months. The difference: §195 is 15-year, §174 is 5-year. Section 174 is faster recovery but only applies once you have a real business. Section 195 has a $5,000 first-year expense provision (with phase-out above $50K of total startup costs). So $5K of pre-revenue costs can be expensed immediately, with the rest amortized over 180 months. Section 174 has no such first-year expense provision after TCJA. Section 41 R&D credit details. The credit equals 14% (under ASC method) of QREs in excess of 50% of the average QREs for the three preceding years. For a startup with no prior QREs, the formula reduces to 6% of current-year QREs (the reduced rate for first claimants). The credit can offset regular income tax liability. Payroll tax offset election. §41(h) permits qualified small businesses to elect to apply up to $250,000 of R&D credit (subsequently increased to $500,000 by IRA 2022 §13902) against employer FICA/Medicare tax. Qualified small business: gross receipts under $5M in the credit year, and no gross receipts in any year before the 5th tax year preceding the credit year. So a SaaS company in its first year of revenue, with revenue under $5M and the first year of any gross receipts being less than 5 years old, qualifies. The payroll tax offset is HUGE for early-stage SaaS founders. Pre-profit, no income tax liability to offset. But the company pays payroll tax on owner-employee W-2 wages and any other employees. The R&D credit reduces that payroll tax cash outflow dollar-for-dollar. Real cash benefit. Capital vs operating cost classification. Some costs that LOOK like development might actually be operating costs. AWS hosting for the production environment (where customers use the SaaS) is an operating cost, not §174. AWS used to run development/staging environments — §174. AWS used to run pre-production load testing — §174. The line is whether the activity is research-and-experimentation vs running the production service. Stock-based compensation. If you grant stock options or restricted stock to early-stage employees and contractors, the value of those grants when they vest creates a §174 issue. The grant value allocable to research activities is §174 capitalizable. This is complex and rarely handled correctly by solo founders without specialty CPA help. Real-world advice. (1) For solo developer building SaaS on the side, the §174 issue is real but tractable. Track development costs separately. Apply §174 to actual out-of-pocket costs and to your own W-2 wages (if S-corp). Claim §41 R&D credit. (2) Engage an R&D credit firm for the first credit study. They produce the documentation, file Form 6765, and typically work on a contingency fee of 10-30% of credit obtained. (3) Keep contemporaneous notes on technical uncertainty and experimentation — emails, design docs, GitHub PRs, commit messages. (4) Don’t ignore the issue and hope it goes away. The IRS is aware of widespread non-compliance with §174 and audit risk is growing.
Am I an SSTB consultant or a non-SSTB software developer for QBI purposes when my work mixes coding and architecture advisory?
The SSTB analysis for software developers is one of the trickiest parts of §199A. The answer depends on what your work product actually is. Treas. Reg. §1.199A-5(b)(2) defines SSTBs by category. ‘Consulting’ is in the list. The regulation defines consulting as ‘the provision of professional advice and counsel to clients to assist the client in achieving goals and solving problems.’ That sounds broad. It could capture software architects who advise on system design. But the regulation also gives exceptions and clarifications. Treas. Reg. §1.199A-5(b)(2)(xi) excludes from consulting: services ancillary to the sale of goods (e.g., advice given as part of a software product sale). And Treas. Reg. §1.199A-5(b)(2)(xiv) provides specific guidance on computer-related activities. The key distinction. Producing software (or other tangible the work) = non-SSTB. Providing advice without producing the work = potentially SSTB consulting. Example A: Non-SSTB. A freelance developer is hired to build an iOS app for a client. The work involves: requirements gathering, architecture decisions, writing code, testing, deployment, and post-launch support. The deliverable is the working app. This is non-SSTB software development regardless of how much architecture/advisory the developer also does in the process — the engagement is for delivering software. Example B: Potentially SSTB. A ‘fractional CTO’ is hired to advise a startup on technology strategy, hiring decisions, build-vs-buy decisions, and vendor selection. The deliverable is advice. No code is delivered. This looks like consulting. SSTB analysis applies if income exceeds the threshold. Example C: Mixed. A developer-consultant does $150K of pure coding work and $50K of pure advisory work. Treas. Reg. §1.199A-5(c)(1) addresses mixed-activity businesses. If SSTB activities are less than 10% of gross receipts (or 5% if gross receipts exceed $25M), the entire business is treated as non-SSTB. The developer’s $50K of advisory is 25% of $200K — over 10%. Two options: (1) treat the entire business as SSTB (worst case); (2) separate the activities into distinct businesses (better, but requires real separation with separate books, separate operations, separate marketing). If separated into two businesses, the $150K developer business is fully eligible for QBI deduction. The $50K consulting business is SSTB and subject to phase-out above the threshold. Below the threshold. SSTB classification doesn’t matter below $241,950 single / $483,900 MFJ (2026). The full 20% QBI deduction is available regardless of business type. So for a freelance developer earning $180K, the SSTB question is moot. Above the threshold but below the phase-out ceiling. The QBI deduction phases out for SSTBs between $241,950-$341,950 single / $483,900-$583,900 MFJ. The phase-out is linear. Above the ceiling, SSTB QBI deduction is zero. For non-SSTB taxpayers, the deduction is limited (not phased out) by the W-2 wage and UBIA tests above the threshold. So non-SSTBs still get a deduction; it’s just capped at 50% of W-2 wages (or 25% of W-2 + 2.5% of UBIA, whichever is greater). Positioning strategies. (1) Contract language. Write contracts that recite ‘software development services’ rather than ‘consulting’ or ‘advisory.’ Bill on a deliverable basis (project basis) rather than hourly advisory. (2) Output. The work include code, software, documentation, deployment artifacts. The output is tangible software, not advice. (3) Marketing. Position yourself as a developer who happens to also advise, not a consultant who happens to also code. Your website, LinkedIn, business cards say ‘Software Engineer’ or ‘Software Developer.’ (4) Time allocation. If you keep time records, track time spent producing code vs. time spent in advisory meetings. The IRS may look at time allocation as evidence of activity mix. Trap: ‘reputation or skill’ SSTB. Section 199A(d)(2)(A) also classifies as SSTB ‘any trade or business where the principal asset is the reputation or skill of one or more of its employees or owners.’ Treas. Reg. §1.199A-5(b)(2)(xiv) narrowly construes this to apply only to specific situations: licensing/royalties from the use of an individual’s image/likeness/name/signature, appearance fees, and similar celebrity-type income. Software development by name-brand developers is NOT caught by this provision (the regulation explicitly excludes ordinary commerce based on individual skill). Solo developer comfort level. For most freelance developers earning below $250K of taxable income, the SSTB question doesn’t bite. QBI deduction is available. For developers earning above the threshold, SSTB analysis matters and benefits from intentional positioning. Document the position. If you’re claiming non-SSTB above the threshold, keep documentation showing the business produces software (not pure advice). Sample the work. Sample contracts. Sample invoices. The IRS may challenge the position on audit. Above the threshold and SSTB. If you can’t avoid SSTB classification (you’re a fractional CTO with zero code the work), consider strategies that reduce taxable income below the threshold: pre-tax retirement contributions, HSA contributions, cost segregation on real estate, charitable contributions, defined benefit plans for higher contribution limits. Activities that are clearly non-SSTB software development. Building custom software for clients. Developing SaaS products. Mobile app development. Embedded systems development. DevOps engineering (infrastructure, deployment automation). Data engineering (pipelines, ETL). Machine learning model development. Game development. Open source contribution work (when paid). Any work where the output is software code or software systems. Activities that look like consulting (potential SSTB). Technology strategy advisory without the work. Fractional CTO/CIO roles. Architecture review without implementation. Vendor selection consulting. Pre-acquisition technology due diligence (when output is opinion/recommendation rather than software). Speaking engagements about technology. Authoring technical books (royalty income, separate analysis). Activities in the gray zone. Software development with significant advisory component. DevOps consulting (often a hybrid). Solution architects who design but don’t code. Senior engineers paid hourly for code review/mentorship. Technical leadership for client engineering teams. How the IRS approaches the analysis. The IRS doesn’t typically pre-decide SSTB classification — taxpayers self-classify on Form 8995 or Form 8995-A. The IRS audits if the position is aggressive. Audit defense relies on: business activity descriptions in contracts, billing rates and structure (project-based vs hourly advisory), the work produced, marketing/positioning of the business. Mixed activity election. Treas. Reg. §1.199A-5(c)(2) allows a single trade or business to be treated as a single unit if it includes both SSTB and non-SSTB activities, provided the activities are sufficiently integrated. The analysis becomes whether the combined activity is predominantly SSTB or non-SSTB. The 10% / 5% de minimis rule under Treas. Reg. §1.199A-5(c)(1) provides a safe harbor: if SSTB activities are less than 10% of gross receipts (5% if receipts exceed $25M), the entire business is non-SSTB. Separating businesses. To treat coding and advisory as separate businesses for §199A purposes, you need genuine separation. Separate operations. Separate marketing (different websites or service offerings). Separate contracts (some say ‘software development services,’ some say ‘advisory services’). Separate books (different income statements). Separate bank accounts ideally. Time tracked separately. The IRS scrutinizes when taxpayers conveniently separate just before tax filing — the separation must be real and consistent. Practical positioning summary. Brand yourself as a software engineer. Bill on project basis when possible. Document the work. Avoid ‘consultant’ label on contracts and invoices. Use ‘software development services’ or ‘software engineering services’ as the service description. Maintain a public-facing portfolio of code/products produced. Below the threshold, none of this matters; above the threshold, this is the difference between a $40K deduction and zero.
How much can I deduct for my home office if I rent a 1-bedroom apartment in San Francisco for $4,500/month and use a 150 sq ft corner as my office?
Renters can take substantial home office deductions under the regular method because rent is the largest component of housing cost. Let’s work through the SF apartment numbers. Step 1: Calculate business-use percentage. Office: 150 sq ft. Total apartment: typically 600-700 sq ft for a SF 1BR. Use 650 sq ft total. Business-use percentage: 150 / 650 = 23.1%. Step 2: Annual rent. $4,500 × 12 = $54,000. Business portion: $54,000 × 23.1% = $12,474. Step 3: Utilities and other home costs. PG&E electric/gas (~$80/month = $960/year). Internet ($90/month = $1,080). Renters insurance ($300/year). Water (usually included in SF rent, otherwise $30/month = $360/year). Total: $2,700. Business portion: $2,700 × 23.1% = $624. Step 4: Total home office deduction (regular method, Form 8829). $12,474 + $624 = $13,098. Simplified method comparison. 150 sq ft × $5 = $750. Max $1,500 for up to 300 sq ft. Capped. Regular method wins by $12,348. For SF renters with high rent and dedicated office space, regular method is dominant. Federal tax savings. $13,098 × 24% marginal rate = $3,144 federal income tax. Plus reduction of SE tax: $13,098 × 0.9235 × 15.3% = $1,852. Total federal tax savings: $4,996. State tax (California). California conforms to home office deduction for personal income tax. $13,098 × 9.3% (CA marginal at this income) = $1,218. Combined federal + state savings: $6,214 from the home office deduction. Exclusivity test. The 150 sq ft must be used exclusively for business. A ‘corner’ of a 1BR apartment is tricky. The IRS has won cases disallowing partial-room offices when the area isn’t physically separated. To strengthen the position: use a room divider, bookshelf, or partition to physically demarcate the office space. Avoid using the office area for any personal activities (no exercise bike, no entertainment center, no overnight guests sleeping on a couch). Regular use. The IRS expects regular business use. A developer working from the home office 30+ hours/week clearly qualifies. Principal place of business test. The 1999 amendment to §280A(c)(1)(A) allows home office as principal place of business if used for administrative/management activities and no other fixed location is used for substantial admin/management. For a freelance developer with no other office, this is easy to meet. Audit risk. Home office deductions are statistically over-audited (about 2x base rate for Schedule C filers). Mitigation. Photos of the office showing dedicated setup (desk, monitors, technical books, no personal items). Floor plan with measurements. Time logs or calendar entries showing daily business use. Receipts for the listed expenses. What if the lease forbids business use? Most residential leases prohibit ‘commercial’ use. The IRS doesn’t care about your landlord’s lease — the tax deduction is based on actual use, not lease compliance. But your landlord could potentially evict for breach. Practical reality: solo freelance work from a home apartment rarely triggers landlord action. Industrial or retail use would. Furniture and equipment in the office. Desk, chair, monitor, lighting — these are tangible business assets, separately depreciable or §179 expensable. A $3,500 ergonomic Herman Miller chair + $1,500 standing desk + $800 monitor are 100% deductible business expenses. Don’t fold them into the home office calculation — track separately. Cell phone. Since TCJA removed cell phones from listed property, deductible based on reasonable business-use percentage. A solo developer using their cell 80%+ for business: 80% deductible. Coworking space + home office. Some developers maintain both a home office and a coworking membership (WeWork, Industrious). Both deductible. Coworking is fully deductible (rental of business property). Home office deduction continues to apply for the home office portion. Moving partway through the year. If you move mid-year, allocate the home office deduction based on actual days at each location. New apartment with bigger office in October — separate calculation for the October-December portion. Renting vs owning. SF renters benefit massively from regular-method home office because rent is the dominant cost. SF homeowners benefit too but less dramatically because mortgage interest deduction is already capped (SALT cap on property tax, $750K mortgage limit). For a renter paying $54K/year rent, capturing 23% as deductible is a $12K hit on Schedule C income — that’s real money. Documentation file. (1) Floor plan or layout with measurements. (2) Photos. (3) Copy of rent receipts or lease showing $4,500/month rent. (4) Utility bills. (5) Annual computation worksheet. (6) Form 8829 attached to Schedule C. Keep for 7 years (3-year audit period + 4-year extension if substantial understatement). Form 8829 mechanics. Form 8829 calculates the regular-method deduction. Part I: percentage of home used for business. Part II: indirect home expenses (utilities, insurance, etc.) × business-use percentage. Part III: depreciation on the office portion. Part IV: carryover of unused deduction. Output goes to Schedule C line 30. Direct expenses vs indirect expenses. Direct expenses (Form 8829 Part II line 7 column ‘direct’) are 100% deductible — these are expenses solely for the office (painting the office, repair to office window, dedicated office phone line). Indirect expenses (line 7 column ‘indirect’) are × business-use percentage — these are home-wide expenses (utilities, insurance, rent, mortgage interest). Loss limitation. §280A(c)(5) limits the home office deduction to gross income from the business activity less other business expenses. A loss can’t be created or increased by the home office deduction. Excess deduction carries forward to next year. Carryforward of unused home office deduction. If your home office deduction is limited by the income limitation, the unused portion carries to next year (Form 8829 Part IV). Useful for solo developers with lumpy income or transition years. Renting from a related party. Some developers form an LLC for the freelance business and have the LLC rent office space from the owner’s personal home. Rental income to the owner, rental deduction to the LLC. Net effect similar to home office deduction but provides more flexibility. Watch §280A(c)(6) which limits this for some entity-to-related-party rentals. Also watch §469 passive activity rules — rental income from related parties may not qualify for active treatment. Office equipment refresh cycle. Developers typically refresh hardware every 2-4 years. Plan equipment purchases for years with high income to make the most of §179 deductions. A $4,000 MacBook Pro + $2,000 ultrawide monitor + $1,500 standing desk + $1,000 ergonomic chair = $8,500 of §179 expensable equipment, fully deductible in the year of purchase. Internet redundancy. Some developers maintain two internet connections (primary cable, secondary cellular hotspot or fiber) for reliability. Both deductible as business expense if used for business work. The full cost of the backup connection is deductible based on its actual business use, separate from the home office allocation. Lighting and ergonomics. Office lighting, ergonomic accessories (vertical mouse, ergonomic keyboard, footrest), monitor arms, cable management — all deductible business expenses. Treat as supplies (under $2,500) or equipment (§179).
I’m thinking of moving from California to Texas to escape state income tax. How long before California stops being able to tax me?
California is one of the most aggressive states for chasing former residents. The Franchise Tax Board (FTB) routinely audits ‘departures’ for 2-3 years after the alleged move. Most defenses fail because the move wasn’t real enough. Here’s the playbook. California residency rules. Cal. Rev. & Tax. Code §17014 and §17015 define California resident for tax purposes. A resident is anyone domiciled in California (intent to make CA home) OR a non-domiciled person in CA for other than a temporary or transitory purpose. The ‘safe harbor’ for non-residence: a domiciliary leaving CA for a definite indefinite period under an employment-related contract, or for 546 consecutive days (about 1.5 years) under certain conditions. Domicile. The key concept. Domicile is your true permanent home — the place you intend to return after temporary absences. You can only have one domicile at a time. Acquiring a new domicile requires (a) physical presence in the new location, AND (b) intent to make it your new permanent home. Establishing Texas domicile. Required actions, in order of FTB scrutiny weight: (1) Sell or lease out your California home. Or at minimum, no longer treat the CA home as your primary residence. If you keep the CA home, the FTB will argue it’s still your home. Renting it out is better than keeping it as a vacation property. Selling is best. (2) Buy or lease a permanent home in Texas. Not a hotel or short-term rental. A real apartment lease (12+ months) or purchase. The Texas home should be of comparable quality to your former CA home (the FTB is suspicious if the ‘new home’ is a budget apartment while the ‘former home’ is a $3M mansion). (3) Move family and belongings to Texas. Spouse and minor children physically relocate. Furniture, art, vehicles, pets — all move. The FTB will ask: where are your kids in school? Where do family events happen? (4) Texas driver’s license. Surrender CA license. Get TX license. (5) Texas vehicle registration. Transfer all vehicles to Texas plates. (6) Texas voter registration. Register to vote in Texas. Vote in Texas elections. (7) Primary banking in Texas. Move primary checking, savings, brokerage relationships to Texas branches or Texas-based institutions. Notify all financial institutions of address change. (8) Primary medical providers. Establish primary care doctor, dentist, specialists in Texas. Cancel CA providers. (9) Religious/social affiliations. Join Texas-based church, synagogue, mosque, country club, gym. Cancel CA memberships or downgrade to non-resident status. (10) Will and estate planning documents. Update will, powers of attorney, healthcare directives to reflect Texas residency. Texas-licensed attorney for estate planning. (11) Mailing address. All bills, statements, business mail to Texas address. No CA P.O. box. Notify employers, clients, vendors. (12) Phone number. Get a Texas area code phone number for primary use. CA area code phone signals continued CA ties. (13) Time spent in California. Limit physical presence to less than 183 days/year (otherwise you might be a CA resident under the day-count test independent of domicile). 90 days is safer. 30 days is best. Documentation. Create a contemporaneous ‘departure dossier’ showing the actions you took. Date-stamped photos of the Texas home with your belongings. Texas driver’s license issuance date. Texas voter registration confirmation. School enrollment confirmation. Lease or purchase documents. Bank account opening documents. Medical provider establishment letters. Common mistakes. Maintaining a CA business address. Keeping a CA bank account as primary. Spouse staying in California (the FTB will argue your domicile follows the family unit). Keeping CA driver’s license. Voting in CA election the year after the move. Returning to CA for more than half the year. Keeping the CA home as ‘temporarily vacant.’ Telling friends or social media you’re still a Californian. How long does the FTB chase? The FTB statute of limitations is generally 4 years from the return due date (extended to 6 years for substantial omission). Practically, the FTB sends residency audits 2-4 years after the alleged move year. The audit asks for documentation supporting the move. If your documentation is thin, the FTB will deem you still a CA resident and assess back taxes plus interest and penalties. Part-year residency. The year you move, you’re a part-year CA resident. CA taxes income earned while a CA resident (and CA-sourced income while a non-resident, like CA real estate gain or CA-located services). File Form 540NR. Allocate income by date. Once a real Texas domicile is established with the actions above and 6-12 months of consistent behavior, California’s chance of successfully recharacterizing you as a resident becomes low. But the documentation needs to be maintained for years. Convenience-of-the-employer trap. If you’re a W-2 employee of a California company while living in Texas, your CA wages may still be taxed by California under CA’s convenience-of-the-employer interpretation (though CA has historically taken a different position than NY here — discuss with a CA-specialist CPA). As a freelance developer, this isn’t usually an issue because you’re a contractor, not a W-2 employee. CA-source income after the move. Income from CA sources is still taxable to CA non-residents. Examples: CA real estate gains, CA-located rental income, services performed in CA, distributions from CA-formed entities for CA-source income. If your freelance work involves on-site work for CA clients (you fly in for meetings), the income for those days is potentially CA-sourced. Texas pros. No state income tax. No state intangibles tax. Lower property tax in many areas. Cheaper cost of living than coastal CA. Friendly business environment. Texas cons. Property tax can be high in certain counties (Austin metro, Houston metro). Sales tax 6.25% state + up to 2% local. Hot summers. Hurricane risk in some areas. Net benefit. A solo developer earning $300K with 9.3% CA marginal state rate saves ~$28,000/year by moving to Texas. Over 10 years, that’s $280K. Not bad for a successful relocation. But the IRS still wants its full share of federal tax, which is the bigger number for most developers. Specific California planning tactics. (1) Document the move with a contemporaneous ‘departure binder’ showing all the actions taken. (2) Sell the CA home or get a long-term tenant on a real arm’s-length lease. (3) Don’t return to CA for more than 30-45 days/year in the first 2 years. (4) If your spouse works in CA, the FTB will argue your domicile follows your spouse. Both spouses should move together. (5) File Form 540NR for the part-year of the move with careful allocation of income. (6) Some taxpayers preemptively obtain a private letter ruling from the FTB confirming the change of residency — expensive but provides certainty. Trust planning. Even after a successful CA exit, distributions from CA-irrevocable trusts may be CA-source income for the beneficiary. Trust residency rules are complex. CA-resident beneficiaries of out-of-state trusts may pay CA tax on the distribution. Plan around this if relevant. Exit timing. If you have a large pending event (sale of business, RSU vesting, large project completion), time the residency change BEFORE the event. CA-source income is taxed by CA regardless of residency; non-CA-source income at the time of receipt isn’t. So selling an out-of-state business after the move avoids CA tax. Selling a CA business before the move pays full CA tax. Wait for the move and then sell, when possible.