Business process automation consultants hand you a runbook. Clone ships a cron entry.

Typically: a current-state process map (BPMN 2.0 swimlane), a future-state design document, a vendor-selection memo, an implementation runbook, and a training session. The runbook is the line item that actually changes your Monday. It is a 30-80 page PDF or Confluence page that walks a human operator through each procedure step with screenshots. The other deliverables describe the system; the runbook is the interface the human uses to execute it. Clone's equivalent deliverable is a ritual markdown file plus a cron entry, and the cron replaces the human at run time.

Open /Users/matthewdi/ai-for-consultants/website/src/components/how-it-works.tsx and scroll to lines 60-75. The step is titled 'It works while you don't' and ships with a hardcoded Monday 08:00am schedule listing five actions: pulling last week's billable hours from Timely, generating six invoices in QuickBooks, sending them to clients via email, logging outreach in HubSpot, and drafting the Friday retro in Notion. The closing line reads '4.2 hours of admin completed while you were asleep.' The significance is cross-tool: one cron entry drives five different apps without an operator. No consulting runbook can do that, because a runbook's runtime is always a human.

Structurally they overlap: both name the procedure, the tools, the rules, and the order of operations. The difference is the consumer. A runbook PDF is consumed by a human at Monday 08:00; they read page 12, click in QuickBooks, and move on. A Clone ritual file is consumed by the Planner layer (architecture.tsx line 14) at cron tick; the Planner hands specific actions to the Computer Agent, which drives the screen. Same spec, different runtime. One requires coffee and a clear head; the other requires neither.

For the common cases, no. Clone induces most rituals by observing the last 90 days of your sent folder, calendar, CRM, and time tracker (see the observation angle on /t/ai-automation-consulting). For edge cases, a consultant can be useful: a new service line, an unusual compliance regime, a complicated multi-entity retainer structure. The engagement in that case is typically one week, because the consultant edits ritual files, not a full SOW. The role shifts from 'runbook author' to 'edge-case editor'.

Correct, and that is deliberate. A swimlane diagram is a visualization of a process aimed at a human stakeholder. It has no runtime consumer. If your partner or your compliance team wants a swimlane, Clone can render one on demand from any ritual file, because the file contains the same information (tools, steps, rules) a BPMN diagram encodes. The primary artifact is the ritual; the diagram is a view of it. The consulting category inverts this: the diagram is the primary artifact, the runtime is an afterthought encoded in the runbook.

The Computer Agent fails the QuickBooks step, the Action Log records the failure, the Planner halts the current ritual, and the remaining steps (Gmail, HubSpot, Notion) route to the morning review queue. Clone does not retry blindly or skip ahead. When you open the laptop at 09:00 you see three green steps, one red, and a prompt to re-run the QuickBooks leg when the outage clears. A consulting runbook handles this with a page-47 exception callout that depends on the operator noticing the failure; Clone's failure mode is explicit and queued.

Solo ($49/mo) gives you personal rituals and a personal schedule. Boutique ($129/seat/mo) adds firm-level rituals: one monday-invoicing.md shared across the firm, with per-seat scheduling if a principal invoices separately from an associate. See pricing.tsx lines 28-42. The consulting equivalent is the 'change management' workstream on a BPA SOW, which is typically billed as a separate line item and teaches each new hire the runbook. Clone's equivalent is a new seat reading the shared ritual folder on first login.

Yes, because the Computer Agent (architecture.tsx line 19) reads the screen and clicks. It does not depend on APIs. If your Monday 08:00 ritual currently hits a custom Rails admin, a 20-year-old Access database, or a practice-management system with no public API, Clone drives it the same way you would: by clicking. A BPA consultant's usual response to the same situation is a multi-quarter migration project. Clone lets you keep the legacy app on the schedule while you decide whether to migrate at all.

Open ~/.clone/logs/2026-04-20.jsonl (or whatever the date of the run was). The file is JSON-lines, one action per line: screen reads with pixel coordinates, keystrokes, file writes, sent messages. A typical Monday run has 30-50 lines. You can grep it, pipe it to jq, or commit the logs folder to a private git repo for long-term retention. This is the evidence a compliance team typically asks for and a consultant-produced runbook does not deliver on its own.

In a BPA engagement, training is needed because the runtime of the procedure is human. Humans need to be trained to execute the steps consistently. When the runtime shifts to the Clone daemon, training shifts to 'here is how to read the review queue' and 'here is how to edit a ritual file.' Both of those fit in a 30-minute onboarding, not a multi-day training package. The savings are not in the hour rate of the trainer, they are in the number of humans who need the training in the first place.

Install Clone, grant access to your time tracker, QuickBooks (or your invoicing app), and Gmail. Type: 'every Monday at 08:00, pull last week's hours from Timely, draft invoices in QuickBooks, send them, log in HubSpot, draft the retro in Notion.' Clone writes ~/.clone/memory/rituals/monday-invoicing.md and adds the cron entry. On the next Monday you see the run happen. The whole setup is under ten minutes, which is the number on get-started.tsx line 52: 'from install to first task'.

Generic automation platforms (Zapier, Make, n8n) ship schedules too, but they require you to wire each step as a workflow and they cannot drive apps without APIs. BPA consultants produce runbooks that assume an operator; their value proposition is 'the procedure is correct for your business.' Clone fuses those: the ritual file is as specific to your business as the consultant's runbook (it was induced from your actual history), and the Computer Agent executes without APIs, on the same schedule you would otherwise pay a VA to cover. The Monday 08:00 tick is the single surface where the two categories meet and only one of them runs without a human.