Resources
Thinking on independent technology intelligence, technical due diligence, and the decisions that shape software organizations.
Why high-stakes software decisions — M&A, AI governance, modernization, board oversight — need a continuous, evidence-based read of the system, independent of the team that built it.
You were hired for your judgment, then handed a system you didn't build and a CEO who wants a plan by Friday. How to back the read with evidence, not opinion.
Codebases don't become unmaintainable because the code degrades. They become unmaintainable because the decisions behind them walk out the door with the people who made them — and how to recover them.
Most technical reviews tell you what a system looks like today. An engineering system audit excavates why it became that way — before a migration or acquisition makes the gaps expensive.
PE firms are asking the wrong question about AI. The question isn't how to protect your portfolio from disruption. It's how to use AI to make it 2-5x more valuable.
Every engineering organization has heroes. The ones who built the critical systems. The ones everyone asks. Here's why that's a risk.
Six hours, a PDF, done. The checkbox approach to technical due diligence is leaving millions on the table. Here's what actually matters.
You inherited a codebase, a team, and years of decisions you weren't part of. Here's how to get operational intelligence fast.
Everyone knows they have technical debt. Almost nobody knows how much it's actually costing them. A framework for measurement.
Why we don't deliver dashboards or scores. The origin of our approach to technology intelligence.
You ask "how's the tech?" and get reassurance or headcount requests. Neither tells you what you need to know. Here's why.
