One new client, narrated

The Implementation Tour

Ridgeline Outdoor Supply Co. switches providers mid-year — two states, existing data and all — without losing a day, a data field, or a dollar of history. Walked through out loud, stage by stage, in under two minutes.

1 daySigned to provisioned

7Import formats supported

$0YTD lost in the switch

~90 secNarrated run time

Or skip it — everything below reads on its own, no audio required.

The moment the contract is signed

A live environment before the ink is dry

Signing doesn't start a queue — it starts the tenant. The moment the deal is marked won, Ridgeline's environment provisions itself: a workspace, a login for their HR admin, an implementation case already open.

Client provisioning — Ridgeline Outdoor Supply Co.Complete · 0 tickets filed

Step 1

Contract signed

→

Step 2

Tenant created

→

Step 3

HR admin login invited

→

Step 4

Implementation case opened

This is the same handoff The Presales Tour ends on — a closed-won opportunity, not a fresh manual setup.

Whatever system they're leaving

The data doesn't have to be perfect to move

Ridgeline's census, leave balances, and pay register import straight from their outgoing provider — seven formats supported. Every row gets graded automatically: clean data passes, and a real problem blocks the batch instead of becoming a payroll mistake three weeks later.

Census import — Ridgeline Outdoor Supply Co.1 green · 3 amber · 3 red

✓Clean rows1 — imported automatically

!Warnings3 — imported, flagged for review

✕Blocked3 — missing required fields

A blocked row has to be fixed or explicitly acknowledged before the batch commits — nothing quietly vanishes.

Mid-year switches are the hard case

Nobody's numbers reset to zero

Ridgeline moved over mid-year, not January 1st — the case a lot of providers get wrong. Year-to-date wages and taxes carry forward so Social Security and Medicare caps stay correct, and every employee's leave balance comes across with them.

Mid-year takeover — Ridgeline Outdoor Supply Co.YTD carried forward

✓Year-to-date wages & taxesCarried forward — caps stay correct

✓Opening leave balancesVacation · Sick · Personal · PTO bank

✓Go-forward leave plansConfigured in the same flow

Two states, day one

The paperwork gets done before anyone asks

Ridgeline pays people in California and Texas. Both states' tax registrations and workers' comp classifications get set up as part of implementation — not discovered missing the week of the first run.

Implementation — compliance setup2 of 2 states registered

✓California state tax registrationRegistered

✓Texas state tax registrationRegistered

✓Workers' comp classificationSet for every employee

Before the first run

Go-live is checked, not just checked off

Readiness isn't a self-reported checklist a coordinator fills out and hopes is true — it's derived from Ridgeline's real, live configuration, every time it's viewed.

Go-live readinessVerified

✓Funding accountOn file

✓Service agreementSigned

✓State tax ratesEntered

The payoff

The first payroll runs like the hundredth one

Ridgeline's first payroll goes out clean — the same engine, the same compliance checks as every run after it. And every employee who came over gets the same onboarding as the new hire in The Onboarding Tour — the same checklist, just all at once instead of one at a time.

Ridgeline's first payrollCompleted

Same as run #2

One calculation engine

→

Same as run #2

One compliance pre-flight

→

Same as run #2

One funding review

→

Result

Ridgeline's first paycheck, on time

Six stages, one client, and a switch that didn't cost anyone their history — data, compliance, or a day of waiting. Every employee who came over gets the same first day as the one in The Onboarding Tour; this is just what happens before any of them log in.

RIDGELINE OUTDOOR SUPPLY CO. · CLIENT IMPLEMENTATION · PEO CO-EMPLOYMENT

Talk track — for a rep reading this live, or recording your own voiceover