Deputy Plans: Seats, Hubs, and Qualifying Tiers
Choose your Deputy plan by mapping must-haves to qualifying tiers — seats, hubs, pools, and add-ons — not homepage “from” tiles.
Quick answer
Choose a Deputy plan by mapping must-haves for applicant tracking / recruiting to a qualifying tier — seats, hubs, pools, and add-ons included — not by comparing homepage “from” tiles. Confirm core hris (Lite+) and payroll processing (Lite+) are on the package you will actually buy. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/deputy/.
- List day-one must-haves
- Map to a researched qualifying plan
- Price hubs / add-ons you will actually use
- Confirm trial or free proving ground
- Write the quote before you buy
Deputy packaging rules
- Tiles are the bottom layer — Deputy is often sold on seats, hubs, pools, or quote packaging in our snapshot — treat homepage tiles as marketing, not a bill of materials. Confirm live packaging on the pricing page.
- Gates change the bill — Plan-gated in research: core hris (Lite, Core, Pro); payroll processing (Lite, Core, Pro).
- Free is a proving ground — Our snapshot records no trial length for Deputy — ask for an evaluation window in writing before you commit seats.
- Wrong cluster, wrong comparison — Do not compare Deputy (applicant tracking / recruiting) to frontline scheduling or a GPS time clock on a single price tile.
Deputy qualifying configuration
1. List must-haves, then qualify
Must-haves should match post one live role, move three candidates through stages, and collect interview feedback. Research-supported features include applicant tracking, career site and job boards, core hris, and payroll processing. Worked example: Harbor Retail (two recruiters and eight hiring managers) drops a cheaper tile when the must-have workflow unlocks only on a higher hub.
2. Compare like for like
Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/deputy/. Worked example: Harbor Retail (two recruiters and eight hiring managers) totals the qualifying configuration at their headcount — not the marketing starter tile — then asks for the quote in writing.
Deputy must vs nice
- Core job on entry plan
- Gated capabilities
- AI / SMS / extra hubs
Deputy checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1List day-one must-havesFeatures that must ship without an unused enterprise tier.
- 2Map to a qualifying planUse researched plan names — not marketing starting tiles.
- 3Get the qualifying quote in writingSeats, hubs, add-ons, and implementation fees.
3. Map must-haves to plan names in writing
Feature gates researched on Deputy: core hris (Lite, Core, Pro) and payroll processing (Lite, Core, Pro). Map each must-have to the plan that unlocks it.
Compare published tiers on the same headcount assumption.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance screenshots the plan shown in demo and matches it to /pricing/deputy/.
4. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Deputy. Compare totals — not entry tiles.
5. Get a written quote on the qualifying configuration
Ask Deputy for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance files quotes in the same folder with identical date and headcount headers.
6. Map must-haves to plan names in writing
Feature gates researched on Deputy: core hris (Lite, Core, Pro) and payroll processing (Lite, Core, Pro). Map each must-have to the plan that unlocks it.
Compare published tiers on the same headcount assumption.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance screenshots the plan shown in demo and matches it to /pricing/deputy/.
7. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Deputy. Compare totals — not entry tiles.
8. Get a written quote on the qualifying configuration
Ask Deputy for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance files quotes in the same folder with identical date and headcount headers.
9. Map must-haves to plan names in writing
Feature gates researched on Deputy: core hris (Lite, Core, Pro) and payroll processing (Lite, Core, Pro). Map each must-have to the plan that unlocks it.
Compare published tiers on the same headcount assumption.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance screenshots the plan shown in demo and matches it to /pricing/deputy/.
10. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Deputy. Compare totals — not entry tiles.
11. Get a written quote on the qualifying configuration
Ask Deputy for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: Multi-location hourly operators who need scheduling + time + labor compliance files quotes in the same folder with identical date and headcount headers.
12. Before you sign with Deputy
Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/deputy/ and the evaluation scorecard so finance can audit the same assumptions at renewal.
13. Write the decision memo
Name the job, the qualifying Deputy configuration, and what you are not buying yet. If stakeholders cannot explain why an alternative lost, the trial was not fair.
Frequently asked questions
Does a free Deputy plan count?
Our snapshot records no trial length for Deputy — ask for an evaluation window in writing before you commit seats.
Should we pay annually?
Only after the qualifying configuration is written. Annual discounts do not fix the wrong hub.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.