ADP Run customers outgrow it 6 months too late — what the 50-employee cliff actually looks like.

ADP Run is officially positioned as "payroll for 1–49 employees." It's the right product for a 12-person agency that wants payroll, basic benefits admin, and 1099 contractors handled without a controller in the chair. For that buyer, it's hard to beat.

The graduation happens later than it should — and the cost shows up as friction, not as a number on an invoice.

What Run is actually built for

Run's core surface is intentionally narrow:

• Full-service payroll, multi-state, with garnishments and tax filings
• Basic time tracking via the Time & Attendance add-on
• 1099 contractors — genuinely best-in-class for small employers
• Benefits admin through ADP's broker network — light lift, not deep configuration
• ZipRecruiter integration for sourcing and basic performance review templates in HR Pro
• 1095-C generation (Run can technically file ACA — it just lacks the look-back measurement engine)

What it isn't built for:

• Production-grade applicant tracking and recruiting workflow
• LMS / course assignment / compliance training
• Shift-differential and complex pay-rule engines
• HRBP-quality analytics — headcount-by-department-by-month with attrition trending

For a 12-person team, those gaps don't matter. For a 60-person team, two of them are already broken.

The 50-employee cliff

Three things start happening at roughly 45–55 headcount:

1. ACA stops being "light."

You crossed the 50 FTE Applicable Large Employer threshold, which means 1095-C filings, look-back measurement, and a real ACA strategy. The 2026 ACA affordability threshold is 9.96% (up from 9.02% in 2025) — small drift, but enough to retrigger Safe Harbor math. Run handles the filing. It doesn't handle the strategy. Most controllers I talk to are spreadsheet-managing the measurement period outside the system.

2. Performance and reviews become a real conversation.

HR teams that ran annual reviews in Google Docs at 25 employees can't do it at 60. Run's HR Pro tier has basic review templates, but quarterly cycles, calibration, and 9-box mapping aren't there. So a $4–8 PEPM third-party tool (Lattice, 15Five, Leapsome) shows up — and now identities are stitched across two systems.

3. The reporting ceiling becomes visible.

Run's standard reports are clean and pre-built. The custom report builder is functional but limited. Once a CFO wants headcount-by-department-by-month with attrition rates and labor-cost trending, Run hits a wall and the answer becomes "export to Excel." (Note: even WFN customers report needing the WFN Analytics add-on for conditional reporting.)

None of these are bugs. They're product-scope boundaries that were correctly set.

Why graduation happens 6 months late

The reason customers stay on Run past the cliff isn't loyalty. It's three things:

1. Run's monthly cost is low. A 50-employee company pays roughly $1,200–$1,600/mo all-in (Essential tier base + PEPM + T&A + per-payroll-run fees). Workforce Now starts closer to $1,800–$2,500/mo at the same headcount with the modules that solve the cliff problems.
2. Migration sounds painful. It's actually clean inside ADP — tax IDs carry, YTD wages carry, year-end consolidates. Typical conversion is 4–8 weeks with 1–2 weeks of parallel-run validation. The data carries; reconciliation is the actual work.
3. Nobody owns the decision. The HR generalist sees the gaps. Finance sees the invoice. The CFO sees neither until a board meeting where headcount reporting falls apart.

What graduation looks like when it goes well

The companies that handle it cleanly do three things:

• Plan the move 3–4 months ahead of a natural inflection — usually open enrollment or fiscal year. Not at the cliff. Before it.
• Scope WFN to the actual gaps. The Select → Plus → Premium tier path is the typical step: payroll + HR → add benefits → add time. Talent, Performance, and Compensation are separate paid add-ons, not bundled. You don't need them on day one.
• Use ADP's in-network migration team. The data conversion is solved. The parallel-run plan is where projects slip. Get it in writing before signing.

The 50-employee cliff isn't a Run problem. It's a sign that the org outgrew the right tool for last year.