About
I've spent more than twenty years building software, long enough to see the same pattern in company after company. Teams add features and integrations customers want, but when new work is tightly coupled to everything already there, the cost shows up twice: more moving parts on the technical side, and more people coordinating on the human side. That coordination overhead is a cost almost nobody counts, even though it's often the larger of the two.
I'm based in Warsaw, where I write and speak about those costs: how to find them, how to measure them, and what it takes to grow a software business without quietly drowning in expenses nobody ever asked for.
What I Do
I put numbers on the true engineering costs of software, because they're rarely small and they're real money. As founder of Beamer I'm building the SaaS that measures those costs, and my book The Engineering Tax lays out how to do it yourself. The premise behind both is simple: customers demand product performance, and any engineering cost that doesn't trace back to that demand drains profitability. Every technical decision is also a business decision, and the good ones make that impact visible before it shows up in the margins.
The Engineering Tax
I'm writing a book about the unmeasured costs that eat software product margins: the coordination overhead, the structural friction, and the engineering costs that never satisfy customer demand. The Engineering Tax gives engineering and business leaders a shared way to measure those costs and decide what's worth keeping.
Contact
Curious what your systems are actually costing you, or want to talk about scaling by subtraction? Reach out below.
Let's exchange numbers
I don't publish my number openly, but you can request it here.