⚠ Synthetic pre-research — AI-generated directional signal. Not a substitute for real primary research. Validate findings with real respondents at Gather →
Projected from interview analyses using Bayesian scaling. Treat as directional estimates, not census measurements.
Side-by-side comparison of sentiment, intent, buying stage, and decision role across all personas.
Complete question-by-question responses with per-persona analysis. Click any respondent to expand.
Tanya is a measured skeptic, not an opponent. She sees potential value in AI SDR tooling — particularly for scaling coverage without headcount — but has two hard blockers: accountability clarity and proof of enterprise-grade pipeline quality. Her current SDR motion is functional but imperfect (self-rated 6/10), and she's open to change if the evidence meets her bar. Her tone throughout is analytical and risk-aware rather than hostile. The accountability theme is her dominant concern and she raises it unprompted across nearly every question, suggesting it is a genuine unresolved problem rather than a rhetorical deflection.
Tell me what's top of mind for you on this topic right now — what are you wrestling with?
Right now the biggest thing I'm wrestling with is accountability. If my SDR team misses, I can make personnel moves, show the board I'm responding, buy some time to fix things. If I've handed that function over to an AI tool and it misses — or worse, starts spamming our target accounts — that's on me with no buffer. The risk profile feels different. The other piece is just figuring out where AI actually fits in the workflow versus where we still need humans. I'm not convinced the full replacement story makes sense for our segment, but there's probably something real around using it to scale coverage without adding headcount. I just haven't seen a clean model for how that works in practice at the enterprise level.
What's the most important thing you need to understand or solve here?
Right now, my biggest concern is accountability. If my SDR team misses, I can dig in — figure out who's underperforming, make changes, work the problem. If I hand that function to an AI tool and we miss quota, I'm not sure where I point fingers. And more importantly, my leadership isn't sure either — which means the finger points at me. The other piece is just pipeline quality. I need meetings that actually convert, not volume for its own sake. So before I'd commit to anything in this space, I'd want to understand how AI SDR activity translates into real pipeline, not just activity metrics.
What does 'good' look like to you — and how far are you from that today?
For us, "good" means a consistent, qualified pipeline that my AEs aren't constantly questioning. Like, meetings that actually convert — not just activity metrics that look good on a dashboard but fall apart in discovery. Where we are today? Probably a 6 out of 10. The volume is there, but quality is still inconsistent, and my team spends too much time triaging what SDRs are handing them. That handoff friction is probably my biggest day-to-day headache right now.
What would change your perspective on this entirely?
If I saw consistent, verifiable pipeline data from companies at our scale — not a startup with 50 accounts, but an actual enterprise motion — showing that AI SDRs were generating qualified meetings that converted at rates comparable to a solid human SDR, that would move the needle for me. Right now I'm not seeing that. The other thing that would shift me is accountability clarity. Right now if my SDR team misses, I have levers — I can coach, I can restructure, I can make personnel decisions. If I've handed that function to a vendor's AI and we miss a quarter, I'm not sure what I do with that. If someone could show me a clear framework for how that accountability works, I'd take it more seriously.
What question are you not being asked that you wish someone would ask?
The accountability question, honestly. Like, if an AI SDR burns through a contact list or tanks your sender reputation with a prospect segment, who owns that? Is it a vendor problem, an ops problem, a sales problem? Right now nobody has a clean answer to that, and I think it matters a lot more than the "will it book meetings" conversation everyone leads with.
"If I hand that function to an AI tool and we miss quota, I'm not sure where I point fingers. And more importantly, my leadership isn't sure either — which means the finger points at me."
Priya is a skeptical but genuinely open evaluator of AI SDRs, held back by two substantive and well-reasoned concerns rather than general resistance. First, brand risk: in enterprise retail, she sells into a defined community of decision-makers and views poorly calibrated AI outreach as a reputational liability she personally owns. Second, accountability: she is unsatisfied with how responsibility is allocated when AI systems underperform, and anticipates that 'the AI underperformed' will not be accepted by her board. She is also navigating real internal pressure to show pipeline growth, which she notes creates incentives to optimize for volume metrics that don't reflect revenue quality. Her stated path to conviction is narrow but specific — comparable peer evidence from enterprise retail contexts and contractual accountability for brand risk — suggesting she is persuadable under the right conditions rather than categorically opposed.
Tell me what's top of mind for you on this topic right now — what are you wrestling with?
Right now the board pressure piece is real. We're being asked to show pipeline contribution from marketing, and AI SDRs keep coming up in those conversations as a potential lever — like, "why aren't you doing this, everyone else is." So I'm wrestling with the gap between what's being promised by vendors and what I'm actually seeing in terms of evidence that it works at our scale and for our buyer profile. The other thing is brand risk. We're in enterprise retail, our buyers know us, and a poorly calibrated outreach sequence that feels robotic or off-message does real damage. I'm not cavalier about that. So even if the efficiency case is there, I'm thinking about what happens when something goes wrong and it's our brand on the receiving end of a prospect's frustration.
What's the most important thing you need to understand or solve here?
For us, the core question is whether AI SDRs actually protect pipeline quality or quietly erode it. We're an enterprise retailer — our brand matters, and if an AI is sending outreach that feels off-brand or just spammy, that's a reputation problem I own, not just a sales operations problem. The second piece is accountability. Right now if pipeline misses, there's a conversation to have — you can look at the team, adjust the playbook, make changes. With an AI system, I'm less sure where the accountability lands when things go sideways, and my board is not going to accept "the AI underperformed" as an answer.
What does 'good' look like to you — and how far are you from that today?
For us, "good" means a prospect actually wants to take the meeting — not just a booked slot that no-shows or cancels within 24 hours. The quality signal I care most about is whether the conversation that gets scheduled actually advances into pipeline that the sales team is excited about working. Where we are today? Honestly further from that than I'd like. We've got tools layered on tools, and there's a lot of activity that looks like progress in a dashboard but doesn't hold up when you trace it back to revenue. The board pressure to show pipeline growth is real, and that creates incentives to optimize for volume metrics that don't always tell the right story. The other piece is brand. In enterprise retail, our reputation with buyers matters — we're selling into a relatively defined community of decision-makers. A poorly calibrated outreach sequence, AI-generated or otherwise, does damage that's hard to quantify but very real.
What would change your perspective on this entirely?
For me, it would really come down to seeing consistent, verifiable performance data from companies that are actually comparable to us — enterprise retail, complex brand considerations, long buying cycles. Right now most of the case studies I see are from either very high-volume transactional environments or early-stage companies where the bar for "pipeline" is pretty different. The other thing that would genuinely shift my thinking is if the brand risk question got a cleaner answer. We have real NPS exposure if a prospect gets a bad AI interaction and associates that with our brand — and I haven't seen a vendor make a compelling argument for how they're managing that at scale. Show me that, with real accountability built into the contract, and I'd take a much harder look.
What question are you not being asked that you wish someone would ask?
That's a fair question. I'd say it's something like: "How does your brand reputation hold up when AI gets it wrong at scale?" Everyone wants to talk about pipeline volume and cost per meeting, but in retail, our brand *is* the relationship. If an AI SDR sends thousands of off-brand or just plain awkward outreach messages to our retail partners or key accounts, the reputational cleanup is not a line item anyone's modeling. I sit in board meetings where we're being pushed on pipeline ROI, and nobody's asking what the failure mode looks like at scale — they're only asking about the upside. That's the conversation I'd actually want to have.
"Everyone wants to talk about pipeline volume and cost per meeting, but in retail, our brand is the relationship. If an AI SDR sends thousands of off-brand or just plain awkward outreach messages to our retail partners or key accounts, the reputational cleanup is not a line item anyone's modeling."
Chris is an analytically-oriented demand gen leader who is genuinely evaluating AI SDRs but remains unconvinced. His skepticism is specific and operational: he questions whether the tools move real pipeline or just generate measurable activity, doubts the CAC math given ongoing human oversight requirements, and sees attribution as a compounding problem rather than a solvable one. He's not dismissive — he articulates clear conditions that would change his view (downstream conversion data, clean attribution integration) — but he's nowhere near a buying decision. His most distinctive concern is accountability: when an AI tool underperforms, the ownership structure is murky in ways that human SDR management is not. Overall tone is measured, skeptical, and analytically grounded.
Tell me what's top of mind for you on this topic right now — what are you wrestling with?
Right now the main thing I'm wrestling with is whether AI SDRs actually move pipeline or just create activity that looks like pipeline. We've been under a lot of pressure to grow qualified pipeline without growing headcount, so on paper it seems like an obvious thing to evaluate. But every demo I've sat through, the vendor is promising something close to full replacement of outbound motion, and I'm skeptical of that framing. The more practical tension for me is attribution. If an AI SDR touches a prospect and then one of our AEs follows up and closes it six months later, how do I even measure whether the AI was additive? That's not a new problem — I deal with attribution headaches constantly — but it gets messier when you're layering in a system that's running semi-autonomously and logging things inconsistently in Salesforce. The other thing I keep coming back to is CAC. If I'm paying for a platform, plus still need someone to oversee it, QA the messaging, and handle anything the AI can't close — what's the actual cost reduction? I haven't seen math that convinces me yet.
What's the most important thing you need to understand or solve here?
For us, the core question is whether an AI SDR actually moves pipeline or just moves activity. We can instrument a lot — sequences sent, replies, meetings booked — but connecting that to closed revenue in a way that's attributable is genuinely hard. And CAC is something I watch closely, so if I'm spending on tooling plus still needing humans to close, I need to understand where in the funnel the AI is actually creating leverage versus just generating noise. The secondary piece is quality control. At our stage, a bad outbound experience with the wrong prospect can burn a segment of our ICP. That's not a recoverable mistake in a small market.
What does 'good' look like to you — and how far are you from that today?
For us, "good" is a consistent, predictable pipeline that I can actually trace back to specific channels and activities. Like, I know what we spent, I know what came in, and I can tell a coherent story to the CRO about CAC by segment. That's the dream. How far are we? Honestly further than I'd like. Attribution is still messy — we're running a mix of paid, content, some outbound, and partner stuff, and the multi-touch models we have don't fully account for the overlap. So there's always this negotiation about what "counts" toward pipeline. That's probably my biggest day-to-day headache right now — not the execution side, but the measurement side.
What would change your perspective on this entirely?
If I saw consistent, clean data showing that AI SDR-sourced pipeline was closing at rates comparable to rep-sourced pipeline — not just booking meetings, but actually converting — that would move me. Right now the thing I can't get past is that booked meetings are a vanity metric if the downstream conversion falls apart. The other thing would be better attribution clarity. Our stack is already a mess when it comes to knowing what touched what before a deal closed, and adding an AI layer that's doing outreach in parallel with everything else just makes that harder. If a vendor could show me how their tool integrates cleanly and doesn't blow up my existing attribution model, I'd take that conversation a lot more seriously.
What question are you not being asked that you wish someone would ask?
The accountability question, I guess. Everyone asks whether AI SDRs work — open rates, meeting booked rates, pipeline influenced. But nobody really asks: what happens when it goes wrong and who owns that? With a human SDR, there's a clear escalation path. Performance management, coaching, eventually a personnel decision. With an AI tool, if you exhaust a segment or burn through a list with bad messaging, that accountability kind of dissolves. Did the vendor underdeliver? Did we configure it wrong? Did RevOps set the wrong parameters? It gets murky fast, and in my experience that murkiness is where budget decisions go to die. I'd love someone to ask how teams are actually structuring ownership around AI SDR outcomes — not just who bought the tool, but who's on the hook when the numbers don't move.
"If I'm paying for a platform, plus still need someone to oversee it, QA the messaging, and handle anything the AI can't close — what's the actual cost reduction? I haven't seen math that convinces me yet."
James is a measured, analytically oriented CFO who is neither opposed to AI SDR tooling nor enthusiastic about it. His primary concern is measurement validity — he consistently rejects activity-based ROI metrics (emails sent, sequences run) in favor of P&L-visible ratios like revenue per employee, cost of revenue, and sales cycle length. A secondary but equally firm concern is accountability: he has no clear answer for who owns failure when an AI system underperforms, and vendor conversations have not addressed this. He is also attentive to data quality and relationship risk, the latter being particularly salient given a concentrated manufacturing customer base. He has not made a purchase decision and expects the topic to become active in the next budget cycle. He is open to being persuaded, but specifically by clean before-and-after pilot data from a comparable environment — not broad efficiency narratives.
Tell me what's top of mind for you on this topic right now — what are you wrestling with?
Right now the core question for me is headcount. We've got SDRs on payroll, and every conversation about AI SDRs eventually comes back to: do we reduce the team, retrain them, or just layer a tool on top and call it efficiency? Nobody's giving me a clean answer on that. The second thing is measurement. I've sat through enough vendor pitches where the ROI story is built around "hours saved" or "sequences launched." That doesn't move anything on my P&L. What I actually want to see is whether pipeline quality changes, whether sales cycle compresses, whether revenue per rep improves. Those are the ratios I care about. We haven't pulled the trigger on anything yet. We're in a watch-and-see mode, but the pressure from the commercial side of the house to do something is building, so I expect this becomes a real decision in the next budget cycle.
What's the most important thing you need to understand or solve here?
The accountability question is probably the biggest one for me. If we bring in an AI SDR tool and pipeline suffers — who owns that? With human SDRs, you have a clear performance management chain. You can put someone on a pip, you can make a hiring or firing decision, you can point to where the breakdown happened. With an AI system, that accountability gets murky fast, and I'm not sure most vendors have a clean answer for that. The second piece is just measurement. I've seen too many of these tools get evaluated on "hours saved" or activity volume — emails sent, sequences run. That doesn't tell me anything about revenue per opportunity or what happened to conversion rates downstream. If I can't tie it to something on the P&L, it's a hard conversation to have with the board.
What does 'good' look like to you — and how far are you from that today?
For us, "good" means the tool is moving a metric that shows up in a ratio I actually track — revenue per employee, cost of revenue as a percentage of revenue, sales cycle length. Not "hours saved" on some spreadsheet that nobody checks. Right now we're pretty far from that with AI SDRs specifically. We've had a couple of vendors come through the door, and the conversations tend to stay at the activity level — emails sent, sequences run, response rates. I'm not hostile to those metrics, but they're not where I land when I'm evaluating whether a headcount decision was right. I need to see it compress the pipeline or reduce what I'm spending per closed deal. The other piece is the data architecture underneath it. Our CRM is fine but it's not pristine, and I've been around long enough to know that if the inputs are messy, whatever the AI is doing with them is going to be messy too. So before I'd call anything "good," I'd want a narrow pilot with a clean before-and-after on one specific workflow — not a broad rollout where we're just hoping something improves.
What would change your perspective on this entirely?
If I saw clean before-and-after data on pipeline quality — not just volume metrics — from a company in a similar manufacturing environment, that would move the needle for me. Right now most of what I'm seeing from vendors is activity-based ROI: emails sent, sequences run, contacts touched. That's not how I think about the business. I care about revenue per employee and whether sales cycle length actually compressed. The other thing that would shift me is if someone showed me a genuine small-scope pilot with a clear owner and defined success criteria that held up over two or three quarters. Not a 500-seat rollout with a vague efficiency narrative. If the data architecture is clean and the measurement is honest, I'd take a harder look.
What question are you not being asked that you wish someone would ask?
That's a fair question. I'd say it's something like: "Who owns the accountability when the AI SDR gets it wrong?" Right now every vendor conversation I've had is about the upside — pipeline generated, sequences sent, response rates. Nobody's walking me through what happens when the tool spams a prospect who turns out to be a key relationship, or sends the wrong message at the wrong time in a deal we were already working. In manufacturing, our customer base isn't huge. You burn a relationship, that's real money, and it doesn't show up in the AI vendor's dashboard.
"If I can't tie it to something on the P&L, it's a hard conversation to have with the board."
Synthetic pre-research uses AI personas grounded in real buyer archetypes and (where available) Gather's interview corpus. It produces directional signal — hypotheses worth testing — not statistically valid measurements.
Quantitative figures are projected from interview analyses using Bayesian scaling with a conservative ±49% margin of error. Treat as estimates, not census data.
Reflect internal response consistency, not statistical power. A 90% confidence score means high AI coherence across interviews — not that 90% of real buyers would agree.
Use this to build your screener, align on hypotheses, and brief stakeholders. Then run real AI-moderated interviews with Gather to validate findings against actual respondents.
Your synthetic study identified the key signals. Now validate them with 150+ real respondents across 4 audience types — recruited, interviewed, and analyzed by Gather in 48–72 hours.
"What do revenue leaders actually think about AI SDRs — promise or pipeline risk?"