You ran the Stack Sprawl Index. You got a number, a label, and a rough annual operating cost. This guide explains what those outputs actually mean — and what to do with them before you cancel a single subscription or book a rebuild.
The calculator is intentionally blunt. Five questions, about ninety seconds, rough numbers welcome. It is not a forensic audit. It is a sprawl signal: enough signal to decide whether you are fine, drifting, or already paying for middleware labor you have not put on the invoice.
If you have not run it yet, start there — then come back: Get your Stack Sprawl Index →
01 · How the score is built
Five inputs, one directional index
The Index combines what most teams already feel but rarely quantify in one place:
- Tool count — how many apps touch marketing, sales, or ops
- SaaS spend — monthly software on the card
- Support / agency spend — retainers and contractors keeping the stack alive
- Lock-in risk — how hard it would be to leave (CMS, CRM schema, Zap logic)
- AI readiness — whether the stack can absorb automation, or whether glue work still sits on a human
From those, you get a 0–100 Stack Sprawl Index, a band label, a monthly / annual operating cost estimate (software + support + estimated manual work), and a short recommendation.
02 · The four bands
What each label is telling you
Clean stack (≤ 30)
Your tool count and spend are in a range most small teams can still reason about. That does not mean zero waste — unused seats and one brittle Zap can still hurt — but you are not drowning in middleware yet.
Next step: Spot-check for dormant licenses and one painful handoff (form → CRM is the usual offender). Re-run the calculator after any big hire or campaign tool gets added.
Growing sprawl (31–60)
This is the most common band we see. The stack still “works,” but reporting is fragmented, someone is copying data between tools, and support spend is creeping up beside the SaaS line.
Next step: Inventory every recurring charge and every SSO app. Map the three highest-volume data flows. Do not rebuild yet — audit first.
High sprawl (61–80)
Software cost is no longer the whole story. Coordination cost — the office manager as integration layer, the agency retaining four platforms — often exceeds the subscriptions themselves. An owned system starts to create leverage: one CRM pipeline, one site form destination, one email layer.
Next step: Run the full five-step audit, then price migrate vs keep. Bring the Index printout (or emailed report) into an audit intake.
Owned-system candidate (81+)
The stack is likely the bottleneck. You are paying for seats you underuse, glue you do not own, and labor that never appears on the invoice. Staying put is a decision with a price; so is rebuilding — but at this band, not looking is usually the expensive option.
Next step: Book a structured audit. Use the calculator’s annual operating cost as the “rent” side of a three-year comparison against an owned build.
03 · Reading the cost line
SaaS + support + manual work
Under the score, the calculator shows something like:
SaaS $X/mo | N tools | Support $Y/mo | Manual $Z/mo
That last term is the one teams forget. Manual work is the hours spent moving leads, reconciling lists, and checking whether a Zap fired. It is the same pattern we tear down in the Webflow + Zapier + HubSpot cost article and the solar stack teardown: the subscription is not the bill.
If Support + Manual is larger than SaaS, you are not buying software — you are buying people to sit between software. That is the definition of sprawl worth fixing.
04 · What to do after you score
A short decision tree
- Run or re-run the Stack Sprawl Index with honest ranges (underestimating tool count is the usual bias).
- Email yourself the report if you want a paper trail for the team.
- Browse free tools on /tools — more invoice and checklist tools are on the roadmap.
- If you are Growing or higher, follow the audit guide before you cancel or rebuild.
- If you are High or Owned-system candidate, start an audit intake with your score in the notes.
Conclusion
A score is only useful if it changes the next week
The Index will not cancel HubSpot for you. It will tell you whether this week’s work should be “tidy the seats,” “map the flows,” or “stop guessing and audit the whole stack.” That is enough — if you act on the band you are in.
Run it again after every tool you add. Sprawl is quiet until the score is not.