Your are here

Your idea for a business rule engine that integrates into event-driven architectures falls into a category where there's minimal market activity. This could be because the problem you're solving is very niche, or perhaps not considered a high priority by potential users. With only two similar products identified and zero comments across them, it's difficult to gauge the potential engagement. Essentially, there's not enough data to confidently say there's strong demand. Because of that, before you start investing heavily into building it, you need to validate that actual demand exists. Don't be discouraged but be realistic: you must find evidence that people are actively seeking this kind of solution.

Recommendations

1. Start by identifying online communities, forums, or industry groups where your target customers (developers, architects using event-driven systems) congregate. Share your idea, emphasizing the specific pain points it solves, and gauge their initial reactions. Are they nodding along, or shrugging their shoulders? Explicitly ask if they've encountered these issues and what their current solutions are.
2. Offer to manually solve the problem for a small number of potential customers (2-3). This could involve consulting, prototyping a rule engine for a specific use case, or providing custom integrations. It’s hands-on validation to determine if your approach truly addresses their needs and generates tangible value. Document their current workflow, pain points, and how your manual solution improves their process. This gives you real-world insights and validation you can leverage later.
3. Create a concise (under 2 minutes) explainer video showcasing the core functionality and benefits of your business rule engine. Focus on a specific use case and visually demonstrate how it simplifies complex decision-making within event-driven architectures. Track the video's completion rate - are people watching it fully? This indicates genuine interest. Use a platform like YouTube to also track likes and comments.
4. Consider creating a waiting list and asking for a small, non-refundable deposit (e.g., $10-20) to join. This demonstrates commitment and helps gauge the seriousness of potential users. Frame it as early access to a beta program with exclusive features. If you can't find at least 5 people willing to put down a deposit within 3 weeks, it's a strong signal to reconsider the viability of your idea or pivot.
5. Refine your target audience. Focus on a specific industry or type of application where event-driven architectures and complex decision-making are particularly prevalent. This targeted approach can help you better understand their needs and tailor your solution accordingly. Document and A/B test your marketing to each of the audience, and see if that improves your use and buy rates.

Questions

1. Given the minimal market activity, what are the most critical assumptions you're making about the prevalence and severity of the problem you're solving, and how can you directly validate those assumptions through targeted customer interviews or experiments?
2. Considering the lack of engagement with similar products, what unique aspects of your business rule engine will differentiate it and create a compelling reason for users to switch from their current solutions or manual processes?
3. If initial validation efforts reveal a need for significant customization or consulting to integrate your engine into existing event-driven architectures, how will you balance scalability and profitability in your business model?