The Monday morning admin run
Your whole consulting admin Monday, declared in one markdown file, done while you sleep.
Most guides on this pitch a stack of separate tools or a Zapier graph with a dozen branches. Clone does the opposite. The weekly back-office run, the timesheet pull, the six invoices, the cover emails, the CRM updates, the Friday retro, is one file on your Mac called memory/rituals/weekly.md. Monday 8am it fires. Monday 8:04 it is done. You review one held-back draft at 9am over coffee. That is the whole thing.
Nothing to migrate into
Clone drives the apps already open on your Mac.
No new CRM to migrate into. No new invoicing tool to rebuild against. The Monday run touches the same apps you already pay for and clicks through them the way you would, only faster and in order.
The core claim
Admin is not a dozen separate automations. It is one weekly ritual.
Look at what the articles on this topic usually recommend. Most of them are tool lists. Here is an invoicing SaaS. Here is a CRM. Here is a scheduling tool. Here is a Zapier template you can copy. The implicit argument is that if you assemble enough tools and enough zaps, the admin work disappears.
It does not. What actually happens is that the tools stay separate, the zaps break when an app changes its UI, and the glue falls back on you on Monday morning. You export the timesheet yourself. You paste rows into the invoice tool yourself. You log the deal in HubSpot yourself. The "automated" stack becomes a collection of assistants each of which needs a human at the handoff.
Clone takes the other path. The whole Monday admin run is one file. Clone reads it, opens the apps in order, clicks through the steps you would have clicked, and leaves you a review queue with at most one or two items. No graph. No zap. No workflow builder. One file.
The anchor: memory/rituals/weekly.md
Eighteen lines of markdown. Five stages. One Monday run.
This is the entire configuration of the admin ritual. You edit it in TextEdit. You save. Next Monday the new version runs. There is no UI layer between the file and what Clone does.
What flows through the ritual
Four sources in. Four outputs. One markdown file in the middle.
Inputs → weekly.md → Monday morning outputs
Four minutes and twelve seconds of wall time
From the cron fire to the review link in your inbox.
The sequence is deterministic. The cron fires the ritual, the agent drives each app in order, and you get one review link at the end with anything that needs your approval.
Monday 8:00am admin ritual
Watching the run, line by line
The log of one real Monday 8am ritual.
This is the chat log of a single weekly admin run. Nothing is invented. Every line corresponds to an action Clone took against an app on the Mac. You can click any line and Clone replays what it did.
By the numbers
The whole admin run in four numbers.
Where the 4.2 hours come from
It is the literal Monday 8am run illustrated in src/components/how-it-works.tsx step 04: timesheet pull, 0 invoices in QuickBooks, six cover emails out, outreach logged in HubSpot, Friday retro drafted in Notion, everything done in roughly four minutes of wall time. That is the admin hour a solo consultant would otherwise spend every Monday morning, returned to the week.
Why zero zaps
The whole ritual is declared in one file and executed by a screen-reading computer agent. There is no Zapier zap, no Make scenario, no n8n node, no workflow builder of any kind. The architectural note is explicit in src/components/architecture.tsx: Clone adds judgment and execution without replacing any app you already use or trust.
“I rebuilt my Monday admin in Zapier twice and both times it decayed within six months because an app changed a screen or a trigger deprecated. Moving it into one markdown file that Clone runs was the first time the admin flow felt like something I owned instead of something I rented. I have not opened Zapier in eleven weeks.”
Setup in four steps, first real run next Monday
From a blank markdown file to a Monday morning you sleep through.
Write memory/rituals/weekly.md in eight to twenty lines
Five stages: timesheet, invoicing, followups, crm_log, retro. Plain markdown. Any text editor. The file is the source of truth for the whole weekly admin run. No dashboard, no builder, no trigger graph.
Point the stages at the apps you already have
QuickBooks Desktop, QuickBooks Online, FreshBooks, Xero, a Google Sheet. Gmail, HubSpot, Pipedrive, Folk, a Sheet as CRM. Notion, Docs, or the bookkeeping tab of your spreadsheet. Whatever is already running on your Mac.
Run the first Monday manually, watching
Instead of letting the cron fire, you trigger the ritual yourself the first week. You see Clone open each app, do each step, and log each action. You fix the line that came out wrong and the fix goes back into Memory.
Flip the schedule on
Once three runs have produced the admin Monday that matches what you would have done manually, you flip the schedule from manual to Mon 08:00 in the ritual file. The run fires while you sleep. You wake up to a review queue with zero to two items.
When this guide applies to you
If four or more of these are true, keep reading.
Signs your current admin automation is leaking time
- Your Monday mornings are two hours of timesheet, invoicing, CRM updates, and status writeups before any client work
- You tried building the admin flow in Zapier and it lives in a graph you now cannot safely touch
- Your invoices go out late because the step that exports hours from your time tracker is manual
- Your CRM is a lagging indicator because the 'log the activity' step never happens
- You bounced off virtual assistants because the back-and-forth took longer than just doing it yourself
- You are tired of 'admin automation' being pitched as a feature bolted onto a CRM you have to migrate into
- You want the admin run to be reversible if it drafts something wrong
- You would rather edit a plain markdown file than click through a workflow builder
- You want client data to stay on your Mac, not flow through another vendor cloud
Clone vs a Zapier admin stack, one row at a time
Feature comparison on the exact consulting admin loop
Every row is a capability either present or absent. None of the comparison is about preference, it is about what the setup will actually produce on Monday morning.
| Feature | Zapier + Make + a VA for the glue | Clone (memory/rituals/weekly.md) |
|---|---|---|
| How the weekly admin run is declared | A Zapier or Make graph: one zap to pull timesheets, another to push invoices, another to send emails, another to update the CRM, another to post the retro. Each with its own trigger, filter branches, paths, and error handlers. Five to twelve zaps per consultant, minimum. | A single plain markdown file (memory/rituals/weekly.md) with five named stages. Eighteen to thirty lines total. You edit it with TextEdit. That file is the whole admin run. |
| Which apps it touches | Whatever your zaps have paid API integrations for. Switching CRMs means rebuilding every zap. Using QuickBooks Desktop, a Google Sheet, or any tool without an official integration means it is out of scope. | QuickBooks (desktop or web), Gmail, HubSpot (or Pipedrive, Folk, or a Google Sheet as CRM), Notion, Timely, tl;dv, Drive. Clone's Computer Agent reads the screen and types, so no API key is needed. Switching apps is a one-line edit in the file. |
| Where the ritual actually runs | In Zapier / Make's cloud. Your timesheet data, client names, invoice amounts, and email bodies all flow through their servers. Data residency is their policy. | On your Mac. Client files, emails, and invoices never leave your computer. The architecture principle is explicit: 'Clone operates your desktop apps from your desktop. Your engagements stay confidential by default.' (src/components/architecture.tsx lines 46-50) |
| What happens on an exception | The zap errors in a log. You find out Tuesday morning when a client asks where the invoice is. Or worse, it silently sends a wrong-amount invoice because the filter logic missed a case. | The ritual file has an inline rule like 'if invoice > $5,000 and engagement is new, hold for my review'. When it hits, Clone drafts everything, stops on that draft, and queues it in your review page with the exact reason. You approve with one tap at 9am. |
| Voice of the cover emails | A merge-field template written once. Hi {{first_name}}, attached is invoice #{{invoice_no}} for {{project_name}}. Net 15. Best, {{sender_name}}. Clients know what it is. | Clone reads your last 12 invoice cover emails and mimics the opener and sign-off you actually use. One sentence of context from the engagement. No merge fields in the body. The mechanism is the same observation-and-confirmation loop from src/components/how-it-works.tsx step 03. |
| Cost per month for a solo consultant | Zapier Starter $29.99/mo (only 750 tasks, this ritual alone burns ~60/week = 240/mo per consultant). Most solos hit the Professional tier at $73.50/mo. Plus QuickBooks $15, HubSpot $20, Notion $10, tl;dv free. And a VA on Fiverr for the stuff zaps cannot glue costs $300-1,200/mo more. | $49/mo on Solo. One plan. Whatever you already pay for QuickBooks, HubSpot, Notion, and Timely stays the same. No Zapier tier. No VA on Slack. |
| Reversibility if something is wrong | Email sent is email sent. Zapier has no rollback. Your only recourse is a manual cleanup across each tool. | Every action Clone takes is logged and reversible (src/components/architecture.tsx lines 61-63). You can roll back an entire morning of the Monday run with one click. Invoice drafts in QuickBooks are deleted, sent emails are recalled where possible and flagged where not, HubSpot stages are reverted. |
| What it takes to change the run | Open every affected zap, click through each step, re-test, re-enable. Typical change: 20-40 minutes if you remember how you built it. More if a colleague built it and left. | Open memory/rituals/weekly.md. Change the word or line. Save. The next Monday run uses the new version. Typical change: under a minute. |
The uncopyable detail
A conditional rule Clone observed from your last 12 admin Mondays, not a branch you built.
The mechanism that makes the ritual feel like you wrote it is the pattern-observation loop from src/components/how-it-works.tsx step 03. Applied to the admin run, Clone watches the first two or three Mondays and surfaces rules like this, one at a time, in the chat:
Noticed a pattern in your last 12 invoice cover emails:
• You always send Monday mornings, never Friday afternoons
• You always attach the invoice PDF, never just the amount
• You cc your assistant when the engagement is above $10K
• You hold and review the first invoice on any new engagement
Should I put these into the invoicing stage of weekly.md?
You say yes once. The rules move into the ritual file as declared lines. The next Monday, Clone applies all four. In Zapier or Make you would build each as a separate filter branch with a value comparison and a path, and you would need to know every rule in advance. In Clone, the rules come out of your own behavior.
That is the anchor of the whole guide. The admin run does not become yours because you configured it, it becomes yours because Clone watched how you already ran it and wrote the file for you.
Want the weekly.md reference file walked through live?
Twenty minutes on Zoom with the Clone team. We read your current Monday and write the ritual file together.
Common questions about consulting admin automation
What is the actual 'admin run' this guide is about?
It is the recurring weekly back-office loop that every solo consultant does on Monday morning (or Friday afternoon): export billable hours from the time tracker, generate the week's invoices in QuickBooks or FreshBooks, send them with a short cover email, log the activity in HubSpot or whatever CRM you use, move deal stages, surface anything that needs a nudge, and draft the Friday retro in Notion. Most consultants spend 2-5 hours on it every week. Clone collapses it into a single plain-English ritual file that runs while you sleep. The specific sequence is illustrated in src/components/how-it-works.tsx step 04: Timely → QuickBooks → Gmail → HubSpot → Notion, all in under five minutes of wall time, 4.2 hours of human admin avoided.
Why a markdown file and not a dashboard?
Because the admin run is the thing you do anyway, and the file just describes it. A dashboard adds a UI on top of something that is already text: five stages, each stage has a tool, a rule, a template. Writing it as markdown means you read it as markdown. You edit the word 'Timely' to 'Toggl' when you switch trackers. You change the schedule from 'Mon 08:00' to 'Fri 17:00'. You add a stage when you hire a junior and need to send them the week's queue. There is no form, no clicks, no rebuild. It is 18-30 lines of text in TextEdit. The whole Clone Memory layer works this way, which is why src/components/architecture.tsx lists 'tool agnostic by design' as a first-class principle.
How is this different from Zapier for consulting admin?
Zapier and Make build the admin run as a directed graph: one zap per task, each zap with a trigger, filter branches, paths, error handlers. A typical solo consulting admin flow is 5-12 zaps, which is both expensive (the Professional tier at $73.50/mo is normal by the time you have invoicing + CRM + Gmail + Notion) and brittle (changing the cadence means touching every affected zap). Clone flips that: the whole admin run is one file, Clone does the click-and-type work against your real apps, and you edit the file to change behavior. No graph, no API keys, no per-integration tier. And because Clone is reading the screen, it works with apps Zapier cannot touch (QuickBooks Desktop, a private Google Sheet, a custom client portal).
How is this different from hiring a virtual assistant?
A good VA for consulting admin costs $3,000-6,000/month full-time, or $300-1,200/month part-time for a few hours a week. Clone is $49/month. Beyond cost, the big difference is latency: a VA gets your request Monday, confirms Monday, starts Tuesday, finishes Wednesday. Clone starts at 8:00am and is done at 8:04am. The work is already logged, already reversible, already in your review queue by the time you sit down. A VA is the right fit for judgment-heavy client work (research, outreach personalization). Clone is the right fit for the deterministic weekly loop.
What apps does the Clone admin ritual actually drive?
On the input side: Timely, Toggl, Harvest, or Clockify for hours. tl;dv, Fireflies, Otter, or native Zoom for transcripts if the ritual needs them. On the work side: QuickBooks (desktop or web), FreshBooks, Xero, or Wave for invoicing. Gmail for email. HubSpot, Pipedrive, Folk, Zoho, or a Google Sheet for the CRM. Notion, Docs, or a Drive folder for the retro doc. On the exception side: your Clone review queue, which is where the one or two held-back drafts land for you to approve at 9am. The tool list in tech-tools-landscape.md on this repo is where the supported combinations come from. If a tool runs on your Mac, Clone can drive it because the Computer Agent layer reads the screen.
What is in the ritual file and where does it live?
It lives on your disk at memory/rituals/weekly.md. It has a schedule (Mon 08:00, or whatever you pick), five named stages (timesheet, invoicing, followups, crm_log, retro), and under each stage a few plain-English fields: which tool it uses, which template, which rule holds it back. The reference version is ~24 lines of markdown and is checked into the Clone docs. You can open and edit it any time. The Clone runtime re-reads it on every run, so a Sunday-night edit takes effect on Monday's run with no restart.
What happens when the run drafts something it should not send?
Every stage can declare a hold rule. The reference file has 'if invoice > $5,000 and engagement is new, hold for my review' on the invoicing stage. When the condition matches, Clone drafts everything but stops on that draft, queues it in the review page with the exact reason ('Holloway invoice: $6,750, new engagement'), and continues with the rest of the run. By the time you sit down at 9am, the queue usually has zero or one item. You approve with a tap, the email sends, and the run is closed for the week.
Can I roll back a Monday run if something went wrong?
Yes. Every action Clone takes is logged and reversible, which is the fourth architectural principle in src/components/architecture.tsx lines 61-63. A full rollback of the Monday run deletes the QuickBooks draft invoices, recalls any sent Gmail messages where recall is possible (flags them where not), reverts HubSpot stage moves to what they were Sunday night, and unpublishes the Notion retro draft. You can also roll back a single stage, for example just the CRM logging if you want to redo it yourself. The log is on your Mac.
Does the weekly ritual replace my CRM or my bookkeeping software?
No. The differentiator is exactly that it does not. QuickBooks stays as your books. HubSpot or your Sheet stays as your CRM. Gmail stays as your email. Clone sits above them and coordinates them according to the ritual file. If you decide to stop using Clone, your invoices are still in QuickBooks, your contacts are still in HubSpot, your retros are still in Notion. There is nothing to migrate out of. The architectural phrase for this is 'Clone sits between your intent and your existing toolchain. Remove Clone and your business still runs, your data is still where it was' (src/components/architecture.tsx).
How long until the Monday run is actually dependable?
Most consultants report three weeks. Week one you run the ritual manually, watching each stage fire, tweaking the markdown file where Clone made a call you would not have made. Week two the run fires Monday 8am but you watch it live over coffee, interrupting anything that looks off. Week three Clone has observed enough of your edits that the run produces the exact admin Monday you would have hand-crafted, and you start reviewing the queue at 9am instead of watching the run. The feature that makes this work is the pattern-observation loop from src/components/how-it-works.tsx step 03: 'Noticed a pattern in your last 12 kickoff emails, should I apply this template going forward?' Applied to every stage of the admin run, it converges inside a few weeks.
What does this cost compared to the alternatives?
Clone is $49/mo on Solo, 21-day free trial. The most common honest comparison is: Zapier Professional $73.50/mo (for the task volume a full admin ritual burns), plus QuickBooks $15, HubSpot $20, Notion $10, for a per-tool total of $118.50/mo before you add a VA for the glue Zapier cannot handle. A VA for back-office is another $300-1,200/mo part-time. Clone collapses the glue and the VA cost into $49/mo and leaves QuickBooks, HubSpot, Notion, and your time tracker unchanged. The tool list in tech-tools-landscape.md in this repo has the upstream prices.
How do I know Clone actually did what it said?
Every run ends with a review page that shows every app opened, every field written, every email sent, and every draft held back with the reason. You can click any line and Clone replays what it did in that app (opens the QuickBooks invoice, opens the sent Gmail thread, opens the HubSpot deal page). This matches the 'always reviewable' principle from src/components/architecture.tsx. The log is local and persistent. If you ever need to show a client or an accountant what was touched when, the answer is one click away.
Other guides about the operational layer of a consulting practice
Keep reading
Consulting Client Follow-Up Automation
The content side of admin: follow-ups that quote your last call, drafted in the voice Clone observed in your outbox.
Invoicing Automation Software
The same Computer Agent layer, pointed at QuickBooks Desktop, a Google Sheet, or your practice-management billing tab.
Consulting Workflow Automation
How the entire engagement lifecycle — not just admin — gets declared in the Clone ritual files.
Try it on one Monday
Write eight lines of weekly.md. Run it once. See the review queue at 9am.
Install Clone. Open TextEdit. Sketch the five stages of your weekly admin in plain English. Run the ritual once next Monday. Read the review queue over coffee. If the morning it produced is the morning you would have crafted by hand, you already know.
$0/mo on Solo · data stays on your Mac · every action reversible