Guide, 8 Nov 2026, read 8 Nov 2026
How to run an agent pilot in 30 days
Week one: pick and set
- Pick the process the diary shows the platform runs: onboarding on Shapes or Humaans end to end; part of it on Rippling, Workday, Gusto, Factorial or Paylocity.
- Write the approval rule in one sentence: who approves the record write, the message, the policy assignment, and the wave.
- Switch the agent on for one team only; find the off switch before you need it (Shapes: three switches; Rippling: enable or disable; BambooHR: Account Settings).
- Mark the sensitive fields the agent must not read, and test with a salary question.
Weeks two and three: run it
Every new starter on the pilot team goes through the agent: the trigger fires, the draft lands, the approver clicks, the actions run, the log fills. The People team does nothing it would normally do for those starters except approve, and it keeps a tally of the minutes it would have spent. Shapes's pre-launch count and Humaans's request triaging are the places to watch; a draft that needed editing is a note, not a failure.
Week four: read the log and decide
Export the agent's actions for the three weeks with the approver on each line, and read them with the security reviewer. Count: starters onboarded, drafts edited, approvals refused, actions in other systems, and People minutes saved. Decide on the number and on the log, not on the demo; a pilot whose log cannot be exported has already answered the audit question.
Sources
- Shapes agents, read 8 Nov 2026
- Shapes pre-launch count, read 8 Nov 2026
- Humaans Athena, read 8 Nov 2026
- Rippling automations, read 8 Nov 2026
Last reviewed 8 Nov 2026.