Think about your own work or business in this area: the product is an easy-to-use staff leave planner. Keep your team organised with our annual leave software. Try for free today. 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
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
What this panel suggests
Across the synthetic responses, the dominant problem is not a lack of interest in leave planning software; it is the burden and risk of managing leave manually across disconnected tools. Respondents describe spending substantial time cross-referencing spreadsheets, calendars, chat approvals, and payroll cutoffs just to avoid clashes. The business cost they emphasize is operational: missed coverage, double-bookings, delayed site visits, and the possibility of payroll mistakes or missed client commitments. The current process is portrayed as fragile and stressful, with one respondent calling it a “ticking time bomb” and another describing “low-level stress.” They have already tried improvised stacks of Excel, Google Calendar, Slack, Notion, wall charts, and handwritten notes, but those workarounds still require constant checking and reconciliation. A recurring objection is skepticism that a leave planner will really be “easy-to-use” enough to replace the reliability of their current workarounds, especially where approvals, payroll timing, and holiday rules are involved. These are synthetic reactions to the problem space, not validated market demand or pricing evidence.
Recurring themes
“The biggest problem is the sheer amount of manual cross-referencing I have to do.”Read Leona Hansen’s response →
“Last quarter, a site visit nearly clashed with someone's holiday because of a last-minute entry.”Read Leona Hansen’s response →
“My current system, a mix of a complex Excel spreadsheet, a wall chart and handwritten notes for our part-time staff, is frankly a nightmare.”Read Rose Franecki’s response →
Objections to investigate
- Reliability and error risk in automated systems
- Regional holiday configuration complexity
- Skepticism about 'easy-to-use' claims versus current process reliability
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.
Leona HansennegativeThe biggest problem is the sheer amount of manual cross-referencing I have to do. Engineers submit leave requests, and I have to spend hours checking our project schedule in Excel to make sure there are no clashes. It's time-consuming and frankly, I worry about making a mistake. Last quarter, a site visit nearly clashed with someone's holiday because of a last-minute entry. We haven't tried anything specific yet, beyond me being extra vigilant and keeping a separate logbook, but it feels like a ticking time bomb. The cost is my time, which could be better spent elsewhere, and the risk of disruption if a clash isn't caught.
Simulated interest: 70/100
Roland HuelnegativeThe biggest problem isn't just planning leave; it's the manual cross-referencing. I spend hours verifying PTO requests against Google Calendar for four department leads and then reconciling with payroll cutoffs. A single oversight can lead to scheduling conflicts that disrupt projects, or worse, payroll errors, which I've thankfully avoided but the risk is significant. This takes up a considerable amount of my time each week, time I'd rather spend on more strategic HR initiatives. I've already implemented a secondary verification step, but the core issue is the disconnected systems.
Meenakshi PillainegativeMy biggest problem right now is the sheer inefficiency of our current leave tracking. It's a constant back-and-forth between Google Sheets and WhatsApp, which is incredibly time-consuming and prone to errors. Last Saturday, I spent hours reconciling conflicting requests! This disorganization directly impacts team capacity planning and can lead to last-minute scrambles for coverage, potentially affecting client deliverables. We've tried creating more detailed spreadsheets and setting stricter communication rules, but it's still just not integrated enough.
Simulated interest: 75/100
Rose FraneckinegativeThe single biggest problem is the sheer amount of time I spend wrestling with it all. My current system, a mix of a complex Excel spreadsheet, a wall chart and handwritten notes for our part-time staff, is frankly a nightmare. It’s probably costing me at least five hours a week, especially during busy periods. I've tried to streamline it by creating templates, but it's still incredibly fiddly ensuring bank holidays and training days don't clash with essential chair coverage for our 28 staff. It’s a constant source of low-level stress.
Simulated interest: 40/100
Gloria BerniernegativeHonestly, the biggest problem I have is the sheer overhead of managing multiple, disconnected tools. We're juggling Slack for approvals, a Notion table for logging, and Google Calendar. It's functional, but it requires constant manual syncing and is prone to errors. This eats up valuable time I could be spending on strategic growth. I've tried standardizing our internal processes as much as possible, but the lack of integration is a persistent friction point. I'm concerned about scalability and ensuring clear communication as we grow, which this fragmented system doesn't easily support.
Simulated interest: 40/100
Henning BringmannnegativeAn 'easy-to-use' staff leave planner? We already have a system, an Excel sheet that works. My biggest problem is ensuring regional holidays are always correctly accounted for, which seems to be a common oversight with automated systems. For example, last year it cost us a few hours reconciling an error related to a specific local holiday not being recognized. I already spend days each month verifying everything manually, so I'm wary of anything that might introduce a 'black box' problem. I need to be absolutely sure it's more reliable than my current process, not just 'easier'. What happens if the 'easy' system makes a mistake I can't easily spot?
Simulated interest: 10/100
Victoire MaillardnegativeAn 'easy-to-use staff leave planner'? The biggest problem I have is with the paper register. It takes me at least an hour each week, sometimes more, to reconcile it with the shared calendar. During busy periods, like holidays, I spent an entire afternoon fixing discrepancies last year. It's not just the time lost, which is significant given my workload, but the potential for error. If I miss something, a lawyer might be double-booked or a client call goes unanswered because coverage wasn't properly arranged. We've always done it this way, so I'm hesitant to change, but it feels increasingly fragile.
Simulated interest: 40/100
Jordy CornelissennegativeHonestly, managing last-minute leave requests that clash with project timelines is a constant headache. We've had instances where a key supervisor calls in sick right before a critical phase, forcing us to scramble, pull resources from other sites, or even delay work. This costs us valuable time, adds stress, and can potentially damage client relationships if we miss deadlines. We're currently relying heavily on our manual handover notes and constant phone calls to mitigate this, but it's far from ideal. I'm always looking for a way to better predict and manage these disruptions.
Simulated interest: 75/100
Batilda MirabellanegativeThe biggest problem is the constant back-and-forth required to align our Google Sheets with the Microsoft Teams calendar. It's not just about who is off, but ensuring the *right* people are available for client meetings and site visits. This manual cross-referencing consumes hours each week, and during busy periods like summer holidays, it becomes a significant stressor. We’ve tried more stringent sign-up procedures, but people forget or make mistakes. The risk of a miscommunication costing us a client presentation or delaying a critical site visit is always present, which is unacceptable for our studio's reputation.
Simulated interest: 75/100
Benjamín Oquendo EspinalnegativeThe biggest problem we have is ensuring our part-time agents, who have highly variable schedules, get their leave approved quickly without creating coverage gaps. Factorial helps, but there's still a lot of manual cross-referencing with shift schedules and manager approvals. This lag can lead to agent anxiety and, occasionally, last-minute scrambles for cover, which eats up maybe 5 hours of my week manually juggling things and potentially impacts our SLA if a client needs immediate support and we're short-staffed. I’ve tried streamlining the approval notifications, but the core issue is balancing flexibility with guaranteed coverage.
Keep exploring.
Find your next question or see which topics divide AI panels.
What would you ask next?
Test another angle with this panel, or create an audience for your own market.