Mantyl.devUse cases · one handover, many seats

The agency shipping client work

An agency running AI-assisted delivery has a throughput problem it wanted and a consistency problem it did not: five developers, five agents, five private histories of how each project actually got built. The client sees none of that machinery. They see the handover, and the handover is where agencies get compared.

The consistency problem, honestly stated

In an agent-heavy team, the knowledge of how a project works fragments across session transcripts on individual machines. When the developer who steered the build moves to the next engagement, the agency’s institutional memory of that project is whatever made it into the repo. Client questions months later become internal archaeology, billed to nobody. And every delivery closes slightly differently, depending on who ran it and how much Friday was left when they did.

A standard a junior can run

The fix is a delivery standard that does not depend on seniority. The evidence half is one command sequence: the CLI reads the repository and every agent’s session history, executes the setup in a clean sandbox, and produces the passport with each statement labelled by how it was established, including the decisions recovered from transcripts that would otherwise leave with the laptop. The human half, credentials, access confirmation, support boundary, is a checklist any team member can follow; the agency delivery standard writes it out in full. Make both part of the definition of done and every project closes the same way, whichever desk it shipped from.

What the client experiences

Delivery day gains a ritual. The client logs into everything themselves while you are on the call. They receive the hosted passport link, with the recipients page alongside so their non-technical stakeholders can read the labels unaided. And they watch one command, run on their side, compare the delivery against the passport and come back clean. Agencies that do this report the same thing: the final call stops being the tense one. For engagements where procurement or an investor wants third-party assurance, Mantyl Verified signs an independent re-execution for £19 to £49 per project, which fits agency economics precisely because it is per delivery, not per seat; the arithmetic is on the pricing page, along with where the team tier with white-label passports is heading.

The margin argument

Handover used to be the unpaid week at the end of every engagement. With extraction and verification automated, the evidenced close costs minutes of tooling plus a checklist, which means it belongs in the quote as a named deliverable rather than absorbed as goodwill. It also shrinks the post-delivery support tail, because the honest unknowns were listed at delivery instead of discovered by the client one ticket at a time. The wider practice, and why we think handover is becoming a discipline rather than a courtesy, is the AI code handover guide. For the individual version of this seat, see the freelancer delivering to a client; for the engagement-ending variant with contract stakes, see contractor offboarding.

Guides · Docs · PricingWritten against the real product