TL;DR: Public sector identity verification programmes can stall after award when customer success teams cannot read contracts, navigate governance, or advocate internally, according to Incode. For agencies, the platform is only part of the decision; the operating team can determine whether adoption, milestones, and option-year outcomes hold together.
NHIMG editorial — based on content published by Incode: Public sector IDV succeeds or fails on customer success quality
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
Questions worth separating out
Q: How should agencies evaluate an IDV vendor beyond biometric performance?
A: Agencies should evaluate the vendor's operating model, not only the verification engine.
Q: What fails when the support team does not understand public sector governance?
A: Delivery slows because issues move through internal handoffs instead of being owned.
Q: How can procurement teams measure whether customer success will actually help?
A: Look for evidence that the account team can explain governance artefacts, handle escalation without relaying every question, and translate programme feedback into product action.
Practitioner guidance
- Score the vendor operating model alongside the platform Add customer success staffing, public sector experience, escalation authority, and contract literacy to the same scorecard used for biometric accuracy and fraud coverage.
- Test contract fluency before award Ask the proposed account team to walk through CLINs, QASP deliverables, acceptance criteria, and modification triggers without internal translation.
- Verify named escalation ownership Require a clear named path for issues that reach engineering, legal, or finance, and confirm the account executive remains engaged after go-live.
What's in the full article
Incode's full article covers the operational detail this post intentionally leaves for the source:
- The five procurement questions the vendor recommends using in RFPs and source selection.
- Examples of how public sector customer success should respond inside governance reviews and contract milestones.
- The article's explanation of how account executives and customer success managers should work together across months three, six, and 12.
- The vendor's view of how agencies should test advocacy capacity when larger commercial accounts compete for engineering attention.
👉 Read Incode's analysis of public sector IDV customer success and procurement risk →
Public sector IDV customer success: what procurement teams should test?
Explore further
Vendor team quality is part of identity assurance, not a post-contract convenience. In public sector IDV, the delivery team becomes part of the assurance model because it controls whether incidents, milestones, and change requests are handled with the required discipline. A technically strong platform can still fail an agency if the support function cannot interpret contracts or escalate internally. Practitioners should treat the vendor operating model as a governance dependency.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time.
A question worth separating out:
Q: Who is accountable when an IDV programme stalls after award?
A: Accountability sits with both the buying agency and the vendor team, but the agency must define the support expectations clearly in procurement and governance documents. If the contract does not specify who owns escalation, communication, and delivery follow-through, the programme can stall without a clear recovery path.
👉 Read our full editorial: Public sector IDV succeeds or fails on customer success quality