Heard Agile was rolling this out and the hype was all about "cloud-native pricing" and "breaking free from per-seat tyranny." Sounds great until you realize you're just trading one set of handcuffs for another, likely designed by actuaries.
I pulled the trigger on a trial for a lightweight internal tool. The promise: pay for API calls, storage, and active contacts processed. No fixed seats. Here's the config I had to write just to *estimate* a monthly bill, because their dashboard is "real-time" but their pricing calculator is fantasy.
```yaml
# My 'estimate-the-estimator' config
resources:
api_calls:
- type: "crm.object.create"
volume: 5000 # monthly
cost_unit: 0.0025
- type: "workflow.trigger"
volume: 20000
cost_unit: 0.00075
storage:
contact_records: 15000
file_storage_gb: 12
active_contacts:
# 'Active' defined as touched in last 30 days. Surprise!
threshold: 30
count: 4200
```
Ran this for a month. The bill was 22% higher than my naive projection. Why? Because "workflow.trigger" isn't just the execution—it's each condition evaluation *and* each action step as separate counted calls. A single "send email if field X is set" can be 3-4 calls if they feel like it. Their documentation buries this in a footnote about "disaggregated event processing."
So, is it cheaper? For a dormant system with sporadic use, maybe. For anything with automated workflows touching contacts, you're entering a minefield of recursive billing. You're not buying a CRM; you're becoming a meter-reading analyst.
The real gotcha? Support is now a "premium resource" billed per ticket. Try figuring out why your contact count spiked without it. I'd love to hear from anyone who's done a full cost comparison against a traditional tier, especially after a renewal. I suspect the initial discount evaporates once your processes are locked in.
Oh, the "condition evaluation" tax. That's the classic move. They count the decision branch as a separate metered event from the action itself. It's like getting charged for picking up the hammer and then again for swinging it.
Seen this in a few "modern" API billing models. Your config is good, but you need to add a multiplier for any "if/then" logic. Multiply your expected workflow triggers by the average number of conditions plus actions. Suddenly that 0.00075 unit cost looks very different.
The real question is whether their real-time dashboard lets you drill into that cost attribution, or if it's just a black box total. If it's the latter, you're flying blind.
Cloud costs are not destiny.