The Friday block, replaced
Consulting admin batching is a workaround for context-switch cost. Clone has none, so the block dissolves into a queue.
Every batching playbook for solo consultants tells you the same thing: defend a 2pm Friday block, group like-tasks, power through. The reason it has to be a block is the 23-minute context-switch tax humans pay between tools. Clone does not pay that tax. So instead of a calendar block, you get a six-line file at memory/queues/admin.md. Each line is an event and a handler. Each handler runs in 30 to 90 seconds the moment its trigger fires. You stop defending Fridays.
Same apps. No migration.
The queue fires the apps you already pay for.
No new CRM. No new invoicing tool. No new project tracker. Each event handler in memory/queues/admin.md drives the apps already open on your Mac.
The argument
Batching is not a discipline. It is a tax dodge.
The standard batching advice for consulting admin is the same in every guide on the topic: pick a recurring block, defend it on the calendar, group all admin into it, do not let client work bleed in. The framing is moral. The advice presents batching as a virtue, the mark of a disciplined operator who refuses to let admin sprawl.
That framing is wrong. Batching exists for one specific economic reason: switching between tools and tasks costs the human brain real time. The most cited number comes from the Mark, Gonzalez, Harris study at UC Irvine: roughly 23 minutes of focus recovery after a meaningful interruption. Across a typical admin chore list of fifteen items, switching costs alone exceed the actual work. The block amortizes that cost across the chores.
That economic logic is real. The block is a rational response to a constraint. But the constraint only applies to humans. A computer agent that reads your screen and types does not experience focus decay. It does not need ramp-up time when it switches from Gmail to QuickBooks to HubSpot. The 23-minute tax is zero for it.
Once the tax is zero, the entire reason the block exists evaporates. You do not need to amortize a cost that no longer exists. Each admin task can fire the moment its triggering event lands, run in seconds, and finish before the next event in the queue arrives. The calendar block is no longer a virtue. It is a leftover.
The math
Four numbers that explain why the block dissolves.
The anchor: memory/queues/admin.md
The whole admin queue, declared in twenty lines.
This is the entire configuration for a solo consulting admin queue. Four event handlers, one wall-clock handler, and a hold rule. You edit it in TextEdit. You save. The next event uses the new behavior. There is no UI between the file and Clone.
What flows through the queue
Four event types in. Five outputs. One queue file in the middle.
Events → admin.md → fanout into your existing apps
Friday block vs event queue
Two ways to handle the same admin load.
Same six invoices, same fifteen followups, same CRM logging. Different shape of work. Toggle between them.
The shape of admin
Defend a two-hour calendar block. Show up with a bullet list of every admin chore that piled up since Monday. Power through it before energy fades. Hope you finish by 4pm.
- Two hours blocked, every week
- Six invoices stacked into one marathon
- All call transcripts processed at once, latest first
- Followups land Friday evening (worst response window)
- If you skip the block, the work compounds
- Calendar defense is a discipline tax
The five canonical batches, dissolved one by one
What each batch looks like once it has an event handler.
The invoicing batch
Old way: Friday afternoon you export hours from Toggl, paste into QuickBooks, draft six cover emails, send them all in one push. New way: Friday 17:00 the timesheet_synced event fires and Clone drafts six invoices in four minutes against your real QuickBooks. The hold rule catches the one new engagement above $5K. You approve it at 9pm.
The CRM batch
Old way: end of the week you scroll Gmail and try to remember which conversations you owe a CRM update on. New way: every zoom_call_ended event writes a log in HubSpot with the call summary, the date, and the contact. The CRM is current at all times, not weekly.
The followup batch
Old way: a Friday block where you draft fifteen followups from memory of conversations that happened on Tuesday. New way: each followup is drafted seconds after the call ends, while context is fresh, in your voice, ready to review.
The receivables batch
Old way: every other Friday, you reconcile QuickBooks against your bank, send polite invoice nudges, mark deals paid. New way: invoice_paid fires on the webhook, Clone sends the thank-you, moves the HubSpot stage, logs the payment in Notion, all without you opening any of those tabs.
The proposal-nudge batch
Old way: you scan your sent folder Friday and feel guilty about three ghosted proposals from two weeks ago. New way: proposal_unanswered fires on day 14 and Clone drafts a polite nudge that references the SOW. Held for your review by default. You approve in fifteen seconds, not twenty minutes.
What 'on: zoom_call_ended' actually looks like
48 seconds of agent work, end to end.
Pick the event handler that matters most: a Zoom call ending. The sequence below is what Clone runs from the moment you click 'End Meeting' to the moment the followup is sent (or held for review).
Single event handler: zoom_call_ended
The queue, line by line
Two real call-end events, processed in under two minutes total.
This is the chat log of two Zoom call endings on a Tuesday morning. One ran clean. One held for review because the SOW was over the $5,000 threshold. Both finished while you were already on the next call.
Friday block vs event queue, row by row
Where the two models diverge
Each row is something a solo consultant runs into in real life. The block was a rational response to the human cost of switching. The queue is what becomes possible once that cost goes to zero.
| Feature | A defended Friday admin block | Clone (memory/queues/admin.md) |
|---|---|---|
| Why the batch exists in the first place | Because context-switching is expensive. The classic University of California Irvine study (Mark, Gonzalez, Harris) found it takes around 23 minutes to fully recover focus after an interruption. Batching amortizes that cost across many similar tasks. The block is a discipline tax you pay to dodge a cognitive tax. | Clone has no context-switch cost. The Computer Agent layer (described in src/components/architecture.tsx) reads the screen and types. It does not lose its place when it moves from Gmail to QuickBooks to HubSpot. Each task is 30 to 90 seconds, regardless of how many tabs are open. The whole reason batching exists evaporates. |
| Where the schedule lives | On your calendar, defended in red, weekly. Move it once and it tends to evaporate for the rest of the month. | In a six-line file, memory/queues/admin.md, declared as event triggers. Edit a line in TextEdit. Save. The next event uses the new behavior. No calendar defense. |
| When the followup goes out after a call | Friday afternoon, when the block fires. That is two to four days after the call. Response rates drop fast after 24 hours. | Within 60 seconds of the call ending, drafted in your voice from the call transcript. Either auto-sent or held for one-tap review depending on your rules. |
| What happens when you skip the block | Work compounds. Next Friday's block has 1.5x the load. Two missed Fridays in a row and the admin layer breaks. CRM goes stale, invoices go late, followups never go out. | Nothing changes. The events fire whether you sit down or not. There is no block to skip. Take a Friday off, take a week off, the queue runs. |
| How many invoices in a single push | Six. Twelve if you skipped a week. The whole point of the batch is to stack them, push hard, and clear them in one painful sitting. | One at a time, queued, drafted in QuickBooks the moment its triggering event fires. The Friday timesheet sync is one event that fans out into six invoice drafts over a few minutes. You review one or two holds, ignore the rest. |
| What the apps look like during admin work | Six tabs open: Toggl, QuickBooks, Gmail, HubSpot, Notion, your bank. You alt-tab forty times per task, each switch resets a thread of attention. | You have zero tabs open. Clone has the tabs open on its side and runs them. Your screen stays on the client work. The only Clone surface you see is the review queue with anything held back. |
| Where the data lives | In each tool, with you as the human glue. Or scattered through a Zapier graph that is one UI change away from breaking. | In the same tools as before. Clone never replaces them. Remove Clone and your invoices are still in QuickBooks, your contacts still in HubSpot, your transcripts still in Drive. The architectural principle is in src/components/architecture.tsx: 'Remove Clone and your business still runs, your data is still where it was.' |
| Cost per month for a solo consultant | A virtual assistant for the glue work runs $300 to $1,200 a month part-time, $3,000 to $6,000 full-time. Plus QuickBooks $15, plus HubSpot $20. The block itself costs you 8 hours a month at your hourly rate, which is $1,200 to $2,400 in opportunity cost for a $150-300/hr consultant. | $49 a month on Solo, one plan. The block opportunity cost goes to zero. Everything you already pay for stays. No VA on Slack. |
“I had defended my Friday 2pm to 4pm admin block for four years. Two weeks after I wrote my admin.md, I noticed the block was empty: the followups went out after each call, the invoices drafted Friday at 5pm, the CRM was current. I deleted the calendar event. That was three months ago. I have not put it back.”
Setup in four steps, the block is gone by week three
From a blank file to a Friday afternoon you stop defending.
Open TextEdit and write twelve to twenty lines
List the events that already trigger your admin work today, even if you do them by hand. Calls ending. Weeks ending. Invoices being paid. Proposals going stale. That list is your queue file. Save it as memory/queues/admin.md.
Hand the file to Clone and run one event manually
Pick the easiest event, usually 'on: zoom_call_ended', and ask Clone to handle the next call you finish today. You watch it open Drive, save the transcript, log HubSpot, draft the followup. You correct anything that came out wrong.
Add hold rules where stakes are real
On the invoicing handler, add 'hold for review if amount > $5000'. On the followup handler, add 'hold if proposal_amount > $5000 and engagement is new'. On the proposal-nudge handler, hold by default and let yourself approve in one tap.
Delete your Friday admin block
After two weeks of the queue running, you will notice the Friday block is empty. There is nothing left in it. Delete the calendar event. Use that time for client work, deep work, or a long lunch.
Want your admin.md drafted live, on a 20-minute call?
Twenty minutes on Zoom with the Clone team. We read your week, write the queue file together, and you walk away with the four event handlers that delete your Friday block.
Common questions about consulting admin batching
What does 'consulting admin batching' usually mean?
It refers to the standard time-management practice solo consultants and freelancers adopt to keep weekly admin from bleeding into client work. The pattern: pick a fixed block on the calendar (often Friday 2pm to 4pm, sometimes the first hour every morning), defend it, and group all admin chores into that block. Invoicing, CRM updates, followups, expense tracking, status emails, all stacked together. The reason the block has to be that long is the cognitive cost of switching between tools and tasks. The Mark, Gonzalez, Harris study at UC Irvine put recovery time around 23 minutes per interruption. Batching is the workaround. This guide argues the workaround is no longer needed once Clone is doing the work.
Why is the Friday admin block 'dead'?
Because the cost it amortizes goes to zero with Clone. Batching exists to spread the 23-minute context-switch tax across many tasks of the same type. Clone has no context-switch tax: the Computer Agent reads the screen and types, and it can move from Gmail to QuickBooks to HubSpot instantly. Each handler runs in 30 to 90 seconds. The math that justified the block (one block of two hours is cheaper than fifteen separate two-minute interruptions) no longer applies, because Clone is the one doing the two-minute tasks, and you are not interrupted at all.
What replaces the block, concretely?
An event-driven queue, declared as memory/queues/admin.md on your Mac. Each line names a triggering event and the steps Clone runs the moment that event fires. The reference file in this guide has six handlers covering the five canonical batches a solo consultant runs: zoom_call_ended (CRM + transcript + followup), timesheet_synced every Friday at 5pm (invoicing), invoice_paid (thank-you + stage move), proposal_unanswered after 14 days (nudge draft), and you can add more. The whole file is twenty lines of plain English. No graph, no zap builder, no calendar event.
What does 'event-driven' mean if the timesheet is still pulled on a Friday?
Some events are intrinsic (a Zoom call ends, an invoice is paid). Others are wall-clock cadences disguised as events (timesheet_synced every Friday 5pm, end_of_week every Sunday midnight). The queue file handles both. The point is not that every event is real-time, the point is that you do not sit at a calendar block while these events are processed. The Friday 5pm sync triggers six invoice drafts that finish before you have packed up your laptop. You wake up Monday with an empty review queue or one or two holds.
How is this different from a Zapier zap on the same triggers?
Zapier requires per-app paid integrations, branching logic stored in a graph, and tasks measured in dollars per month. The typical solo consulting zap stack is 5 to 12 zaps and runs $30 to $75 a month before you have done anything. Each zap breaks when an app changes a UI or deprecates an event. Clone replaces the entire graph with a six-line markdown file and a Computer Agent that reads the screen. There are no API keys to manage, no integration tiers to upgrade into, and no graph to maintain. Switching CRMs is one line. Adding a tool is one line. The mechanism is described in src/components/architecture.tsx as 'tool agnostic by design'.
How is this different from hiring a virtual assistant?
A VA for solo consulting admin runs $300 to $1,200 a month part-time. Clone is $49 a month. Beyond cost, the latency profile is different. A VA gets your request Monday, asks for clarification Monday, starts Tuesday, finishes Wednesday. Clone runs the moment the event fires, in seconds, against your real apps. A VA is a great fit for judgment-heavy work like prospect research and outreach personalization. Clone is the right fit for the deterministic event handlers in the admin queue.
What happens when Clone is unsure about something?
It holds the action and queues it for your review. The reference admin.md file has explicit hold rules: 'hold for review if amount > $5000', 'hold if engagement is new', 'hold all if utilization < 50% for the week'. When a hold fires, Clone drafts everything but pauses on the held action and surfaces it in your review queue with the exact reason. You approve in one tap. The default thresholds are conservative. You loosen them per client as trust builds.
Can I run both schedules and event triggers in the same queue file?
Yes. The reference file in this guide mixes both. 'on: zoom_call_ended' is a real event. 'on: timesheet_synced (every Friday 17:00)' is a scheduled cadence written as an event. 'on: invoice_paid (Stripe / QuickBooks webhook)' is a real webhook. 'on: proposal_unanswered (>14d after sent)' is a derived event computed from your sent folder. Clone treats them all the same: a trigger condition and a handler block.
What are the actual apps Clone touches when handling these events?
On the input side: Zoom (or Google Meet), tl;dv, Fireflies, Otter, native transcripts. Calendly. Gmail (sent folder for proposal aging). QuickBooks or Stripe webhooks for invoice_paid. On the output side: Drive (for transcripts), HubSpot or Pipedrive or Folk or a Google Sheet (for the CRM), Gmail (for followups, nudges, thank-yous), QuickBooks or FreshBooks (for invoice drafts), Notion (for the accounting page or weekly retro). The list is in tech-tools-landscape.md in this repo. Anything that runs on your Mac is fair game because Clone drives it through screen reading, not through a paid API integration.
Will this actually free up the Friday block, or just move the work?
It frees it. The work moves from a two-hour block on your calendar to a series of 30 to 90 second background tasks Clone runs the moment their events fire. You see one or two holds in a review queue at the end of the day, and approving each takes around fifteen seconds. The math: if your old block was two hours and your new review work is two minutes, that is 118 minutes back per week, around 100 hours a year. Most consultants in our 21-day trial delete the calendar block entirely by week three. Track it for yourself in the first month before believing it.
What if I do not want to give Clone access to all those apps?
You scope the queue file. If you only want the followup handler running, write only that handler. Clone will only open Gmail and Drive, never your CRM or QuickBooks. Each handler is opt-in and lives as a separate block in the file. You can also stage rollouts: start with zoom_call_ended only, run it for two weeks, then add invoice_paid, then add timesheet_synced. The whole file is on your Mac and editable by you in TextEdit. There is no central dashboard or shared cloud config to lock you in.
How long until the queue is dependable enough to delete the calendar block?
Most consultants we talk to during the 21-day trial say two to three weeks. Week one you watch each handler fire and correct the small misses (Clone drafted the followup too long, Clone used last quarter's rate card, Clone cc'd the wrong assistant). Each correction is written back into memory/queues/admin.md as a rule. Week two the corrections drop to one or two. By week three the queue is producing the exact admin morning you would have hand-crafted, and the Friday block on your calendar is empty enough to delete. That convergence is the same observation-and-confirmation loop described in src/components/how-it-works.tsx step 03.
Other guides about the operational layer of a solo consulting practice
Keep reading
Consulting Admin Automation
The Monday 8am ritual file: timesheet, six invoices, cover emails, CRM updates, Friday retro, all in one markdown file.
Consulting Workflow Automation
How the entire engagement lifecycle, not just admin, gets declared in Clone ritual files and event queues.
AI Meeting Follow-up Emails
The followup handler in the queue, broken open: how Clone writes a followup in your voice the second a call ends.
Try it on one event
Write one handler. Watch the next call end. See the followup drafted in 48 seconds.
Install Clone. Open TextEdit. Write 'on: zoom_call_ended' and the three lines underneath. End your next client call. Watch Clone open Drive, log HubSpot, draft the followup. If it produced the work you would have done Friday, you already know.
$0/mo on Solo · data stays on your Mac · every action reversible