SoftwareGlimpse
HR, Workforce & Training Software

Gusto Plans: Seats, Hubs, and Qualifying Tiers

Choose your Gusto plan by mapping must-haves to qualifying tiers — seats, hubs, pools, and add-ons — not homepage “from” tiles.

By Lee M.Updated Aug 18, 20266 min readFact-checked

Quick answer

Choose a Gusto 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 time and attendance (Simple+) is on the package you will actually buy. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/gusto/.

  • 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

Gusto packaging rules

  • Tiles are the bottom layer Researched plans: Simple, Plus, Premium, Contractor Only.
  • Gates change the bill Plan-gated in research: time and attendance (Simple, Plus, Premium, Contractor Only).
  • Free is a proving ground Our snapshot flags a trial on Simple, Plus, and Premium without a published length — confirm the window on the Gusto pricing page.
  • Wrong cluster, wrong comparison Do not compare Gusto (applicant tracking / recruiting) to frontline scheduling or a GPS time clock on a single price tile.

Gusto qualifying configuration

Gusto plan anatomy: seats, hubs, gates, add-ons.
Read Gusto pricing from must-have gates upward; confirm numbers on the pricing page.

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, core hris, payroll processing, and benefits admin. 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/gusto/. 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.

Gusto must vs nice

Must-have
  • Core job on entry plan
  • Gated capabilities
Nice-to-have
  • AI / SMS / extra hubs

Gusto 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 Gusto: time and attendance (Simple, Plus, Premium, Contractor Only). Map each must-have to the plan that unlocks it.

Compare Simple, Plus, Premium, and Contractor Only on the same headcount assumption.

Worked example: US small businesses running payroll (and benefits) for the first time screenshots the plan shown in demo and matches it to /pricing/gusto/.

4. Model seats, usage, and add-ons together

Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Gusto. Compare totals — not entry tiles.

5. Get a written quote on the qualifying configuration

Ask Gusto for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.

Worked example: US small businesses running payroll (and benefits) for the first time 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 Gusto: time and attendance (Simple, Plus, Premium, Contractor Only). Map each must-have to the plan that unlocks it.

Compare Simple, Plus, Premium, and Contractor Only on the same headcount assumption.

Worked example: US small businesses running payroll (and benefits) for the first time screenshots the plan shown in demo and matches it to /pricing/gusto/.

7. Model seats, usage, and add-ons together

Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Gusto. Compare totals — not entry tiles.

8. Get a written quote on the qualifying configuration

Ask Gusto for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.

Worked example: US small businesses running payroll (and benefits) for the first time 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 Gusto: time and attendance (Simple, Plus, Premium, Contractor Only). Map each must-have to the plan that unlocks it.

Compare Simple, Plus, Premium, and Contractor Only on the same headcount assumption.

Worked example: US small businesses running payroll (and benefits) for the first time screenshots the plan shown in demo and matches it to /pricing/gusto/.

10. Model seats, usage, and add-ons together

Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Gusto. Compare totals — not entry tiles.

11. Get a written quote on the qualifying configuration

Ask Gusto for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.

Worked example: US small businesses running payroll (and benefits) for the first time files quotes in the same folder with identical date and headcount headers.

12. Before you sign with Gusto

Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/gusto/ and the evaluation scorecard so finance can audit the same assumptions at renewal.

13. Write the decision memo

Name the job, the qualifying Gusto 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 Gusto plan count?

    Our snapshot flags a trial on Simple, Plus, and Premium without a published length — confirm the window on the Gusto pricing page.

  • 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.