Quick Pulse: Why We're Here

• In one sentence, what's the single most important reason your team is evaluating an AI-driven talent sourcing platform right now?
• Which of the following best describes the immediate trigger for this project? Options: Strategic hiring initiative (new product/team), Diversity sourcing mandate, Recruiting ops audit showing low engagement time, High-priority role(s) stuck in pipeline, Leadership directive / budget availability, Other
• Who will be the core team directly involved in a 2–4 week calibration (select all that apply)? Options: Sourcers, TA/Recruiting Operations, Recruiters (non-sourcers), Hiring managers, HRIS / Data team, IT / Security, Legal / Compliance, Executive sponsor
• How many dedicated sourcers are on your team today? Options: 1–3, 4–10, 11–25, 26–50, 51+
• What is your current estimate of the percentage of a sourcer's time spent on active candidate engagement (outreach, conversation) versus search/administrative work? Options: <15%, 15–29%, 30–49%, 50%+
• Which sourcing or intelligence tools do you currently rely on (include internal tools, CRMs, browser extensions, boolean libraries)?

If Sourcers Had Twice the Engagement Time, What Would Change?

• If your sourcers suddenly doubled the time they spent talking to candidates, what would you expect to look different in hiring outcomes this quarter?
• Which 3 KPIs would you most want to see improve as a result (choose up to 3)? Options: Pipeline build-rate (qualified candidates/week), Time-to-first-interview, Interview-to-offer conversion, Offer acceptance rate, Diversity % in qualified slate, Sourcer outreach time per candidate, Hiring manager satisfaction
• How quickly would you expect to see measurable change if sourcers spent more time engaging candidates (select one)? Options: Within 2 weeks, Within 4 weeks, Within 8 weeks, By end of quarter, Longer than a quarter
• Which job families or priority roles do you believe would benefit first from increased sourcer engagement? Options: Engineering, Product, Sales / Revenue, Design, Customer Success / Support, Operations / Finance, Leadership / Executive
• Tell us about a recent role where lack of pipeline delayed hiring—what happened, and what was the business impact?

What's Secretly Breaking Your Pipeline?

• What's one repeated sourcing failure your team tolerates because 'that's just how it is'?
• How long has that issue been holding your team back (weeks, months, years)? Options: <1 month, 1–3 months, 3–12 months, 1+ years
• How often do your sourcers rely on handcrafted Boolean strings versus recommendations or algorithmic matches? Options: Almost always Boolean, Mostly Boolean with some tools, About half/half, Mostly algorithmic recommendations, Rarely use Boolean
• Which failure modes block outcomes most frequently (select up to 4)? Options: Stale candidate data, Duplicate profiles across sources, Poor match relevance / false positives, Low outreach response rates, ATS sync failures / mismatched fields, Inaccurate titles or skills mapping, Compliance/privacy limitations
• Give a concrete recent example of a pipeline breakdown (role, what failed, immediate consequence):

What Would Make You Confident After a 2–4 Week Calibration?

• Which single metric improving by a measurable amount during calibration would make you confident to expand the program? Please name the metric and the target improvement (e.g., 'pipeline per role +50%').
• Which of the following success signals should we prioritize during calibration (choose up to 3)? Options: Match precision as judged by sourcers/hiring managers, Candidates added to pipeline per role/week, ATS sync accuracy and latency, Reduction in sourcer search time, Increase in diverse candidates per slate, Hiring manager satisfaction score
• For pipeline build-rate, which weekly candidate-per-role target would you consider a successful outcome during calibration? Options: <5, 5–10, 11–20, 21–40, 40+
• How will you validate match quality during the pilot—who will review matches, how many samples must pass, and what acceptance threshold matters to you?
• Are there specific roles, geographies, or talent pools we must include to prove both breadth and depth? Options: US - Remote, US - West Coast, US - East Coast, EMEA, APAC, Latin America, Specialist/Hard-to-fill roles
• What minimum diversity representation do you want to see in the qualified slate for a role during calibration? Options: No formal target, At least 30%, At least 40%, At least 50%, Other (please specify)

Integration Red Lines — What Can't Move

