Pilot-to-production path, support terms, and current identity gaps.

Recommended pilot sequence

Start with a narrow watchlist and a clear reviewer. Verify source context, alert fields, delivery route, false-positive handling, and escalation before expanding to a larger supplier or portfolio program.

• Week 0: security/procurement packet, watchlist shape, delivery route, and reviewer named.
• Week 1: first watchlist added, alert packet reviewed, webhook/API/email delivery checked.
• Weeks 2-3: tune watched names, severity expectations, suppression, and escalation owners.
• Week 4: decide whether coverage and workflow are strong enough for paid production use.

Support and SLA

Self-serve pilots use lightweight support. Enterprise terms can define support hours, initial response targets, incident notification path, escalation contacts, uptime expectations, and maintenance notice routing.

Admin onboarding

A customer should identify the organization owner, admin users, alert reviewers, webhook/API owner, procurement owner, and security-review owner before production use.

Identity requirements

Password accounts and role-aware organization administration are available today. SSO/SAML/OIDC, SCIM provisioning, MFA policy enforcement, and advanced lifecycle controls are not claimed as generally available and should be scoped before purchase.