Handover means we revoke our own access

There's an uncomfortable truth about consulting: lock-in is a business model. Ship a black box, keep the keys, and the retainer renews itself. Nobody puts it in the proposal, but plenty of engagements are structured exactly that way — and if you've ever tried to leave one, you've felt it.

We structure ours so we can be fired.

What that looks like in practice

• The infrastructure lives in your AWS accounts and your repos from day one. We never host anything you'd have to migrate off later.
• Docs are written while we build, not reverse-engineered as a handover deliverable in the final week — and these days, agents keep them current on every merge, so they don't rot after we leave.
• The last stretch of every engagement is a walkthrough with your engineers driving, not watching.
• And then we revoke our own access. IAM users, roles, SSO grants — removed, while you watch.

That last step sounds theatrical, but it does something useful long before it happens: it audits every decision we make in month one. If we're not going to be around to babysit a thing, that thing has to be boring, documented, and standard. Clever-but-fragile doesn't survive an engagement where the builders delete their own keys at the end.

The bet is simple: we'd rather be re-hired than un-fireable. If you come back it will be for the next block or the next system — scoped and priced from scratch — not because the first one left you unable to leave.