Skip to main content
Felixfusion

ENGAGEMENT TIERS - Three ways to run the engine.

Pilot first, scale after. Pricing is fixed for the single-engagement pilot and rate-card based for ongoing programmes. We do not publish per-seat numbers because the work is not per-seat.

POSTURE · PILOT-READY · CUSTOMER-VPC OR DEDICATED · CONTRACT REVIEW SUPPORTED
TIER.01 · PILOT

Single-Engagement Pilot

Fixed-fee · 4–6 weeks

One named artifact for one named buyer. The cleanest way to validate the engine on a real decision under your governance.

  • Customer-VPC deployment by default
  • One signed deliverable: IC memo, DD pack, compliance matrix, or award memo
  • Named engagement lead on our side
  • Senior-analyst sign-off on every external artifact
  • Audit log + provenance trail exportable
  • Vendor security questionnaire response within 5 business days
MOST PILOT INTEREST
TIER.02 · PROGRAMME

Programme Subscription

Annual · Rate book

For teams running a multi-asset BESS build-out or a continuous capture programme. Sourcing or Athena standing ready on every pursuit.

  • Everything in Pilot
  • Continuous supplier-index or market-surface refresh
  • Library build-out from your archive (one-off ingestion)
  • Compliance matrix on demand across every active RFQ or DD
  • Quarterly post-engagement scorecard refreshes Shortlist weights
  • Named procurement / IC counterpart access
TIER.03 · PLATFORM

Enterprise Platform

Custom · Talk to us

For organisations integrating the runtime across multiple teams. Data residency, custom deployment, and SLA-backed delivery.

  • Everything in Programme
  • Multi-team deployment with team-scoped audit
  • Customer-managed keys (CMK) supported as default
  • Region-locked data residency commitments
  • SLA on questionnaire response, support ticket triage, and incident notification
  • Custom subprocessor approval and change-notice cadence

All tiers run inside a customer-isolated deployment context. We do not publish a unit price because the work is not unit-priced — every engagement is scoped against the artifact you actually need to sign.