← Insights
Guides

Keep / Consolidate / Cut / Rebuild Scoring Explained

How to score each SaaS tool as keep, consolidate, cut, or rebuild — decision criteria, common mistakes, and how it ties to Autonode's interactive audit checklist.

HDHarshwardhan Deshmukh//6 min read

Scoring is step four of the audit — after inventory, cost, and data flows. If you score early, you will cut the wrong things. Use the interactive checklist once the map exists.

01 · The four buckets

Definitions

Score Meaning Typical signal
Keep Unique value, acceptable cost, low glue pain Team lives in it daily; hard to fake
Consolidate Overlaps another keep/rebuild target Two CRMs, two email tools, dual calendars
Cut Low use, low dependence Dormant seats, zombie Zaps, unused seats
Rebuild High dependence, poor ownership, high middleware Site/CRM/email you rent but revolve the business around

02 · Mistakes

What warps the score

  • Scoring before mapping integrations
  • Using sticker price instead of loaded cost (invoice guide)
  • Marking everything rebuild because you are angry at the bill
  • Marking everything keep because change is scary

03 · After you tally

Act in order

  1. Cut true zombies (quick cash)
  2. Consolidate overlaps into the keep/rebuild target
  3. Sequence rebuilds (usually site + CRM + email)
  4. Re-run the Stack Sprawl Index

Common questions

Before you ask.

What does rebuild mean in a SaaS audit?

Replace a rented capability with software you own — usually site, CRM, email, or automation — when utilization of the rented platform is low but business dependence is high.

What is consolidate?

Merge two overlapping tools into one system of record so you stop paying twice and stop reconciling data by hand.

HD
Harshwardhan Deshmukh
Systems & Growth

Harshwardhan writes about owned software systems, SaaS cost, and the operating layer behind modern marketing stacks at Autonode.

HD
Harshwardhan Deshmukh
Systems & Growth
Keep reading