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

Tyrone Sipesneutral

Today, I'm meticulously analyzing production traces after releases and comparing prompt variants in notebooks to ensure our customer-support agent is stable. I maintain a small set of replayable conversations in staging to verify routing, tool calls, and tone before any changes go live. The core issue with Mirrors is that the pricing isn't public. Without knowing the cost, it's impossible to assess its feasibility. I need to understand if it fits within our budget, considering my company's size and the general cost of living in San Francisco. I would be willing to pay up to $250 per month if the value proposition aligns with our needs and the pricing is transparent.

Simulated interest: 60/100

Viola Hillsneutral

What would stop me from trying Mirrors this month? Frankly, the lack of clear pricing. You mention a demo to "scope pricing around that use case," but I need to understand the potential cost before dedicating time to a demo, especially since my current process involves manually tagging thousands of logs in spreadsheets and then running small replay tests with engineers. This sounds very similar to what Mirrors offers, so the 'what if' is whether it scales cost-effectively for our internal policy assistant. If it integrates seamlessly and offers significant time savings over my current approach, I might consider it. My maximum would be $150 per month, billed monthly, but that's a speculative figure without understanding the product's specifics.

Simulated interest: 40/100

Jyotis Singhneutral

What stops me today is the budget. We're really lean, so I'm relying on free observability tools and custom GitHub scripts for monitoring and testing, which means manual reviews are a big part of my week. The idea of routing context mid-conversation without redeploying sounds powerful, especially for quickly iterating on prompt changes. However, the pricing isn't clear at all, saying 'most teams start with one workflow' and to 'book a demo to talk it through.' Without knowing the cost structure, it's impossible to say. If it were a predictable, low monthly fee, maybe $50 USD per month, I might consider it, but it's too ambiguous right now.

Simulated interest: 40/100

Alana Chapronneutral

The biggest hurdle for me right now would be integrating a new tool without disrupting our current workflow, especially since we're focused on improving our conversational agent. I currently handle reproducing production failures by manually exporting conversations into scripts for release checks. This product seems to automate that process, which is appealing. However, the pricing isn't publicly listed, and I'd need to understand how it scales with our usage before committing. I'm not willing to pay anything until I have a clearer picture of the cost and integration effort.

Simulated interest: 30/100

Ludovic Caronnegative

Currently, my team and I meticulously review sampled conversations, then document failure modes in a spreadsheet. We then work with engineers to test routing rule changes based on these findings. The primary concern stopping me from trying Mirrors this month is the lack of clear pricing. The site mentions "scope pricing around that use case" but doesn't provide any figures. Without knowing the cost structure, it's difficult to commit resources or even evaluate its value against our current process. I would need to see specific pricing details to consider adoption. Given this ambiguity, I'd pay $0 per month for a tool with no clear pricing.

Simulated interest: 0/100

Jessie McKenzieneutral

The primary reason I wouldn't immediately jump on Mirrors this month is the lack of clear pricing. You mention it's a subscription, but the FAQ states there's no public price list and pricing is scoped per use case. Today, I manually trace conversations in staging environments and rerun paths to catch edge cases because each client's setup is so unique. Without understanding the cost structure, especially per month, it's hard to assess if it fits our budget. I'd need to see a defined pricing tier, perhaps based on usage or number of workflows, before committing.

Simulated interest: 40/100

Jennifer Rippin-Wilkinsonneutral

The primary obstacle to trying Mirrors this month would be the current workload. My days are heavily focused on analysing trace logs, ensuring policy wording changes don't negatively impact our insurance assistant's behaviour, and meticulously documenting edge cases for our release reviews in a small shared tracker. We have limited engineering resources, so introducing a new tool requires careful consideration of implementation time and potential disruption. Currently, we manage these issues by manually reviewing logs and updating our tracker, which is time-consuming but familiar. Regarding pricing, the page mentions "no public price list yet" and that they scope pricing around a specific use case. Without more clarity on their model, it's difficult to estimate, but I would be hesitant to commit to anything more than $150 per month initially.

Simulated interest: 30/100

Thiago Postneutral

The main thing that would stop me from trying Mirrors this month is the lack of clear pricing. Today, I handle reviewing traces and labeling failures manually in spreadsheets, which is time-consuming. I then use Python notebooks to replay conversations. While Mirrors seems to automate parts of this, I need to understand the cost. Without a public price list, it's hard to commit. If I had to estimate, I'd say I might consider paying up to $150 per month, but that's highly dependent on the features and scale it offers.

Simulated interest: 40/100

Veda Iyerneutral

The biggest factor stopping me from trying Mirrors this month would be the unclear pricing. You mention you don't have a public price list yet and that pricing is scoped around specific use cases, but my clients are SMBs, and we operate on very tight budgets. I need to know potential costs upfront to ensure it fits within our project pricing. Today, I'd be manually analyzing trace exports and spreadsheets to identify routing issues and then incorporating fixes directly into the workflow logic, which is time-consuming. I would consider paying up to $100 per month, but that would be highly dependent on the actual feature set and how it scales with our client base.

Simulated interest: 40/100

Alan Hermannneutral

The main thing that would stop me from trying Mirrors this month is our current process. We rely on free tools, manual checks, and a shared spreadsheet to manage AI testing. It's not ideal, but it's what we have and it's free. I'd need to see a clear demonstration of how Mirrors significantly improves efficiency and accuracy compared to our current, no-cost method, and how it integrates with our workflow without disrupting the team's day-to-day. I'm also concerned about budget; while I see there's no public price list, I'd be hesitant to spend more than $150 per month for a new tool, especially given my focus on cost-effectiveness.

Simulated interest: 40/100