AI solutions for small business where nothing ships without your yes.

In the SERP for this keyword, 'AI solutions' reads as a category: a list of tools that small businesses can buy. In Clone's source, an AI solution is a stack with a gate. The gate is the review queue between drafted and sent work. The foundational claim is at src/components/architecture.tsx lines 60-64 in the marketing site's source: 'Every action Clone takes is logged and reversible. Preview drafts before they send. See every file it touched. Roll back an entire morning of work with one click if you need to.' This is the fourth of four principles in the architecture file and it describes the product's default state, not a premium feature.

Five discrete steps. First, the Planner layer (architecture.tsx line 13) reads your English and picks the surface. Second, the Computer Agent (line 19) drafts the action inside the surface by reading the screen and clicking and typing the way you would. Third, the drafted action becomes a row in the review queue inside Clone. Fourth, you approve, edit, or reject the row. Fifth, on approval, the action leaves your Mac and a session log is written to ~/.clone/memory/sessions/. The gap between step two and step four is the gate the rest of the product category skips.

Zapier and Make are 'auto-agent shaped'. Once a Zap is live, its default state is to run on trigger. The task history is reviewable after the fact, but the action has already fired. Clone inverts this. The default state after an instruction is 'drafted but not sent'. Approval is a precondition for shipping, not a post-hoc audit. Also, Clone runs on your screen, not against a vendor API, so rollback happens at the surface (the QuickBooks draft is voided, the Sheets cell is restored) rather than via API calls that often cannot reach back.

Copilot and Smart Compose are 'suggestion shaped'. They propose text in a sidebar and wait for copy-paste. The gate is correct in spirit but the tool is the wrong shape: you end up doing the app-switching work yourself because the suggestion lives outside the surface where the action needs to land. Clone drafts inside the surface and queues the result, so the gate is where the work already is. Consent without tool-switching.

Auto-agents optimize for throughput and treat your yes as optional. Clone optimizes for not shipping a bad action to a real client. The product's fourth principle is literally 'Always reviewable'. If a small business can afford a bad email, an auto-agent is cheaper; if one wrong invoice or one misfiled CRM record is a bigger problem than five extra minutes of approval, Clone is the correct shape.

Every session writes a session log to ~/.clone/memory/sessions/ with the list of file paths the Computer Agent touched and a snapshot of the pre-action state for each path. 'clone rollback <session-id>' reverses those touches at the surface. A QuickBooks draft invoice is voided. A modified Sheets range is restored from the pre-action snapshot. A saved-then-committed Notion version is reverted to its pre-edit revision. A draft email held in the queue is deleted. For actions that cannot be un-sent (an actual sent email), the session log contains the sent message ID so you can send a correction from the same surface.

After Clone observes the same shape 12 times, it composes the proposal shipped verbatim at how-it-works.tsx lines 42-58: 'Noticed a pattern in your last 12 kickoff emails... Should I apply this template going forward?' You reply 'Yes, save it' to save the pattern as a named file under ~/.clone/memory/patterns/. A 'no' discards. An edited reply ('yes but only cc my assistant above $20K') updates the proposal before saving. No generalization from your sent folder ever becomes a saved rule without a literal yes.

Throughput. If your business can tolerate occasional wrong actions and values speed above all, an auto-agent will move faster because it does not wait for you. Clone adds an approval step to every action, which is roughly five to ten minutes of batched queue-review per major ritual. The trade is less throughput, no bad sends. For a solo consultant or a small-team practice, the math tends to favor consent; for a high-volume outbound-sales floor, it may not.

You can mark a specific saved pattern as 'auto-approve' from its file in ~/.clone/memory/patterns/. That lets repetitive no-stakes actions (for example, filing a receipt into the right folder in Drive) skip the queue after the first approval. You can also unmark it at any time by editing the file. The default for every new pattern is 'queue, not send'.

Only what the Planner layer needs to interpret your sentence. The Planner calls a hosted model to read your English and pick the target app. The Computer Agent runs on your Mac, so the contents of your QuickBooks file, your Sheets template, or your client emails never leave your machine (architecture.tsx line 47: 'Runs on your machine... Client files, emails, contracts, and transcripts never leave your computer'). On Enterprise, the Planner can also run against a local model so even the sentence stays on the Mac.

Three directories under ~/.clone/memory/. Sessions (~/.clone/memory/sessions/) have a markdown log per run with timestamps, touched file paths, and before-state snapshots. Patterns (~/.clone/memory/patterns/) have one markdown file per saved template, human-readable. Rituals (~/.clone/memory/rituals/) have one markdown file per workflow, naming which tool you use per client or per task. You can open all of this in a text editor, commit it to git, or move it between machines as a zip. No vendor database, no export dance.

Most were built API-first, where the default cost of drafting without sending is a second runtime: queue, storage, UI. That cost is only worth paying if consent is a first principle. Clone was built on a Computer Agent that reads the screen, so drafting without sending was the native default from day one: the Computer Agent can stop one click before the Send button. The product shape makes the gate free; the rest of the category would have to rebuild around it.