A business process automation service that works the overnight shift, and lets you roll it all back in the morning.

Every BPA service on page one of Google is a live, fire-on-trigger loop that pushes irreversible actions into your stack as events happen. Clone is the opposite shape. It runs as a scheduled shift (typically overnight), stages every action as a draft, and meets you in the morning with one review of the whole batch. Approve the shift to ship, or roll the entire night back with one click.

The claim is not marketing. It is a named principle in the product source, quoted further down this page verbatim from src/components/architecture.tsx, principle 4, Always reviewable.

Or book a call →
M
Matthew Diakonov
12 min read
4.9from early operators
One human checkpoint per shift, not per action.
Every action logged and reversible, verbatim from architecture.tsx.
Scheduled jobs drive your real apps: Gmail, QuickBooks, HubSpot, Sheets.
$49/mo. 21-day trial. Install to first overnight run in under 10 minutes.

What the rest of page one for this keyword misses.

Run the search for this keyword. The first ten results are the same essay rewritten with different logos. Lists of tools, generic benefits (cost cut 20 to 35 percent), hyper-automation, agentic AI. None of them describe a batch-then-review loop that runs on a scheduled shift instead of on live triggers. None of them describe a reversible morning. That is the shape that actually matches how a solo consultant, a boutique firm, or a 5-person bookkeeping practice wants to operate, and it is the shape the SERP never names.

The platforms below are what the SERP points you at. They are the typical answer, and they are also the trap: a shape that assumes roles, preconditions, and irreversibility your firm does not want.

GmailQuickBooksHubSpotCalendlyGoogle DriveGoogle SheetsNotionZoomStripeTimelyFirefliesFreshBooksPipedriveDubsado

The marquee above is a sample of the apps a typical consulting shift actually touches. Not a vendor marketplace. Not a connector catalog. The tools you already pay for, that Clone drives directly through the screen.

The anchor fact: principle 4, quoted verbatim.

A BPA service that claims to be reversible should be able to point you at the place in its own source where that claim is enforced. Clone's architecture file lists six layers and four principles. The fourth principle is the one that matters for a shift model. Here it is, with no paraphrase.

anchor fact

From src/components/architecture.tsx, principle 4, label Always reviewable:

“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.”

Four sentences, one behavior. The morning review screen and the rollback button are not a feature shipped on top of the automation. They are the principle that shapes what automation is allowed to do in the first place: nothing irreversible until you approve the shift.

What the shift actually touches.

Left side: the inputs Clone reads during the shift. Right side: the tools it stages drafts inside. The hub is Clone itself. Nothing on the right side ships during the shift, everything is held for the morning review.

Inputs → Clone (overnight) → staged drafts for your review

Timely
HubSpot
Zoom / Fireflies
Google Drive
Clone shift
Gmail drafts
QuickBooks invoices
Sheets dashboard
Notion retro

A night with Clone, in six frames.

This is what an actual Sunday-to-Monday shift looks like for a solo consulting practice. Six frames, eight or so real hours, ending at 8:02am with either an approved batch or a wiped night.

Sunday 10:47pm through Monday 8:02am

01 / 06

10:47pm. You close the laptop.

You have ten client tabs open, four untracked Zoom transcripts, and a stack of billable hours that did not get invoiced. Clone is still awake.

The morning review, verbatim.

What you actually see at 8am. A single terminal-style summary of the shift: what was staged, what was flagged, and what your two choices are. Approve the batch, fix the anomaly in place, or run the undo to wipe the night.

clone morning-review · monday 8:00am

The shape of a normal Monday morning.

These four numbers come from the step 04 scheduled pattern in src/components/how-it-works.tsx: the Monday 8am schedule that ships 4.2 hours of staged admin before your first coffee. Pricing comes from pricing.tsx, Solo tier.

0 hrsAdmin staged per shift
$0/moSolo tier pricing
0 minInstall to first shift
0 clickRoll back the morning

vs. a virtual assistant

0x cheaper

$49/mo vs. $3,000/mo (low end of a human VA). Clone also works while the VA sleeps.

irreversible actions during shift

0

