Application: agents for your clients, a few weeks at a time.

Why this shape of work fits

Short engagements with a hard problem and a client team to hand over to is how I have worked since leaving pharma: a 12-month embed on an enterprise SaaS, a marketplace rebuilt in four months, and a run of MCP servers that other people now install. I know what a good handover looks like because I have been on the receiving end of bad ones.

On the framework: I have built with the LangChain ecosystem and I am not religious about it. Where a client's problem is served by LangGraph and LangSmith I use them; where it is served by a plain MCP server and an eval harness, I say so. UK hours, overlap with US Central and Mountain is fine. Project-based, $90/hr, available from 1 September.

A few weeks, four habits

Enterprise agent projects die in the plumbing, not the prompt. These are the four things I do in every engagement so the client keeps something that works after I leave.

1. Ship a working slice in week one. One real workflow, end to end, against the client's actual system, before any architecture debate. It settles what the data looks like, what auth looks like, and whether the agent can do the job at all. Everything after that is widening a path that already works.
2. Evals before features. Every workflow gets a small eval set from real inputs on day one, run in CI, so the client can see the agent get better rather than take my word for it. I shipped a tool-selection eval suite with an injection and red-team pass for coolify-mcp in August; the same harness applies to LangGraph graphs and to RAG retrieval quality.
3. MCP as the integration boundary. Client systems (CRM, ERP, databases, the legacy thing nobody will name) go behind MCP servers with typed tools and resources, so the agent framework can change without the integrations changing. Four shipped, one with 28k installs a month, all with auth from the first deploy.
4. The handover is a deliverable, not a goodbye. Runbook, eval set, tracing dashboard and a recorded walkthrough, written for the engineer who inherits it. A client that can run and extend the thing without me is the point of a short engagement.

The numbers, with sources

Operating numbers, last 30 days, generated 2026-08-27. Sources per tile in profile.json; hover a tile for its source.