What happens when the thing that looks like a financial problem is really an engineering problem, and the thing that looks like an engineering problem is really a policy problem? That is the trap many companies, and now many software founders, are walking into at the same time.
In business, we love the fantasy of the silver bullet: a partnership, a tax election, an outsourcing move, a reorganization, a fundraising round, a clever accounting treatment. Anything that lets us dodge the ugly center of gravity. But there are moments when the silver bullet is not just insufficient. It is a distraction that delays the only move that matters: building a better product faster than the pressure closing in on you.
That is the deeper connection between product crises and tax policy shocks. Both test whether an organization is willing to confront reality directly, or whether it will spend its remaining energy looking for loopholes. In one case, the enemy is a faster rival. In another, it is a tax rule that turns software labor into a five year asset. In both cases, the seductive response is the same: find a workaround. The better response is harder: accept the constraint, then fight through it.
When the environment changes faster than your strategy, the most valuable skill is not cleverness. It is the ability to stop negotiating with reality.
Why the workaround instinct is so dangerous
The trouble with workarounds is not that they are always bad. The trouble is that they are emotionally relieving. They let leaders feel active while postponing the thing that actually determines survival. A company under attack by a stronger product can spend months on partnerships, acquisitions, packaging changes, and legal maneuvers. A startup facing a tax regime that turns current labor into future deductions can spend months exploring foreign subsidiaries, vendor conversion, and entity gymnastics.
All of those moves may have a place. None of them changes the central fact if the product is weak or the economics are distorted: .
This is why the metaphor of the bullet matters. A silver bullet implies a single elegant fix, a decisive trick. A lead bullet is heavier, slower, less romantic. It means repeated impact. It means the thing you wanted to avoid: grinding work, repeated execution, no magic, no shortcut. It is the admission that complex problems usually do not yield to one brilliant move.
The same logic applies to tax distortions. If the rules make software development look profitable before a startup has found product market fit, the temptation is to engineer around the rules. Move IP. Hire offshore. Switch to vendors. Reclassify work. Yet every workaround has a cost, and often that cost is paid in attention. The team begins optimizing the structure around the company instead of the company itself.
That is the hidden tax of bad policy: not only the cash it extracts, but the strategic fog it creates.
The real question is not “Can we avoid the hit?”
The better question is: What kind of organization becomes stronger when the hit cannot be avoided?
There are two broad responses to a brutal constraint. The first is evasive: move the pain elsewhere, soften the optics, preserve optionality, buy time. The second is confrontational: face the bottleneck, improve the product, restore the economics, and accept that this may require disciplined, unpleasant work.
The confrontational response is often mislabeled as stubbornness. In reality, it is usually the only path that compounds. If your server is five times slower, no partnership will save you for long. If your software labor is being treated as a deferred asset, no clever tax planning will make the underlying economics healthy if the business itself cannot absorb the shock. The underlying question is not whether you can survive this quarter. It is whether the company has enough intrinsic strength to justify its existence.
That sounds severe, but it is liberating. A business that cannot win on product quality, speed, or economics is not entitled to survive indefinitely through procedural acrobatics. It may deserve a pivot. It may deserve a different market. It may deserve a different structure. But it does not deserve to ignore the fundamental deficit.
The most dangerous moment is not when a company lacks options. It is when it mistakes a workaround for a strategy.
This is especially true in software, where costs are often invisible until they are reclassified. Developers can look like an operating expense when you are free to expense them, and like a capitalized investment when the tax code says otherwise. The business does not change, but the reported shape of the business does. That shift can produce absurd outcomes, such as a loss making startup appearing taxable, or a local team suddenly looking more expensive than an offshore team not because it is less productive, but because the rules treat its labor differently.
The result is not just accounting complexity. It is a distortion in what leaders choose to build, where they choose to hire, and how much courage they bring to the product itself.
There are two kinds of leverage: structural and substantive
A useful way to think about this tension is to distinguish structural leverage from substantive leverage.
Structural leverage comes from changing the frame around the work. It includes tax treatment, entity design, outsourcing, financing, partnerships, and legal architecture. Structural leverage can be powerful. It can reduce friction, extend runway, and create room to breathe.
Substantive leverage comes from making the actual thing better: faster software, better reliability, sharper positioning, stronger distribution, higher conversion, lower churn, tighter unit economics. This is the kind of leverage that survives contact with reality.
The mistake is to confuse the first for the second. Structural leverage can buy time, but only substantive leverage changes the game. A company under pressure often uses structural moves to protect itself, which is rational in the short term. But if those moves are not feeding into better execution, they become a kind of organizational sedative.
Think of a race car with a perfect pit strategy but a broken engine. It may look strategically sound from the outside. It may even lap competitors for a while under unusual conditions. But when the race gets serious, the engine decides the outcome. Software businesses are like that. In the short run, you can optimize taxes, staffing geography, and capital structure. In the long run, performance, product quality, and time to market decide who matters.
This is why policy shocks often expose weak companies faster than strong ones. A strong company can absorb the hit, because the underlying product keeps creating value. A weaker company experiences the shock as a threat to its survival, because it was already living close to the edge. The policy did not create the weakness. It revealed it.
Why “lead bullets” are the right metaphor for building software
The phrase “lead bullets” sounds unglamorous because it is. That is exactly why it works.
A lead bullet is not a workaround. It is sustained force. It is the willingness to spend effort where the market will actually feel it. In product terms, it means focusing on latency, reliability, performance, onboarding, retention, or whatever bottleneck is determining whether customers choose you or abandon you. In company terms, it means not pretending that a tax amendment, a new entity, or a vendor contract can substitute for product strength.
This is especially important in software because software businesses often live on narratives. The narrative can be that the market is huge, the platform is strategic, the technology is differentiated, the policy environment is temporary, the tax issue will go away. Narratives matter for fundraising and morale, but they do not process requests, retain customers, or close usage gaps.
A good mental model here is the three layers of company truth:
Narrative truth: what we say is happening.
Structural truth: what the legal, financial, and operational setup makes possible.
Mechanical truth: what the product and economics actually do under pressure.
Companies often spend too long at layer one and layer two because both are editable. Layer three is less forgiving. It is the server benchmark, the churn curve, the gross margin, the recruiting pipeline, the cash burn, the response time, the bug backlog, the tax bill. These are not interested in storytelling.
A company that “uses lead bullets” is one that stops spending all its energy on layers one and two and goes after layer three directly. That often feels less sophisticated. It is not. It is more mature.
The policy lesson is not just about taxes
Section 174 is a particularly strange case because it reveals how policy can reshape behavior without changing any technology at all. The software did not become less valuable. The labor did not become less productive. The innovation did not become less real. Yet the tax treatment changed the local incentives enough to push companies toward fewer hires, more layoffs, more vendor spend, and in some cases, foreign incorporation or IP migration.
That should worry anyone who cares about innovation, but it also teaches a larger lesson: systems that misprice investment distort the allocation of talent. When a country or a company makes it harder to invest in future capability, people do not stop investing. They redirect investment toward what is easier to justify in the short term.
That can mean using contractors instead of employees. It can mean shipping work abroad. It can mean building in jurisdictions with better treatment of R&D. It can also mean underinvesting in the very things that would create durable advantage, because the near term optics are worse than the long term payoff.
This is how bad incentives hollow out institutions. Not through one dramatic failure, but through a thousand small reallocations away from the hard thing.
The same dynamic exists inside companies. If leadership rewards only short term margin protection, teams stop doing the expensive work of improving the product. If leadership rewards only fundraising and narrative, they stop caring about performance. If leadership rewards only tax efficiency, they stop noticing that customers are leaving. The organization becomes elegant on paper and fragile in reality.
Every optimization has a shadow cost. The question is whether that cost lands on the edge, or at the center of the business.
Key Takeaways
Do not confuse a workaround with a strategy. A structural fix can buy time, but it cannot replace product strength or sound economics.
Identify your real bottleneck. If the core issue is performance, quality, or retention, focus there before spending months on legal, financial, or organizational detours.
Separate structural leverage from substantive leverage. Reduce friction where you can, but never let tax or entity design become a substitute for building something customers deeply need.
Watch for incentive drift. If a policy or internal rule makes the easy path more attractive than the valuable path, expect long term damage to capability.
Use pressure as a diagnostic. A company that becomes clearer and stronger under pressure is healthy. A company that becomes more evasive is probably hiding a deeper weakness.
The hardest truth: survival has a standard
In the end, the overlap between product crises and tax shocks is not accidental. Both force a company to answer the same question: Are we still good enough to deserve to exist?
That question sounds harsh because it strips away the comforting fiction that cleverness can indefinitely postpone accountability. But there is a gift in that harshness. It returns attention to what matters. If the product is slow, make it faster. If the economics are wrong, fix them. If the rules are distorted, adapt intelligently, but do not confuse adaptation with victory.
Some organizations discover that they need a new structure, a new market, or a new jurisdiction. Others discover that they simply need to stop running and start fighting. Either way, the lesson is the same: the answer will not come from a silver bullet. It will come from a thousand difficult, unglamorous, repeated actions aimed at the true constraint.
That is what lead bullets really mean. Not pessimism. Not brute force for its own sake. Just the recognition that in the moments that matter, reality only yields to sustained, directed effort.
And once you see that, you stop asking how to escape the fight. You start asking whether you have the courage to win it.
