I spent the last few months researching the economics of software engineering. Specifically, what happens to costs when a product grows past what one team can maintain.
The same pattern kept showing up. Teams spend more time coordinating than building. Changes in one module break unrelated parts of the system. Features take twice as long as they should, not because the code is hard to write, but because the code is coupled to things it shouldn't be coupled to.
I call it the Sync Tax. It's a multiplier on every engineering hour. A multiplier of 2.0 means everything costs twice as much as it should. A multiplier of 4.0 means you're burning most of your budget on coordination and firefighting, not on output.
I built a small API around it. You plug in a few numbers about your codebase and team structure, and it returns the multiplier plus a dollar figure. No credit card needed for the free tier.
There's also an MCP server if you want to hook it into Claude, Cursor, or any agent.
https://complexity-cost-calculator.beamercloud.com/ I'm curious what numbers people get when they run their own teams through it.