Most agencies are structurally incentivized to keep you needing them. Not because they are malicious. Because their business model depends on your continued reliance. Here is how to tell the difference.
There is a structural problem with most agency relationships that nobody talks about honestly.
The agency makes money as long as you need them. The moment you stop needing them, they stop making money. This is not a character flaw. It is arithmetic. And it shapes, whether consciously or not, how they work with you.
The deliverable that requires ongoing interpretation. The system that only they fully understand. The strategy that needs regular refinement from the team that built it. The retainer that covers "ongoing support" for something that should have been done once and handed over.
None of this is necessarily deliberate. But it is the natural outcome of an incentive structure where your independence is their revenue loss.
The clearest sign of a dependency-building engagement is documentation. Or the absence of it.
At the end of a proper engagement, you should have everything you need to run the systems that were built without the people who built them. SOPs for every process. Documented configuration for every tool. Training for every team member who touches the system. A clear picture of what each component does and who owns it.
What you usually get instead is a login to a platform, a brief handover call, and a retainer proposal for ongoing management.
The second sign is opaque tooling. Agencies often recommend tools that they know well and that create dependency. Through proprietary platforms, through complex integrations that only they understand, or through tools that require ongoing specialist configuration. The right tool is the one that solves your problem and that your team can own. The agency-preferred tool is often the one that requires the agency.
The third sign is strategy without execution. A deck showing the opportunity. A roadmap showing what could be done. A proposal for the next phase. But week over week, the actual state of your operations does not change.
The alternative is not a perfect service company that has no commercial interests. Commercial interests are fine. The question is what those interests are aligned to.
An operator-built company's interest is in your outcome, because your outcome is what generates referrals, case studies, and reputation. The best advertising for an operator service is a client who got results and talks about it. That only happens if the results are real and the client is genuinely better off.
This creates a different incentive structure. The work is oriented toward making you independent, not dependent. The goal is a business that runs without ongoing involvement. Because that is the outcome that generates the next engagement from the next client.
Before you sign anything with any service company, ask these four questions:
What does the end of this engagement look like? A good answer is specific: trained team, documented systems, clean handover, defined success metrics. A bad answer is vague: "ongoing partnership," "we stay involved," "we'll see how it goes."
What will you document as you go? Every system built should have documentation written during the build, not promised at the end. If the documentation is a deliverable at the end, it often never materialises. Ask to see examples from previous clients.
Who on my team will understand this when you are done? If the answer is "you'll have access to the platform," that is not an answer. There should be a named person on your team who receives training and takes ownership of each component.
What does success look like six months after the engagement ends? This is the most revealing question. An agency oriented toward retention will give a vague answer or talk about the next engagement. An operator oriented toward outcomes will describe what your business looks like running independently.
Not all retainers are bad. There is legitimate value in an ongoing operational partner who stays close to a business, helps with continuous improvement, and provides expertise that it does not make sense to hire full-time.
The distinction is whether the retainer is optional or structural.
An optional retainer is one where you could manage without it. You have the systems, the documentation, the trained team. And you choose to retain ongoing expertise because it adds value. You could exit cleanly if you needed to.
A structural retainer is one where exiting would leave you unable to operate something critical. That is not a retainer. That is dependency that was engineered into the engagement.
At Qann, the success metric for an engagement is whether you need us afterward. We build systems. We document everything. We train your team. We plan the handover before we start, not after we finish.
For some clients, that ends the engagement cleanly. For others, it leads to an ongoing relationship where we work on the next set of problems. Because you chose it, not because we built something that requires it.
We also take equity and revenue share arrangements in select projects, which aligns our interests to your outcomes over years, not months. When we have skin in the game, the incentive to build something that holds is direct and obvious.
The right service company makes you stronger and then gets out of the way. If your current one is not doing that, it is worth asking why.
— Qann Commerce · qann.co