What would stop you from trying Ably (https://www.ably.io/push-notifications) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Page reviewed

Ably cross-platform push notifications with our API

https://www.ably.io/push-notifications (opens in a new tab)
Saved screenshot of Ably cross-platform push notifications with our API
Screenshot saved with this question. The live page may have changed.Open full image ↗

10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Simulated interest

42/100

AI synthesis, not measured demand

Suggested price range

$0–750

Median $150 · simulated willingness to pay

Response sentiment

Positive 0%Neutral 100%Negative 0%
The takeaway

What this panel suggests

The panel is hesitant rather than broadly negative. The main blocker is adoption cost: respondents want to understand how Ably would fit into their existing backend, what engineering work migration would require, and whether they have the staff time to try it this month. A second major friction point is pricing clarity. Even though the page says pricing is consumption-based and mentions a free plan, respondents still want a concrete sense of how monthly spend scales with their own usage before committing. A third theme is inertia from current solutions: some teams already send push notifications directly through Firebase Cloud Messaging and Apple Push Notification Service, while others use in-house systems for receipts, account changes, or fraud alerts. That means Ably is being evaluated as a replacement or simplifier, not as a brand-new category. Willingness to pay is mixed and relatively modest, with a median of $150 and a wide spread up to $750, but that should be read as stated budget ceilings, not proof of demand. Better onboarding, migration help, and cost examples would likely unlock trials.

A hypothesis to test

Pricing & positioning

Lead with a low-friction trial and clear migration path. The strongest follow-up is a concrete cost example tied to message volume, concurrency, and typical notification patterns, plus implementation guidance that shows how Ably fits into an existing backend.

The page’s per-minute, consumption-based pricing and free tier do not fully answer buyers’ budgeting questions. Respondents want to translate usage into a monthly bill before trying it. For this audience, simple calculators, sample bills, and a small entry tier would reduce hesitation.

Recurring themes

Integration complexity and engineering resources
“The primary thing that would stop me from trying Ably this month is that I need to fully understand how it integrates with our existing backend infrastructure.”Read Marta Rogahn’s response →
Pricing model clarity
“What would stop me from trying Ably this month is a lack of clarity on how its pricing scales with our specific usage.”Read Bhagwanti Verma’s response →
Current in-house or alternative solutions
“We currently handle push notifications by building custom logic that calls Firebase Cloud Messaging and Apple Push Notification Service directly.”Read Marta Rogahn’s response →

Objections to investigate

  • High integration effort and resource constraints
  • Unclear pricing structure (consumption vs. fixed)
  • Satisfaction with current manual or custom setups

Use these findings to plan customer interviews or experiments. How to interpret AI research

What the panel said

Click a name to open that persona’s full profile.

Marta Rogahnneutral

The primary thing that would stop me from trying Ably this month is that I need to fully understand how it integrates with our existing backend infrastructure. We currently handle push notifications by building custom logic that calls Firebase Cloud Messaging and Apple Push Notification Service directly. We also need to ensure the data attribution capabilities are robust enough to accurately measure the impact of specific campaigns on user retention. Without a clear picture of the integration effort and detailed analytics, it's hard to commit. Regarding pricing, I'd need to see more details, but based on the mention of consumption-based pricing, I'd be looking at something in the range of $500-$750 per month, depending on usage, as a starting point for exploration.

Simulated interest: 60/100

Ernesto Nicolasneutral

I'm always looking for ways to improve our notification system, but introducing a new third-party service this month feels like a stretch. We're currently routing alerts through a Node service to APNs and FCM, and my colleague and I are the only ones managing it. The thought of adding another dependency, especially for something as critical as transaction and security alerts, requires rigorous testing and validation. I'd need to see comprehensive documentation on error handling, latency guarantees, and how it integrates seamlessly without introducing new failure points. Currently, all of this is handled in-house, which gives us complete control and visibility. If I were to consider Ably, I'd need a clear understanding of their pricing structure, particularly the 'per-minute, consumption-based pricing' – how does that translate to our specific usage patterns and potential spikes? Given our current setup and the need for extreme reliability, I wouldn't pay more than $50 per month, and that's assuming it dramatically simplifies our operations and proves itself thoroughly.

Simulated interest: 20/100

Bhagvan Bhadreshaneutral

The biggest thing is definitely the time commitment. Right now, I'm personally crafting and scheduling all our push notifications using spreadsheets and a checklist. It's quite manual, you see. While this new service looks promising, I'd need to see how easy it is to integrate with our current setup without taking too much time away from other tasks. We're a small team, and time is money. Regarding price, I'm not sure about the exact pricing basis from what I can see quickly, but for something that streamlines this manual process, I'd be willing to pay up to $50 per month. Anything more than that would need a much clearer ROI and proof of efficiency.

Simulated interest: 40/100

Melinda Leiterneutral

Trying out a new push notification platform this month would be challenging given our current roadmap and limited engineering resources. We're focused on optimizing our existing lifecycle campaigns with OneSignal, and any new integration would require significant engineering time for setup and A/B testing, which we don't currently have bandwidth for. We'd need to see clear, quantifiable benefits that outweigh the development cost. Regarding pricing, I'd need more clarity on the consumption-based model and how it scales. Based on the free plan details, I'd consider paying up to $150 per month if it demonstrated significant efficiency gains and didn't require extensive engineering lift.

Simulated interest: 30/100

Apolline Caronneutral

Currently, our in-house push notification system handles our specific needs for receipts, account changes, and fraud alerts. While Ably's capabilities are noted, I'd need to see a clear cost-benefit analysis, especially concerning the migration effort and potential integration complexities with our existing infrastructure. Without a detailed breakdown of their pricing tiers and a pilot program to assess performance and reliability in our payment context, it's premature to consider a switch this month. I'm looking for a predictable cost, so I would pay a maximum of $500 per month.

Simulated interest: 30/100

Clayton Leschneutral

The main thing that would stop me from trying Ably this month is the integration effort. We currently handle our push notifications through Braze, alongside our email and CRM workflows. While Ably's unified API sounds appealing, I'd need to understand how it integrates with our existing stack and if it requires significant engineering resources, which are already stretched thin on our three-person growth team. The problem of attributing push notifications versus email is a persistent one, and I'd need to see a clear path to solving that before committing. Regarding pricing, the page mentions per-minute, consumption-based pricing, but doesn't give specifics. I'd need to see a detailed pricing breakdown to determine what we could afford. Based on our current budget for marketing tools, I might be willing to pay around $300 per month, assuming it scales well and directly addresses our attribution challenges.

Simulated interest: 50/100

Kyle Balistrerineutral

The biggest hurdle for me right now would be integrating another vendor. I'm already juggling six client apps, each with its own mix of iOS, Android, and web, and I schedule sends through separate vendor accounts and shared campaign sheets. It's a real headache and prone to errors. While Ably's unified API sounds appealing, I'd need to be convinced it wouldn't add *more* complexity or require significant time from our already stretched development team to set up. I'd also need to understand how its pricing works for our varied client needs – is it per app, per user, or something else entirely? I'd be willing to pay up to $200 per month if it genuinely simplified things and demonstrated clear value across our clients.

Simulated interest: 50/100

Sjors Eversneutral

Currently, our notification system is built in-house and I'm focused on refining its architecture to handle growth. The immediate concern is ensuring we can scale this critical piece without disrupting current operations. While Ably's offering is interesting, I'd need to see a clear path for migrating our existing logic and data, especially concerning the single full-stack developer who owns our current endpoint. A proof of concept and migration plan would be essential. Given the current focus on optimizing existing infrastructure, I'm not looking to add new external services this month. As for pricing, the 'per-minute, consumption-based pricing' mentioned isn't clear enough to estimate a monthly cost without knowing the specifics of our expected usage. I would need to understand message volume, connection concurrency, and how that translates to minutes to even begin estimating a budget. Therefore, I cannot provide a maximum monthly payment at this time. $0

Simulated interest: 30/100

Bhagwanti Vermaneutral

What would stop me from trying Ably this month is a lack of clarity on how its pricing scales with our specific usage. We currently manage our notifications in-house, relying on our engineering team, Ravi and Priya, to handle bugs and implementations. While the promise of a unified API is appealing, I'd need to understand if it integrates smoothly with our existing Android and web alert systems and if there are any hidden costs for higher message volumes. We're always looking to optimize, but budget is a key consideration. I'd be willing to pay up to $150 per month for a service like this, provided it demonstrably reduces our current operational overhead and is billed monthly.

Simulated interest: 60/100

Ben Ortizneutral

Right now, we're handling reminders and alerts with a custom service tied into Firebase and a cron job. It's a lean setup, and honestly, it works for us. My main concern with adopting something new like Ably this month would be the integration effort and whether it truly simplifies things or just adds another layer to manage. I'm always looking for efficiency, so if it means more complexity for the same or similar outcome, I'd hesitate. The pricing model seems to be consumption-based, which is good, but without seeing specific numbers for our current usage or projected growth, it's hard to commit. If the free tier is generous enough to cover our current needs and the transition is straightforward, I might consider it. Realistically, I'd pay up to $50 per month, assuming it covers our core notification needs without requiring significant development time to implement and maintain.

Simulated interest: 50/100

Keep exploring.

Find your next question or see which topics divide AI panels.

Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.