How to Sell HR Software: Buyers, Headcount Triggers and Timing
How to sell HR software: who signs and who stalls, the headcount thresholds that force a purchase, the HR calendar, and the signals that show timing.
TL;DR: HR software gets bought when headcount forces the question. Crossing 50 or 100 employees brings new federal obligations, and a company posting its first People role is telling you it already feels the load. Most of how to sell HR software comes down to finding companies at those moments, selling to the head of People with finance and IT involved from the first call, and planning the go-live around payroll and open enrollment.
This is for founders and first sales hires selling into People teams. For the wider plan from zero to ten customers, start with getting your first B2B SaaS customers. To see these signals set up as searches, our page for HR tech startups has example Plays.
Who signs an HR software deal, and who can stall it
The head of People owns the problem and runs the evaluation. The signature needs more people than that, because HR software touches payroll budgets and employee records that finance and IT own.
- Head of People (CHRO, VP People, HR director). Feels the pain, builds the shortlist and lives with the system for years. Your champion.
- CFO or controller. Approves the spend. If you price per employee, the bill grows with every hire, so bring the per-employee math and a three-year view.
- IT or security. Approves access to employee data, and checks single sign-on and how accounts get created and removed.
- Payroll and benefits administrators. Own the integrations you depend on. A doubt from payroll can stall the whole evaluation.
- Managers and employees. The daily users. They never sign, but their adoption decides the renewal.
Without a People team, the CEO, COO or CFO buys, sometimes in one conversation. Either way, write the business case in finance terms, on one page a head of People can forward: HR hours returned, payroll errors avoided, a compliance task covered.
How to sell HR software around headcount thresholds
Federal rules change at set headcounts, and each change creates work someone has to own:
| Headcount | What changes | What the People team starts looking for |
|---|---|---|
| 50 full-time employees, including full-time equivalents, averaged over the prior year | The company becomes an applicable large employer under the Affordable Care Act, subject to employer shared responsibility and information reporting on health coverage | Benefits administration, hours tracking for part-time staff, ACA reporting |
| 50 employees in 20 or more workweeks, current or prior year | The employer is covered by the Family and Medical Leave Act | Leave requests, eligibility tracking, manager workflows |
| 100 employees (50 for some federal contractors) | An annual EEO-1 Component 1 report of workforce data by job category, sex and race or ethnicity | Clean demographic fields in the HRIS, reporting |
| Any size, using an automated screening tool for New York City jobs | Local Law 144: a bias audit within one year of use, a public summary of the results, notices to candidates | Hiring tools with an audit behind them |
You can watch a company approach these lines from outside: 25 openings at a 40-person company say it will pass 50 soon. Say that company averages 50 full-time employees across 2027. Under the IRS rule, it becomes an applicable large employer for 2028, with health-coverage reporting someone has to file.
None of this means the company will buy your product. It means a new task exists and someone will be handed it. Your first message can ask who.
The HR calendar decides when a demo lands
People teams work to a calendar that payroll and benefits set, so the same pitch can land in March and go unread in November.
- Open enrollment. For employers whose benefits plan year starts January 1, the fall is open enrollment, and nobody on the team has an hour for a demo.
- Year-end payroll. Closing the payroll year and issuing tax forms takes December and January.
- Review season. Where annual reviews happen at year-end, calibration meetings fill December.
- Budget planning. Ask when next year's budget gets set, and get into it before it closes.
If you replace payroll or the HRIS, the buyer picks a go-live date and works back. Moving payroll mid-year means moving the year's pay history too, so ask early whether they want a quarter or year start. Say onboarding takes eight weeks and a buyer wants January payroll on your system: the contract must be signed by early November, so the first call belongs in late summer.
The security and privacy review People teams run
Expect a security questionnaire for any product that stores employee records, since they hold Social Security numbers, bank details, pay and medical leave. Have five answers ready before your first mid-size deal:
- SOC 2 status. The report, or the date your audit window closes.
- Access control. Single sign-on, automated account provisioning and removal, and who on your team can see customer data.
- Data handling. Where data lives, how it is encrypted, how long you keep it, which sub-processors touch it.
- California staff. The CCPA's exemption for employment-related personal information expired on December 31, 2022, so employee data is covered, and buyers with California staff read your data terms with that in mind.
- AI. If your product scores or ranks candidates or employees, a New York City employer can't use it without the bias audit in the table above. Commission it before the first buyer asks.
Put the answers on a public trust page, so your champion can forward one link to IT.
Signals that show a People team is about to buy
HR teams hire in public, and their job posts tend to name the systems they run.
- A first People hire. A company posting its first HR generalist or People operations role has decided HR is a job, not a side task. The CEO or COO buys until the hire starts; then the new hire does.
- An HRIS analyst or HRIS manager opening. The system is getting attention: an implementation, a cleanup or a migration.
- The HRIS named in a job post. Generalist posts often ask for experience with a named system, from BambooHR and Paylocity to UKG and ADP. If you replace or plug into one, those posts are your list (see finding companies by tech stack). Plenty come from staffing agencies, so check the company is hiring for itself.
- Hiring pace. Openings on the careers page against current headcount show who is heading for the thresholds above. Track this one by hand.
- A fresh funding round. A round brings a hiring plan, and the plan brings HR work, most of all at a company with a dozen openings and no People lead.
- People leaders posting about the problem. Open enrollment questions, review season, turnover, an HRIS that can't produce a basic report.
- A new head of People. They inherit a stack they didn't choose. Spot the announcement by hand, and write once they've had a few weeks to find the gaps.
- Lookalikes of your best customer. Same industry, size and HR setup as the customer who gets the most from you.
Reading job postings as buying signals maps more roles to purchases, and the guide to B2B buying signals covers the types beyond hiring.
Where HR leaders compare notes
HR leaders ask peers, brokers and their payroll provider before they take a vendor call. Spend your time where those questions get answered:
- SHRM chapters. State and local chapters put you in a room with HR managers nearby. Teach something at a meeting, and don't pitch from the floor.
- HR Tech and the big shows. Exhibiting is expensive; walking the floor with meetings booked costs a ticket.
- Benefits brokers. A broker sits with each client at every renewal, so one who trusts your product can raise it at each.
- Payroll and PEO partner listings. Where small companies that run HR inside their payroll provider look for add-ons.
- Your customers' communities. Ask your first five customers which Slack groups and newsletters they read, then answer questions there.
First messages that HR leaders answer
Show you looked at their company: one question the signal makes relevant, no pitch.
- First People hire: "Saw you're hiring your first People Ops manager. Will they inherit spreadsheets, or a system someone already chose?"
- HRIS in the job post: "Your HR generalist posting asks for BambooHR experience. Is the plan to stay on it past 200 people?"
- Threshold ahead: "You're about 45 people with 20 roles open. Has anyone looked at what changes once you pass 50?"
- Post about open enrollment: "Your post about open enrollment questions rang true. Which question did your team answer most this year?"
Write to whoever owns the budget. The generalist who will use the tool is worth a second conversation once the first one is going.
Finding People teams at the right moment with Pancake
Pancake is our product. It finds the people behind a buying signal and opens the conversation in your name. Three signals fit People-team buyers:
- companies posting a first People role or an HRIS analyst opening (companies hiring), with staffing agencies' own posts left out;
- companies whose job posts name the HRIS you replace or plug into;
- People leaders posting about open enrollment, review season or turnover.
Describe the audience in one sentence, such as "Find heads of People at US companies with 50 to 200 employees hiring their first HR generalist," and the Play runs on the schedule you pick. Each lead shows the reason it fits in one line. The first message pitches nothing: "Saw the People Ops opening. Is the new hire inheriting a system, or choosing one?" It goes out from your own account, and a reply stops the sequence.
The limits: Pancake can't see headcount trends, payroll or employee records, knows a company's HRIS only when a job post names it, and sends direct messages, not email. A 15-person company with no People role and no posts leaves nothing to find; reach it through accountants, brokers and payroll partners.
Plans start from $99 a month per workspace with 60,000 credits (pricing); the free trial runs 7 days on 30,000 credits and needs a credit card to begin. See more Plays on our HR tech startups page.
Frequently asked questions
- How do you sell to HR leaders?
- Start from a reason specific to their company, such as a first People hire, an HRIS named in a job post or a headcount threshold ahead, and ask one question about it. Once they reply, bring finance and IT in early, since HR software touches budgets and records they own. Have a per-employee cost model and your security answers ready.
- What is HR tech sales like?
- HR tech sales is a committee sale run on a calendar. The head of People champions the product, finance approves the cost and IT reviews access to employee data. Open enrollment and year-end payroll crowd out demos, and a product that replaces payroll or the HRIS needs a go-live date agreed well ahead. Tools that sit beside the HRIS move faster.
- Who is the buyer for HR software?
- Where there is a People team, its head (CHRO, VP People or HR director) owns the decision and runs the evaluation, the CFO approves the spend and IT signs off on security. Payroll and benefits administrators check the integrations. Without a People team, the CEO, COO or CFO buys, sometimes in a single conversation.
- How do you find companies that need HR software?
- Look for public signs of HR workload: a first HR generalist or People operations job post, an HRIS analyst opening, job posts naming the HRIS you replace, a fresh funding round with a hiring plan, and People leaders posting about open enrollment or turnover. Watch companies close to 50 or 100 employees, where federal obligations change.
- What security questions do HR software buyers ask?
- Expect questions on where employee data is stored and encrypted, who at your company can see it, how single sign-on creates and removes accounts, which sub-processors touch the data, and whether you have a SOC 2 report. Buyers with California staff also check privacy terms, since the CCPA's employee-data exemption expired at the end of 2022.