🚀 De-risk your evaluation

Paid Pilot

Fixed-scope, time-boxed evaluation with explicit success criteria and deliverables. Prove value before committing to production.

Evaluation Pilot

Fixed Fee pilot
2–4 weeks • Fixed scope

Priced to be less than 1–2 weeks of a sanctions ops team's cost. Fee confirmed after 30-minute scoping call; fixed once scoped. Pilot fee creditable against first-year contract (optional).

  • Dedicated sandbox environment
  • Integration with your test data
  • Up to 10,000 screening requests
  • Full evidence pack generation
  • Weekly progress calls
  • Final evaluation report
  • Signed evidence bundle as deliverable
Request Pilot →

📋 Pilot Timeline

Typical 4-week pilot structure

Week 1: Setup & Integration

Provision sandbox environment, configure API access, integrate with your test systems, define success metrics.

Week 2: Data Onboarding

Load your test party data, configure matching thresholds, run initial screening batch, review results together.

Week 3: Evaluation & Tuning

Measure FP/recall against your ground truth, tune thresholds, validate evidence generation, test edge cases.

Week 4: Report & Deliverables

Final evaluation report with metrics, signed evidence bundle, production recommendations, commercial discussion.

✅ Success Criteria

Explicit, measurable criteria agreed upfront

Before the pilot begins, we agree on specific success criteria. Typical examples:

Latency p95 screening latency under agreed threshold (e.g., 100ms)
False Positive Rate FP rate below agreed threshold on your test dataset
Recall Detection rate above agreed threshold for known matches
Evidence Verification All evidence packs pass offline verification
Integration Successful API integration with your test environment
Audit Readiness Evidence bundle acceptable to your compliance team

📦 Pilot Deliverables

What you receive at the end of the pilot

📊 Evaluation Report

  • Latency benchmarks (p50, p95, p99)
  • FP/recall metrics against your dataset
  • Threshold recommendations
  • Integration assessment
  • Production sizing guidance

📋 Signed Evidence Bundle

  • Sample evidence packs from pilot screening
  • ML-DSA-65 signatures (NIST FIPS 204) for all decisions
  • Authority snapshots used (source: official OFAC SDN)
  • Verification instructions
  • Audit-ready documentation

Externally verifiable: An external auditor can verify end-to-end without private vendor context (offline verification).

  • • Verifier included in evidence pack (versioned)
  • • Supported: Ubuntu 22.04+, Python 3.11+, OpenSSL 3.x
  • • Flow: manifest → signature verification → object-lock checks

🔧 Technical Documentation

  • API integration guide
  • Configuration reference
  • Threshold tuning guide
  • Deployment recommendations

📈 Commercial Proposal

  • Production pricing based on pilot volume
  • SLA terms
  • Support options
  • Implementation timeline

❓ Frequently Asked Questions

What data do I need to provide?

A test dataset of party names/identifiers you want to screen. Synthetic data may be used only for integration testing; performance metrics are reported only on (a) your test dataset or (b) a published evaluation dataset, with hashes and artefacts. No production PII is required for the pilot.

Can I use the pilot in production?

The pilot environment is for evaluation only. Production use requires a separate agreement. However, the evidence generated during the pilot is real and audit-grade.

What if the pilot doesn't meet success criteria?

We work with you to understand the gaps. If QuantumVerify isn't the right fit, you still receive the evaluation report and evidence bundle. No hidden commitments.

How quickly can we start?

Typical time from agreement to sandbox access is 3–5 business days. Complex integrations may require additional setup time.

✅ Go/No-Go Decision Output

At pilot end, we produce a clear decision recommendation:

✅ Proceed to Production All success criteria met
⚠️ Proceed with Mitigations Criteria met with noted adjustments
❌ Do Not Proceed Critical gaps identified

"Acceptable to compliance team" means: evidence packs with valid ML-DSA-65 signatures, verified authority snapshot hashes, documented retention proof, and successful offline verification by your team.

📋 What You Can Re-use Internally

All pilot deliverables are designed for immediate re-use by your procurement, compliance, and security teams:

  • Evidence pack + verification steps — audit-grade artefacts suitable for compliance sign-off
  • Evaluation report with hashed datasets — reproducible metrics for internal review
  • Go/No-Go recommendation — clear decision output for steering committee
  • Integration assessment — technical readiness for production planning

📈 Pilot → Production Conversion

If pilot success criteria are met, we offer a streamlined path to production:

Pilot fee credit100% creditable against first-year contract (optional)
Implementation timelineTypical 2–4 weeks from pilot completion to production go-live
Pricing modelVolume-based annual commitment or per-screening usage
Support tiersStandard (email) / Premium (dedicated Slack + SLA)

Ready to Start?

Contact us to discuss your pilot requirements and success criteria.

Request Pilot →