Lead gen and retainer, in one tool.

Is each person on the cheapest defensible seat? Core vs Sales Hub vs Service Hub vs View-Only, with savings math and confidence on every recommendation. Service work counts too: a support agent working a ticket queue keeps their seat instead of reading as idle. Plus marketing-contact bloat: marketable contacts that never open or click but push you into a higher contacts tier.

Unowned records, records owned by deactivated users, stale records, missing critical fields, property sprawl. Across contacts, companies, deals, tickets and custom objects, with RAG bands. Open deals that have sailed past their own close date, measured against the open pipeline rather than the whole object, because every forecast built on them is wrong. Open deals stuck in the same stage for a quarter or more, which a last-modified check never sees because automation keeps touching the record. And how many of your own custom properties carry no description at all, which is how a field nobody recognises survives for years. Marketing assets too: emails declaring one language under two codes split your sends across two translation sets, so where only one code is translated the preference centre and unsubscribe text go out in the portal default instead of the language the email was written in.

Super-Admin proliferation, admins inactive in the window, and stale grants (deactivated users still flagged Super Admin). Plus the automated actors, workflows, connected apps and integrations, already writing to the portal, counted per source. RAG-banded and feeding the health score.

Sequence sends that will fail: a fixed sender who was deactivated or whose connected inbox dropped. Workflow notifications that reach nobody, because the named user or team is gone or the record owner they address is missing. Owner rotations whose team pool holds nobody with the seat HubSpot requires to assign. Plus orphaned sequences, workflows left switched off and abandoned, and the agent-readiness collision surface: which properties enabled workflows already write. Partial because this is the API-readable slice of HubSpot's automation issues, not the whole of it.