Think about your own work or business in this area: Maker launch on DevHunt: Custom notification hub for AI agents and everything else - the product is a notification relay platform built for the AI era. It lets your AI agents,... What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

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

Simulated interest

57/100

AI synthesis, not measured demand

Suggested price range

—

No numeric price estimates in the answers. Ask a pricing follow-up to collect them.

Response sentiment

Positive 0%Neutral 50%Negative 50%
The takeaway

What this panel suggests

The core problem respondents describe is not a lack of ideas, but the operational pain of keeping notification flows working across a messy stack. They repeatedly point to brittle pipelines, manual patching, and ad hoc glue work across tools like Zapier, custom scripts, spreadsheets, Slack, WhatsApp, and Sheets. The cost shows up mainly in engineering time: hours each week spent debugging, triaging failures, and maintaining edge cases instead of building product. Some also describe business risk, especially the stress of missing a critical alert or damaging client trust. A smaller but important thread is cost sensitivity, with some respondents saying they need to stay within tight monthly budgets and avoid extra platform charges or expensive API usage. What they have already tried sounds mostly incremental: patching integrations, stitching tools together, and manually monitoring or fixing failures rather than adopting a fully unified system. Overall, the answers read as a reliability-and-maintenance pain point, with skepticism about whether a new notification hub clearly beats the do-it-yourself alternatives they already use.

Recurring themes

Brittle and Manual Pipelines
“My biggest headache right now is the brittleness of our notification pipeline.”Read Raymond Dare’s response →
Time Sink and Productivity Loss
“This is a significant time sink, costing us hours of developer time each week that could be spent on actual product development.”Read Raymond Dare’s response →
Cost Sensitivity for SMBs
“Many small businesses have very tight monthly spends, often under $50-$100, and I have to be incredibly resourceful to avoid extra platform costs or expensive API calls.”Read Chaaruchandra Sethi’s response →

Objections to investigate

  • Integration Complexity with Existing Stack
  • Unclear Value Proposition vs. Custom Solutions
  • Pricing Viability for Low-Budget Clients

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.

Raymond Darenegative

My biggest headache right now is the brittleness of our notification pipeline. It's a Frankenstein of Zapier, Slack webhooks, and custom scripts. When it breaks, which it does more often than I'd like, urgent support tickets get missed, and the team has to scramble to manually triage them. This is a significant time sink, costing us hours of developer time each week that could be spent on actual product development. We've tried adding more robust error handling and monitoring, but it feels like we're just patching a fundamentally unstable system.

Simulated interest: 70/100

Lori Boyernegative

Honestly, the biggest headache is our reliance on that manual Google Sheet check. It feels so disconnected from the AI agents we're using. Every morning, I'm sifting through it, assigning tasks, and hoping nothing slipped through. It easily eats up an hour of my time each day, and the stress of potentially missing a critical alert that could cost a client is constant. We've tried setting up more complex email filters, but it just created more noise. I worry about scalability with this bottleneck.

Simulated interest: 70/100

Chaaruchandra Sethineutral

Essentially, the biggest problem I face is keeping clients on budget while still delivering effective automations. Many small businesses have very tight monthly spends, often under $50-$100, and I have to be incredibly resourceful to avoid extra platform costs or expensive API calls. I've tried finding clever workarounds, optimizing existing workflows, and suggesting manual steps where automation would be too costly. This new notification hub sounds interesting, but my immediate concern is always the cost. If it requires a significant monthly subscription or has per-notification charges, it likely won't fit my clients' needs, even if it offers advanced features. I'd need to understand the pricing structure very clearly to see if it's viable.

Simulated interest: 30/100

Yunus Sieglingneutral

Our biggest problem is ensuring the Python notification layer can scale reliably as our AI agent's output grows. Right now, it's a critical piece of our infrastructure, and performance bottlenecks mean delays in getting crucial AI findings to Discord and Jira. We've already spent considerable time optimizing the routing logic and enhancing our logging. The cost is primarily in engineering time and the risk of operational instability. I'm not sure how your platform handles the specific complexities of routing varied AI agent outputs without significant custom integration, which is exactly what we're trying to avoid with our homegrown solution.

Simulated interest: 30/100

Jaime Faheyneutral

Honestly, the biggest headache right now is the sheer volume of information. My AI agents are great for initial research and drafting, but then I'm drowning in reports, campaign updates, and client requests. It’s like trying to drink from a firehose. We've tried setting up more granular Airtable automations, but it’s clunky and still requires manual oversight. I'm spending probably 5-7 hours a week just sifting through and organizing outputs, which is time I could be spending on actual strategy or client management. It’s not a direct money loss yet, but it’s definitely a bandwidth killer for my small team.

Simulated interest: 60/100

Orville Schuppeneutral

My biggest problem is the sheer amount of manual effort required to manage our AI onboarding assistant's edge cases. We have an alerting tool for standard issues, but anything outside that requires me to update a complex spreadsheet-based routing system. This eats up hours every week, pulling me away from more strategic tasks. I've tried documenting everything meticulously, but the process itself is the bottleneck. It's a constant risk of human error and significant technical debt I'm desperate to resolve.

Simulated interest: 85/100

Marie Da silvaneutral

This notification hub concept is interesting. My biggest challenge right now is filtering the noise from my current AI agent setup. I'm using Gmail labels, Telegram, and Notion, but it's becoming overwhelming. I spend probably 5-7 hours a week just triaging notifications – distinguishing actual bugs from feature requests or minor suggestions. I've tried tweaking the AI's prompts, but it's a delicate balance. It costs me valuable development time that could go into coding or learning Japanese.

Simulated interest: 60/100

Sitara Abbottnegative

Our biggest problem is definitely the constant manual patching required to connect our AI agents and their outputs across different platforms like WhatsApp, Sheets, and Slack. It's incredibly time-consuming, easily eating up a good half-day each week for my team, which translates to roughly ₹10,000-₹15,000 in lost productivity monthly given our team's blended cost. We've tried building small scripts and using Zapier for some basic connections, but it's brittle and requires constant tweaking.

Simulated interest: 70/100

Mace Blomnegative

The single biggest problem I face is maintaining the reliability of existing notification pipelines without introducing unnecessary complexity. My current setup with shell scripts and n8n works, but when an edge case arises, debugging can be time-consuming. I've spent hours tracing script logic or n8n workflow issues. While these tools are cost-effective and I understand them deeply, the effort to ensure 100% uptime and proper error handling for complex notification routing for AI agents can become significant. I'm not sure this 'custom notification hub' offers a tangible improvement over what I've engineered, or if it would even integrate smoothly with my existing architecture. What specific issues does it solve that my current approach can't, and how does it handle the 'everything else' part of the description?

Simulated interest: 20/100

Colin Goodwin-Daughertynegative

Right now, the biggest problem is reliability in our notification pipeline. We're cobbling together Google Sheets, webhooks, and custom scripts, and it's brittle. I've personally spent hours each week patching it, especially during peak times, which pulls me away from product development. It's costing us valuable development time and, frankly, risking client trust if a notification falls through the cracks. We need something more robust than our current patchwork.

Simulated interest: 70/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.