Experience
I did not start in operations consulting, and I did not start at the technology layer either. I started inside recruitment, which is why I understand these businesses differently to someone who has only worked in SaaS or general consulting.
Recruitment
Inside the operating model: candidate journeys, client requirements, worker onboarding, compliance, scheduling and fulfilment.
Workforce operations
Running the processes that keep a workforce paid, compliant and accounted for: time capture, payroll, invoicing, margin.
Workforce technology
Moving to the technology side of the same problems, understanding what software can and can't realistically fix.
Customer and enterprise delivery
Service delivery, implementation and escalation management across large, complex accounts.
Global operations leadership
Senior leadership across a large operations function, spanning product, engineering, customer and delivery teams.
Independent consulting
Applying nearly two decades of that experience to businesses that need someone who can diagnose and fix, not just advise.
I know recruitment from both sides of the software.
I worked in recruitment before I moved into the technology used to run complex workforce operations. That means I understand candidate journeys, client requirements, worker onboarding, compliance, scheduling, fulfilment, time capture, payroll, invoicing, margin, customer service, account management, reporting and implementation, from direct experience, not from a requirements document.
Problems I have actually worked on
This is career impact, describing scale and complexity I have operated within, not independent client work. Client case studies are shown separately.
Enterprise delivery visibility
Complex programmes had dependencies spread across product, engineering, operations, customer teams and leadership, with no single view of where things stood.
Built clearer governance, RAG reporting, decision ownership, prioritisation and delivery visibility.
Leadership could see blockers, dependencies and decisions before they became customer escalations.
Implementation efficiency
Repeated implementation work was being recreated manually on every new programme, with no shared library of what had already been built.
Identified the repeatable work and converted it into reusable operational assets, templates and standardised processes.
29 operational outputs delivered. 19 of those became reusable assets. An estimated 90 to 190 hours saved across five implementations, roughly a 25 to 40% efficiency improvement.
High-volume workforce operations
Enterprise workforce environments running at a scale where manual oversight alone could not keep pace.
Operated within and contributed to the operational management of that scale directly.
One representative operating sample: 27,485 shifts, 216,648 workforce hours, approximately $4.64m in workforce value. This is scale evidence, not a savings claim.
Enterprise implementation
Programmes spanning complex workforce configuration, time and attendance, payroll, reporting, integrations, customer onboarding, UAT and multi-country requirements, all against fixed commercial deadlines.
Worked across the operational and delivery side of these programmes, coordinating product and engineering dependencies against the commercial timeline.
One enterprise programme alone included 14 BI dashboards, alongside multiple data, reporting and workflow requirements.
Commercial risk and retention
Operational failure at enterprise scale is never just an inconvenience. It becomes lost margin, delayed revenue, renewal risk, customer dissatisfaction, support cost and delivery risk.
Carried operational responsibility connected to enterprise renewals, retention risk and expansion opportunities, not just process design in isolation.
A commercial lens on operational work: understanding what a broken process actually costs the business, not just the team running it.