Engagements

Choose the engagement around the outcome.

Contract delivery is the primary offer. Shorter sprints and advisory are available when the scope is genuinely bounded.

Primary engagement

3–6 months

Contract Lead AI Engineer

Day rate · scope and IR35 dependent

Hands-on leadership for a production AI outcome: architecture, implementation, integration, governance, team alignment, and handover.

Senior / Lead ownership
Agentic systems and LLM applications
London hybrid or UK remote
Outside IR35 where working practices support it

Discuss a contract

2–4 weeks

Delivery sprint

Fixed scope · fixed outcome

A bounded production slice for teams that know the use case but need senior engineering to get it through the whole stack.

One end-to-end use case
Evaluation and observability included
Production path, not a demo
Code, tests, ADRs, and runbook

Scope a sprint

Focused sessions

Advisory

POM packs or team workshops

Architecture review, Claude Code adoption, workflow design, or an honest second opinion before a larger commitment.

Real repo or workflow
Practical output in the session
No generic AI theatre
First 24-minute POM available free

See the advisory POM

Good contract fit

Enough access to own the outcome.

Production AI crosses product, engineering, data, security, and operations. The engagement works when the contract gives the delivery lead room to connect those decisions.

A named production outcome with an accountable business owner
Access to the product, engineering, security, and data decisions needed to ship
A team that wants code, evidence, and knowledge transfer — not a strategy deck
Clear engagement terms, location expectations, and IR35 determination

Start with the production outcome.

Send the objective, team, stack, timing, location, and IR35 status. I will recommend the smallest engagement shape that can credibly ship it.

Discuss the work