What Is 'Cancel Or Clone'? The Framework In Plain English
Cancel or Clone is a habit, not a tool. Every time a software renewal, a vendor invoice, or an open hire comes up, you stop and ask three questions, and the answers give you one of three verdicts. KEEP it, because it does a job nothing cheaper does. SWAP it for an AI-native tool that does the same job for a fraction of the price. Or CLONE it, meaning an agent rebuilds the part you actually use from your own data or the vendor's API, and you own the result. The framework exists because the default, auto-renew and move on, is now the most expensive choice on the menu.
Where it came from
This did not start as a framework. It started as a pattern across five Optimus Mastermind calls between late August and late September 2026, where the same topic came up every single week without anyone planning it: members were questioning every software renewal, and their software bills were dropping sharply as a result.
One agency owner priced an AI-native replacement for a legacy tool at about a tenth of the renewal, then priced rolling their own with an agent at about a tenth of that again. One business owner had taken a software bill of roughly $6,000 a month down to about zero over two years by chipping away at it, one renewal at a time. A tax firm dropped a paid agent tool on cost, built the workflow themselves, and took a week-long review process down to minutes with a human still approving the output.
None of them were following a method. They had all independently stopped auto-renewing and started asking the same questions. Cancel or Clone is those questions written down so you can run them on purpose.
The three questions
Run these on every renewal and every open role, in order.
- Is there an AI-native version? Most legacy software has a competitor built after the models got good, and it is usually priced like a new entrant rather than an incumbent. In the mastermind those came in around a tenth of the legacy renewal. If one exists and does the job, you have a SWAP candidate.
- Is the data or API available so an agent can roll our own? If you can export your data, or the vendor exposes an API, an agent can rebuild the part of the tool you actually use. Not the whole product. The two features your team opens every day. That is a CLONE candidate, and in the mastermind it priced at about a tenth of the AI-native option.
- Compared to what? This is the question that changes the conversation. Every invoice is a hire you are not making, and every hire is an invoice you could be paying instead. "Who are you not hiring because of that?" turns a line item into a staffing decision, which is the level the owner should be deciding at.
The three verdicts
| Verdict | When | What happens |
|---|---|---|
| KEEP | It does a job nothing cheaper does, or moving is riskier than the invoice | Renew, on purpose, with a date to ask again |
| SWAP | An AI-native tool does the same job for about a tenth | Migrate, cancel the old renewal |
| CLONE | The data or API is open and an agent can run the part you use | Build the smallest version, run it alongside, then cancel |
Notice that KEEP is a real verdict. The framework is not an instruction to cancel everything. It is an instruction to decide everything. A tool you have consciously kept, with a reason written down and a date to revisit, is in a completely different category from a tool that renewed because nobody looked.
Why it applies to hires too
The name says software, but the third question drags people into it, and it should. For a $5M to $50M business the biggest line items are not SaaS. They are roles. And a surprising number of roles are, when you look closely, a person running a workflow that a vendor used to sell as software and an agent can now run from your data.
Be careful with the framing here. Cancel or Clone applies to roles and tasks, not to the people in them. The tax firm did not fire its reviewers. It cloned the grunt work of the review and kept the humans on approval, which is exactly where you want expensive judgment to sit. Human in the loop is a design rule of the framework, not an exception to it.
What the framework is not
It is not a one-time project. You do not audit the stack once and go back to auto-renew. Every renewal, every time. The habit is the product.
It is not an argument that building is always cheaper. The first version of everything is rough. The framework asks you to score, pick the smallest clone, and iterate. Not to replace something critical on day one.
It is not anti-vendor. It is anti-unexamined. The tools that hold your data hostage have the biggest gap between what they charge and what they do, and that gap is where the opportunity is. Vendors that earn a KEEP have nothing to fear from it.
How to actually run it
Start with the next renewal on your calendar, not with the whole stack. Run the three questions on that one invoice, write down the verdict and the reason, and act on it. Then do the next one. If you want to do the whole list at once, how to audit your SaaS stack for Cancel or Clone walks through building the renewal list and scoring it with an agent.
When you get to the CLONE verdicts, not every tool is a good first candidate. Which tools are actually worth replacing with agents covers how to pick the ones where the clone will hold up. And before you cancel anything, read the seven mistakes that blow up your operations, because the failure modes are predictable and all of them are avoidable.
FAQ
Does Cancel or Clone mean I should cancel all my software?
No. It means you should never auto-renew. Plenty of tools earn a KEEP verdict because they do a job nothing cheaper does, or because the risk of moving is bigger than the invoice. The framework is about asking the question every time, not about a predetermined answer.
What is the difference between SWAP and CLONE?
SWAP means replacing the tool with a newer AI-native product that does the same job for less. CLONE means having an agent rebuild the part of the tool you actually use, from your own data or the vendor's API, so you own it. SWAP is faster and lower risk. CLONE is cheaper over time and gives you control.
Does the framework apply to people as well as software?
Yes, with care. The third question, compared to what, is explicitly about staffing: every invoice is a hire you are not making, and every open role is a workflow that might be cloned instead. It applies to roles and tasks, not to the people in them. The goal is to put humans on judgment and approval and agents on the grunt work.
Where do I start?
With the next renewal on your calendar. Run the three questions on that one invoice, write down a verdict, and act on it. The free scorecard and the agent prompt that comes with it will run the same audit across your whole renewal list once you have done one by hand.