Nothing leaves the laptop until you approve the batch. Drafts stay drafts.

apps the shift can drive

any with a screen

Computer Agent reads the UI, so no API is required. Desktop apps, legacy tools, niche verticals all count.

Setting up your first overnight shift, in five steps.

There is no workflow builder, no trigger graph, no YAML. The shift is defined in one plain-English paragraph and scheduled like a calendar event.

1

Write the job in plain English.

No BPMN canvas, no trigger/action wizard, no YAML. One sentence with the name of the apps you want touched. Example below.

clone-job: weekly-back-office
2

Pick the shift window.

Clone does not idle on a hot loop waiting for triggers. You tell it when to work: Sunday 9pm to Monday 7am, weeknights 10pm to 6am, or continuously. It schedules itself and sleeps the rest of the time.

3

Clone drives your real apps.

The Computer Agent layer reads the screen, clicks the buttons, types the fields, scrolls the pages. Same UI your clients see. No API required, no connector catalog, no recorded selectors. Works on desktop QuickBooks the same as on Gmail webapp.

4

Actions get staged, not shipped.

Drafts sit in Gmail. Invoices sit in QuickBooks as unsent. Dashboard rows are pre-filled but not shared. The shift produces a reviewable batch, not a stream of side effects.

5

Approve or roll back in the morning.

Open the review. Read one screen. Approve the batch to ship, edit an anomaly in place, or run the undo to wipe the night and put the computer back where you left it. The approval gate is the default, not an add-on.

Shift-then-review vs. fire-on-trigger.

A typical BPA service, a human VA, or a Zapier chain, compared with Clone on the properties that actually shape your mornings.

FeatureTypical BPA serviceClone (overnight shift)
Work windowFires on live triggers, any time of dayRuns on a shift you schedule, typically overnight
Integration surfacePublished connector catalog, API requiredComputer Agent drives any app with a screen
Human checkpointPer trigger, or noneOne review per shift, one click to ship or undo
ReversibilitySide effects land as they fire, cleanup is manualEvery action staged and logged, roll back in one click
Preview before sendDepends on the connector, rarely availableGmail drafts, unsent invoices, unshared docs, by default
Anomaly handlingFires anyway, you see the failure afterFlagged in the morning review, never shipped blind
Works with no-API appsExcluded unless a partner integration existsDesktop QuickBooks, Filemaker, a legacy PM tool, all fair game
Cost$3k to $6k/mo for a VA, 5 to 6 figures for a BPM rollout$49/mo. 21-day trial. No implementation partner.

Row content is specific to the shift-then-review model. Individual vendors vary; this characterizes the category.

What runs in the shift, typically.

Six kinds of work that a solo consulting practice queues for the overnight shift. Your stack picks what applies. Clone drives whichever apps are involved.

Invoicing run

Clone reads your time tracker, applies the rate per engagement, generates branded invoices in QuickBooks or FreshBooks, and drafts the email cover notes. All unsent until you approve.

Follow-up correspondence

Post-kickoff nudges, overdue-payment reminders, renewal reaches, all personalized with notes from last week's Zoom transcripts. Drafts in Gmail. Sent only on your approval.

CRM updates

Every call transcript routed to the right HubSpot or Pipedrive contact, tagged by engagement, summarized by outcome. Next steps become tasks.

Dashboard refresh

Pipeline, utilization, outstanding AR, upcoming renewals. Clone refreshes the Google Sheet every morning. The board you never had to build.

Retro and reporting

Friday retros, monthly client updates, end-of-quarter reports. Clone drafts them in Notion or Google Docs using last week's data. You scan, adjust, ship.

Onboarding handoff

Drop a signed proposal into a folder at 11pm. By morning Clone has provisioned the workspace, drafted the kickoff agenda, booked the call, and staged the welcome email.

Put Clone on one overnight shift with us this week.

On a 30 minute call we install Clone on your Mac, you type the shift (invoices, follow-ups, dashboard refresh, pick any three), and we schedule it to run tonight. In the morning you review the batch and decide whether to ship or roll back. That is the full trial of the overnight-shift model, compressed into one meeting and one night.

Schedule one overnight shift with us

