From our SaaS audits
What we find inside SaaS companies
Patterns from the technical due diligences we run for investors and boards.
Investor
Why AI makes engineering teams smaller, but not simpler
AI is changing what small teams can ship, boilerplate gone, prototypes faster, experimentation cheaper. But lower costs of building don't mean lower costs of building the wrong thing. It just means you can do it faster.
AI didn't change the economics of software engineering
AI made writing code faster, but the real economics of software engineering were never about typing code in the first place.
A founder's commitment to their engineering team
Founders juggle endless demands, investors, sales, suppliers, and employees, all while building the plane mid-flight. But with engineering often being your biggest expense, there's one responsibility you can't delegate: ensuring your team builds the right thing.
The unbundling of engineering value (Part 2)
AI won't make software engineers redundant. It will expose what engineering was always supposed to be about: understanding systems, not just writing code.
Brute force approach to achieve AGI
The race to AGI increasingly looks like brute-force scaling funded by a circular loop: chip makers invest in AI labs, AI labs buy their chips, valuations rise, repeat. Are we building intelligence or inflating a bubble?
The unbundling of engineering value (Part 1)
Here's part one of a post I shared with our team on the radical change and evolution of our jobs. AI won't make software engineers redundant. It will expose what engineering was always supposed to be about: understanding systems, not just writing code.
Communicate or be micromanaged - the CTO edition
CTOs often come from engineering backgrounds and, particularly when newly promoted, tend to focus on what they know best, the technology. While this is understandable given their previous success, technology is rarely the hardest part of the CTO role.
The full-stack enigma
Early-stage startups want full-stack unicorns who can do it all on a tight budget, but asking one dev to wear every hat is less strategic hiring and more duct-taping a rocket and hoping for the best.
On the imminent retirement of the keyboard - the future of software engineering
By 2030, nobody will write code anymore and here is why. The difference between agent-powered engineers and those who handcraft code is huge. Here's our prediction on software engineering.
The hidden cost of multiple repositories
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
The CTO's guide to AI adoption strategy
AI adoption fails when treated as a tool rollout. This guide covers the decision framework, team dynamics, economics, and mistakes from 190+ technical audits.
A guide to vibe coding vs AI-assisted development
Vibe coding or AI-assisted development? The choice isn't binary, but getting it wrong at the wrong stage will cost you. This piece breaks down when to embrace speed over architecture, when to take back control, and why the best teams don't pick sides.
How to introduce AI coding agents into your engineering team
AI coding agents draft code, write tests, and open pull requests autonomously. This guide covers the tool landscape, readiness signals, a phased rollout plan, and the team dynamics that make or break adoption.
AI code review tools: what works, what doesn't, and how to set it up
AI code review catches what humans miss and misses what humans catch. This guide compares the tools, shows what each catches, and walks through setup without replacing human judgment.
The value of code review
Code reviews improve more than code quality. Done well, they shape better problem-solving, expose edge cases, and spread knowledge across teams. Learn how small, focused reviews and AI support help teams ship faster with confidence.