90-Day Pilot
Structure
5-phase, 13-week production pilot. No lock-in, no penalty to exit. Pilot begins within 2 weeks of architecture call. All deliverables written and dated before work commences.
5-Phase Production Timeline
Initial integration of CAIBots with your fraud platform, core banking system, and behavioral biometrics provider. No production traffic — test environment only. Architecture validation session with your technical team completes this phase.
CAIBots runs in parallel with your existing fraud workflow. Analysts continue using Actimize/Verafin as normal. CAIBots processes the same cases and produces HITL packets — but analysts only see them for comparison, not decision-making. No impact to production workflow.
Controlled UAT with selected fraud analysts. 10 structured scenarios covering all fraud typologies and regulatory obligations. Pass criteria defined before UAT begins. Analysts use CAIBots HITL packets for real decisions on agreed case subset.
All fraud analysts use CAIBots HITL packets for all decisions. Production workload, real cases, real regulatory obligations. Actimize/Verafin remains primary system of record. CAIBots enriches every case. Weekly operational metrics tracked against pilot success criteria.
Formal pilot close-out. Executive readout of all pilot metrics vs. targets. Go/no-go decision by client. If go-live: production handoff documentation, SLA agreements, model monitoring schedule, and examination-readiness certification.
10 UAT Scenarios with Pass Criteria
| # | Scenario | Fraud Type | Pass Criterion | Reg Impact |
|---|---|---|---|---|
| UAT-01 | Confirmed ATO · Wire Credential change + outbound wire + new device | Account Takeover | TXN-RISK >85 · Reg E clock started · SAR narrative assembled · HITL packet routed in <90 sec | Reg E · 31 U.S.C. §5318(g) |
| UAT-02 | BEC · Vendor Wire First-time payee + spoofed email + wire $50K+ | Business Email Compromise | GNN first-time payee detection · P0 priority assigned · FBI IC3 referral memo generated · HITL includes wire recall authorization option | SAR (31 U.S.C. §5318(g)) · IC3 |
| UAT-03 | Synthetic Identity · Bust-Out 6-month seasoning + rapid credit utilization | Synthetic Identity | Synthetic probability score >0.80 · Bust-out pattern confirmed by ACCT-STATE · SAR obligation determination correct | SAR |
| UAT-04 | Mule Network · 5+ Accounts Common device + structured P2P flows | Mule Account Network | GNN traversal completes <5 seconds · All mule accounts identified · Network SAR naming all participants generated | SAR Network (31 U.S.C. §5318(g)) |
| UAT-05 | Reg E Provisional Credit · Unauthorized ACH Unauthorized ACH pull · consumer account | Unauthorized Transaction | Reg E obligation confirmed by REG-COMP · 5 business-day clock displayed in HITL packet · HITL requires analyst credit decision | Reg E (5-Day) |
| UAT-06 | Zelle Fraud · P2P Scam Zelle payment under social engineering | P2P / Social Engineering | Correct Reg E determination (authorized vs. unauthorized · bank policy) · Analyst-ready memo with governing regulation citation | Reg E (complex) |
| UAT-07 | SAR Narrative Quality Blind rating by BSA Officer on 10 SAR drafts | All types | BSA Officer rates >85% of narratives as B-or-better on first draft without edits. FinCEN field completeness 100%. | SAR Quality |
| UAT-08 | HITL Gate Function Verify all 5 mandatory gates cannot be bypassed | All types | Attempt to complete any regulatory action without HITL approval fails at system level. Audit log captures all attempts. | HITL Safety |
| UAT-09 | Audit Trail Reproducibility Reproduce case evidence on demand | All types | Three sampled cases fully reproducible within 24 hours: all agent outputs, signal weights, regulatory citations, analyst decisions with timestamps. | Examination Ready |
| UAT-10 | Live AI · Novel Scenario Scenario 05 on institution-specific edge case | Custom | Live Claude API produces a coherent fraud narrative and HITL packet for a fraud type not in Scenarios 01–04. BSA Officer deems output useful. | Live AI |
Pilot Terms
You may exit the pilot at any phase gate with no penalty, no clawback, and no continuing obligation. The pilot is fixed-price and scoped in advance — we do not bill for work not yet delivered. If the pilot fails to meet agreed success criteria, we do not proceed to production billing. Our interest is production deployment, not pilot revenue.
Ready to Start the Pilot?
A 30-minute architecture call maps this timeline to your stack. Production pilot begins within 2 weeks of that call. All deliverables scoped and documented before work begins.