Services
Defined offerings, delivered by the person you speak to.
Start with a health check, or go straight to a build, a fix or a plan. Every engagement is different, so the commercial model should fit the work, not the other way around.
Flagship offer
Workday Integration Health Check
Find what’s fragile before your next release or pay run does.
A read-only review of your Workday integrations that ends with a clear, prioritised fix list. No changes to your tenant, and no open-ended consulting.
Two weeks, start to finish
Fixed price by integration count
Read-only access, no tenant changes
34 checks across six areas
1
Who it’s for
Teams six or more months past go-live whose implementation partner or integration owner has moved on.
2
What you get
A RAG-rated inventory, a prioritised fix list with effort and risk for each item, and a one-hour readout.
3
How it works
Read-only access through an integration system user. Two weeks start to finish, fixed price by integration count.
What the review covers
34 checks across six areas, applied to every integration in scope.
01
Inventory and ownership
What runs, who owns it, and what is no longer used.
02
Operational health
90 days of failures and warnings, and their root causes.
03
Security and access
ISUs, permissions, and credentials close to expiry.
04
Release readiness
Deprecated versions and what the next release could break.
05
Design and build quality
Hardcoded values, error handling and change detection.
06
Supportability
Documentation, runbooks, and who can fix it when it breaks.
Afterwards
Your fix list becomes the plan.
Fixed-price remediation of the findings
New integrations once the basics are sound
Ongoing monitoring, if you want it
Offerings
Everything else, clearly scoped.
Each offering has a defined outcome and a commercial model to match. Not sure which fits? Start with a conversation and I’ll recommend the structure that makes sense.
Integration builds
Deliverable based
End-to-end design and delivery of new Workday integrations using Studio, Core Connectors, EIB, REST and RaaS. Built to be operated, not just demonstrated.
What you get
Integration design document
Build, unit test and system test support
Cutover and hypercare
Handover documentation and runbook
Integration remediation
Fixed price or deliverable based
Diagnosing and fixing broken or underperforming integrations, fast turnaround, minimal disruption. Often the natural next step after a health check.
What you get
Root-cause analysis
Fix, regression test and deploy
Better error handling and alerting
Updated documentation
Integration strategy and architecture
Deliverable based
Integration strategy advisory that aligns your systems, decisions, and roadmap to deliver scalable, long-term outcomes, written down in documents your team can keep using.
What you get
Integration architecture document
Integration design documents and standards
Pattern and tooling recommendations
Roadmap and ownership model
Integration Lead advisory
Day rate
Embedded or advisory Integration Lead services for Workday implementations and AMS engagements, for when you need flexible, ongoing capacity.
What you get
Integration workstream leadership
Design reviews and quality gates
Third-party and vendor coordination
Coaching for internal teams
Support and AMS
Retainer
Application managed services after go-live, so the context built during delivery is not lost. Includes expert review of integration support tickets with clear remediation guidance for your internal team.
What you get
Ticket assessments
Integration monitoring and failure triage
Release readiness checks
Minor enhancements
Specialism: PECI and payroll
Deep specialist experience in payroll integration, PECI, PICOF and related patterns, across every offering above.
How I work
Practical, and still there after release.
I take a practical approach: understand the business process, map the ownership, then choose the smallest reliable design that the team can actually support. That includes payroll patterns such as PECI and PICOF when they are the right fit.
Start with ownership
Before a build begins, I want to know who owns the process, the exception path, and the next change.
Stay past release
If you need AMS support, I stay involved. The person fixing a production issue already understands why the integration exists.
Add people when needed
For broader engagements, I work informally with Considered Group, a co-op of independent consultants. You get a wider bench without losing the direct relationship.
Engagement models
How we work together
Every engagement is different, so the commercial model should fit the work, not the other way around.
Day rate
For embedded or advisory work where you need flexible, ongoing capacity.
Typically used for
Integration Lead advisory
Retainer
For AMS and support arrangements where predictable coverage matters more than a fixed scope.
Typically used for
Support and AMS
Deliverable based
For defined builds or remediation work with a clear scope and outcome.
Typically used for
Health check, builds, remediation, architecture
Whichever model fits, the person doing the work is the person you spoke to at the start. Tell me what you’re solving for and I’ll recommend the structure that makes sense.
Need someone who will still be there after go-live?
Tell me what you are working through. I’ll give you a straight view on where I can help.