What would stop you from trying Sense_ (https://sensepm.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).

Page reviewed

Sense — Talk it through. Sense writes the ticket.

https://sensepm.com/ (opens in a new tab)
Saved screenshot of Sense — Talk it through. Sense writes the ticket.
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

57/100

AI synthesis, not measured demand

Suggested price range

$0–50

Median $25 · simulated willingness to pay

Response sentiment

Positive 0%Neutral 100%Negative 0%
The takeaway

What this panel suggests

The main reason people would not try Sense_ this month is not that the core idea is unattractive; it is that adoption has to fit an existing workflow immediately. Respondents described today’s process as manually recording screens, reviewing Loom-style feedback, and then converting the content into Linear or ClickUp tickets by hand. That makes Sense_ appealing as a time-saver, but also sets a high bar for trust and compatibility. The biggest objections were unclear pricing, uncertainty about how well it integrates with their current ticketing setup, and concern that the AI could miss nuance, invent details, or create extra cleanup work. Budget was mentioned too, but more as a practical constraint than a hard rejection. The willingness-to-pay data suggests a wide spread, from $0 up to $50 per month, with $25 as the midpoint, so a simple entry offer matters. Overall, the audience seems interested, but they want proof that the product is reliable, transparent, and easy to slot into the tools they already use.

A hypothesis to test

Pricing & positioning

Use a free-to-start funnel and test a low-friction paid tier around the reported median willingness to pay, with a higher tier only if teams see clear workflow fit and reliability.

Reported willingness to pay spans from $0 to $50/month, with a median of $25.Pricing clarity matters because uncertainty about the plan itself is an objection.A starter plan that removes setup risk would better match the current hesitation pattern than an upfront commitment.

Recurring themes

Current Manual Workflow Inefficiency
“Right now, I spend a lot of time recording my screen and then manually creating tickets in Linear”Read Helen Steuber’s response →
Integration & Tool Compatibility Concerns
“I'd need to see how well it integrates with ClickUp, as that's our primary tool”Read Tomas Roob’s response →
AI Accuracy & Nuance Skepticism
“My main concern is ensuring it captures the nuances correctly and doesn't create more work by generating tickets that aren't quite right”Read Helen Steuber’s response →
Budget Constraints
“Well, the fact that we don't have a budget for new tools right now”Read Ellen Salzer’s response →

Objections to investigate

  • Unclear Pricing Structure
  • Integration Friction with Existing Tools
  • Risk of AI Hallucination or Loss of Context
  • Lack of Immediate Budget Allocation

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.

Helen Steuberneutral

This looks like a really interesting tool for how I currently work. My biggest hesitation would be integrating it into our existing workflow seamlessly. Right now, I spend a lot of time recording my screen and then manually creating tickets in Linear, so a tool that automates that process is very appealing. My main concern is ensuring it captures the nuances correctly and doesn't create more work by generating tickets that aren't quite right. I'd want to test it thoroughly with my team to see how it handles complex bugs and edge cases before committing. The idea of it directly feeding into Linear is great, though. Given the stage of our company and my personal budget, I'd be willing to pay up to $40 per month for a tool that genuinely saves me time and improves clarity for the dev team.

Simulated interest: 70/100

Arnold Macejkovicneutral

What would stop me from trying Sense this month? Honestly, the process of manually highlighting timestamps and summarizing recordings is a significant time sink for me, so the appeal of automating that is huge. My main hesitation would be ensuring the AI doesn't invent details or misinterpret nuances. Today, my team records screens, and I manually extract the key moments and summarise them into ClickUp tickets. I'd need to see a pilot run or a very convincing case study from someone in a similar industry before committing budget. I'm not sure about the pricing, as it's not specified per month in USD, but given my cautious approach, I would not pay more than $30 per month.

Simulated interest: 60/100

Ellen Salzerneutral

What would stop me from trying Sense this month? Well, the fact that we don't have a budget for new tools right now, and I'm already spending quite a bit of time manually creating repro videos and writing tickets in Linear. The idea of automatically generating tickets from recordings sounds appealing, especially since I often have to re-watch those videos to get the exact moment right. However, integrating a new tool takes time, and I'm already struggling to balance feature development with bug reporting. I'd need to see how seamlessly it integrates with our current Linear workflow and if it truly saves me time. My maximum acceptable price would be $0 per month. We simply don't have the budget for new subscriptions, and my current role doesn't include software procurement.

Simulated interest: 30/100

Tomas Roobneutral

The concept of Sense sounds very appealing, especially the idea of turning screen recordings directly into developer tickets with timestamps. My current process involves manually creating these recordings in Loom, then logging them in Notion and pasting timestamps into ClickUp, which is a significant time sink. However, I'd need to see how well it integrates with ClickUp, as that's our primary tool. Also, the pricing isn't immediately clear – is it per user, or per recording? Without a clear pricing structure that aligns with our agency's budget, it's hard to commit. I'd be willing to pay around $50 per month for a tool that reliably automates this feedback loop for our four-person team.

Simulated interest: 60/100

Ismael Kuphalneutral

What would stop me from trying Sense this month is the lack of clear pricing. The page mentions "Maker launch on fazier" and "Pricing basis: USD per month subscription" but doesn't give specific tiers or costs. Today, I handle this by recording my screen, often with Loom, and then manually copying the relevant parts into ClickUp, which can be time-consuming. If the pricing were clear and reasonable, I might consider it, but without that, I'm hesitant. The maximum I would pay per month is $20.

Simulated interest: 30/100

Suryakantam Jhaneutral

The idea of Sense_ is interesting, especially the part about automatically writing tickets from screen recordings. Right now, I use a free screen recorder and then manually type out each issue into a spreadsheet, one ticket per recording. This can be time-consuming, and sometimes I worry about losing the full context. Sense seems to automate that, which could save me a lot of effort. However, I'm hesitant to try it this month because my workload can be inconsistent, and I need to ensure I can justify any potential costs. If it integrates well with my current workflow and truly saves time, I might consider paying up to $15 per month, but I'd need to see how it performs first. I'm also curious if it works with other tools besides Linear and ClickUp.

Simulated interest: 60/100

Aline Le gallneutral

Our current workflow involves recording screens and then manually converting those into Linear tickets. Sense_ seems like it could automate that conversion, which is appealing because processing those recordings takes a lot of time. However, I'd need to see how well it integrates with our existing processes and if it truly saves time rather than adding another tool to manage. I'd also want to ensure my team can adopt it easily without disruption. If it proves to be a significant time-saver and integrates smoothly, I could see paying around $20 per month, per user.

Simulated interest: 70/100

Jorge Uribe Herreraneutral

The main thing stopping me from trying Sense this month is that I already have a system that works for me. I record my screen, log it in Google Sheets with timestamps, and then create ClickUp tickets. While Sense seems to automate the ticket creation part, I'd need to see how seamlessly it integrates with my current workflow, especially since we don't use Linear or ClickUp exclusively for all our development tasks. I'd be willing to pay around $15 per month, but only if it significantly streamlines my current process without adding complexity.

Simulated interest: 60/100

Natasha Cummingsneutral

What would stop me from trying Sense this month is that I'm not entirely clear on how it integrates with our current ClickUp workflow beyond just sending tickets. My current process involves recording Loom clips, adding detailed notes, and then manually assembling those into ClickUp tasks, often collaborating with a designer to ensure the issue is perfectly clear. While Sense sounds like it automates the ticket creation from recordings, I'm concerned about whether it captures all the nuances a designer and I would add manually, and if it truly streamlines the entire handoff process. I'd be willing to pay around $30 per month for something that demonstrably saves me significant time in documentation and improves the clarity of our developer handoffs.

Simulated interest: 60/100

Goswamee Pandeyneutral

The way I handle bug reports now is quite specific: I record my screen and narrate the issue in detail, then meticulously craft tickets in Linear for my developer. Sense_ seems to automate this exact process by turning recordings into tickets with timestamped narration. The biggest hesitation I have is the risk of losing the personal touch and nuance my customers appreciate. I'd need to see if it truly captures the context as well as I do. If it works as advertised and integrates smoothly with Linear, I might consider paying around $25 per month, as I'm very budget-conscious.

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.