Enterprise is not a third product line. It packages the same two workflows for teams that need named analyst handling, governed delivery, visibility for stakeholders, procurement review, and contract-scoped support.
Default wedge
Governed Deep Search
Delivery model
Visible analyst layer
Customer surface
Visibility portal
Packaging paths
Start with the workflow you already sell publicly. Enterprise changes the operating model around it, not the product truth underneath it. Governed Deep Search is the normal first path; Monitoring-led and mixed programs follow when the operating need is already recurring or cross-functional.
Deep Search-led
The default enterprise entry point for sensitive investigations that need named analyst handling, shared review, and export-ready delivery.
Custom scoped pricing
Monitoring-led
Use this when the team already knows the targets and needs recurring review, analyst triage, alert routing, and escalation ownership.
Custom monitored-scope pricing
Mixed
Package both workflows under one governed operating model when investigations and ongoing monitoring need to live together from day one.
Custom unified-program pricing
Named analyst ownership, stakeholder review, and guided delivery for teams that cannot run sensitive cases from one reviewer seat.
Architecture review before procurement so export formats, support ownership, and operating constraints are agreed up front.
Plan what enterprise stakeholders will see after rollout: status, reports, alerts, and follow-up requests without promising a separate enterprise surface.
Security and support commitments are finalized during scoping instead of being implied by generic public packaging claims.
Escalation signal
FAQ
No. Enterprise packages the same Deep Search and Monitoring workflows for institutions that need named analyst handling, governed delivery, stakeholder visibility, and contract-scoped support.
Move to Enterprise when the workflow becomes multi-user, governance-sensitive, analyst-assisted, or procurement-driven. If one reviewer can handle the work alone, self-serve is usually the right starting point.
Governed Deep Search is the standard first path because sensitive investigations usually create the first need for shared review, export-ready delivery, and named ownership. Monitoring is added when the case becomes an ongoing program.
No. This page describes packaging and scoping. Export, integration, support, and availability commitments are finalized during architecture review and contracting.
No. Enterprise requests start with architecture review and commercial scoping. Contract, invoice, access, and support terms are approved before enterprise delivery begins.
No. Enterprise customers get a governed operating model and a visibility-first customer surface, not a separate enterprise environment or product family.
Yes. Mixed programs package both workflows under one agreement when investigations and ongoing monitoring need to live under one governed operating model from the start.
Next step
Use architecture review to decide whether your team needs governed Deep Search, governed Monitoring, or both under the same enterprise agreement, then confirm the analyst layer and visibility surface before rollout.