The Transfer Engagement Model: How Handoffs Work
The transfer engagement model gives founders full ownership of an AI agent fleet in 2 to 4 weeks. Here is how the handoff works at Armada Works.
The transfer engagement model is a fixed-scope consulting format where a consultancy builds a working system inside a client's codebase and hands it over completely within 2 to 4 weeks. At Armada Works, this means deploying an AI agent fleet (typically 4 to 6 agents handling content, SEO, outbound, and sales operations), training the founder's team to operate it, and leaving. The client owns everything: the agents, the prompts, the dashboards, the documentation. No ongoing retainer required.
Robert Cowherd, founder of Armada Works, describes the transfer model as the lead offer: "If we're still here in twelve months, one of us has failed."
Why Most Consulting Engagements Create Dependency
Traditional consulting firms have a structural incentive to stay. The longer the engagement runs, the more revenue they generate. This creates three patterns that keep clients locked in:
- Proprietary tooling. The consultancy builds on their own platform. Leave, and you lose the infrastructure.
- Knowledge hoarding. Key decisions live in the consultant's head, not in the client's documentation.
- Scope creep as a feature. Every "quick add" extends the contract by another month.
The result is a system that works, but only as long as you keep paying for it. For founders running lean teams, this is a bad trade. You wanted marketing output. You got a vendor dependency.
The transfer engagement model inverts this. The consultancy's goal is to make itself unnecessary. Every decision, every prompt, every automation is built to be understood and maintained by the client's team after handoff.
The Transfer Model: 2 to 4 Weeks, Then It Is Yours
At Armada Works, the transfer engagement follows a structured timeline. Here is how the weeks break down:
- Week 1: Discovery and architecture. We audit your codebase, identify the bottleneck (content, SEO, outbound, or a combination), and design the agent fleet. You approve the architecture before anything gets built.
- Week 2: Build and deploy. Agents are deployed into your repo. They start committing work to
main. You see real output from day one of this phase: briefs, drafts, keyword audits, whatever the fleet is configured to produce. - Week 3: Operate alongside you. We run the fleet while your team shadows. This is where the training happens. You learn to read the dashboard, tune prompts, adjust agent cadences, and handle the daily review.
- Week 4 (if needed): Handoff and documentation. We finalize runbooks, transfer all credentials, and do a clean exit. The system is yours.
Not every engagement needs four weeks. A founder with strong git discipline and a clear bottleneck can be self-sufficient in two. We scope it on the kickoff call and price it accordingly: $10,000 to $20,000 for the setup, with an optional $1,500/month light-touch support tier for founders who want a safety net.
For a full breakdown of how the engagement runs week to week, see how we engage.
What Gets Handed Off
The handoff is not a PDF and a handshake. It is a working system inside your codebase. Specifically:
| Deliverable | What It Includes |
|---|---|
| Agent fleet | 4 to 6 configured agents (CMO, SEO, Content, Sales Lead, Outbound, or custom) running on scheduled cadences |
| Prompt files | Every agent's full prompt, version-controlled in your repo at docs/agents/ |
| State files | Git-committed state and daily briefs at docs/agents/state/, giving you a full audit trail |
| Dashboard | A founder-facing admin view showing agent briefs, status, and output |
| Documentation | Runbooks for prompt tuning, adding new agents, debugging common issues |
| Training session | A walkthrough (recorded) covering daily operations, prompt editing, and escalation patterns |
Everything lives in your repo. There is no external platform to log into, no SaaS dependency, no API keys that stop working when the contract ends. You own the git history, the prompts, and the system architecture. If you want to modify an agent's behavior after we leave, you edit a markdown file and commit it.
Who This Is Right For
The transfer engagement model is not for everyone. It works best for a specific type of founder and team.
Good fit:
- You have a bottleneck on content, SEO, or outbound that hiring has not fixed
- You want to own the system, not rent access to a vendor's platform
- Your team has a codebase, uses git, and is comfortable reading diffs
- You have tried "using more AI" and hit the coordination wall, not the tooling wall
Not a fit:
- You want someone else to run marketing indefinitely (that is our Operate tier)
- You do not have a codebase or git workflow
- You need product engineering, not marketing operations (that is our Build tier)
The transfer model is for founders who want to learn how the system works so they can run it themselves. It is teaching, not outsourcing.
Frequently Asked Questions
What happens if something breaks after the handoff?
The optional $1,500/month support tier covers exactly this. We monitor agent output, answer questions, and fix prompt issues. Most founders use support for the first 2 to 3 months, then drop it once the system is routine.
Can I add more agents after the transfer?
Yes. The documentation includes a guide for adding new agents to the fleet. The architecture is designed to scale. When we first ran this system against our own product, we started with 5 agents and expanded to 9 as the operation matured.
What if I want you to keep running the fleet instead?
That is our Operate tier: a monthly retainer where we manage a 4 to 6 agent fleet on your behalf. Some founders start with Transfer, realize they would rather not manage the fleet themselves, and switch to Operate. That is a fine outcome. See all three tiers on our pricing page.
Do I need technical staff to maintain the agents?
You need someone comfortable with git and markdown. The agents are configured via prompt files (plain text), not code. A non-technical founder who uses GitHub daily can manage the fleet. A founder who has never opened a terminal cannot.
How is this different from buying an AI marketing tool?
AI marketing tools give you features. The transfer engagement gives you a system. The agents coordinate through git-committed state files, a synthesizer agent reads all output daily, and the architecture is tailored to your specific bottleneck. You are not configuring someone else's product. You own the architecture itself.
What does the $10,000 to $20,000 range depend on?
Fleet size, complexity of the bottleneck, and how much custom prompt work the engagement requires. A straightforward content and SEO fleet for a founder with a clean Next.js codebase is closer to $10,000. A multi-channel operation with outbound, sales ops, and custom integrations is closer to $20,000. We scope it on the discovery call.
Ready to see if your codebase is a fit? Book a 30-minute discovery call or read how we engage to see the full methodology.