Here's something most agencies will never tell you: their business model depends on you staying.
Monthly retainers. Ongoing management fees. "Strategic advisory" contracts that never end. The incentive structure is simple, the longer you need them, the more they earn. So they build systems that require their involvement, use proprietary tools that only they understand, and keep just enough knowledge in their heads that walking away feels risky.
We do the opposite. Every That Works engagement ends with full ownership transfer. The systems, the playbooks, the automations, the data, the documentation, all of it becomes yours. We leave, and everything keeps running.
This isn't altruism. It's strategy. And it makes us better at what we do.
The Problem With Dependency
The agency dependency model is broken for everyone involved, even the agency.
For the Client
When your marketing infrastructure lives inside an agency's accounts, managed by their team, documented in their systems, you're hostage. You can't change agencies without rebuilding everything. You can't bring capabilities in-house without a painful knowledge transfer. You can't even evaluate whether the agency is doing good work, because you don't fully understand what they've built.
We've taken over from agencies where the client had been paying $15,000/month for two years and couldn't explain what they were getting. The agency ran campaigns, sent reports, and joined monthly calls. But the client had no idea how the systems worked, what data was being used, or why certain decisions were being made.
That's not a partnership. That's a subscription to someone else's expertise with no equity building in your own.
For the Agency
Dependency creates perverse incentives. When your revenue depends on ongoing involvement, you're incentivised to build complexity, not simplicity. To create systems that need you, not systems that run independently. To gatekeep knowledge, not transfer it.
The best agency people, the ones who could build genuinely great systems, are constrained by a model that rewards the opposite of what clients actually need.
The Ownership Transfer Model
Here's how we work:
Phase 1: Build (Weeks 1-8)
We design and implement the system, CRM configuration, automation workflows, enrichment pipelines, outreach sequences, reporting dashboards, lead scoring models, whatever the engagement requires.
Everything is built in the client's accounts, using the client's tools, with the client's data. We never use proprietary tools or platforms that create dependency. If we use Clay, it's in the client's Clay account. If we build automations in Make, it's in the client's Make workspace.
Phase 2: Document (Weeks 6-10, overlapping with Build)
Documentation isn't an afterthought. It's a core deliverable. Every system we build comes with:
- Architecture documentation: What exists, how it connects, and why it was designed that way
- Process documentation: Step-by-step guides for every recurring task, adding new campaigns, updating lead scoring, troubleshooting common issues
- Decision logs: Why we chose specific tools, configurations, and approaches, so your team can make informed changes later
- Runbooks: What to do when things break, including common failure modes and their fixes
This documentation is written for the person who will own the system after we leave, not for us. It assumes no prior context and explains the "why" as much as the "how."
Phase 3: Train (Weeks 8-12)
We train the client's team to own and operate everything we've built. This isn't a two-hour walkthrough. It's structured training:
- System overview sessions: understanding the full architecture
- Hands-on workshops: building campaigns, modifying workflows, interpreting reports
- Shadowed operation: the client's team runs the system while we observe and coach
- Solo operation with support: the team operates independently with us available for questions
By the end of training, the client's team should be able to run, modify, and troubleshoot the system without calling us.
Phase 4: Handover and Exit (Week 12)
We formally hand over everything:
- All credentials and access (verified and documented)
- All documentation (reviewed and approved by the client's team)
- A "90-day roadmap" of recommended improvements and optimisations they can make independently
And then we leave.
Why This Makes Us Better
You might think this model limits our revenue. In a narrow sense, it does, we don't earn ongoing retainer income. But it makes us better in ways that more than compensate:
It Forces Quality
When you know your client will be living with your work after you leave, maintaining it, modifying it, troubleshooting it, you build differently. You build for clarity, not cleverness. You build for maintainability, not impressive complexity. You document properly because someone else will need to understand it.
Agencies that manage their own systems can get away with duct tape and workarounds. We can't. Everything we build must be clean enough for someone else to own.
It Forces Honesty
We can't hide behind jargon or complexity. If a system doesn't work well, the client will discover it within weeks of our departure. There's nowhere to hide. This keeps us honest about what's working, what isn't, and what trade-offs we're making.
It Generates Referrals
Clients who own their systems and get genuine results become our best marketing channel. They tell other founders "That Works built our entire GTM system, trained our team, and left, and it's been running for six months without issues." That story is more powerful than any case study we could write.
It Attracts Better People
The best operators want to build things that work, not manage retainers. Our model attracts people who take pride in craftsmanship, in building systems so good that they don't need ongoing babysitting.
The Question We Always Get
"But what if we need you again?"
Then call us. We offer ad-hoc support for alumni clients. Need help with a new campaign type? A system upgrade? A new hire who needs training? We're available.
But the key word is "need." You call us because you have a new challenge, not because the old system stopped working. There's a fundamental difference between choosing to engage an expert and being forced to because your systems don't work without them.
The Bottom Line
Dependency isn't a business model. It's a trap, for clients and agencies alike. The best work happens when both parties know the engagement will end, because it forces everyone to focus on what matters: building something that lasts.
We hand everything over because it's the right thing to do. But we also hand it over because it makes the work better, the relationships stronger, and the results more durable.
Build it right. Document it well. Train the team. Walk away.
That's how you build something that works.