Same engine, many employers
One determination model across the book. Each result still has a citation and a Why.
Determinations across the book of business
Call the same engine for every employer. Each result still has a Why. Specialists stay on exceptions, not every offset.
The relationship
Keep the client. Run the determination.
LEAN is the engine under your leave service — not a replacement brand in the employee’s inbox, and not a reason to send the whole function to an outsourcer.
Why this market is different
Employer software math does not apply to a book of business
- Volume is the product Each client employer adds determinations. Hiring specialists in lockstep with that volume is the wrong cost curve.
- Multi-employer, multi-state, one operating team Consistency has to hold across handbooks, worksites, and statutes — not just one company’s policy.
- The outsourcer risk Handing leave to a third-party administrator can solve capacity and lose the relationship that sold the PEO.
- You still need an answer you can show Clients, examiners, and your own ops leaders need a cited, auditable determination — not a black box.
What you run
The engine in your stack. Specialists on exceptions.
You stay in the client conversation
Leave stays a PEO service. LEAN computes the leave; the chrome can stay yours.
Determinations API
Call LEAN from the platform you already operate. Surveys, Why, and the recorded result stay attached.
A partnership conversation
Tell us about the book of business. We’ll talk determination volume, where specialists still matter, and how you keep the client relationship.
No spam. We’ll reply with a calendar link.