An enterprise identity verification platform at the Inflection Point.

38 million enrolled members. $900.8M 2025 revenue. Record Q4 2025 bookings, doubling YoY, inside a profitable public company. Vertical proof points across leading health systems, a federal healthcare agency, and a major telecom — where identity risk and compliance matter most. Regulatory infrastructure: HIPAA, NIST IAL2/AAL2, Kantara certified, FedRAMP Moderate In Process. The platform has moved from uncertainty to traction. The next move is from traction to conviction.

Federal is opening — FedRAMP Moderate In Process with a flagship federal agency as sponsor. Federal scale punishes improvisation. The compliance moat is about to become a growth lever. Healthcare is replicating — A flagship health system was the crack; Epic Toolbox is the playbook. The question: can the platform support 50 health systems without bespoke implementations? The public narrative is shifting from member scale to enterprise durability. Durability requires proof: NRR, contract velocity, platform leverage.

1. 01

   Sales ahead of product

   A flagship federal agency closed December 2025. FedRAMP In Process wasn't until April 2026, four months after contract close. The current motion: executive relationship creates trust, marquee deal closes, press release validates, product retrofits the commitment, customer success becomes the reporting layer, a new vertical leader is hired. The pattern repeats.

2. 02

   Manual partner evaluation

   Partners cannot run a single test without the company manually issuing credentials. Every pilot is bespoke. The result: a sales-cycle drag and a structural cap on how many partners can be in evaluation at the same time.

3. 03

   Narrow connector coverage

   Fast-path for Epic, Okta, Auth0. No pre-built connector for Workday, ServiceNow, or Salesforce. Each missing connector is either a deployment-time penalty or a deal the platform cannot serve cleanly.

4. 04

   No self-serve analytics

   Partners cannot see their own verification funnel. The CSM becomes the reporting layer — a structural cost on every customer relationship.

5. 05

   Unclear economics

   The platform is likely sub-10% of revenue. No public metric proves bookings convert to durable NRR. Without metric architecture, the executive team cannot distinguish good growth from expensive growth.

1. 01

   Product gate that defines safe commits does not exist

   Sales should know which commitments are standard, which require review, and which require executive sign-off. Today, the pattern is commit-then-build. The shift is to commit-within-capability or escalate-with-visibility.

2. 02

   Developer experience is treated as cost, not channel

   Sandbox, documentation, sample apps, partner dashboard should be treated as revenue infrastructure. DX is the mechanism that turns evaluation into pipeline without adding headcount.

3. 03

   Vertical product theses are undifferentiated

   Healthcare, federal, and workforce identity are not the same market. Each has different compliance, buyer psychology, and integration patterns. The product thesis should define which verticals are 'expand' vs 'defend' and what product gaps remain in each.

Public company momentum, executive sales velocity, certified compliance infrastructure. The constraint is not market validation. It is the absence of a translation layer between enterprise commitments and platform capability.

• Define product thesis by vertical — healthcare, federal, workforce identity each get their own 'expand' or 'defend' frame and a named product-gap inventory.
• Install a sales-product gate — commit-within-capability, escalate-with-visibility, no more commit-then-build.
• Build DX as a growth channel — sandbox, documentation, sample apps, partner dashboard as revenue infrastructure.
• Sequence the connector roadmap with a model weighing market coverage, implementation compression, and revenue contribution. The connector roadmap becomes the clearest signal of vertical strategy.
• Build the metric architecture — NRR by vertical, contract-to-go-live time, verification funnel rates, connector attach rate, partner contribution margin.

• Healthcare replication outruns implementation capacity

  MitigationConnector-first sequencing for the Epic Toolbox playbook. Self-serve sandbox to absorb evaluation load before implementation engineering is touched.

• Federal cadence collides with commit-then-build pattern

  MitigationSales-product gate installed before the next federal close. Federal scale punishes improvisation.

• Narrative shifts to durability before the metrics exist to prove it

  MitigationScorecard architecture in the first 90 days. The executive team needs the language to defend durability before public scrutiny intensifies.