BambooHR

What it is

BambooHR is an HRIS for companies with 25–500 employees that covers the full employee lifecycle — job posting and applicant tracking, onboarding, time-off management, performance reviews, offboarding — in a single system. It is not an enterprise HCM: it lacks Workday’s depth on global compliance, compensation planning, and workforce analytics, but it costs a fraction of what Workday charges to implement and run. Since July 2026 it also ships Bamboo AI, an embedded agent layer covering report generation, shift scheduling, payroll anomaly detection, and benefits Q&A — plus an MCP connection that exposes BambooHR workforce data to ChatGPT, Claude, and other assistants under the same permission model the UI enforces. The closest analog at the upper end is Rippling, which extends BambooHR’s scope into IT provisioning and payroll automation; at the lower end, Gusto, which handles payroll-first SMBs. BambooHR sits in the middle as the default HRIS choice for TA-led and HR-generalist teams who need one login that works across hiring, onboarding, and people records without a dedicated HRIS admin.

Why it shows up in recruiting stacks

• It is the integration target every ATS ships first. Greenhouse, Lever, and Ashby all have pre-built, one-click BambooHR connectors because BambooHR is where the hired record needs to land. When a recruiter moves a candidate to “Hired” in Greenhouse, BambooHR receives name, start date, role, compensation, and manager automatically — no manual re-entry. That handoff is the most-integrated step in the SMB recruiting workflow, and BambooHR lists over 150 integration partners behind it.
• The built-in ATS ships in the entry plan, and its cap is the plan lever. Applicant tracking, offer letter templates, new-hire packets, and e-signatures are all in Core, the $10/employee/month tier — but Core allows only 5 concurrent job openings. Pro raises that to 25, Elite to 50. Teams running a handful of openings at a time and not doing complex structured interviewing often skip a dedicated ATS entirely; teams that outgrow the slot count pay for the whole headcount to get more of them.
• Onboarding is where the HRIS earns its keep. BambooHR’s onboarding module lets HR build templated new-hire packets — documents, e-signatures, task checklists for IT and the hiring manager, benefits enrollment prompts — that trigger automatically on a set start date. For a team making 5–20 hires per month, this removes 15–20 minutes of manual setup per new hire.

Pricing reality

BambooHR now publishes list pricing, which it did not do a year ago. Three tiers, priced per employee per month: Core at $10, Pro at $17, Elite at $25. Companies with 25 employees or fewer pay a flat rate starting at $250/month instead of the per-employee rate. Volume discounts are applied automatically as headcount grows rather than negotiated, registered nonprofits get an additional 15% off, and terms run month-to-month or extended.

A 100-person company on Pro pays roughly $1,700/month, or $20,400/year at list, before add-ons and before the automatic volume ladder. The add-ons — Payroll (US employees only), Benefits Administration (US employees only), Time & Attendance, and Global Employment powered by Remote — carry no published price; third-party buyer reports put payroll around $6–8/employee/month. Combining Payroll and Benefits Administration takes 15% off both, US employees only.

Vendr’s data across 114 BambooHR deals puts the median annual contract at $16,197, with a range of $9,490–$78,783 and average savings of 9.79% against the opening quote. That median lands near Core-to-Pro list for a 100–150 person company, and the sub-10% average discount is the tell: most of what a buyer saves here comes off the automatic volume ladder, not off the negotiating table. Bundle the add-ons at initial signature — adding Payroll or Performance after the fact forgoes the bundle discount.

Best for

HR generalists and TA leads at 50–250-person companies running structured hiring through a dedicated ATS (Greenhouse, Lever, Ashby) who need a clean handoff into onboarding and one system of record for employee data. Pro at $17/employee/month is the practical target: it lifts the ATS to 25 concurrent openings, adds 360° review cycles and 1:1s, and lets the AI assistant answer from uploaded policies and handbooks rather than HRIS fields alone.

Do not buy BambooHR if: you are well under 25 employees — the $250/month floor works out to $10/employee at 25 people but $25/employee at 10, which is Elite pricing for Core features; you need US payroll without a separate module; or you want a proactive sourcing ATS, because BambooHR’s ATS processes inbound applicants and has no sourcing, no candidate database search, and no AI ranking of candidates. Skip it too if you need global payroll or GDPR-grade data residency controls — payroll is US-only, and the EMEA compliance story is thin.

Versus the alternatives

Greenhouse is the comparison that comes up most often in the 100–500-person range: Greenhouse wins on structured interviewing, scorecard discipline, and analytics depth, but it requires BambooHR (or another HRIS) alongside it — they are complementary, not competing. The real question is whether to run BambooHR’s built-in ATS or Greenhouse as the ATS with BambooHR as the HRIS. Pick Greenhouse-plus-BambooHR when your TA team runs panel interviews, enforces rubric scoring, and cares about time-to-hire reporting by department. Pick BambooHR alone when your concurrent openings fit inside the Pro cap of 25 and the ATS job is mainly posting, tracking, and handing off to onboarding.

Rippling is the fastest-growing entrant in this segment — valued at $16.8B in its May 2025 Series G ($450M raised), with Sacra estimating it crossed $1B in annualized revenue in March 2026. Rippling adds IT provisioning, device management, and modular payroll to an HRIS core, which is the meaningful upgrade when you want app-access provisioning to run off the same trigger as the new-hire record. Pick Rippling when your ops team is past 100 headcount and wants HR and IT on one platform; pick BambooHR when you want simpler HR without the IT surface and your helpdesk is already handled elsewhere.

HiBob is the premium mid-market alternative (100–500 employees), more expensive and stronger on culture and engagement. It bought FP&A platform Mosaic in February 2025 for a reported $35M and reached general availability on native US payroll and benefits administration on 1 January 2026, running on Gusto’s payroll engine and PlanSource’s benefits stack. Pick HiBob when you are culture-forward, geographically distributed, and want headcount planning inside the HRIS; pick BambooHR when you want lower cost and cleaner ATS-to-onboarding handoffs.

Watch-outs

• The ATS opening cap is a headcount-wide upgrade trigger. Core allows 5 concurrent job openings, Pro 25, Elite 50 — and you buy the tier for every employee, not for the recruiter who needed the slot. A 100-person company that hits 8 concurrent roles pays the Core-to-Pro step across all 100 employees: $700/month more for job slots it could have bought as a handful of ATS seats. Guard: count your active-at-peak concurrent openings before signing, and if the count sits between 6 and 25, price the Core-to-Pro delta against a dedicated ATS (Greenhouse, Lever, or Ashby) running alongside BambooHR-as-HRIS before assuming the upgrade is the cheaper path.
• Payroll and benefits administration are US-only add-ons. BambooHR Payroll handles US domestic payroll and nothing else; EMEA, LATAM, and APAC employees fall outside it. Global Employment routes them through Remote as employer-of-record or contractor management, which is a different product with different cost per head. Guard: map every employee location before scoping the deal, and if any payroll is non-US, budget a separate provider (Rippling Global, Remote, Deel) and confirm the data handoff format before signing rather than after.
• The MCP connection inherits BambooHR permissions, which cuts both ways. Bamboo AI’s MCP connection carries the requesting user’s role and permissions into ChatGPT or Claude, so an assistant reads exactly what that person can read — including compensation and sensitive identifiers if their role grants field access. That is the right design, and it means an over-broad HR admin role becomes an over-broad agent. Guard: audit which BambooHR roles carry compensation and SSN field visibility before enabling MCP, and tighten field-level permissions first; the permission engine is the only control surface here, so a role that was merely generous in the UI becomes a data-egress path once an external assistant is on the other end.