• If one technical or security requirement isn't met, would you pause or halt the project altogether? Please describe which and why.
• Which ATS do you use today? Options: Greenhouse, Lever, Workday, iCIMS, SmartRecruiters, Taleo / Oracle, Other / In-house
• What level of API/ATS access can you provide for calibration (select all that apply)? Options: Read-only candidate and job fields, Read/write candidate sync (create/update), Webhook notifications for status changes, Sandbox or staging ATS instance, Limited-field access only (PII redacted), No API access yet
• Which security or compliance approvals will be required before integration (select all that apply)? Options: SOC 2 Type II, ISO 27001, Vendor Risk Assessment (VRA), Data Processing Agreement (DPA), Penetration test / security attestation, Privacy review
• Are there data residency, PII, or export constraints we must design around (be specific)? Options: US-only data residency, EU data residency / GDPR constraints, Anonymized data only for pilot, No email/contact export, Other (please describe)
• Target timeline to complete integration entitlements (admin users, API keys, SSO, etc.): Options: Immediately / same week, Within 1 week, Within 2 weeks, 3–4 weeks, Longer than 4 weeks

Which Real-World Scenarios Should We Run?

• Which 2–3 hiring scenarios must succeed during calibration for this to feel like a clear win?
• Select scenario types to include in calibration (choose up to 4): Options: Urgent critical role (time-sensitive), Volume hiring (many similar roles), Diversity-slate building, Passive executive / leadership search, Geography-limited search (e.g., EMEA), High-compensation market-intel negotiation, Competitor mapping / counteroffers
• For validation, what minimum sample size should we aim for per scenario (candidates per role or roles)? Options: 1–3 candidates per role, 4–7 candidates per role, 8–15 candidates per role, 16+ candidates per role
• Do you have sample job descriptions and hiring manager notes available for the selected scenarios? Options: Yes — full JDs + hiring manager context, Partial JDs only, Only titles/skills, No, we need help crafting them
• Which market intelligence elements are mission-critical to surface during scenarios (select all that apply)? Options: Compensation benchmarks by role/location, Talent supply density heatmaps, Competitor hiring spikes / headcount changes, Skills adjacencies and likely career paths, Relocation likelihood / mobility insights
• Who will be the sourcer(s) running these scenarios and how many hours per week can each dedicate to calibration activities?

Who Holds the Keys — Decision & Blocker Map

• Who on your side could pause or accelerate this project with a single decision, and what influence do they hold?
• Which stakeholders must formally sign off after pilot completion (select all that apply)? Options: Head of TA, VP / Director of Recruiting, TA Operations Lead, IT / Security, Legal / Compliance, Finance, Hiring Managers
• What is your expected decision timeline after the 2–4 week calibration completes? Options: Immediate (same week), Within 1 week, Within 2 weeks, Within 1 month, Longer / TBD
• What are the most likely internal objections we should be prepared to address (select all that apply)? Options: Data security concerns, Integration cost/effort, Sourcer adoption resistance, Match accuracy skepticism, Competing vendor relationships, Budget timing
• How do you prefer we escalate and resolve blockers during calibration (choose one)? Options: Weekly stakeholder meeting, Twice-weekly tactical sync, Ad-hoc calls as issues arise, Shared Slack/MS Teams channel for real-time triage

Commitments That Make This Real

• If we leave this engagement without firm commitments, what single omission would most likely cause the pilot to fail?
• Which of the following commitments can you make before calibration begins (select all that apply)? Options: Provide API/ATS access, Designate 1–2 dedicated sourcers, Deliver sample JDs and hiring manager notes, Grant sandbox ATS or test environment, Share historical pipeline and response-rate data, Pledge weekly calibration reviews
• When can you provide sample data and admin users to start integration? Options: Immediately / same week, Within 3 business days, Within 1 week, Within 2 weeks, Longer than 2 weeks
• What communication cadence do you want during calibration? Options: Daily standup (15 min), Twice-weekly tactical check-ins, Weekly sync, Bi-weekly, On-demand/as-needed
• Who will be the primary day-to-day contact for coordination (name and role)?
• Are there external stakeholders (vendors, compliance teams, ATS partners) we should loop in now? If yes, list them and the appropriate contacts. Options: Yes, No
• If you answered 'Yes' above, please list the external stakeholder names, roles, and best contact details:

