PUBLIC PACKAGES

Buy the narrowest package that proves control.

Pricing is not organized around feature vanity. It is organized around the smallest deployment that can prove deterministic execution, replay visibility, and policy alignment in a real repository.

PACKAGE RULES

Login model No hosted login in the current phase
Deployment Private install or customer-controlled environment
First proof One real workflow with replay and audit visibility
ENTRY Quick Pilot smallest proof that demonstrates control
DEFAULT Team Pilot best fit when more than one workflow matters
GOVERNANCE Enterprise Pilot used when reporting and policy pressure shape the deal

PACKAGE CARDS

Choose the package based on execution scope, not on vanity feature count.

QUICK PILOT

USD 1.5k - 3k

For one repository, one workflow, and one technical owner who needs a fast proof.

  • 1 repository
  • 1 deterministic workflow
  • Replay and audit baseline
  • Short setup and operating guidance
Best for

Founder-led teams and small product groups testing fit fast.

TEAM PILOT

USD 4k - 8k

For one team and one repository that need multiple workflows under one execution standard.

  • 2-3 deterministic workflows
  • Onboarding and handoff
  • Review rhythm and pilot summary
  • Operator guidance for the team
Best for

Engineering teams ready to move from proof to operational consistency.

ENTERPRISE PILOT

USD 8k - 15k

For private install, stricter policy alignment, and stakeholder-facing reporting expectations.

  • Private install planning
  • Stricter policy alignment
  • Stakeholder reporting
  • Rollout planning after pilot
Best for

Platform, compliance, or security-sensitive organizations.

COMPARISON TABLE

Procurement should be able to see scope, boundary, reporting burden, and next-step risk at a glance.

PROCUREMENT VIEW

Package comparison for a first controlled rollout
scope governance reporting
Package Price Recommended Approval complexity Procurement fit Execution scope Control boundary Reporting surface Operator burden Next commercial move
Quick Pilot1 repo / 1 workflow USD 1.5k - 3k Use when the team needs a fast first proof with one owner. Low Fast founder or engineering approval, low ceremony, low stakeholder count. One repository, one owner, one workflow under deterministic control. Private install inside an existing team workflow without broad rollout. Replay baseline, audit visibility, short operator notes. Low. One team owner and short adoption path. Expand to Team Pilot if the first path proves operational value.
Team Pilot1 repo / 1 team USD 4k - 8k Default choice when more than one workflow or reviewer matters. Medium Standard engineering budget approval with operational stakeholders involved. One repository and 2-3 workflows under a shared execution standard. Private install with team-level policy, onboarding, and handoff rhythm. Replay surface, summary outputs, handoff guidance, review cadence. Moderate. Requires active owner plus team adoption discipline. Default path toward a deeper private rollout.
Enterprise PilotPrivate install focus USD 8k - 15k Use when governance, reporting, or stakeholder review shape the deal. High Security, platform, or compliance review is part of the purchase path. Private install planning with stricter policy and reporting requirements. Customer-controlled environment with narrow governance alignment first. Stakeholder-ready outputs, rollout planning, stronger review surface. Higher. Requires cross-functional review and tighter policy mapping. Use when governance pressure shapes the first deployment decision.
Decision rule Buy the smallest package that proves replay, review, and policy alignment.
Commercial bias Team Pilot is the default when more than one workflow matters.
Governance trigger Enterprise Pilot is used when stakeholder review changes the buying path.

Public pricing is shown as a range because workflow complexity, policy constraints, and reporting needs vary by customer. The delivery model itself does not change: private install, pilot-first, deterministic proof.

AFTER PACKAGE SELECTION

The next step is not a platform migration. It is a narrow, real proof.

01

Select the repo

One repository and one technical owner are locked before setup work starts.

02

Define the workflow

One or more workflows are chosen based on where execution variance hurts most.

03

Install and align

Runtime surfaces, tools, policy boundaries, and replay expectations are configured.

04

Review outputs

The team reviews replay, audit visibility, and next-phase rollout needs after the pilot.

COMMERCIAL LADDER

Buy the first proof first. Expand only after control is visible.

PILOT SETUP

USD 3k - 10k

Delivered inside a real repository with one workflow, replay setup, and working handoff.

  • Private install in customer environment
  • 1 workflow under deterministic control
  • Agent and tool alignment
  • Replay plus audit setup
  • Live proof with the customer codebase

INTEGRATION AND EXPANSION

USD 2k - 8k

Extend the first proof into additional workflows, stronger policy boundaries, and repo integrations.

  • Additional workflows
  • Custom graph design
  • Policy layer setup
  • Repository and tool integration work

SUPPORT AND OPERATION

USD 1k - 5k / month

For teams that want active optimization, replay analysis, and ongoing operating support.

  • Workflow optimization
  • Debugging and replay analysis
  • Runtime support
  • Continuous improvements

You are not paying for code alone. You are paying for controlled, reliable AI execution inside your own environment.

REQUEST A PACKAGE REVIEW

Use pricing as a filter, not as a substitute for workflow scoping.

The right package depends on repository access, technical ownership, workflow count, and governance pressure. The first commercial conversation should resolve those four things.

Request package review See pilot process

No external booking link is configured yet. Current fallback: hello@execinspector.com