See the overnight shift run. Roll the whole morning back if it misreads.

Twenty minutes together. We demonstrate a scheduled ritual that runs while you sleep, and the one-click rollback you have when it does.

Overnight shift, honest questions.

What does 'overnight shift' mean in practical terms, what is Clone actually doing?

Clone is a Mac or Windows app that you keep running on a computer you already own. You give it a recurring job in plain English: Every Sunday 9pm through Monday 7am, do X, Y, Z. At the scheduled time it wakes up, opens the apps it needs, and drives them from the keyboard and mouse layer: reads the screen, clicks, types, scrolls. It does not push irreversible actions. Invoices are drafted, not sent. Emails are drafted, not sent. The dashboard row is updated, the document is filled. Actions that would touch a client stay staged. In the morning you get one review of the whole batch.

How is this different from Zapier, Make, or a typical BPA platform?

Zapier and Make run on live triggers. An event fires, a Zap runs, the side effect lands. If the draft was wrong, the email is already in the client inbox. There is no batch, there is no checkpoint, there is no rollback. Clone inverts that shape: it works a shift on your schedule, stages every action, and pauses at a single human checkpoint in the morning. One approval ships the batch, one undo wipes the night. The work happened while you slept, the judgment stayed with you.

What exactly can be rolled back?

Anything Clone did during the shift that has not yet been approved. Gmail drafts sit as drafts, QuickBooks invoices sit as unsent, Sheets rows and Notion docs can be reverted from the shift log. The rollback is a wipe of the night: the computer goes back to where you closed the laptop. After you approve the batch, ordinary actions that hit the outside world (sent email, issued invoice) follow the rules of the target system. Approval is the point of no return, not the trigger.

Where is this 'reversible by default' claim actually coming from in the product, can I verify it?

Yes. It is a named principle in Clone's architecture source file. Open src/components/architecture.tsx in the product source and read the fourth principle, labeled Always reviewable. Quoted verbatim: 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. That line is the spine of this page.

Do I have to use new software, or does Clone sit on top of what I already pay for?

Clone is tool-agnostic. It drives your existing Gmail, your existing QuickBooks or FreshBooks, your existing HubSpot or Pipedrive, your existing Google Sheets or Notion. Because the Computer Agent reads the screen and operates the UI, it does not require any app to expose a public API. Desktop QuickBooks counts the same as QuickBooks Online. A legacy tool that shipped in 2014 and was never updated counts the same as a modern SaaS. Remove Clone and your business still runs, your data is still where it was.

How do I know Clone did not break something while I was asleep?

Two guardrails. First, nothing that would leave the computer gets sent during the shift. Drafts are drafts, invoices are unsent. You can see everything before the world sees it. Second, the shift produces a log of every file touched, every click made, every field typed. In the morning the review surfaces the batch along with any anomalies Clone flagged, like a missing rate card or a stale client record. You approve, you edit the anomaly in place, or you roll the whole night back.

Why an overnight shift specifically, why not run continuously?

Two reasons. One is cognitive: a single batch with a single review is cheaper to process than a stream of notifications. Two is practical: most back-office work (invoicing, CRM hygiene, reporting, follow-up drafting) is rate-limited by data that changes daily, not per-second. Running it as an overnight job collapses the day's work into one scheduled window, which matches how a solo consultant actually wants to operate: the business runs while I sleep, I review it while I drink coffee. You can schedule continuously or during working hours instead if you want, the shift model is the default, not a requirement.

What does this cost, and what does it replace?

$49/mo for a solo consultant, $129/seat/mo for a boutique firm, custom for enterprise. There is a 21-day free trial. What it replaces depends on what you were doing. If you had a virtual assistant handling admin at $3,000 to $6,000 a month, Clone covers most of the same surface and runs 24/7. If you were pricing a BPM rollout through Appian or Pega, you avoid the five and six figures of licenses and the quarters of modeling work. If you were duct-taping Zapier chains that fire irreversible actions on live triggers, Clone is the grown-up version that gives you a review gate.

Tonight: one shift. Tomorrow: one review, one click. $49/mo, 21-day trial.

Book the overnight shift call