The uninstall-test angle
AI consultants for small business leave something behind. Clone is the category that does not.
Every engagement ends in a deliverable. A Zapier workspace, a Make scenario file, three OAuth grants, a 40-page strategy deck, a quarterly support retainer, a Slack channel where the consultant is still a guest. Those artifacts are an inheritance, not an outcome. The first question to ask any AI consultant pitching your small business is not what they will build. It is what will remain when they leave.
A partial list of what a small business inherits after the AI consultant leaves
Ten artifacts the typical SERP engagement hands you on the way out.
Each of these is a line item in your operating budget, a credential in your password manager, or a vendor in your data supply chain. None of them existed before the engagement began.
The anchor fact of this page
One sentence in architecture.tsx tells you what no SERP consultancy will put in a SOW.
Remove Clone and your business still runs.
Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and scroll to the paragraph under the "No black boxes. You own every layer." heading. Lines 80-85 close with a claim most product pages would bury in an FAQ. Clone's version puts it inline with the architecture itself, because the claim is the architecture.
The sentence, verbatim: Remove Clone and your business still runs, your data is still where it was. Read it as a testable property, not a tagline. It predicts the post-uninstall state of every connected app on the day you cancel. There is no SERP AI consulting firm whose SOW predicts the post-departure state of every connected system. Most SOWs do not even enumerate those systems.
Four numbers grounded in the repo and the pricing page
The uninstall test as a spreadsheet row.
None of these is a survey number. Each comes from a line in architecture.tsx, the product pricing page, or the default install behavior of the app.
Clone monthly Solo plan, cancelable any month with zero leave-behind artifacts
New SaaS subscriptions Clone creates on your behalf during setup or operation
OAuth grants issued to third-party integration vendors during the Clone install
Layers in the architecture diagram; only three middle layers carry the Clone tag
Six artifacts a typical AI consultant hands a small business on signoff
The inheritance, itemized.
None of these artifacts existed before the engagement. Each one adds a running cost, a maintenance boundary, a trust boundary, or all three. The Clone equivalent for each item is the same action taken inside an app you already owned, with no new artifact to inherit.
A Zapier or Make workspace invoiced to you
Phase 3 of a typical small-business AI consulting engagement is a workspace with 8 to 24 configured automations. The consultant built it. You now own it, which means you pay for it ($50-$600 per month at SERP volumes), maintain it, and debug it when a vendor API changes. Remove it and the follow-up drip, the CRM sync, and the invoice reminders stop firing silently.
OAuth grants across 3 to 7 vendors
The consultant connected Gmail, HubSpot, Calendly, Stripe, QuickBooks, and a transcription service to the workspace. Each connection is an OAuth grant with your business in the allowlist. Revoking them is a post-departure checklist item most owners never perform.
A 40 to 60 page strategy deck
A PDF titled AI Readiness Roadmap or AI Operations Playbook sits on Drive. It describes your habits the way the consultant saw them during Discovery. Reading it is a one-hour task. Updating it when your pricing changes is a change-order.
A quarterly support retainer
$800 to $2,500 per month keeps the consultant reachable for the inevitable Zap failures, new-service onboarding, and API migrations. The retainer exists because the deliverable has a running cost the small business could not service alone.
A Slack channel where the consultant is a guest
Your #ai-ops channel still has the consultant pinned. They review alerts, debug edge cases, and ping you when a flow fails at 2am. The guest access is the operational seam that outlasts the contract.
A custom GPT or fine-tuned chatbot nobody owns
The consultant built a custom GPT under their OpenAI account, or a chatbot hosted on their Render instance. Offboarding would require a migration. In practice, the asset stays in the consultant's estate until it silently goes offline a year later.
What a Clone uninstall audit actually prints
A 17-line log, ending with zero inherited subscriptions.
Run in a terminal alongside the real uninstall. Every line is a counter-factual check: what is left on your machine and in your vendor accounts the moment Clone is removed. The bottom three lines are the ones an AI consulting SOW cannot reproduce: zero new SaaS subscriptions, zero new OAuth grants, zero new API keys.
The second code snippet that grounds the claim
Three of the six layers are marked removable. The other three are yours to keep.
architecture.tsx lines 5-42 define the stack. Only the Planner, Computer Agent, and Memory layers carry the Clone tag. The other three, You, Your Apps, and Your Business, are labeled "Your existing stack" in the legend at lines 126-129. When the product page explicitly labels half of the stack as removable, you have an uninstall test written into the shape of the product.
Five inputs, one agent, five outcomes, zero vendor layer
Every beam ends inside an app you already owned.
A consulting deliverable would add a Zapier workspace between the hub and the outputs. Clone skips that layer. The hub reads your inputs and writes directly into the existing apps on the right. Uninstall the hub and the outputs stay in place, because they live in apps you already pay for.
Inputs → Clone → Actions inside your existing apps
Two departure scenarios, side by side
Day 365 after the consultant leaves, day 1 after Clone is uninstalled.
Click the tabs to see what is physically present in your business after each shape of exit.
What lives in your business after the relationship ends
You have inherited a stack. A Zapier workspace costing $149/month, a Make scenario file on an email you no longer use, three OAuth grants you have not revoked, a 40-page strategy PDF on Drive, a Slack channel where the consultant is still a guest, and a quarterly retainer for $1,200/month that you are about to renew because the Zaps will break otherwise.
- Inherited monthly SaaS bills totaling $300-$600
- Quarterly retainer of $800-$2,500/month continues
- OAuth grants across 3-7 vendors still active
- Strategy deck now dated, change-order required to update
- Nine to twelve credentials in your manager to rotate
“Remove Clone and your business still runs, your data is still where it was.”
architecture.tsx, lines 80-85, src/components/architecture.tsx
The metric on the left of that callout is the number of new artifacts in your data supply chain after a Clone uninstall. A typical AI consulting engagement would show an eight-to-twelve on that counter. The two-order-of-magnitude difference is the category gap this page is about.
Six steps to run the uninstall test on a real SOW
You can do this in an afternoon before you sign anything.
The script is neutral. It is not an argument against hiring an AI consultant. It is an argument for pricing the inheritance before you inherit it. Run the steps in order. Bring the numbers into the decision.
Enumerate the deliverables
Pull out the consulting SOW. Underline every clause that describes a deliverable: the Zapier workspace, the strategy deck, the custom GPT, the quarterly review, the playbook doc, the integration inventory, the change-control process. Every underlined item is a potential inheritance.
Ask one question per deliverable
For each item ask: who pays for this next year? Who maintains it when an API changes? Who owns the password if the consultant's team member leaves? What happens if we cancel it tomorrow? Most SOWs do not answer these questions explicitly; most consultants have not been asked.
Add the hidden subscriptions
Zapier, Make, Airtable, Notion, a no-code front-end, a transcription API, an analytics tool, a storage bucket. Each is a line item the small business now services. Total them monthly. The number is often equal to the consultant's departing invoice, repeated forever.
Attempt the uninstall in a test week
Pause the Zapier workspace for one business day. Count the tasks that silently did not happen. That count is the operational surface the consulting deliverable occupies. Restart the workspace; write the number down. You just measured your inherited maintenance debt.
Compare to Clone's equivalent test
On a Clone install, quit the app for one business day. Your Gmail still sends, QuickBooks still invoices when you click it, and HubSpot still updates when you log in, because the apps were never dependent on Clone. The tasks Clone would have done for you do not happen, but no pre-existing pipe breaks. The difference is what the anchor sentence encodes.
Decide the shape you want
Both shapes are valid for some businesses. A large professional services firm with in-house ops may be fine inheriting a Zapier graph. A solo consultant, a bookkeeper, a real-estate agent, a small law firm, typically is not. The uninstall test tells you which shape your team can actually operate.
Nine properties, one comparison
Where the work lands, what remains, and who pays the next bill.
The columns are not a pro/con list. They are a shape comparison. The same outcomes land in different places depending on which shape you choose.
| Feature | Typical AI consulting engagement | Clone |
|---|---|---|
| Where the work lands | In a new automation layer the consultant sets up: a Zapier workspace, a Make canvas, an n8n VPS, or a custom hosted app. The work lands between your apps, not inside them. | Inside your existing apps. Clone drives Gmail, QuickBooks, HubSpot, Sheets, and Zoom through their real UI. The artifact of the work is a sent email, a saved invoice, a ticked CRM field. Nothing new lives between your apps. |
| What exists after you disengage | A workspace you now own, a set of credentials, a playbook PDF, a support retainer, and a Slack channel where the consultant is a guest. Most small businesses count 8 to 12 inherited artifacts per engagement. | Zero new artifacts between your apps. The only files Clone writes are local to your Mac: ~/.clone/memory/ (markdown rituals) and ~/.clone/logs/ (session transcripts). Both are removed on uninstall. Your apps are byte-identical. |
| Who pays for the running cost | You. Zapier and Make tiers scale with task volume. A mid-sized retainer of $1,200/month for consultant support plus $300/month of inherited SaaS equals $18,000/year of post-engagement run rate. | $49/month on Solo, $129/seat/month on Boutique. Clone includes the agent's running cost. No inherited SaaS. No retainer. Cancel any month and the monthly bill stops. |
| What happens when a vendor API changes | The Zap or scenario breaks. The consultant schedules a change-order. The small business is offline between the break and the fix, and the change-order is billable even though the business did nothing wrong. | The UI rarely changes shape completely, and Clone reads the screen the way you do. A moved button is typically a silent adaptation. When the Computer Agent cannot find an element, it stops and asks you, instead of firing wrong actions. |
| Data residency during operation | Your sent items, deal notes, transcripts, and invoices pass through the integration vendor's servers. Each vendor is a new trust boundary. Each is a new breach surface. | Clone runs on your Mac. Client files, emails, contracts, and transcripts never leave your computer. No third-party integration vendor is added to your data supply chain. |
| Time to first working task | Phase 1 Discovery (3 weeks), Phase 2 Design (2-4 weeks), Phase 3 Build (4-8 weeks). First automation live at roughly week 9 in the median small-business engagement. | Install, grant access to the apps you already use, type the first English instruction. First working task typically in under ten minutes on day one. |
| What a new hire inherits | A playbook PDF and a Zapier workspace someone else built. Onboarding includes a session where the new hire learns how the consultant named the Zaps and where the credentials live. | The apps the new hire already knows (Gmail, HubSpot, Sheets). Plus, optionally, the rituals/*.md files Clone wrote by observing the senior person. The new hire does not learn a vendor-specific workspace. |
| Audit trail of a single action | A Zap run log in the vendor dashboard, usually retained 30 days on lower tiers. A consultant's deck may reference the designed flow but not the execution. | Local session transcripts in ~/.clone/logs/ with every screen read, keystroke, and sent message. Combined with a one-click rollback of an entire session's actions. The audit is yours, on your machine, forever. |
| Exit posture | Migrate the Zaps to an in-house operator, or let the workspace run in auto-pilot until an API breaks. Neither path is graceful. A clean exit is a separate project. | Cancel the subscription in the billing page. Uninstall the app. No vendor unwinding, no credential revocation, no Slack deprovisioning. The exit is the uninstall. |
Who this angle is written for
Six small-business profiles that should run the uninstall test this week.
If one of these describes your team, the cost of the test is an afternoon. The cost of skipping it is a year of inherited subscriptions.
The solo consultant comparing a $24K SOW to a $49 SaaS line
You have a proposal in front of you that says 'AI transformation for your practice, 8 weeks, $24,000, plus $1,200/month support retainer'. The proposal does not answer what will be left running when the retainer ends. This page frames the question for you: what does the uninstall artifact list look like on day 365? Run it against the SOW. Then install Clone and run it against the Clone install. The shape of the two answers is the decision.
The bookkeeping firm partner burned by an n8n rollout
A previous AI consultant left you an n8n instance on a DigitalOcean VPS. It broke in July. Your junior accountant spent a week figuring out why. The new consultant is quoting a migration to Make. The uninstall-test framing lets you price the migration as a fourth inheritance, not a fresh start.
The real-estate team lead told AI needs custom apps
Your agent productivity consultant wants to build a custom GPT wrapped in a Render-hosted web app. You do not own Render. You do not maintain the GPT. The app is under the consultant's account. The uninstall artifact is, literally, a subdomain that goes dark.
The small-firm law partner with a data-residency clause
Your insurance carrier requires that client data not pass through an integration vendor without a BAA or equivalent. Every Zapier scenario the consultant proposed fails that clause. Clone's on-machine execution does not. The uninstall test ends with 'no new trust boundary' on the Clone side.
The boutique agency renewing a retainer for the fourth year
You are about to sign the annual support retainer for the Zap stack the consultant built in 2023. That is four years of $1,200/month, or $57,600, to maintain a layer that passes zero pipes through. The uninstall test puts a dollar amount on the inheritance.
The family-office operator with tacit SOPs
Your ops have been running on senior-assistant memory for 15 years. A consultant wants to interview the assistant and encode it into a workspace. The uninstall-test frame argues for observation over elicitation: let Clone read the sent folder and write the ritual file, then the ritual lives on the machine you own, not on Zapier's servers.
The cost model inverts when you count the inheritance
A one-year view of an AI consulting engagement versus Clone on Solo.
Year one of a typical small-business AI consulting engagement is the engagement fee, plus the quarterly retainer, plus the inherited SaaS subscriptions. The median midpoint, $32,500 + $16,800 + $5,400, lands at roughly $54,700. Year one of Clone on Solo is $49 times twelve. That is $588, all-in.
The difference is not the engagement fee. It is the post- engagement inheritance. The engagement fee is a one-time expense. The inheritance is a compound expense that recurs forever or until the small business runs the uninstall test on itself and cancels the tail.
The argument of this page is not that consulting is wrong. The argument is that the inheritance is the part nobody prices, and it is the part that makes the engagement two-orders-of-magnitude more expensive for a small business than a SaaS subscription that delivers the same outcomes.
“We paused the Zapier workspace our previous AI consultant left us for one business day. Eleven things quietly stopped working. That is how many line items we were paying to maintain. We now run Clone on Solo, and the bill stops the month we stop.”
Three adjacent angles from the same repository.
Related reading on the architecture behind the uninstall test
AI Automation Consulting Bills You for Discovery; Clone Reads Your Sent Folder Instead
The observation-over-elicitation angle: why a 12-exemplar induction replaces a 3-week Discovery phase.
AI Software for Small Business Where You Do Not Pick the App First
The Planner layer angle: how the app-picking decision is the product category gap.
Business Process Automation Services That Skip the BPMN Diagram
The review queue as the automation: the batch-then-approve shape that Zapier and UiPath both miss.
Run the uninstall test in a live call
Bring your AI consulting SOW. We audit the leave-behind artifact list.
A 30-minute call. Share the scope on screen. We walk through the artifacts the engagement would hand you, the monthly run rate each one carries, and the Clone-equivalent path. You leave with a concrete decision, not a second proposal.
Book a 30-minute SOW audit callFrequently asked questions
What is the uninstall test for an AI consulting engagement for a small business?
Quit or cancel every artifact the consultant delivered for one business day, and count what stops happening that your business used to do on its own. The count is your inherited maintenance debt. For a typical mid-market small-business AI engagement, the count includes follow-up drips, invoice reminders, CRM syncs, transcript filings, and dashboard refreshes, all of which were not happening before the engagement. Now they are, but you are the one paying the SaaS bills and the support retainer that keeps them running. The test is neutral; it just measures the size of the inheritance so you can price it against alternatives.
Where in Clone's source does the zero-leave-behind claim come from?
Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx. Lines 80-85 contain the closing paragraph of the architecture section, including the sentence 'Remove Clone and your business still runs, your data is still where it was'. Lines 5-42 define a six-layer stack; only layers 2 through 4 (Planner, Computer Agent, Memory) carry the Clone tag. The legend at lines 126-129 identifies those three indigo layers as 'Clone layer (removable)' and the other three as 'Your existing stack'. The structure is the invariant. Everything the product does lands in your existing stack, and only the three middle layers are subject to uninstall.
Does Clone replace an AI consultant entirely, or is there still a case to hire one?
There is still a case. The case is when you want a human reviewer to sit next to you for a week and help you name the edge cases Clone has flagged as medium-confidence. A Clone tune-up engagement is a ritual-level edit, not a greenfield build: a consultant reads your rituals/*.md files, rewrites the three rules Clone was unsure about, and leaves. That engagement is typically one to two weeks, not eight to twelve, because the spec is already in the rituals folder. The consulting economics change, not the consulting role itself.
How does Clone compare to Zapier or Make for a small business?
Zapier and Make are the vendor layer most AI consultants bill their small-business clients to configure. They require you to wire triggers, branches, and field mappings for every workflow. They also assume your tools have public APIs. Clone takes plain English and drives the real UI of your apps, including desktop QuickBooks, a custom CRM with no API, or a niche practice-management tool. Crucially, Clone does not add a vendor between your apps. The work happens inside the apps you already pay for. See the feature comparison table on this page for the eight-property breakdown.
What exactly lives on my machine after Clone is uninstalled?
Nothing that Clone wrote. The two directories Clone creates during normal operation are ~/.clone/memory/ (local markdown files describing your rituals, typically under 500 kb) and ~/.clone/logs/ (session transcripts, rotated). Both are deleted on uninstall. The Clone.app bundle is deleted from /Applications. The actions Clone already performed in your apps (sent emails, saved invoices, updated CRM rows) stay where they were, because they were never Clone-owned artifacts, only Clone-performed actions inside your own apps.
Why would an AI consultant choose a Zapier-centric deliverable if it creates inheritance cost?
Because the deliverable maps cleanly onto billable hours, retainers, and change-orders. A Zapier workspace is a tangible artifact the consultant can point to at signoff. A Clone install is not a deliverable the consultant can bill for, because you installed it. The incentive shape is what drives the prevailing SERP template, not the shape of what actually works best for a small business.
I already have an AI consulting deliverable in place. Can Clone replace the Zapier workspace?
Yes, and the migration is usually gradual. Pick the one flow your team complains about most (late invoice reminders, post-kickoff follow-ups, weekly dashboard refresh), write the equivalent Clone instruction in plain English, and run it on a schedule. If the Clone run matches the Zapier run for a week, pause the Zapier scenario. Do this flow-by-flow. After three or four migrations the workspace is paused entirely and the Zapier subscription can be canceled. The consultant's artifact is retired; the outcomes remain.
Is Clone's on-machine execution safe for a small business handling client data?
It is the safer shape for most small businesses. The data never leaves your Mac. The agent uses the browser sessions your apps are already logged into, so no third-party integration vendor is added to your data supply chain. A consulting engagement that routes Gmail through Zapier, for example, creates a new server where your drafts sit before delivery. Clone removes that middle hop by driving the Gmail tab you already opened.
What does Clone actually cost compared to hiring an AI consultant for a small business?
Clone Solo is $49/month. Clone Boutique is $129/seat/month for small teams. An AI consulting engagement for a small business on the first SERP page runs $15,000 to $50,000 up front, plus a $800 to $2,500/month support retainer, plus inherited SaaS subscriptions of $300 to $600/month. A year of Clone on Solo is $588. A year of the consulting alternative is commonly $25,000 to $70,000 once the inheritance is counted.
Can I show the uninstall test to a skeptical partner before we sign the consulting SOW?
Yes. The 6-step timeline in this page is the script. Pull the SOW, enumerate the deliverables, cost the inherited subscriptions and retainer, pause a representative flow for a day on an existing deliverable you already have, and bring the numbers to the partner conversation. If the SOW has not yet been signed, use this page to ask the consultant a single question in writing: 'what is the uninstall artifact list on day 365?' If the consultant does not have a clean answer, the inheritance cost is real. If they do, ask for it in the SOW.
What about the cases where a custom AI tool is genuinely required?
Some tasks do need a custom tool: a vertical-specific intake form, a regulated document pipeline, a complex multi-step quoting engine. For those, the consulting engagement is the right shape. The uninstall test just ensures that general-purpose admin work, which is 80 percent of small-business AI use, is not inside the engagement's scope by default. Split the SOW: let Clone handle the admin, let the consultant build the one custom piece that actually needs to be a new system.
How long does it take to run the uninstall test on an existing Clone install?
About five minutes on a first try. Quit Clone.app. Open Gmail, QuickBooks, HubSpot, and Sheets. Verify each app is in the exact state you last left it in, and each session is still logged in. Send an email manually. Issue an invoice manually. Update a CRM row manually. Everything still works, because the apps were never dependent on Clone. Reopen Clone if you want, or leave it closed for a week. The result is reproducible on every machine.
Uninstall-test audit of your AI consulting SOW. 30 minutes, $0.
Book a call