This guide is for anyone who just ran the Stack Sprawl Index and has a number, a label, and a rough annual cost. By the end you’ll know which band you are in, and whether this week’s work is tidying seats, mapping the flows, or auditing the whole stack.
The calculator is intentionally blunt. Five questions, about ninety seconds, rough numbers welcome. It is not a forensic audit, and it is not a published sample of fifty companies. It is a sprawl signal: enough to decide whether you are fine, drifting, or already paying for labor that never hits the software invoice. If you have not run it yet, start with the Stack Sprawl Index, then come back.
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. The five-step pass is How to audit your SaaS stack before you rebuild.
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 the emailed report, to the audit at the end of this page.
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.
02b · What early runs keep showing
Three patterns, before you trust the first number
Early runs of the Index, teardown work, and client audits keep landing on the same three patterns. This is a qualitative read, not a dataset with a sample size we can publish.
The bookmark bar is not the stack. The first count is the tools people can name. It misses contractor tools on someone else’s card, trials that converted and kept renewing, and apps authorized in Google Workspace or Okta that nobody remembers approving. Pull the SSO list and run it again. The gap is where the forgotten spend lives.
Support plus manual work often rivals the software, especially once the score is 61 or higher. The office manager who reads a form email and types it into the CRM is not on any software invoice. The solar teardown pattern put that re-keying near six hours a week. When that line rivals the subscriptions, you are renting people to operate software.
High scores and the form-to-email-to-CRM handoff travel together. Gyms and field-service companies rhyme here because the path is the same: a form notifies a person, a person creates the record, a person books the next step. The score tells you to look. The handoff is what you find.
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. The subscription is not the bill. That argument is made in full in You’re paying for middleware.
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 Index with honest ranges. Undercounting tools is the usual bias.
- Email yourself the report if you want a paper trail for the team.
- If you are Growing or higher, follow the audit guide above before you cancel or rebuild.
- If you are High or an owned-system candidate, bring the score to the audit at the end of this page.
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.