Quick Snapshot: Your Sourcing in a Sentence

• In one sentence, how would you describe your team's current sourcing approach right now?
• Who on your team is primarily responsible for designing sourcer workflows and prioritization? Options: Head of Sourcing, TA Operations Lead, Recruiting Manager, Individual Sourcer, Shared/Rotating, Other
• How many full-time equivalent sourcers work across your active requisitions? Options: 1–3, 4–7, 8–15, 16–30, 30+
• Approximately what percentage of a typical sourcer's workweek is spent on direct outreach to candidates (vs research, boolean design, admin)? Options: <20%, 20–30%, 31–45%, 46–60%, >60%
• Which geographies, functions, or roles are absorbing the majority of your sourcing effort today? Options: US - Nationwide, US - Regional, EMEA, APAC, Remote/Global, Specific function (e.g., Engineering), Other
• What single hiring constraint feels most urgent to solve in the next quarter (e.g., time-to-fill, diversity targets, sourcer bandwidth, data quality)? Options: Time-to-fill, Candidate quality, Diversity hiring, Sourcer bandwidth, Data freshness, ATS integration, Other

Are You Comfortable Throwing Sourcer Hours at the Problem?

• How often do sourcers end up spending more time crafting Boolean strings and managing tools than actually engaging candidates? Options: Almost always, Often, Sometimes, Rarely, Never
• Tell us about a recent role where sourcing consumed unexpected time—what happened and what was the impact?
• Do you measure sourcer time allocation formally (time tracking or activity metrics) or by estimation? Options: Formal time tracking, Activity dashboards, Manager estimates, No measurement
• What percentage of sourcer time is your target for outreach (ideal) versus what is actually happening?
• How does the team feel about current workload balance—frustrated, resigned, optimistic, or something else? Options: Frustrated, Resigned/accepting, Optimistic, Indifferent, Motivated to change

Where Do Candidates Fall Through the Cracks?

• Which single failure mode most often kills a candidate opportunity before it becomes a pipeline lead—data, process, response delay, or qualification? Options: Stale/incorrect data, Process handoffs, Slow follow-up, Poor qualification, ATS sync issues, Other
• List the top three failure modes you've seen during sourcing-to-screen (e.g., duplicate outreach, wrong contact info, lost ATS stage).
• How frequently do you see candidates contacted more than once by different sourcers or teams (duplicate outreach)? Options: Daily, Weekly, Monthly, Rarely, Never
• When a promising candidate drops out, do you typically know why? Share recent examples and how they made you feel as a hiring team.
• How often do ATS or CRM sync issues directly prevent progressing a candidate (e.g., profile lost, notes not recorded)? Options: Very often, Often, Occasionally, Rarely, Never

If Your Pipeline Had a Heartbeat, Is It Flatlining or Racing?

• Are you driving pipeline growth with volume (lots of candidates) or by quality (higher-fit, higher-response), and which approach is failing you right now? Options: Volume-driven and failing, Volume-driven and working, Quality-driven and failing, Quality-driven and working, Mixed approach
• What are your current conversion rates from outreach → screened → interview → offer (estimates are fine)?
• How long does it typically take, from brief to a qualified pipeline for a mid-level role in a priority function? Options: <1 week, 1–2 weeks, 2–4 weeks, 4–8 weeks, >8 weeks
• What numeric target would feel like a meaningful improvement for pipeline build-rate or quality in a 2–4 week calibration? Options: 2x pipeline rate, 1.5x pipeline rate, Double qualified interviews, Reduce time-to-first-qual by 50%, Other
• Describe a recent requisition where pipeline health surprised you—what signals did you track and how did you react?

Are Your Tools Helping or Creating Work?

