Workflow automation
After the offer
Before day one
Day one
First 90 days
- Runs on its own · 21
- Still by hand · 6
- Needs a person, or retired · 9
- Every new hire set off 36 manual steps, chased by email across 5 offices.
- I built 11 automations connecting the applicant system, the tracker, Outlook and IT.
21 of 27 stepsthat can be automated now run on their own
53 hiresthrough it since June
63 min savedper new hire
Key decisions
Split the work between Claude and a flow
Claude checks for new offers twice a day. A flow writes the row.
Nothing runs until a person approves the hire
A mistake here would reach someone on their first day.
Replaced the AI step with a script
Managers reply on a fixed template, so a script reads it in 1 to 2 minutes.
Every step (21)→
- New hires were entered and chased by hand
- The flow designer kept failing
- Showed the first working automations
- Teams meetings can't book a room
- Booked rooms through the Graph API
- Gave every flow one shared record
- The applicant system can't start a flow
- Split the work between Claude and a flow
- Nothing runs until a person approves the hire
- A network filter blocked the first live run
- Paused for 12 days instead of relying on a workaround
- Fixed it in one session with IT
- Connected to the applicant tracking system
- Moved the flows into code
- The AI step couldn't read managers' replies
- Replaced the AI step with a script
- Moved into versioned code
- One flow failed silently for a week
- Every flow now reports its own failures
- Colleagues now propose changes
- Most of onboarding now runs on its own