HR Buyer Discovery Call Script for Founders

An HR buyer discovery call has to do more work than a typical user interview, because you're not just trying to understand pain — you're trying to understand budget reality, an already-crowded tool stack, real compliance constraints, and a buying process that's often more bureaucratic than it first appears. Eighteen questions, organized into four blocks, get you through all of it without turning the call into an interrogation.

Quick Answer: Run an HR buyer discovery call in four blocks — current pain and workflow, existing tool stack and what it can't do, budget and compliance reality, and buying process — and always ask about specific past events and actual current spend rather than hypothetical future interest, following Mom Test discipline throughout.

The Call Script, Ready to Copy

Block 1: Current Pain and Workflow

  1. "Walk me through how your team currently handles [specific workflow] on a normal week."
  2. "What's the most time-consuming or frustrating part of that, specifically?"
  3. "Tell me about the last time this caused a real problem — what happened?"
  4. "How has this changed as your team has grown?"

Block 2: Existing Tool Stack

  1. "What tools do you currently use for this, and for adjacent workflows?"
  2. "What do you like about your current stack?"
  3. "What's missing or actively frustrating about it?"
  4. "Have you evaluated or switched tools for this in the past two years? What happened?"
  5. "Is there anything in your stack today that you're actively unhappy with and thinking about replacing?"

Block 3: Budget and Compliance Reality

  1. "Roughly what does your team currently spend on HR tools in total?"
  2. "Who controls that budget — you directly, or does it need approval above you?"
  3. "Are there specific compliance or data requirements — SOC 2, specific data residency, industry-specific regulation — that any new tool would need to meet?"
  4. "Has a compliance or legal review ever blocked or slowed down a tool purchase you wanted to make?"
  5. "What's the realistic budget range for solving a problem like this, if you had to guess?"

Block 4: Buying Process

  1. "Walk me through how the last new tool actually got approved and purchased."
  2. "Who else needs to be involved — IT, security, finance, legal?"
  3. "How long did that process take, start to finish?"
  4. "What's made a promising tool evaluation stall or die in the past?"

Question-by-Question Intent

Block 1's questions (1–4) exist to get a detailed, specific picture of the real workflow rather than a summary — question 3, asking for the last specific instance of a real problem, is the core Mom Test move that converts a general complaint into concrete, checkable evidence.

Block 2's questions (5–9) map the competitive landscape as the buyer actually experiences it. Question 8, asking about a past evaluation or switch, is particularly valuable because it reveals how this buyer actually behaves when genuinely motivated to change tools — a much stronger predictor than their stated opinion about your specific idea.

Block 3's questions (10–14) surface the two things that most often sink an otherwise promising HR tech pitch after the fact: budget reality and compliance constraints. Question 10's direct ask about current total spend gives you a real anchor for pricing; question 12's compliance question, asked early rather than discovered late in a sales process, can save months of wasted effort building toward a deal that a security review was always going to block.

Block 4's questions (15–18) map the actual buying process — not the theoretical org chart, but what really happened the last time this buyer bought something. Question 18, asking what's made a promising evaluation die before, is often the single most valuable question in the entire script, because it surfaces the specific failure mode you need to design your own sales process around.

Filled Example: Excerpts From a Discovery Call

Founder testing an idea for a lightweight performance-review tool, talking with an HR Director at a 120-person company:

Q3 (last time it caused a problem): "Our last review cycle, I had three managers who just didn't submit reviews on time, and I ended up chasing them individually over Slack for almost two weeks past the deadline — by the time we finished, the comp committee meeting had already happened, so those three people's raises got delayed to the next cycle."

Q10 (current spend): "We're paying about $9 a seat a month for our current performance tool, so across the company that's... I want to say somewhere around $13,000 a year, plus whatever time I personally spend chasing people, which is not nothing."

Q12 (compliance requirements): "Nothing formal yet, honestly — we're small enough that we haven't had a real security review process. But our CTO has started asking about SOC 2 for anything that touches employee data, so I'd guess that's coming soon."

This excerpt gives the founder three usable, specific data points: a concrete, costly failure story tied to a real business consequence (delayed raises), a real current spend number to price against, and an early warning that a security review requirement is emerging even though it isn't formalized yet — exactly the kind of detail a vaguer "tell me about your performance review process" question would likely have missed.

Adaptation Notes: HR Generalist vs. CHRO vs. People Ops

For an HR generalist at a smaller company, often wearing multiple hats, spend more time on Block 1 and 2 — they're closer to the actual day-to-day pain and less likely to have a fully formed sense of budget or formal buying process, so Block 3 and 4 answers may be rougher estimates rather than precise numbers.

For a CHRO or senior HR executive, shift weight toward Block 3 and 4 — they're more likely to have real visibility into budget authority and the formal buying process, and their Block 1 answers may be somewhat removed from the day-to-day workflow detail a generalist or people ops specialist would give you directly.

For a People Ops specialist, who often sits closer to both the daily workflow and some budget authority depending on company size, expect a useful blend across all four blocks — this role is frequently the best single interview if you can only get one conversation at a target company, since they typically span both the user's daily pain and enough of the buyer's process knowledge to be genuinely useful on both fronts.

Key Takeaways

Frequently Asked Questions

How long should this discovery call take?

Thirty to forty-five minutes is enough to work through all eighteen questions with a genuinely engaged buyer, though you should prioritize depth on the questions that produce the most specific, useful answers over rigidly covering every single question if time runs short.

What if the buyer doesn't know their own budget or compliance requirements?

That's real, useful information — it often means the company is early enough in its growth that formal processes haven't caught up yet, which can mean either a faster, less bureaucratic sale in the near term, or a compliance requirement that emerges suddenly mid-process once the company scales, both worth tracking for your go-to-market planning.

Should I ask about pricing directly, or wait until later in the sales process?

Asking about current spend (Q10) during discovery, rather than waiting, gives you a real anchor early and avoids investing significant sales effort into a deal that turns out to be priced far outside what the buyer can actually spend — this is different from pitching your own price, which can reasonably wait until you understand their situation more fully.

How is this different from a general customer discovery interview?

The core Mom Test discipline is the same as general customer research for founders, but this script adds HR-tech-specific blocks around compliance and formal buying process that matter more in this category than in many consumer or lower-stakes B2B categories.

What do I do if the person I'm interviewing isn't actually the real decision-maker?

Ask directly, ideally early in Block 4 — "who else needs to be involved in a decision like this" — and if it becomes clear you're talking to an influencer rather than the actual approver, treat this conversation as valuable workflow and pain research while working to get introduced to the real decision-maker for the budget and process questions specifically.