• Which tool in your current stack does sourcers most often blame for wasted time (pick the one that elicits the loudest complaints)? Options: Primary ATS, Spreadsheet/manual trackers, Boolean search tools, Sourcing plugins/chrome extensions, Outreach platforms, Other
• Which systems are currently integrated into your ATS (select all that apply)? Options: LinkedIn Recruiter, Email/Outreach tool (e.g., Gem), Sourcing platform A, HRIS, None, Other
• Describe any manual steps your team must perform to move candidate data between tools (exports, copy/paste, tagging conventions).
• Do you have security, SSO, or procurement constraints that commonly slow new integrations? Options: SAML/SSO required, IP allowlisting, Legal/DP review needed, Third-party data restrictions, None, Other
• Which integrations would be a hard requirement for adoption (e.g., ATS write-back, single-sign on, user provisioning)? Options: ATS write-back, Read-only ATS sync, SSO/SAML, SCIM user provisioning, Encryption/Security audit, None required, Other

Is Your Candidate Data Trustworthy—or a Mirage?

• How often do you encounter candidate records that are outdated, incorrect, or unverifiable on first contact? Options: Very often, Often, Sometimes, Rarely, Never
• Which data signals are most important to you for an actionable match (select up to three)? Options: Current role/title, Recent job changes, Skills and endorsements, Location/relocation willingness, Contactability (email/phone), Likelihood to move, Diversity indicators
• Do you require specific source provenance for candidate data (e.g., public web only, professional networks, proprietary database)? Options: Public web only, Professional networks, Proprietary databases, Mix of all, No preference
• Share an example where poor data quality led to a visible problem (e.g., wasted outreach, candidate upset, compliance issue). What happened and how long did it take to resolve?
• How important is freshness (how recently a profile was updated) when you evaluate a recommended candidate? Options: Critical, Very important, Somewhat important, Not important

What Would a Fast, Small Win Look Like in 2–4 Weeks?

• If a 2–4 week calibration had to prove value quickly, what are the three non-negotiable outcomes you would want to see?
• What acceptance criteria will you use to judge success (pick up to three measurable signals)? Options: Match accuracy (%), Pipeline build-rate increase, Sourcer outreach time saved, ATS sync reliability, Candidate contact rate, Diversity of pipeline
• Who will sign off on whether the pilot succeeded (title/role), and who needs to be consulted before a go/no-go?
• What logistical constraints could block a 2–4 week calibration (security review, sample data, admin access, stakeholder availability)? Options: Security review, No sample data, No API/ATS access, Stakeholder bandwidth, Procurement delays, None
• Realistically, what would make you say 'this was worth it' after the calibration window—be specific (numbers, behaviors, or workflows)?

Quick Snapshot: Your Integration Landscape

• Which ATS or HRIS system are you primarily using today? Options: Greenhouse, Lever, iCIMS, Workday Recruiting, BambooHR, SmartRecruiters, Custom/Proprietary, Other
• What’s your ideal target date for completing the 2–4 week calibration and moving to production? Options: Within 2 weeks, 2–4 weeks, 1–3 months, 3+ months, No firm date (depends on approvals)
• Who will own integrations on your side (name, role, and best contact)?
• How many sourcers or recruiters do you intend to include in the calibration window? Options: 1–2, 3–5, 6–10, 11–25, 25+
• Do you already have a sandbox/staging environment we can use for testing (vs. working in production)? Options: Dedicated sandbox with test data, Limited staging with partial data, Only production available, Not sure / need to confirm
• Which of the following outcomes is highest priority for this deployment? Options: Faster pipeline build-rate, Higher match accuracy, Improved sourcing efficiency (more outreach time), Diversity of pipeline, Market intelligence for hiring managers, Other

Why Do Integrations Stall in Your Org?

• When you think about past integrations, what single organizational behavior most commonly slows projects down? Options: Extended security reviews, Procurement negotiations, IT resource availability, Unclear data ownership, Executive sign-off delays, Other
• Which teams are most likely to create friction on an ATS/API integration? Options: IT/Engineering, Security/InfoSec, Legal/Compliance, Procurement, TA Operations, Sourcing leadership, HRIS
• How long do approvals typically take for a new vendor integration from request to green light? Options: < 2 weeks, 2–4 weeks, 1–2 months, 2–3 months, 3+ months
• When an integration is delayed, what rationales do you usually hear (pick all that apply)? Options: Outstanding security questionnaire, Insufficient budget or procurement hold, No sandbox for testing, Missing data mapping, Priority shifted by leadership, Other
• Tell us about the last time an integration missed its target—what went wrong, and how did that impact hiring outcomes?
• Who at the executive level must sign off on production ATS access in your organization? Options: Head of TA, CHRO, CISO, VP/Head of Talent Ops, Procurement Director, No executive sign-off required, Other

