Blog

KaaS Newsletter

Research on what AI changes in engineering delivery, for CTOs and VPs of Engineering at startups and scaleups. Every number cited.

We email you each new post. You can leave at any time. Privacy

Latest

  1. What does a Claude Code enterprise setup need first?A Claude Code enterprise setup is five controls an admin owns. Managed settings, plugins, review, metrics and a gateway, with a checklist to copy.
  2. Building an AI-native engineering team by what you checkAn AI-native engineering team is defined by what it checks, not what it uses. Four stages and the first change at each, for 20 to 150 engineers.
  3. Measure AI impact on engineering by delivery over activityTo measure AI impact on engineering, track lead time and change failure rate against your own baseline. A plan for teams of 20 to 150 engineers.
  4. Cost per merged change should count only surviving changesCost per merged change is the AI ROI number to bring your CFO: the whole bill over changes that survived, paired with stability, at 20 to 150 engineers.
  5. How to fix the AI code review bottleneckThe AI code review bottleneck comes from pull requests nobody verified before review. What to measure and change at 20 to 150 engineers.
  6. AI coding costs land in review and not on the invoiceAI coding costs per engineer are a small share of pay. Review time decides whether delivery rises, and how to measure it at 20 to 150 engineers.

Bring us the work that waits.

A 30 minute call with the founder about where AI should start in your company.