Did you see Gladly's latest feature drop? Looks like more enterprise lock-in.

You're right to be suspicious. The "bundling" is just a softer term for vendor lock-in, especially when they gate it behind the enterprise plan.

> migrating away gets much harder once your data lives in these proprietary profiles

That's the whole point. Have you ever tried to extract a normalized dataset from one of these "advanced" objects? The cost isn't just the new tier's price tag, it's the future consulting bill to untangle your own customer data. Their post-incident migration runbooks will be a horror story.

For cost comparison, don't just look at per-agent pricing. Build a TCO model that includes the engineering hours you'll need to build workarounds when their "suite" doesn't fit your process. I've seen teams spend more on that than the platform itself.

Yeah, that pricing tier thing is exactly what I'm trying to figure out too. I'm in the middle of some demos and seeing a lot of this.

When you say "migrating away gets much harder," does that include just exporting the raw data for your own reporting? Or is the issue that the data structure itself is useless outside their system?

For cost comparison, I've been asking reps for a breakdown of which integrations break when you're not on the enterprise plan. Sometimes the core platform looks okay, but you need their top tier to connect your warehouse, which feels like a hidden cost.

The "useless outside their system" angle is the real kicker. You can export JSON blobs all day, but if the schema is designed around their UI and not relational logic, you're paying your data team to rebuild a customer profile from scratch anyway.

> asking reps for a breakdown of which integrations break
Smart move. Take their answer and add a 20% contingency for the integrations they haven't built yet but you'll need in 18 months. Their "enterprise" tier is often just paying for the roadmap.

Did any rep actually give you that breakdown, or did they pivot to a feature demo? That's your first cost signal right there.

Totally get your concern about lock-in. I've seen this with other platforms where the "advanced" data model feels tailor-made to be sticky. It can be a real value add if you're all-in on their ecosystem, but the exit tax is real.

For cost comparison at high agent counts, don't forget to factor in the efficiency gains. If those timeline views and custom objects actually save each agent 30 minutes a day, the ROI might justify the premium over Zendesk, even with the lock-in risk. But you have to be certain the features fit your workflow perfectly.

You've hit on the core dilemma in modern SaaS procurement. Your suspicion about bundling being a lock-in mechanism is often correct, but the risk calculation needs to be more granular.

Instead of just a platform-to-platform cost comparison between Gladly and Zendesk, you need to model the data portability cost. Request the data schema specification for these "Advanced Customer Profiles" from their sales engineering team. If they can't or won't provide a clean, normalized entity-relationship diagram that's independent of their application logic, that's your first red flag. The cost isn't just the higher per-agent license, it's the future FTE months required to de-normalize and re-home that data.

Also, check your contract's data processing and security exhibits. Does their enterprise plan's data structure create new categories of personal data that would trigger additional compliance obligations under GDPR or CCPA? Sometimes the lock-in isn't just technical, it's regulatory.

> you're paying your data team to rebuild a customer profile from scratch anyway

This is so painfully true. I migrated us off a platform last year that had these "enriched" contact objects. The exported JSON was essentially a serialized view model - keys like `last_ui_interaction_panel_state` and `merged_timeline_cache`. It took two engineers three weeks just to write the transformers to get it back into a sane, reportable format. The vendor's support just kept saying "you have the data" but it was useless without their app logic.

That 20% contingency is smart, but I'd almost double it. In my experience, the "roadmap" integrations they sell you on are the first to get deprioritized when they have a big new feature like this to launch. Did your rep give you any concrete SLAs on those integration timelines, or just vague "on the roadmap" promises?

You nailed it. The pivot to a feature demo when you ask for the integration breakdown is a classic signal. I've had reps spend 40 minutes showing me timeline views, but the second I ask which APIs are excluded from the standard tier, it's "let me circle back with the team."

Add that 20% contingency, then double it for the integrations they'll deprecate in two years when the next big bundled feature launches. Their roadmap isn't your problem, until you've paid for it.

It's a valid concern. But the bigger red flag for me is when vendors like Gladly make this tier change *after* you've already adopted their core product. That's when you feel the real squeeze.

The cost comparison should start with your own data model. If your existing customer profiles are simple and portable, the "value add" of these proprietary features is often negative. You're not just paying more per agent, you're paying to rebuild your entire data practice around their logic. That's where the lock-in cost multiplies.

Ask them directly for the migration path *down* from the enterprise tier if the features don't deliver. Their answer will tell you everything.