Who Holds the Keys—and Who Gets Blindsided?

• Who is currently responsible for creating and rotating API keys or service accounts in your environment, and how often does that change?
• Which admin roles should we plan to provision during calibration (grant only what's needed)? Options: Platform Admin, Sourcer (limited access), Recruiter (read/write), Hiring Manager (read), IT Admin, HRIS Admin, Other
• Which identity providers or user-provisioning tools do you use for SSO/SCIM? Options: Okta, Azure AD, OneLogin, Ping Identity, Google Workspace, Custom/Other, We do not use SSO/SCIM
• How do you prefer handling credentials for vendor integrations? Options: Centralized secrets vault (e.g., HashiCorp), Per-service tokens managed by IT, Temporary keys for onboarding, Long-lived shared keys (not preferred), Unsure—need guidance
• Who will be the day-to-day contact for authentication or permissions trouble tickets (name, role, contact)?

What Data Are You Ready to Share (and What Feels Off-Limits)?

• If we need sample candidate records to tune matching, what would make you decline that request? Options: PII restrictions, Legal concerns, Internal policy against sharing records, Not enough anonymization options, No concerns—happy to share
• Which data fields do you consider essential for meaningful calibration? Options: Candidate name, Email, Phone, Profile/Resume text, Current title, Skills/keywords, Location, Work history/timeline, Custom ATS fields, Candidate status (active/passive)
• Do you have rules or policies limiting export of PII or candidate profiles for vendor testing? Options: Yes — strict (no PII exported), Yes — conditional (anonymized only), No formal policy, Unsure—need to check
• Can you provide anonymized or synthetic sample data as an alternative to live records for initial tuning? Options: Yes — full anonymized dataset available, Partial synthetic/anonymized data available, No — only live data, Unsure
• What custom fields, workflows, or mappings in your ATS should we know about up front?
• Which method do you prefer for transferring sample data to our team? Options: CSV export, API feed, SFTP transfer, Shared secure staging DB, Manual secure upload, Other

Are Your APIs Friendly or the Hidden Landmines?

• Are there undocumented limits, IP allowlists, or maintenance windows that typically surprise integrators here? Options: Yes—several known constraints, A few, but manageable, No, APIs are stable and documented, Unsure / need to check
• Do you have API documentation and a sandbox key we can use immediately? Options: Complete docs + sandbox key, Partial docs / limited sandbox, Only production API access, No docs / need IT assistance
• What are your API rate limits or typical throttling policies we should design around? Options: <100 requests/min, 100–500 requests/min, 500–2000 requests/min, Custom rate limits (specify), Unknown
• Do you require vendor traffic to come from static IPs, via VPN, or through a PrivateLink/Direct Connect? Options: Static IP allowlist, VPN/PrivateLink required, No special network requirements, Unsure—need to confirm
• Are real-time webhooks supported for ATS events (candidate update, application, status change)? Options: Full webhook support, Limited webhook support, No webhook support (polling only), Unsure
• Have you experienced recent API outages or quirks we should plan around? If so, please describe.

Security Red Lines — Tell Us What Will Stop The Project

• Which single security or compliance requirement would immediately disqualify a vendor in your evaluation? Options: Lack of SOC 2/ISO evidence, No DPA in place, Unwillingness to sign specific contractual clauses, Inability to support data residency rules, Other
• Do you require a signed Data Processing Agreement (DPA) or equivalent before any sample data is exchanged? Options: Yes, mandatory before testing, Yes, but can be parallel to testing, No DPA required, Unsure
• Which certifications or attestations do you expect from vendors? Options: SOC 2 Type II, ISO 27001, GDPR readiness, HIPAA (if applicable), None required, Other
• Will your security team require a penetration test, code review, or a third-party risk assessment as part of onboarding? Options: Penetration test, Code review, Vendor security questionnaire (e.g., SIG, VRM), Threat modeling session, None required, Unsure
• Who is the security or privacy reviewer for vendor integrations, and what is their typical review timeline?

What Does a Successful 2–4 Week Calibration Actually Prove?

• If calibration completes and nothing in downstream hiring changes, what would make you still call the exercise a success? Options: Demonstrable match accuracy lift, Reliable ATS sync, Sourcers spending more time engaging candidates, Clear path to operationalization, Won't consider it a success unless hires improve
• Which concrete metrics will you use to judge the calibration period? Options: Match accuracy / precision, Pipeline build-rate (candidates/week), Sourcer active outreach time, Response rate to outreach, Diversity representation in pipeline, ATS sync error rate
• What sample size of roles or candidate interactions do you consider minimally valid for calibration results? Options: 1–3 roles, 4–10 roles, 10–25 roles, 25+ roles, Prefer metric-based threshold (specify)
• Which sourcer behaviors are you explicitly trying to change by the end of the calibration window? Options: Increase time on outreach, Improve response rates, Shortlist higher-quality candidates faster, Increase diversity in pipelines, Reduce time spent crafting Booleans
• What numerical acceptance thresholds (e.g., % match precision, candidates/week) would you consider a 'go' for production?
• How often should we run checkpoint reviews during calibration? Options: Daily standups, Twice weekly, Weekly, Midpoint + final only, Other cadence

Who Will Run the Machine After Go‑Live?

• Once live, which team should own ongoing tuning, measurement, and vendor coordination—and are they staffed for it? Options: TA Operations, Sourcing Leadership, Recruiting Engineering, Vendor Success (joint ownership), Procurement (oversight), No clear owner yet
• How many active sourcers do you expect on the platform in month 1 and in month 3? Options: 1–3, 4–10, 11–25, 25+, Unsure
• What internal SLA should we aim for when addressing sync issues or data mismatches post-deployment? Options: 4 business hours, 24 business hours, 3 business days, Weekly triage, Other
• Which training approach will maximize adoption for your team? Options: Live hands-on workshops, Recorded micro-lessons, Train-the-trainer (internal champions), Embedded in-app help + office hours, Combination of the above
• Which channels do you prefer for real-time support and escalation during calibration and after launch? Options: Slack dedicated channel, Email, Ticketing system (Jira/ServiceNow), Dedicated workspace / portal, Phone/on-call roster
• What recurring reports or dashboards would you like us to deliver after go-live? Options: Match accuracy dashboard, Pipeline velocity report, Sourcer activity metrics, Diversity breakdowns, Integration health logs, Custom reports

Next Move: Remove Friction in a Single Week

• If you could remove one bottleneck this week that would meaningfully accelerate deployment, what would it be? Options: Security questionnaire completion, Provide sandbox/staging access, Assign integration owner, Map sample data fields, Approve budget/PO, Other
• Which of these high‑impact tasks would you like us to own in the next 7 days? Options: Deliver API smoke tests, Map sample data to ATS fields, Set up staging access & test sync, Complete vendor security questionnaire, Run initial sourcer calibration session
• Who must be looped in immediately to unblock that task (name, role, contact)?
• What format would you prefer for a short go/no‑go decision deliverable (pick one)? Options: One‑page decision memo, Live demo + Q&A, Metric snapshot dashboard, Signed security/ops checklist, Other
• When would you like the next check‑in to review progress and remove new blockers? Options: Within 48 hours, This week, Next week, When key approvals are ready, No preference
• Is there anything else—concerns, constraints, or buried context—we should know to make the first week decisive?

Tell Us About Who's in the Room

• Who are you and which people will actively influence sourcing decisions for this initiative? Options: Sourcing Manager, Head of Talent Acquisition, TA Operations Lead, Hiring Manager, VP/Head of Business Unit, Legal/Compliance, Other
• How many full-time sourcers and recruiters will regularly use the platform? Options: 1–3, 4–9, 10–24, 25–49, 50+
• What's the typical split of sourcer time today between active outreach (engagement) vs. search/boolean and admin work? Options: <20% outreach, 20–30% outreach, 31–50% outreach, 51–70% outreach, >70% outreach
• Which ATS and core HR systems must we integrate with during the pilot? Options: Greenhouse, Lever, Workday, iCIMS, SmartRecruiters, Breezy, Other/Proprietary
• What strategic trigger is driving this project right now (pick primary)? Options: Strategic hiring push, Diversity hiring mandate, Sourcing efficiency initiative, Recruiting ops review, Cost reduction, Talent mapping for future roles, Other

Are You Comfortable Letting Sourcing Be the Bottleneck?

• If sourcers stay below 30% time on outreach for the next 6 months, what would that mean for your hiring goals and business outcomes?
• Which hiring outcomes suffer most today when sourcing time is squeezed? Options: Pipeline velocity, Time-to-fill, Quality of hire, Diversity of slate, Hiring manager satisfaction, Offer acceptance rates
• Which KPIs do you currently track to measure sourcing effectiveness? Options: Pipeline build-rate (candidates/week), Match-to-submission ratio, Response rate to outreach, Time-to-first-contact, Diversity slate percentage, Other
• How would you quantify the business cost of slow or poor sourcing for a single critical role (time or $)? Give an example.
• Who in your org interprets sourcing KPIs and makes decisions based on them? Options: Sourcing Manager, TA Ops, Hiring Manager, People Analytics, CCO/Revenue Leader, Other

Where Does Talent Hide Today—and Why We Miss It

• If your single best passive candidate showed up today, how confident are you your current stack would surface them before a competitor did? Options: Very confident, Somewhat confident, Uncertain, Unlikely
• Which sourcing channels and data sources do you rely on most (rank up to 5)? Options: LinkedIn, GitHub/StackOverflow, Job boards, Proprietary databases, Public web (blogs, portfolios), Talent pools/CRM, Referrals, Other
• How often do you believe your candidate data is stale or missing critical signals (skills, current employer, openness to move)? Options: Daily issues, Weekly issues, Monthly issues, Rarely
• Describe a recent failure mode where sourcing repeatedly produced low-value candidates—what happened and why did it keep recurring?
• Do you use Boolean-heavy workflows today? If so, roughly what percent of a sourcer's time is spent building and tuning queries? Options: None, <10%, 10–25%, 26–50%, >50%

Tell Me About a Recent Win—and a Near‑Miss

• Think of your last great hire sourced from passive talent—what specifically made that process succeed where others didn't?
• How long did it take from initial source to interview and what touched that candidate (messages, referrals, intel)? Options: <1 week, 1–2 weeks, 2–4 weeks, 4+ weeks
• Now describe a close miss—a candidate who slipped away. What signals did you miss or react to too late?
• Which insights or market intelligence would have changed the outcome in that near-miss (comp, competitor activity, candidate motivation, relocation constraints)? Options: Compensation benchmarks, Competitor hiring signals, Geographic supply density, Candidate intent data, Role trajectory fit, Other
• When you think about scaling wins like that, what internal process or skill gaps are most limiting? Options: Sourcer training, Data integration, Playbook consistency, Hiring manager alignment, Analytics/visibility

What Would Make Your Team Feel Like Trusted Advisors?

• If sourcers could reliably build a 3x pipeline in the same time, how would hiring managers’ expectations and behavior need to change?
• Which outcome would you prioritize for a 2–4 week calibration (pick primary and up to two secondaries)? Options: Match accuracy, Pipeline build-rate, Diversity of slate, Time-to-first-contact, Candidate engagement rate
• What acceptance thresholds would make you say the pilot succeeded (e.g., match accuracy %, weekly pipeline, response rate)? Please give target numbers where possible.
• Which integrations are non-negotiable for your acceptance (select all that apply)? Options: ATS sync (bi-directional), Single Sign-On (SSO), HRIS, Email sequences / outreach tools, Analytics / BI feed, None required
• How important is vendor-provided market intelligence (comp, supply maps, competitor hiring) to your sourcer's advisory role? Options: Critical, Very important, Nice to have, Not important

What’s Standing Between That and Today?

• What single technical or organizational barrier scares you most about rolling out a new sourcing platform?
• Which of these are real gating issues for you right now? Options: Security/compliance approval, API/ATS access delays, Budget or procurement, Change management/adoption, Data privacy concerns, Lack of internal resources
• How long does your typical security/compliance review take for new vendor integrations? Options: <2 weeks, 2–4 weeks, 1–3 months, 3+ months, Unsure
• Who on your side would lead integration and who would own sourcer training? Please name titles and expected bandwidth.
• What change-management friction have you seen when introducing new sourcing tools in past pilots?

How Will You Know This Worked (Be Brutally Specific)

• If we handed you the calibration report in 4 weeks, what three metrics on that report would make you say 'yes, this is working'?
• Pick acceptable ranges for these thresholds (choose the range that matches your bar): match accuracy, weekly pipeline per sourcer, and outreach response rate. Options: Match accuracy: <40% / 40–60% / 61–80% / >80%, Pipeline per sourcer: <10 / 10–25 / 26–50 / >50, Response rate: <5% / 5–15% / 16–30% / >30%
• Who signs off on go/no-go after calibration and what decision criteria will they use beyond the metrics (budget, stakeholder buy-in, SLA commitments)?
• How will you validate ATS sync and workflow adoption—what do you want to see in the ATS after go-live? Options: Candidate imports with source tags, Activity logs for outreach, Pipeline stages auto-updated, Interview scheduling integrated, Other
• What level of documentation, training, and on-call support do you expect during the calibration window? Options: Daily check-ins + training, Weekly check-ins + office hours, On-demand support only, Full-time on-site/virtual assistance

What Would Make Us Partners, Not Vendors?

• What vendor behaviors would convince you we are invested in your long‑term success rather than just closing a sale?
• Which commercial or contractual terms are essential to feel protected during the pilot? Options: Pilot pricing, Clear SLAs, Exit/rollback terms, Data ownership guarantees, Success milestones tied to payment
• How would you prefer progress and escalations be communicated during the pilot? Options: Weekly stakeholder call, Dedicated Slack/Teams channel, Daily standup (early days), Asynchronous updates via email, Executive summary weekly
• What does 'trusted advisor' look like from our side—examples: proactive market signals, joint candidate playbooks, or co-delivered hiring manager briefings? Options: Proactive market signals, Coached sourcer sessions, Hiring manager briefs, Custom dashboards, Other
• Would a joint success plan with named owners, milestones, and acceptance criteria increase your confidence? If yes, who should be included? Options: Yes, Maybe, No

Practical Next Steps to Get to Go / No‑Go

• If integration were delayed by one month, what is the tangible cost to hiring outcomes?
• Which readiness items can you provide within one week (select all that apply)? Options: API/ATS credentials, Sample candidate data, SSO configuration, Security questionnaire, Admin user list, None available this week
• Who will be the day‑to‑day point of contact for technical issues and who will approve final acceptance criteria?
• What is your ideal timeline for a 2–4 week calibration to start and finish? Options: Start immediately (this week), Start in 1–2 weeks, Start in 3–4 weeks, Start in 1–2 months, Undecided
• Which sequencing matters most to you: security sign-off first, or a lightweight sandbox to begin sourcer training while security completes? Options: Security sign-off first, Sandbox and training first, Parallel approach, Undecided

Final Thoughts — Anything You’re Holding Back?

• What questions do you wish vendors asked you more often about your sourcing challenges?
• Are there internal stakeholders or historical decisions we should know about that could block or accelerate adoption?
• What would make you nervous to share with us right now, if anything (security, politics, past vendor experience)?
• Would you like us to prepare a short, role-specific brief for your hiring managers or executives ahead of pilot kickoff? Options: Yes—Hiring Managers, Yes—Executives/Leadership, Yes—Sourcers/TA Ops, No, not necessary
• Anything else we should capture now to make the calibration and validation as frictionless as possible?