1,013 karma · joined August 1, 2013
Bluesky/Linkedin/etc: @mjwhansen
Wrote "Deploy Empathy" a book for developers & founders about interviewing customers: https://deployempathy.com
Founding organizer of the Small Software Business Alliance, an advocacy organization for tech companies to fix Section 174 (since stepped back, now run by advocacy professionals): https://ssballiance.org/
Congressional staff are required to keep tabs on everyone who calls in about an issue, so your time is well-spent.
The November 17 continuing resolution is our best chance to get this fixed, but only if enough members of Congress hear from their constituents about it!
Oh man, I feel this. I’ve been doing a lot of furniture refinishing lately as a hobby. One piece is 90% done and another is 80% done. I was working on the 90% done one today, and was planning to lacquer it today so I can put the hardware on tomorrow and be done… but instead I found a few places where I should really touch up the paint. That pushes back completing it at least one more day as the lacquer needs to sit for a day and… I just need to “ship” the darn thing. I realized it’ll probably never be 100% perfect, and that’s okay - done is better than perfect, as they say. Having the courage to create something that isn’t perfect is a skill.
Until 2022, companies had the choice between expensing and amortizing software development under Section 174. (Section 174 specifically calls out all software development as falling under that section.) So they would only time track when they wanted to get the R&D tax credit, which only covers a portion of software development activities. R&D tax credit software development is a much narrower scope than R&E software development. So it didn't matter until now.
So now small businesses and startups are being thrown into crisis because Congress has accidentally implemented policy that they haven't gotten around to fixing.
On the one hand, Section 174 clearly stipulates: "(3)Software development For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure." [1]
Section 174 R&E expenses are much more expansive than what qualifies under the R&D tax credit criteria. This article has a rundown of some of the activities included in 174. It's well beyond software or salaries -- it also includes things like market research. It also includes any expenses in connection with R&E, so for example time using a server for new features or new products would have to be amortized but maintenance (bug fixes) wouldn't. Even if a company files for R&D tax credits, they won't be able to offset this increase. [2]
Lastly, since Congress was widely expected to revert this before it took effect, the IRS didn't issue full guidance on how to implement it. They've never had to define software development before, but the interpretation that Big 4 accounting firms are taking is that it covers new products AND new features on existing commercial products, but not straight maintenance.
[1] https://www.law.cornell.edu/uscode/text/26/174 [2] https://www.forbes.com/sites/lynnmucenskikeck/2023/03/24/fiv...
https://www.wsj.com/articles/u-s-cfos-ask-congress-to-repeal...
Small companies don’t have CFOs.
It is especially problematic since it categorizes all software development as R&D even if we don't think of it as R&D. It's still unclear what the IRS considers "software development" since they've never had to define it, but the way most big companies with their well-paid accountants are proceeding are that it covers new product development AND new features on existing products, but not bug fixes/maintenance.
Let's take a simple example. Imagine a profitable small software company that made $1M in revenue last year, spent $700,000 on developer salaries and $200,000 on other expenses. Ordinarily, they'd be able to write off $900,000 and have a taxable net income of $100,000 that matches their actual profit. Assuming a tax rate of 25% that's a $25,000 tax bill.
Now, if you assume developers spent 50% of their time building new products and new features, and 50% of other expenses were on new features, only $420,000 of the salary costs and $110,000 of other expenses are write-offs. Their taxable income just went from $100,000 to $470,000.
Assuming a 25% tax rate, their tax bill is now $117,500 for 2022 — which exceeds their actual net income. This also inflates their quarterly tax payments for 2023, both of which hit right now.
This gets even worse for companies that aren't profitable, as they don't have the cash flow to cover a tax bill when they hadn't planned on having one at all. And given the current financial environment, it's hard for startups to get any kind of additional financing or funding.
This news article about our effort gets into this a bit more: https://technical.ly/civic-news/section-174-small-software-c...
Many accountants aren't even aware yet, meaning that some people who have already filed their business taxes for 2022 will end up owing the stratospherically higher bill PLUS interest and potentially penalties when the IRS notices (or their accountant notices and they re-file). The IRS starts charging interest as of the due date.
This includes servers and etc.
The changes to Section 174 are a massive problem for companies that build and sell software because now all software development -- which includes both building new products and adding new features to existing ones -- must be amortized. (Time and resources spent on fixes can still be expensed.)
If you're unfamiliar with the issue, I have an explainer thread here. This thread was fact checked by tax experts before posting. [1.1]
This includes salaries as well as other expenses, like servers. I did an example breakdown in this post.[1.2]
There's a lot of confusion with this and the R&D tax credit. Software development falls under what the tax code calls "R&E" (research and experimental), which is a much broader category than R&D. This article [2] does a good job explaining the difference.
Reverting Section 174 to allow companies to expense software development has widespread and bipartisan support in Congress, but unfortunately they feel no urgency on the matter. Big companies have been engaging with Congress on this for four years, but it still hasn't happened -- likely because it's seen as a big business issue even though it impacts companies of any size. This is where small software companies come in, and this letter specifically.
The goal of sending this letter on Tax Day is to make Congress understand that these changes are already making small software companies' tax bills skyrocket to the point where they may have to go out of business. It makes funded unprofitable startups profitable and taxable (and who can raise extra capital right now?!), and lean but profitable bootstrapped companies are taking out lines of credit just to pay their tax bills.
This is not a hypothetical issue. People are already receiving these astronomically-higher tax bills. [3,4] We have to join together so Congress knows this is an urgent problem.
NOTE: Please only sign this if you're a US citizen with a US company. There will be a point later when we'll bring others into the effort. But for right now, in order to get small businesses into the legislative conversation and shake things up and hopefully speed this along, we are focusing on founders at the moment. Small businesses are politically sympathetic but horribly disorganized as a bloc, and we have to change that first if we have any hope of this ever coming to a vote.
[1.1] https://twitter.com/mjwhansen/status/1640696365637419008
[1.2] https://www.indiehackers.com/post/this-us-tax-change-could-k...
[2] https://www.forbes.com/sites/lynnmucenskikeck/2023/03/24/fiv...
[3] https://twitter.com/LandonB32/status/1636026627887964162
[4] (Paywalled) https://www.wsj.com/articles/small-businesses-face-big-tax-b...
Most don’t have fancy degrees or companies on their resumes, though a few do. Many don’t have a college degree at all.
It’s definitely possible to build a profitable small tech business. We’ve been running our own company full-time for over 6 years now, and make a better living than we did as employees. It did take 3 years of patience as it grew from a side project (so we’re in year 9 now, all told).
FWIW self-funding a hardware company, especially when outside expertise is required, is definitely bootstrapping on hard mode. (Though I do know someone who bootstrapped a rocket company!) Most of us do software.
I encourage you to check out a MicroConf Local if you’re interested in learning more about the indie founder world.
Edit: on a more serious note as a seasoned baker: for the typical person who makes maybe one pie a year if that, blind baking your bottom crust and making sure your top crust has adequate ventilation will do more to impact the flavor of your pie than finding the perfect apples. (If you don’t vent the crust, they will steam and get mushy; if you don’t blind bake the bottom, it will be soggy.)
Fussing over apple varieties when your crust is underbaked is like spending weeks picking the perfect JS framework for a side project.
> First: Lift people up. When someone does something even remotely cool, it takes almost no effort to respond (or quote-tweet!) and say as much. > Second: Stay positive. Nobody is drawn to negative vibes on Twitter. > Third: Share what you’re doing because people are drawn to other people in motion. They’ll either relate or be inspired.