Notifications
Clear all
Topic starter
25/06/2026 5:23 pm
TL;DR: Customer success is not an add-on but a core part of identity programme outcomes, according to SailPoint, which points to 500 customer success professionals, 100,000 Compass Community members, and 7,000 developers as evidence of scale and engagement. The real takeaway is that IAM value now depends on execution, education, and lifecycle support, not deployment alone.
NHIMG editorial — based on content published by SailPoint: What makes SailPoint different? Our relentless pursuit of customer success
By the numbers:
- SailPoint says it has over 500 customer success professionals dedicated to customer outcomes.
Questions worth separating out
Q: How should identity teams measure whether customer success is improving programme outcomes?
A: Measure whether the programme is reducing operational risk, not just whether implementation tasks are complete.
Q: Why do identity programmes often weaken after go-live?
A: They weaken when governance is treated like a project milestone instead of an ongoing operating model.
Q: What do security teams get wrong about identity vendor support?
A: They often treat support as a service wrapper instead of part of the control environment.
Practitioner guidance
- Tie identity governance to outcome metrics Track review completion, remediation speed, entitlement drift, and exception volume together so the programme can show whether risk is falling rather than only whether tasks are closing.
- Build post-go-live operating cadences Set a recurring rhythm for policy tuning, certification follow-up, and connector checks so identity controls do not decay after initial rollout.
- Use community knowledge to reduce implementation friction Capture repeatable patterns from administrators, developers, and reviewers so common identity issues do not have to be solved from scratch in each business unit.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- How the customer success organisation is structured across support, education, and community functions
- Examples of the digital onboarding and self-service processes used after deployment
- The specific ways SailPoint describes tailored implementation support for different customer needs
- How Identity University and related enablement resources are positioned for practitioners
👉 Read SailPoint's blog on customer success in identity security →
Customer success in identity programmes: what teams actually need?
Explore further
25/06/2026 6:01 pm
Identity success is an operating model problem, not a deployment problem. The article is really about the gap between installing identity tooling and sustaining identity governance. Organisations often overestimate go-live readiness and underestimate the work required to keep policies, certifications, and lifecycle decisions current. The practitioner lesson is to judge identity programmes by operating discipline, not implementation completion.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, according to The State of Secrets in AppSec.
A question worth separating out:
Q: How can organisations keep identity controls effective as the environment changes?
A: By building a continuous operating cadence for policy review, entitlement cleanup, and reviewer education. Identity environments change constantly through new applications, role changes, and lifecycle events, so controls must be revisited regularly if they are to remain accurate and enforceable.
👉 Read our full editorial: Identity programme success depends on service and lifecycle execution
