What would stop you from trying Sherlocks.ai (https://www.sherlocks.ai/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Gregory Cartwrightneutral

This sounds intriguing, especially the promise of automated root cause analysis. My biggest hesitation would be integration and potential noise. We already deal with alert fatigue, and I'd need to understand precisely how Sherlocks interfaces with Datadog and Grafana to ensure it's actually reducing noise, not adding to it. The current process involves a lot of manual correlation between alerts and Jira tickets, so anything that automates that linkage is appealing. I'd also want to see how it handles intermittent issues, which are our biggest headache. Without a clear understanding of those integrations and a proof of concept showing it doesn't just add more alerts, it's hard to commit. As for pricing, I'd need to see a clear breakdown of what constitutes an 'investigation' and perhaps trial it before committing to a monthly fee. I could potentially see paying up to $500 per month if it significantly reduces our MTTR and manual triage time.

Simulated interest: 60/100

Candice Veumneutral

My current process for incident investigation relies heavily on our meticulously maintained, albeit manual, spreadsheet-based runbooks. While this system captures institutional knowledge, it’s a bottleneck during critical incidents, consuming valuable engineering hours that could be spent on preventative measures. The thought of automating this is appealing, but I'd need to see how Sherlocks.ai integrates with our existing toolchain and, more importantly, how it handles the specific compliance and audit traceability requirements we face. The product mentions SOC 2 compliance, which is good, but I'd need to understand the granular details of its data handling and audit logging capabilities before even considering a trial. Pricing isn't immediately clear for our scale, as the free tier mentioned seems geared towards smaller teams. Without a clear understanding of the enterprise offering and its audit trails, I can't commit to a price.

Simulated interest: 30/100

Manoj Ganakapositive

I'm always looking for ways to improve our incident response, especially since I'm still involved in the on-call rotation. The idea of an AI SRE investigating incidents and finding root causes automatically sounds incredibly valuable. What would stop me from trying it is understanding how it integrates with our specific AWS and Kubernetes setup, and what kind of upfront effort is required. Today, my team and I manually sift through logs and update Notion runbooks. I would be willing to pay up to $300 per month for a service like this, assuming it proves its worth during a trial.

Simulated interest: 70/100

Leopold Buschneutral

My primary concern with trying Sherlocks.ai this month would be the potential for alert fatigue. We already deal with a significant number of alerts from our microservices, and I need to be sure this tool won't just add to the noise. Currently, we rely on Rootly for incident timelines, but the root cause analysis itself still requires manual finalization in Confluence. I'd need to understand how Sherlocks.ai integrates with our existing setup and if it truly automates RCA without introducing more complexity. Regarding cost, I'm not currently in a position to commit to a new monthly subscription without a clearer understanding of its value and integration.

Simulated interest: 30/100

Maryann Rogahnneutral

My main concern with adopting a new tool like Sherlocks.ai this month would be integrating it into our current workflow without disrupting our existing processes. Today, my reliability group handles incident analysis manually, meticulously documenting timelines and root causes in Jira after each major event. We also rely heavily on Datadog for monitoring. While the promise of AI-driven root cause analysis is appealing, especially for reducing MTTR, I need to be confident it truly complements our existing stack and doesn't introduce more complexity or require extensive re-tooling. The ability to integrate seamlessly with Datadog and Slack, as mentioned, is a positive point. I would be willing to pay up to $500 per month for a solution that demonstrably improves our incident response times and provides actionable insights without significant overhead.

Simulated interest: 60/100

Lorenzo Willemsneutral

What would stop me from trying Sherlocks.ai this month? Honestly, it's the 'Enterprise plan is custom-priced' part. We already have robust incident review tooling in place, and before I commit significant time or budget to a new solution, I need to see concrete pricing. My team relies on capturing alert history and remediation steps, and while an AI SRE sounds appealing, understanding the cost structure is crucial. Today, we handle incident reviews by meticulously documenting everything in our existing system. I'm looking for a solution that demonstrably improves upon that without introducing ambiguity in cost. The free plan with 30 investigations is a start, but for our operational load, that's likely too limited for a fair evaluation of its impact. I wouldn't pay more than $300 per month for this, and that's only after a thorough trial proves its value beyond our current tooling.

Simulated interest: 60/100

Claude Hayesneutral

While the promise of an AI SRE finding root causes automatically is intriguing, what would stop me from trying Sherlocks.ai this month is our current process. We deliberately maintain a human-led approach for root-cause analysis. My role involves meticulously reviewing logs and correlating events myself before any changes are made to our runbooks. Introducing a tool that bypasses this critical diagnostic step, even if it claims to be faster, would conflict with our commitment to rigorous understanding and auditability. I'm concerned about losing the depth of insight gained through manual investigation. We currently have no budget allocated for such tools, and given my salary range, I'm cautious about adopting new subscriptions without a clear, quantifiable benefit that aligns with our established practices. The free tier with 30 investigations per month sounds like a starting point, but I'd need to see how it genuinely integrates without undermining our existing validation process.

Simulated interest: 30/100

Sheela Jhaneutral

Our current setup with Prometheus, Grafana, and a spreadsheet runbook is quite lean, and honestly, it gets the job done for our 12-person startup. The biggest hurdle to adopting something new like Sherlocks.ai this month would be the time and effort required to integrate it and ensure it genuinely adds value beyond what we already have. We're on-call 24/7 with just four engineers, so any new tool needs to be a clear win and not add to our workload. I'd need to see how it fits with our existing Prometheus and Grafana setup without causing disruption. Regarding pricing, I'd be looking at a free or very low-cost tier initially, perhaps up to $100 USD per month if it proved significant value in reducing our incident response time and fatigue.

Simulated interest: 40/100

Violette Durandneutral

This sounds interesting, especially the promise of reducing MTTR and automating root cause analysis. My main concern would be how well it integrates with our current setup, particularly our log aggregation and incident.io workflow. We spend a good amount of time fine-tuning alerts to avoid fatigue, so I'd need to see how Sherlocks.ai complements that without adding more noise or complexity. The VPC native option is reassuring for security. Regarding cost, I'd need more details on what constitutes an 'investigation' and how it scales. For now, I'd consider a free trial, and if it proved valuable, perhaps up to $300 per month for our team size, assuming it significantly reduces our manual review time.

Simulated interest: 60/100

Chris Medhurstneutral

My primary concern is the integration with our existing stack. We currently rely heavily on Datadog, Jira, and custom Python scripts for monitoring and incident response. While you mention integration with Datadog and other tools, I need to understand precisely how Sherlocks.ai would overlay or replace parts of our current workflow without causing more noise or requiring a complete overhaul. The fact that you run entirely within our VPC and are SOC 2 compliant is reassuring for security, but the operational integration details are key. I'm willing to consider a pilot, but the pricing is unclear without knowing the exact limits of the "Free" plan beyond "30 investigations." If the Enterprise plan is custom-priced, I'd need more details to estimate. My budget for a tool like this would be around $500-$750 per month, assuming it demonstrably reduces MTTR and alert fatigue for my small SRE team.

Simulated interest: 50/100