HiBob pricing review - hidden costs for additional modules and support

That 30% add-on isn't hidden, it's just how they bundle features. You're paying for their segmentation.

Their standard API is absolutely rate-limited. We hit a 5,000 requests/day hard cap with the base tier. Daily syncs for 150 engineers? That'll blow through it by lunch. The "enterprise" unlock cost us another $3/user/month.

Premium support is overkill for a broken sync. Just build a circuit breaker and alert on it. Their 48-hour SLA means they won't fix your code, which is fine.

We're looking at HiBob too, for a similar size marketing team. I hadn't considered the API rate limiting, but that's a crucial point for daily syncs. If the base tier can't handle our daily active user data pulls to our CDP, it's a non-starter.

You mentioned the 48-hour SLA for support. Did your sales rep clarify if that's just for the initial response, or a resolution? I've seen some vendors where the clock starts ticking on a reply, not a fix, which makes that SLA feel misleading.

Yeah, the SLA distinction is key. In our contract, the 48 hours was for the *initial* response, not resolution. It's basically a "we'll get back to you" guarantee.

You might want to ask them to explicitly define what a "support incident" is. For us, that first reply was often just a request for logs, which reset the clock. The actual fix timeline was a separate "best effort" clause.

For the API limits, definitely push for the exact numbers during your trial. Our sales rep gave us a "soft limit" verbally that didn't match the docs.

You've put your finger on a critical contractual nuance. The difference between a "response" SLA and a "resolution" SLA is a classic point of negotiation in vendor agreements. In my experience, you can often get them to amend the clause so the clock only starts after they've confirmed they have a complete, actionable ticket, not after an automated acknowledgment.

That practice of resetting the clock with a request for logs is something we've seen elsewhere. We started explicitly logging and attaching all diagnostic output to the initial ticket submission as a matter of process. It forces the vendor to engage with the full context immediately and significantly improved our actual time-to-resolution, even without a stricter SLA.

Your point about pushing for exact API numbers during the trial is sound, but I'd take it further: get the documented rate limits, burst capacity, and any quotas baked into an appendix of the contract itself. Verbal assurances from sales are worthless post-signature.

"Just how they bundle features" is a generous way to say "how they unbundle the price." It's segmentation designed to make the core platform look palatable until you realize you need the actual functionality to, you know, run your business.

Your point about the enterprise unlock costing $3/user/month is the real sticker. That might sound trivial to a sales rep, but over 150 users for 3 years, that's over sixteen grand to just... use their product normally. That's not a feature add-on, that's a toll booth for getting your own data out at a usable rate.

You're right to be concerned. That quote climbing by 20-30% per module is a common pattern for platforms that sell a core "dashboard" first, then charge extra to actually act on the data within it.

For your specific use case, the daily sync requirement is the real budget driver. Even if the standard API isn't technically rate-limited, they often have severe throughput limits that make daily bulk syncs impractical without the enterprise add-on. I'd ask the sales rep to demonstrate a full daily sync cycle for your 150 engineers during the trial, using only the proposed base tier API credentials.

The 48-hour SLA for standard support is indeed just for initial response. For breaking syncs, a 48-hour response means your provisioning could be halted for days. If you proceed, get a commitment in writing on what constitutes a "critical" ticket for your integration and how those are prioritized.

The 5,000 requests/day hard cap is the key data point. That's low enough to dictate your entire integration architecture. You'd be forced into batch polling instead of event-driven streaming, which adds latency and complexity to your provisioning pipeline.

Your point about building a circuit breaker is pragmatic, but the core issue is that the limit forces you to treat a business-critical sync as a brittle, error-prone process you have to actively manage, rather than a reliable service. That's the real cost of the "segmentation" - operational overhead, not just the $3/user/month.

The 48-hour SLA is for a first human reply, not resolution. That's useless for a broken provisioning pipeline.

Your daily sync requirement determines the real cost. If you have 150 engineers and need to update multiple systems, the 5k request/day base cap user400 mentioned means you'll blow through it instantly. The "enterprise" API isn't a feature, it's a requirement.

Get the exact limits in writing, then calculate the per-request cost of the add-on. It's usually absurd.

That's exactly the right pattern to watch for with HRIS quotes. The core looks affordable, but the add-ons for the real operational tools become mandatory for a use case like yours.

For your first question, the standard API is rate-limited and you need to get the exact numbers in writing before moving forward. User400 mentioned a 5k requests/day cap, which is a critical data point for your daily syncs.

On the support SLA, it's almost certainly a 48-hour *initial response* guarantee. For a broken provisioning sync, that's not acceptable. They often sell the premium tier as the fix, so I'd ask for a clause that treats a broken critical integration as a priority incident, regardless of your support tier. Otherwise, a failed sync could mean new engineers are locked out of your DevOps tools for days, which is a huge risk.

The 20-30% per-module uplift isn't just an add-on cost, it's a redefinition of the total cost of ownership. For your team of 150, you need to calculate the three-year impact of every necessary module against your base quote. That's the only number that matters for your business case.

>Is their standard API rate-limited?
Assume it is until you get the exact limits in writing. The "enterprise-grade access" add-on usually indicates a restrictive base tier. For daily syncs of 150 users to multiple systems, you'll likely exceed a standard throughput cap. Ask for the documented requests-per-second and daily aggregate limits for the base API, then model your exact sync pattern against it.

Their 48-hour SLA for Standard support is a response time, not a resolution time. For a broken provisioning sync, that's an operational risk. You should quantify the cost of a developer being locked out of systems for two days versus the premium support tier's price. That's your justification for either pushing back on the clause or budgeting for the higher tier.

Oh man, the "enterprise-grade access" add-on line is a classic. That almost always means the standard API has restrictive caps. For 150 engineers, a daily sync to even two systems could easily hit a 5,000/day limit others mentioned, which would break your provisioning.

For the support SLA, push them on what "resolution" means for a priority 1 ticket. In my last role, we got burned because their "4-hour resolution" guarantee only applied to them *classifying* the ticket, not fixing it. The actual fix was still "best effort." If your sync breaks on a Friday afternoon, that's a real problem.

Spot on about the "per-request cost of the add-on" being absurd. I've seen the math where that $3/user/month for enterprise access works out to fractions of a penny per API call. Which makes you wonder why the base tier has such a restrictive cap in the first place, other than to force the upsell.

The real kicker is when you ask for a custom SLA for critical integrations and they treat it like you're asking for the moon. Their standard support is structured so that a broken pipeline isn't technically their problem, it's your "feature requirement."

Your post highlights the exact phase of discovery where the real platform cost emerges. Everyone else has given you good numbers on the API limits, so I'll focus on the support side since you cut off there.

You're right that 48 hours is too slow for a broken sync. The catch with that "4-hour resolution" tier is usually that the clock starts when they accept it's their problem, not when the pipeline fails. We had to get a specific clause added that defined a failed core integration as an automatic P1. Without that, they spent the first four hours determining if it was a configuration error on our end.

For your business case, model the total cost with every module you need for a full, production-ready integration. Then add 20% for the modules they'll inevitably introduce next year. That's your true three-year cost.

Great questions. You've hit on the two main pressure points - API limits and support SLAs are exactly where the real cost emerges.

On the support SLA, you're correct to be wary. That 48-hour window is for a first touch, not a fix. For a broken sync, even the 4-hour "resolution" tier often means 4 hours to *acknowledge* it's a platform issue, not 4 hours to restore service. Push them to define "resolution" in the contract for a P1 incident related to core integrations.

For your business case, I'd model the total cost with both those modules and the enterprise API add-on. That's your true baseline, not the initial quote.