HR tech pilots

People leaders will hand you an ATS sandbox, five open reqs, a "try it with the innovation people team," and a dashboard tour without much thought. None of that makes a pilot. A convertible pilot has a named use case (one BU, one job family, one region, one workflow), a compelling event, written criteria people ops and finance can underwrite, and a path to a PO or MSA if the proof lands.

Keep unpaid sandboxes, design-partner content co-builds, and open-ended "people innovation" labs separate from customer pilots. Lab work can create evidence later, and it seldom closes deals this quarter. If one SOW mixes unpaid sandbox scope with a paid commercial path, name which clock you are on.

Hunt for compelling events: an ATS / HRIS migration or module go-live, a headcount ramp or hiring-freeze thaw, a RIF or reorg, an EEO / pay-equity / audit deadline, open enrollment, a performance-cycle close, a talent-marketplace launch, a works-council consultation window, or post-acquisition people-systems integration.

Map these buyers early: the people-ops or CHRO champion, the economic buyer (often the CFO, COO, Head of Talent Ops, or a CHRO with a budget line), the TA / recruiting lead, HRIS / IT / identity, privacy / legal / employee relations / works council, payroll, and procurement. One people champion won't get you to a PO.

HR buyers expect HRIS integration work to start up front. In the first week of serious interest, start the vendor-risk questionnaire, the SOC2 packet, a DPA for employee PII, SSO / SCIM, HRIS / ATS integration (Workday, SuccessFactors, BambooHR, ADP, UKG, or equivalent), the background-check / I-9 / E-Verify path if in scope, and privacy / legal / works-council review. Run them before or in parallel with the product proof so you aren't starting after the champion has said they like the candidate experience.

Write down the committee. The people-ops or CHRO champion is often not the economic buyer. The check-writer is often the CFO, COO, Head of Talent Ops, or a CHRO with a named budget line. Champion enthusiasm without HRIS clearance and a budget line dies after the demo.

Work backwards from your target ACV and the MSA process. If production requires SSO, HRIS sync, or a named BU owner, start those while the pilot runs instead of after the recruiter tour.

Write criteria a people-ops owner and a finance lead can both sign, and instrument them inside the pilot window on a bounded scope (one BU, one job family, one region, one workflow): time-to-fill, offer-accept rate, days-to-productivity, recruiter / HRBP hours per req or per employee, onboarding completion SLA, interview-to-offer conversion, or 90-day retention on the pilot cohort.

"Recruiters liked the UI" and NPS-only or eNPS-only lines won't pass as success criteria. Price the pilot when you can, and put the phase-two commercial terms (BUs, job families, regions, modules, ACV intent, MSA path) in writing so the pilot can't turn into a permanent unpaid sandbox seat.

Land a quick win in weeks 1–2 that people ops and finance can see without living in the console. A one-page memo with one underwritable metric (time-to-fill, offer-accept, or recruiter hours/req on the named cohort) beats another product tour.

Hold a formal midpoint against the written scorecard, with people ops and finance or the economic buyer in the room or represented. Adjust only against the criteria, and don't expand to all BUs, all regions, or a second workflow (recruiting plus performance plus payroll) without saying so.

Keep vendor risk, SSO / SCIM, HRIS / ATS integration, the DPA, works council / privacy, and procurement moving each week. HR tech pilots miss the ATS go-live, headcount ramp, or audit date when the team finds the HRIS sync or employee-PII DPA stall in the final week.

Restate the criteria, the evidence, and the commercial path from the agreement, then ask for the PO or MSA schedule. "Loved the demo" without a signature is a stall.

If budget or risk appetite wobbles, cut to one BU, one job family, one region, or one module. Hold list price and per-employee pricing, and don't teach procurement that a successful people pilot earns a permanent haircut.

Name the HR tech stall mode before you improvise.

Treat the pilot scope (one BU, one job family, one region, one workflow) as a proof sample. Expand from the phase-two price and the MSA terms in the agreement.

Add BUs, job families, regions, or modules after production is live. A published win (with permission) helps you sell the next people-ops owner. If you keep "pilot seat" or pilot-SKU / per-employee discount pricing going across the company, each expansion starts at a discount.

Use this as a pattern drill. It is not a claimed case study, and the numbers are illustrative.

Use the HR tech pilot scorecard template for the blank worksheet, a filled example, the SSO / HRIS / employee-PII parallel-path checklist, and a copy-ready AI prompt.