The Stack Sprawl Index was built to make sprawl discussable in ninety seconds. We do not yet have a polished “N=50 audits” dataset — and we will not invent one. Here is what early runs, teardown research, and client work are already teaching us about how people use the score.
01 · Pattern: undercounted tools
The bookmark bar is not the stack
Teams routinely omit contractor tools, “free” trials that converted, and apps authorized in Workspace but paid on a personal card. The Index rewards honesty: if your score feels low but your week feels chaotic, re-run with the SSO list open.
Guide: What your Stack Sprawl Index means
02 · Pattern: Support + Manual ≥ SaaS
The invoice is incomplete
When people enter realistic support retainers and weekly admin hours, the result screen often shows coordination cost matching or beating software. That is the middleware thesis in calculator form.
Next tool: /tools/saas-stack-cost
03 · Pattern: high scores and handoffs
Form → email → CRM is the tell
High sprawl bands cluster with the same architecture: marketing site forms that email a human, a CRM that never sees the lead automatically, and Zaps that paper over the gap. Gym and solar teardowns rhyme for a reason.
Score the pieces: /tools/saas-stack-audit · then /tools/own-vs-rent