Payroll was chosen in year one. The company is in year six.
The payroll platform was the cheapest one that worked at twelve employees. Time tracking came with the point-of-sale system. Benefits enrollment is a spreadsheet and a carrier portal. The employee file is a folder. Four systems, four versions of the truth, and every open enrollment is rebuilt by hand.
The fix starts with requirements, not demos: what the company needs the system to do for the next three years, scored before a vendor is in the room. Then an implementation that gets the data right on day one — because a platform configured at its defaults is the problem it was bought to solve.
Choose it right. Set it up right.
Selection
For the company comparing demos without a scorecard.Requirements gathered from the people who will use the system, a scorecard built from them, platforms compared against it, and a recommendation with the reasoning written down. Vendor-neutral: the recommendation comes from the scorecard.
Implementation
For the company that bought the platform and never got past the defaults.Configuration against your policies, data migrated and reconciled, carrier and payroll connections tested, managers trained on the parts they touch. Payroll cutovers timed to a quarter so tax reporting stays clean.
Which platforms do you work with?
The selection is vendor-neutral: the scorecard is built from your requirements — headcount, states, benefits, integrations, budget — and the platforms are compared against it, not the other way round.
Can you fix the system we already have?
Often. Most platforms are underconfigured rather than wrong — set up at the defaults and never revisited. A configuration review is a smaller project than a migration, and it comes first.
How long does an implementation take?
It depends on the platform and the data; the scope states it. Payroll migrations are timed to a quarter boundary so the tax reporting stays clean.
Does this connect to the benefits work?
Yes. Benefits enrollment, carrier feeds and the census the audit runs on all live in the same system — a clean HRIS makes the benefits side faster every year after.
How is it paid for?
Scoped in writing before any work starts: a fixed-scope selection, a fixed-scope implementation, or both. Nothing is billed that wasn't scoped.
Start with what you have.
A configuration review of the current platform comes first — it's a smaller project than a migration, and sometimes it's the whole fix.
Scope a systems review