The question Mapi asked on our first call
Mapi from The Joy of Impact asked me a real question. She said the idea was great, but "no se si tu seas un modelo de negocio porque en este momento cualquier persona puede hacer cualquiera de esas cosas by themselves." She was right to ask. If everything I install is yours, why would you keep paying me?
The honest answer is that the retainer continues only because new workflows keep emerging and you want me to build the Skills for them. Not access. Output.
How most AI vendors solve the lock-in problem
They build the system on their platform. They hold the prompts, the data structures, the integration keys. The minute you cancel, the value disappears. You spend a year embedding the tool into your workflows, then you discover the switching cost is the moat.
Pieter at NEXT Legal told me about exactly this pattern: "you spent money on a tool two years ago, nobody used it, and that still stings." Adoption failed and the buyer was still tied to the contract. I work the opposite way.
What lives in your accounts
Every Skill I build for you sits in your Claude account, in your Drive, in your Cowork project. The CLAUDE.md file, which is the brain that tells Claude how your business works, lives in your folder. Code I write goes into your repository. Automations run on your accounts at Vercel, Supabase, or wherever the data lives.
I do not host anything for you. I do not put your logic behind a login page that I control. See what a Skill plus CLAUDE.md actually contains for the deeper architectural picture.
Why the retainer continues anyway
The retainer makes sense for a different reason. As your business changes, new workflows appear. A new client type requires a new proposal template. A new reporting requirement means a new automation. The Skills file gets richer over time, and most of that work is technical enough that it is faster for you to call me than to learn it yourself. That is what you pay for monthly.
This is also how the retainer is justified by output, not access. If month three has the same numbers as month two with no new shipped work, the retainer drops.
The contract that reflects this
Month-to-month, no annual lock, with 30-day notice. If you cancel, I send you a clean handoff document covering every Skill, every file, every account.
Frangela got this exact handoff structure even at her $150 per month tier. So did Sami at Almaga. The contract has to mean the same thing at $150 a month as it does at $10,000 a month. Anything else is a tell.
A real test of no-lock-in
A year after we stop working together, can your team still run the system without you needing to call me? If the answer is no, I built it wrong. The goal is not dependency. The goal is a working system that survives me. The training side of that is how I train your team to maintain the system.
This is also why the newer Anthropic models reinforce the approach instead of threatening it. The operating file under the model becomes the durable asset. The model gets smarter every release. The Skills file is the moat.