What is business process automation? Answered by what you type on day 1.
Every top search result defines BPA as “technology that executes recurring business processes.” That sentence is true. It also tells you nothing about which tool to pick, because every BPA tool passes that test. The real variable is the day-1 input surface: the first thing you type or draw or record to teach the tool what your business does.
Five tools, five surfaces. Zapier is a graph. Make is a canvas. HoneyBook is a template. UiPath is a screen recording. Clone is a sentence in a file at ~/.clone/memory/rituals/, induced from your last 180 days of Gmail and Calendar in about 90 seconds.
Why the dictionary definition fails you.
Open the top five results for this query. Every one of them opens with the same sentence shape. Business process automation is the use of technology to do X so you can stop doing X. The words change; the pattern does not.
This definition is not wrong. It is just too abstract to help you pick anything. Zapier, Make, HoneyBook, UiPath, Dubsado, Pipefy, n8n, and Clone all pass this test. Every one of them is “technology that executes recurring workflows.” The sentence sells a category, not a tool.
The question a person searching this keyword actually wants answered is closer to: if I were to start today, what would I actually type, draw, or record first? The answer to that question differs by tool by a factor of ten in effort, cost, and long-term maintenance burden.
SERP definition vs. a working definition
"Business process automation is the use of technology to execute recurring tasks or processes in a business where manual effort can be replaced." Useful for a textbook. Useless for picking a tool.
- Defines BPA by its mechanism, not its interface
- Says what it replaces, not what it requires you to produce
- No mention of how you tell the automation what to do
- No mention of what artifact lives on your disk afterwards
The four parts every BPA tool has.
If you dismantle any product that legitimately calls itself business process automation, you find the same four parts. None of them is optional. A tool that only has three is a task manager or a scheduler, not BPA.
1. A recurring instruction
What the automation should do when it runs. Lives as either a visual graph, a YAML file, a stored procedure, a recorded macro, or a plain English sentence. This is the part every BPA tool picks a different shape for.
2. A clock
Something that decides when the instruction fires. A cron entry, a webhook, a calendar trigger, a manual run button. Without a clock, an instruction is just a doc.
3. A pause point
A place the instruction can wait for a human decision without abandoning the run. Clone calls this a fork line. Zapier calls it a "delay until approval." HoneyBook calls it a "client action." Not optional for real consulting work.
4. A log
Something on disk (or in a vendor dashboard) that records what actually happened. Plain text beats a dashboard row. Grep-able beats paginated. Ownable beats vendor-locked.
Every BPA tool has all four
What changes is the interface for part 1. Zapier: drag nodes. Make: draw modules. HoneyBook: pick a template. UiPath: record your screen. Clone: type an English sentence and let the observer induce it from your existing inbox.
The anchor fact: a file on your disk.
Clone picks a specific answer for the instruction surface. One plain English sentence per ritual, at the top of a markdown file under ~/.clone/memory/rituals/. The body captures the branches. The file is the answer to “what is my BPA.”
anchor fact
On day 1, the only command you run is clone observe. In about 0s it scans your last 180 days of Gmail Sent and Google Calendar, clusters recurring patterns, and writes a handful of files to ~/.clone/memory/rituals/. A typical solo consulting practice produces 4 to 7 of them on first run. Each file is editable prose. Nothing runs until you explicitly enable one.
What the observe command prints.
The first time a new operator runs Clone, the entire interaction is the same terminal session. Grant the two read-only OAuth scopes, run one command, wait under two minutes, get a folder of editable rituals. There is no wizard and no builder.
How the observer turns your inbox into files.
The observer is not a scraper and not a generic LLM prompt. It is a clustering step followed by an induction step. Both run locally. The raw email text never leaves your machine; only the cluster summaries do.
Grant read-only Gmail + Calendar scopes
A standard Google OAuth consent screen. Clone only requests read scopes for Gmail and Calendar on day 1. No write scopes until you run a ritual on purpose.
Run `clone observe`
The command takes a fixed window (default: 180 days). It reads the Gmail Sent folder and the Calendar events, not the inbox. It looks for threads and events that repeat on a cadence.
Cluster by day-of-week and subject
The observer groups similar outgoing messages. 41 Monday-morning emails with subjects like 'invoice for <client>' cluster into one candidate ritual. A cluster needs at least 8 examples to produce a file.
Induce the instruction
Each cluster becomes one ritual file under ~/.clone/memory/rituals/. The first line is a plain English sentence that names the trigger. The body captures the branches the cluster implies (missing hours, unknown rate, new client).
Review, edit, or delete
Open the folder. Every file is yours to keep, edit, or throw away. Nothing runs until you explicitly tell Clone to enable a ritual. The observe step is a draft step.
One first-run, by the numbers.
These are the numbers from a typical 4-year-old solo consulting practice (8 active clients, a healthy email volume, a recurring Monday morning cadence). Bigger practices produce more files; newer ones produce fewer. The shape is the same.
Five day-1 input surfaces, one output.
All five tools can produce the same drafted invoices, queued emails, calendar holds, and chat posts. The difference is entirely in what you type or draw or record to get them there. The input surface is the product. The output is the commodity.
five input surfaces, one output set
Clone vs. a typical graph-editor BPA
The same columns decide every BPA selection. The day-1 input surface and the shape of the edit surface after day 1 are the ones that matter most.
| Feature | Zapier / Make / HoneyBook | Clone |
|---|---|---|
| Day-1 input surface | Graph editor with trigger/action nodes | Plain English sentence in a markdown file |
| How the first ritual appears | You build it, step by step, from scratch | Observer induces it from your last 180 days of Gmail + Calendar in ~90 seconds |
| Editing after day 1 | Open the builder, click through nodes | Open the .md file in any editor, edit one line, save |
| Onboarding a new hire | Share a read-only link to the visual flow | Hand them the rituals/ folder; every file is readable prose |
| When a vendor app changes | Re-wire the trigger/action nodes | Clone reads the new screen the same way; usually no edit |
| Pricing baseline | $20-80/user/mo for most SaaS BPA; $99+/mo for proposal-style | $49/mo flat, 21-day free trial |
“I spent three years trying to explain my invoicing rules in a Zap. Clone read my sent folder and had the first draft of the ritual in under two minutes. I edited one line.”
Early Clone operator, 5-year solo advisory practice
When does work actually qualify as BPA?
Not every repetitive task is BPA. The shorthand we use: if it is recurring, has forks, crosses apps, needs a trail, and touches real money or trust, then writing a ritual for it pays off. Miss any of those, and a cron script or a calendar reminder is the right answer.
Recurring
Fires on a clock or a cadence, not once. Monday 08:00, after every new lead, first of the month. One-off work is delegation, not automation.
Has forks
Real runs branch. A client with zero hours, a missing rate, an unfamiliar app. If the work has no forks, you can use a script or a scheduler. BPA earns its keep at the forks.
Crosses apps
Reads from Timely, drafts in QuickBooks, posts to Slack, logs to Notion. Inside one app is a vendor feature. Across apps is BPA.
Has an audit trail
You can point at what happened afterwards. Not a "workflow ran green" success box. The actual decisions, inputs, outputs, deferred items, with timestamps.
Touches real money or client trust
Invoicing, billing, status updates, contract follow-ups. If a wrong send hurts the relationship, the pause point is the feature. A BPA without a pause point is a hazard.
“The moment I stopped trying to define BPA in the abstract and started asking 'what would I type to teach it my invoicing?' the product shortlist went from twelve tools to two.”
See what your rituals folder looks like on your first run.
On a 30-minute call we install Clone on your Mac, grant the two read-only scopes, run the observe step, and read the induced ritual files together. You leave with a folder of prose you could hand to a new hire tomorrow.
Book a 30-minute callDay 1, what do you actually type? We type it together.
Twenty minutes together. You bring one repeatable task; we write the one-line English instruction Clone runs on Day 1, no abstractions.
Frequently asked questions
In one sentence, what is business process automation?
It is four things, not one. A recurring instruction (something the automation does), a clock (something that fires it), a pause point (somewhere a human can decide mid-run), and a log (something on disk that records what happened). Every BPA tool contains all four. What changes between tools is the interface for writing the instruction. Clone's interface is a plain English sentence in a markdown file at ~/.clone/memory/rituals/<name>.md.
What does the word 'ritual' mean here, and why not 'workflow'?
A workflow is a diagram a vendor owns. A ritual is a markdown file you own. Both describe recurring work. Ritual is the word we use for the file format so it is obvious that you are dealing with prose, not a proprietary graph structure. The file is the ritual. Open it in any text editor, grep it, commit it to a private git repo.
How long does `clone observe` take, and what does it produce?
About 90 seconds on an average consulting inbox. It scans the Gmail Sent folder and Google Calendar for the past 180 days (both configurable), clusters recurring patterns, and writes one markdown file to ~/.clone/memory/rituals/ for each cluster with at least 8 examples. A typical 4-year-old solo practice produces 4-7 rituals on first run. Nothing runs yet; the files are drafts you review.
Is this attended automation (a human watches each run) or unattended (fully autonomous)?
Attended by default. Every ritual has fork lines where Clone pauses and asks a question in chat. You can turn this off by writing explicit defaults into the ritual file for every branch, but the opt-out is a conscious decision per ritual, not the default. The reason is consulting work. An invoice sent to the wrong client or a contract attached to the wrong email damages relationships; the pause is the feature.
How is Clone's definition of BPA different from Zapier, Make, or HoneyBook?
Zapier and Make define BPA as a graph: nodes for triggers, nodes for actions, branches as explicit decision nodes. HoneyBook defines it as a workflow template: pick a package, drop in a client, the template sequences the sends. Clone defines it as a sentence: one English instruction per ritual, interpreted at run time by a planner that reads the screen and drives the existing vendor tools. The graph, the template, and the sentence are three different answers to the same question.
What apps does Clone drive on day 1?
Whatever is already on your Mac. QuickBooks, Clio, FreshBooks, Google Sheets, HubSpot, Pipedrive, Gmail, Calendar, Drive, Slack, Notion, Calendly. There is no integration list to check. Clone opens the app, reads the screen, and types into it the same way you would. If the app has a GUI, it is drivable. This is the mechanical reason "what apps do you support?" is the wrong question.
Why is the observer reading only my Sent folder and Calendar, not my inbox?
Sent and Calendar capture what you do. Inbox captures what is done to you. Automation is a map of your outgoing behavior, so the signal lives in Sent. Reading the inbox would mostly induce rituals for responding to other people's emails, which is the wrong shape for BPA. This is a read-only scope on day 1 and is revokable in your Google account at any time.
Can I write a ritual from scratch instead of letting the observer induce one?
Yes. ~/.clone/memory/rituals/ is a regular folder. Create a new file, give it a name like custom-ritual.md, type a plain English sentence on the first line, run `clone enable custom-ritual`. The induced files and the hand-written files are identical in shape; the observer is just a head-start, not a required step.
What is the actual difference between $49/mo Clone and a $3,000-6,000/mo virtual assistant?
A VA is labor. Clone is a tool. A VA needs onboarding, time-off coverage, payroll, and context refresh every week. Clone runs 24/7, remembers every decision, and costs one monthly number. The VA handles the fraction of consulting work that is genuinely human (relationship building, tough negotiations, judgment calls). Clone handles the fraction that is recurring enough to have a ritual file (invoicing, status, follow-ups, onboarding pipeline). The two fractions rarely overlap.
Where is the log for a run, and what is in it?
Every time a ritual fires, Clone writes ~/.clone/memory/logs/<date>-<ritual-name>.md. The file is a sequence of timestamped lines: read (what it observed), decide (what it resolved on its own), fork (where it had to stop), ask + reply (operator questions with answers), draft (what it produced), write (what it shipped). You can grep the folder across every run you have ever done. Your answer to 'what happened' is a cat command.
What makes this page different from the other BPA definitions on the web?
Every top SERP result defines BPA by what it does (executes workflows) and what it delivers (efficiency, cost savings, morale). None compare the actual input surface across tools, which is the variable that decides which tool fits your business. This page compares five input surfaces side by side, shows what Clone writes to disk, and shows the exact command that produces the file. If you read this and still do not know what BPA is in your practice specifically, open your terminal and run the observe step; the answer will be a folder with 4-7 files in it.
BPA defined as a sentence in a file, induced from your inbox in ~90 seconds. $49/mo.
Book a call