Scale by subtraction
High output comes from what you remove, not what you add.
Most software companies grow by adding features, teams, and process. Each addition creates friction that slows the next one. Scale by subtraction flips that logic: find what has no demand, remove it, and let the system breathe.
Remove before you add
When coordination costs compound, hiring and process rarely fix the problem. They add more surface area. Subtraction means making the cost of complexity visible, deciding what no longer earns its keep, and removing it without breaking what customers still pay for.
Beamer applies this philosophy in products and consulting: measure the Sync Tax, map connascence, and treat modularization as a capital decision—not a vibes-based refactor.
See the tax
Name the hidden multiplier on every change so leaders and engineers share one language.
Decide what goes
Tie removal to demand and margin, not politics or habit.
Remove safely
Use strangler patterns and clear contracts so subtraction doesn't become downtime.
The book
The Engineering Tax
Scale by subtraction is the idea. The Engineering Tax is the playbook: economic language for CEOs, structural tools for CTOs, and a repeatable way to find invisible costs that destroy software product margins.
Revealing the Invisible Costs That Destroy Software Product Margins.
Who this is for
Leaders who want a philosophy that connects product strategy to engineering cost—not another framework deck.
Teams ready to measure complexity, subtract waste, and ship from a leaner system. Start with the book when you need the full economic model.
What is scale by subtraction? · Scale by subtraction for CTOs