The SaaS Playbook Has a Citation Problem

SaaS leaders regularly make expensive decisions using familiar numbers: deploy weekly, target DORA Elite performance, reserve 10% of every cycle for technical debt, and keep R&D spending near a fixed percentage of revenue.

But where did those numbers come from, and do they describe a company like yours?

Our research report, The Evidence Gap: A Critical Audit of the SaaS Product Engineering Playbook, traces five repeated engineering beliefs back to their evidence. It shows how a nuanced finding becomes a conference soundbite, loses its caveats in a blog post, and eventually reaches a board deck as an industry rule.

Inside the report, readers will see which principles are supported by large, multi-year research, which depend on company stage or go-to-market model, and which originated as one company’s internal practice before being generalised.

The report examines DORA performance tiers, deployment frequency, AI-assisted coding, product-led MVP doctrine, technical-debt allocation, R&D benchmarks, and the architectural trade-off between multi-tenant efficiency and incident blast radius.

It also introduces a Calibration Model for testing borrowed benchmarks against your own business. Instead of asking whether a number sounds authoritative, leaders learn to examine its source, sample, date, company stage, commercial motion, risk profile, and intended outcome.

The conclusion is not that engineering benchmarks are useless. It is that good evidence becomes dangerous when its label disappears.

Before putting another industry number into your roadmap or board deck, find out what it measured.

[Download The Evidence Gap Research Report →]