- Data sync
Two Wurqurs, Watchtower and Sync Keeper, read 2,000 signals a month so the sales team reads 200.
~$47,000 saved a year for an industrial equipment distributor
See howEvery team owned its own piece. Nobody owned what happened between them.
Onboarding Runner and Offboarding Runner run the sequence end to end when someone joins or leaves a 300-person professional services firm, with Exception Handler catching whatever either can't resolve.
Professional services firm · 300 employees · five systems
The gap
Onboarding and offboarding had become a set of disconnected tasks. HR worked in Workday, IT in ServiceNow, identity ran through Microsoft Entra ID, documents through DocuSign. Each team owned its part. Nothing owned the sequence between them. Offboarding was the sharper risk: a missed access removal is a security problem, not an admin one.
HR had already written a thorough playbook covering most of it. The gap wasn't a missing process. It was that no single system ran the one they had, so people chased each other across departments by hand, working from checklists.
A missed access removal is a security problem, not an admin one.
What we found, and left alone
HR had already written a thorough playbook. A lot of what was documented could become real workflows, and together they could run onboarding and offboarding almost completely. Where the playbook itself calls for a person to confirm or deny, that stayed exactly as written, and exceptions still go to a person with the context attached.
What we built
An event-driven workflow where the employee record is the trigger. A qualifying Workday record starts Onboarding Runner: IT tickets, document collection, and tracking what's outstanding, all in the right order. A departure starts Offboarding Runner: access removal, equipment recovery, manager confirmation. Exception Handler owns anything either one can't resolve on its own, a step that fails or stalls, or access still live past the leave date, and makes sure it doesn't sit.
Onboarding Runner
Runs every downstream step in order across every system: accounts, access, equipment, paperwork. Chases what stalls.
- exception
Exception Handler
Owns whatever the onboarding sequence couldn't resolve, with the context attached.
Offboarding Runner
Removes access everywhere, recovers equipment, closes accounts, and keeps proof that all of it happened.
- exception
Exception Handler
Owns anything still open after someone leaves, including access still live past the leave date.
What changed
someone joins or leaves
Days of chasing
Minutes
96–120
events a year, orchestrated
480–720 hrs
a year, back to HR and everyone else involved
~$21,600
a year
What used to cost them roughly $1,800 a month by hand now runs on three Wurqurs for $163/month.
Where the humans stayed
Exceptions, and every approval that already existed. We replaced none of their systems. We made the joins between them stop leaking, and the parts of the playbook that call for a person to confirm or deny stayed exactly as written.
What it connects
Where the trigger comes from, the three Wurqurs, and where the sequence lands.
where it arrives
- Workdaythe employee record, joining or leaving
what runs
- Onboarding Runnerruns the joining sequence, chases what stalls
- Offboarding Runnerruns the leaving sequence, proves it happened
- Exception Handlerowns whatever either one couldn't resolve
where it lands
- Microsoft Entra IDidentity and access
- Microsoft 365accounts and mailboxes
- ServiceNowIT tickets and equipment
- DocuSigndocument collection
What it took
Five weeks. Four to build and deploy, one to shadow-run and confirm it in production.
The same idea, somewhere else
Signals nobody has time to read, filtered down to the 200 that actually need a person.
Every company has a process nobody owns end to end.
Tell us the job. We will tell you whether a Wurqur can hold it.