Pricing

Pricing built for reality.

Everyone loves simple pricing. Vendors love it most, because it hides the messy part: variable usage costs, third party fees, and what it actually takes to run automation at scale. We separate cost into three buckets and we never blur them.

Three buckets, never blurred

You always know what is fixed and what varies.

Stable

Services and implementation labor. Fixed scope, fixed fee.

Recurring

Managed operations. Monitoring, tuning, and a developer day each month.

Variable

Tokens, SMS, voice, enrichment, and automation platform fees. Metered, with caps and alerts.

This protects you from surprise bills and protects us from pretending AI usage is free.

How to buy

Packages, not a consulting treadmill.

Fixed Fee Diagnostic

Two weeks. A fixed scope engagement that produces the prioritized Make.com scenario list, the integration and governance plan, and the ROI estimate. The correct first step for any serious build.

Fixed Scope Implementation

Four to eight weeks. Production scenarios, a test suite, demo recordings, a runbook, and 30 days of support. Fixed in scope and measured by acceptance criteria.

Milestone Rollouts

For complex environments. Delivery broken into milestones with acceptance at each gate.

Managed Automation Plan

Monthly. Monitoring, operations, one developer day, and vendor costs passed through. Production systems are not set and forget.

Hourly Blocks

Exception only. Minimum 40 hours. Used for out of scope fixes, not as a default. If you want predictable outcomes, you buy packages.

AI usage policy

Two options. The controls are mandatory either way.

Option A, preferred

You own and pay the vendor accounts directly. VaultedAI configures and operates inside your accounts. You get direct cost visibility and no rebilling.

Option B

VaultedAI pays the vendors and rebills usage with a stated platform fee for administration, monitoring, and governance overhead.

Cost controls, built into every engagement

Predictable under cost pressure.

  • Budget alerts at 70, 90, and 100 percent. Approval required at 90 percent.
  • Cap behavior set per client: hard stop or degrade mode.
  • Degrade modes documented per workflow: smaller model, cached response, reduced run frequency, high priority only, or human approval.
  • No surprise bills. Monthly statements include vendor invoices and usage reports.

Pricing that holds up in production.

Book a Diagnostic and get a scoped plan with the cost model laid out before you commit.