Think about your own work or business in this area: Show HN launch (205 pts, 2020-03-17): the product – APIs for enterprise features like SSO/SAML. Site shows pricing/signup. 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

54/100

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

Positive 0%Neutral 20%Negative 80%
The takeaway

What this panel suggests

The answers point to a fairly consistent operational pain: handling enterprise SSO/SAML requests is experienced as manual, brittle, and distracting from core product work. Respondents describe relying on spreadsheets, documentation, Notion-style checklists, and email threads, but still feeling stuck with a bottleneck. The main cost is not just inconvenience; it is engineering time and reduced velocity. One respondent says the work can consume “10-15 hours a week,” while others frame the impact as delayed shipping and lost capacity for core development. Several also worry about process errors, security risk, and the fragility of depending on a single engineer who understands the workflow. This reads as a workflow-friction problem more than a feature wishlist. No willingness-to-pay signal was established in these answers, so there is no basis here for pricing conclusions.

Recurring themes

Manual Operational Overhead
“The biggest problem is the sheer amount of manual overhead and the potential for error in managing SSO/SAML requests.”Read Zachary Nikolaus’s response →
Engineering Bottlenecks & Opportunity Cost
“costing us valuable engineering time that could be spent on core product development.”Read Zachary Nikolaus’s response →
Fragility of Current Workarounds
“We've tried documenting everything meticulously, but it's still a bottleneck.”Read Zachary Nikolaus’s response →

Objections to investigate

  • High manual effort required for setup and tracking
  • Risk of errors and security issues in ad-hoc processes
  • Single points of failure (reliance on one engineer)

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.

Zachary Nikolausnegative

The biggest problem is the sheer amount of manual overhead and the potential for error in managing SSO/SAML requests. We're coordinating through Notion, having one engineer build it out, and support logging details in Intercom. It’s fragile and inefficient, costing us valuable engineering time that could be spent on core product development. It also creates friction for sales and customer success when we're trying to close deals with mid-market clients who expect seamless integration. We've tried documenting everything meticulously, but it's still a bottleneck.

Simulated interest: 60/100

Doreen Ortizneutral

The biggest problem right now is manual verification of SSO enablement and tracking admin contacts. It consumes an immense amount of my time – easily 10-15 hours a week – that I could spend on strategic improvements. I've tried standardizing processes with checklists, but the sheer volume and constant changes mean it's always a reactive effort. We're a small team of 24, and our sole backend engineer is already swamped. Any automation here would be a huge win, freeing me up to actually *lead* operations instead of just wrangling spreadsheets.

Simulated interest: 70/100

Connor Manznegative

The single biggest problem we face right now is the manual effort involved in setting up our SAML integration for pilot customers. It's a process that takes me a significant amount of focused time, often several hours per client, which directly impacts our onboarding speed and is frankly, a bottleneck for growth. We've tried standardizing the process as much as possible, but each enterprise has unique requirements. I'm concerned about the potential for errors with this manual approach, and the time it takes away from developing core features. It essentially costs us engineering velocity and potentially delays our ability to scale.

Simulated interest: 70/100

Sukanya Koccharnegative

The biggest problem for us is the sheer amount of manual effort spent tracking onboarding exceptions and provisioning details. We're paying for a third-party identity service, but the surrounding administrative overhead is still managed in spreadsheets and scattered ticket comments. This is a significant drain on my small team's time – easily a few hours per customer setup that could be spent on more strategic work. It also introduces a risk of errors or missed information, which is not ideal for customer credibility. We've tried documenting the workflows, but it's just highlighting the inefficiency rather than solving it.

Simulated interest: 70/100

Aymonde Bourgeoisnegative

The biggest problem for us is the manual effort and potential for error in provisioning enterprise SSO. Sales comes with requests, often with tight deadlines for potential clients. We have homegrown scripts and rely heavily on email threads with support and sales to manage it. It's time-consuming and introduces inconsistencies. I've tried to streamline it with a Notion checklist, but it doesn't address the core process. It feels like a recurring overhead that distracts from core product development, and I worry about the security implications of our current ad-hoc approach. I haven't even begun to quantify the exact hours lost, but it's significant.

Simulated interest: 75/100

Ada Reichelnegative

The single biggest problem we have right now is our reliance on one engineer for all SAML setups. This creates a significant bottleneck, especially as we bring on more enterprise clients. It means delays in onboarding, and frankly, it keeps me up at night wondering what happens if he's sick or leaves. We've tried to mitigate it by creating detailed documentation, but it doesn't solve the core capacity issue. It's costing us potential client satisfaction and definitely adds time pressure on our engineering resources.

Simulated interest: 10/100

Eugene Morarneutral

The biggest challenge right now is managing administrative overhead as we scale. We're a three-person team, and tasks like handling user roles and occasional SSO requests are handled by custom scripts and free tiers. While it works for now, it's time-consuming and brittle. I estimate we spend maybe 5-10 hours a week collectively on this, which detracts from core development. We've tried a few open-source solutions, but integration is often more complex than the scripts themselves. The spreadsheet for enterprise features is also becoming unwieldy as we get more requests.

Simulated interest: 75/100

Marijn Dijkstranegative

The biggest problem is the sheer manual effort and potential for error in tracking our SSO/SAML rollouts. We currently use a spreadsheet, which is brittle and time-consuming. For each school district client, it's hours of configuration and then meticulous updates. This is a significant time sink for my team – easily a few hours per client that could be spent on core product development. We've tried to standardize some internal scripts, but they don't cover all edge cases, and keeping them updated is a burden. It feels like technical debt we're actively accumulating.

Oscar Emardnegative

The biggest problem we face right now is the manual handoff between our team, support, and engineering for complex SSO/SAML requests during prospect onboarding. It's a significant time sink, often costing us hours per request and occasionally delaying pilot setups, which can impact customer acquisition. We've tried improving our internal documentation and building out a shared tracker, but the intricate nature of some configurations still requires manual intervention. It's frustrating when a process we've tried to streamline still creates bottlenecks.

Simulated interest: 0/100

Gautam Acharyanegative

The biggest problem is the sheer engineering time and complexity involved in building and maintaining robust SSO/SAML integrations for our enterprise clients. Right now, it's a patchwork of custom code and manual configuration that one engineer struggles to keep up with. Every time we have to build it out for a new client, it pulls them away from core product features and introduces potential security risks. We've tried internal development, but it's a constant drain. I can't estimate a cost in terms of money precisely, but it's easily weeks of engineering time per integration, which, given our lean team, translates directly into delayed feature releases and lost opportunities.

Simulated interest: 60/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.