Three pilot postures, one shared scope
Every ClearOpspilot is six weeks, one production stream, and a drafted corrective action plan in your team's hands within a week. The three postures below differ on blast radius and detection envelope — pick the one that matches how much risk you want to take on for the trial.
Cautious keeps the detector narrow and every draft routes through a human reviewer before it lands anywhere. Standard tunes detection to your real cycle and lands drafts in the ITSM your team already works. Aggressive widens the envelope, runs a twice-weekly readout, and escalates across ITSM + Slack + paging when severity crosses the threshold.
Smallest blast radius
1 production stream · 6 weeks · weekly readout · narrow detection envelope
$500 / month
- Stream connector and baseline-learning window on your existing telemetry
- Narrow threshold-vs-baseline detection — only the high-confidence patterns flag
- Drafted corrective action plan per flagged anomaly — affected systems, root-cause hypothesis, next three steps
- Human-in-the-loop review for every draft before it lands anywhere
The default pilot
1 production stream · 6 weeks · weekly readout · threshold-vs-baseline tuned to your cycles
$500–$1K / month
- Stream connector and baseline-learning window on your existing telemetry
- Threshold-vs-baseline detection tuned to your daily / weekly / seasonal cycles
- Drafted corrective action plan per flagged anomaly — affected systems, root-cause hypothesis, next three steps
- Routing into the ITSM ticket your team already works (ServiceNow, Jira SM)
- Human-in-the-loop review for every draft before it lands in the ticket
- Weekly call to walk through the anomaly queue and adjust detection rules
Larger blast radius
1 production stream · 6 weeks · twice-weekly readout · broader detection envelope
$1K+ / month
- Stream connector and baseline-learning window on your existing telemetry
- Broader threshold-vs-baseline detection — wider envelope across the heavy stream
- Drafted corrective action plan per flagged anomaly — affected systems, root-cause hypothesis, next three steps
- Routing into the ITSM ticket your team already works (ServiceNow, Jira SM)
- Multi-channel routing — Slack + email + paging when severity crosses the threshold
- Faster escalation — twice-weekly readout and same-day turnaround for high-severity drafts
- Human-in-the-loop review for every draft before it lands in the ticket
Alerts/month hitting your detection system
Fraction, 0–1. Shown as 60% on first paint; raw value 0.60 in the field.
Stored in cents ($75.00).
$3,000.00 – $6,000.00
Six-month run at the published $500–$1,000/month band — the actual scope the customer purchases.
$288,000.00
320 hr/mo × $75.00 × 80% triage × 1.60 FPR overhead
Estimated 12-month savings (band)
$282,000.00 – $285,000.00
Low end assumes the pilot costs $1,000/month. High end assumes $500/month. Either way, savings are measured against twelve months of your current reactive spend.
Pilot band $500–$1,000 / month × 6 months. 80% triage rate; ~15 min per triggered alert; false-positive rate adds re-investigation overhead. The 12-month savings band compares that six-month pilot against twelve months of current reactive spend — extend with caution.
One-page PDF for sharing internally — same numbers the calculator shows above.
| Compare | Cautious | Standard | Aggressive |
|---|---|---|---|
| Anomaly volume | Low (narrow detection envelope — only the high-confidence patterns flag) | Medium (threshold-vs-baseline tuned to your daily / weekly / seasonal cycles) | High (broader envelope across the heavy stream — wider anomaly detection) |
| Verticals covered | One stream on your existing telemetry (no-bias / ‘one team’s data’) | One stream on your existing telemetry, tuned to your real cycle (same bias default) | Wider envelope across the heavy stream on your existing telemetry (wider bias) |
| Posture bias default | Restraint-first — every drafted plan lands through a human reviewer first | Balanced — tuned to your cycles, same default behavior as /early-access today | Breadth-first — broader detection on the heavy stream; multi-channel routing when severity crosses |
| Intake cadence | Weekly readout — what was drafted, what routed, what is next | Weekly readout (twice-weekly on request) | Twice-weekly readout plus same-day turnaround on high-severity drafted plans |
| Human-in-the-loop approvals | Every drafted plan is reviewed by a human before it lands anywhere (no auto-landing) | Every drafted plan is reviewed by a human before it lands in the ITSM (ServiceNow / Jira SM) | Every drafted plan is reviewed, then multi-channel escalation routing into Slack / email / paging |
| Alerting channels | Drafted plans communicated in the readout; no live paging, no Slack / email escalation | Routing into your ITSM ticket (Slack and email not added at this posture) | ITSM + Slack + email + paging when severity crosses the threshold (your team still receives, only the channels grow) |