Conversation group

Live reaction: moving Halyard to usage-based pricing

We're considering moving Halyard from seat-based to usage-based pricing (per event processed). Honest reactions — good idea or not?

Ryan Walsh

Good idea for teams like mine. Seats never matched how we actually use an integration tool — we'd rather pay for volume.

Oliver Schmidt

Careful. For a 1000-person org, a variable bill I can't forecast is a procurement nightmare. I need a committed floor and a ceiling.

Priya Nair

Usage-based is fair, but only with per-event caps and alerts. One buggy loop shouldn't turn into a five-figure surprise.

So if we offered usage-based with hard caps and an optional flat commit, would that unlock it for the larger teams?

Lucas Meyer

Yes — a flat commit with usage on top is the model my finance team can actually approve.

Hannah Kim

Just don't kill the free tier. The whole reason I'd pick Halyard is starting for free and growing into usage.

Aditya Rao

And publish the metering logic. If I can't audit how an 'event' is counted, I won't trust the invoice.

Last one: what would make the pricing page instantly credible to an engineer?

Grace Mensah

A live usage calculator and real examples. Show me '10k events/month = $X' and I'm sold far faster than a 'contact sales' button.

Executive summary

Technical buyers back a usage-based move in principle — it matches how integration tools are actually consumed — but acceptance is conditional. Small/PLG voices love paying for volume and insist the free tier stays; enterprise voices will only sign off with a committed floor plus a hard ceiling they can forecast. Across the board, engineers demand transparent, auditable metering and a self-serve usage calculator over a 'contact sales' wall.

Key themes

Usage-based fits the product — with guardrails

Fairness is welcomed, but caps and alerts are a prerequisite, not a nice-to-have.

“Usage-based is fair, but only with per-event caps and alerts.” — Priya Nair

“We'd rather pay for volume.” — Ryan Walsh

Enterprise needs a floor and a ceiling

A flat commit with usage on top is the only model finance will approve at scale.

“I need a committed floor and a ceiling.” — Oliver Schmidt

“A flat commit with usage on top is the model my finance team can approve.” — Lucas Meyer

Transparency sells the pricing page

Auditable metering plus a self-serve calculator beats a 'contact sales' wall.

“If I can't audit how an 'event' is counted, I won't trust the invoice.” — Aditya Rao

“A live usage calculator and real examples.” — Grace Mensah

Recommendations

Ship usage-based with hard caps + alerts as the default, keep the free tier.
Offer a committed-floor plan with usage on top for enterprise procurement.
Put a transparent metering definition and a live usage calculator on the pricing page.