Managed Rollout Lane

Guided rollout with runtime included.

Use this path when you want decide to help implement policy routing, operationalize evidence, and run KPI-based rollout governance. Queue-in-a-Box includes Decision API runtime with guided onboarding. For API Team/Enterprise, managed rollout can be bundled in the same quote.

Sprint vs Queue-in-a-Box (plain definitions)

Sprint = one-time implementation project

Fixed 2-week scoped rollout for one queue. Outcome is encoded routing, KPI baseline/target, and go/no-go recommendation.

Queue-in-a-Box = guided production lane

Recurring runtime + monitoring + support with hosted queue intake and Ops portal handoff; this is not a one-time implementation package.

If you do not need managed implementation, skip Sprint and use API pricing directly.

Plans

Evaluate

Validation-only

$0 / evaluate

Test payloads and output contract before production commitment.

  • Scope: sandbox/runtime testing and live demo.
  • Usage: not production, non-SLA.
  • Next step: Sprint, Queue-in-a-Box, or direct API tiers for production rollout.
Queue-in-a-Box

Non-technical production lane

Custom / scoped

Hosted queue intake + implementation support + Ops portal handoff for non-technical teams.

  • Best fit: teams that want rollout help before full self-serve API ownership.
  • Expansion: add burst packs (+10k/+25k/+50k) for temporary monthly spikes.
  • Handoff: customer Ops portal unlock after first live checks are stable.
  • Includes: Decision API runtime lane plus implementation support.

Queue-in-a-Box links are loaded from runtime config when available.

Contract snapshot

Explicit difference: sprint is implementation services, Queue-in-a-Box is guided non-technical rollout, and API tiers are direct self-serve runtime plans.

Plan Price Delivery model Decision scope Support model Next step
Evaluate $0 Demo/sandbox validation No production usage Non-SLA Move to Sprint, Queue-in-a-Box, or API tiers for production
Kickoff Sprint $1,500 one-time Managed implementation services 2-week scoped rollout window Weekly operator readout during sprint Move to Queue-in-a-Box or API lane (Sprint itself is optional for API-only buyers)
Queue-in-a-Box Custom scoped Guided rollout + hosted queue lane Scoped queue volume with burst-pack expansion Implementation support plus Ops portal handoff Move to direct API Team/Enterprise or expand queue scope

Onboarding path

Step 1: Scope lock + owner alignment

Confirm queue boundaries, stakeholders, and target KPI table for rollout success criteria.

Step 2: Policy encode + routing map

Implement deterministic policy routing and evidence payload shape against your ticket/workflow surface.

Step 3: Controlled live ramp + readout

Run monitored production ramp and weekly readouts before expansion decisions.