You can't automate a consulting workflow without new software by buying smarter software. The mechanism has to change.

Most claim to, but the claim hides a category split. iPaaS tools (Zapier, Make, n8n) connect to your apps over APIs, but the daily flow happens inside their builder, their dashboard, their alerts. You log in to Zapier every time something breaks. You learn Zapier's branching language. Suites (HoneyBook, Dubsado, Bonsai) replace pieces of your stack outright. A virtual assistant uses your apps but on a person's clock. The category that genuinely doesn't add a new daily app is screen-driving software that runs in the background and operates the apps you already had open. The phrase 'without new software' only has one honest answer in that sense.

Zapier IS new software in the way that matters. You sign up for it. You learn its trigger-and-action vocabulary. You build Zaps in their canvas. You log in to the dashboard when something breaks. You pay them every month. If you cancel, every workflow you built dies. The fact that the data flows into Gmail or HubSpot at the end doesn't change that the workflow lives inside Zapier's product surface. The same is true of Make and n8n. They're better than buying a suite, but they are still net-new tools you maintain forever.

Screen-driving. The agent runs as a background process on your computer. When an event fires (an inbound email matches a phrase, a calendar time hits, a deal stage moves), the agent opens the app you already have, reads what's on the screen, types into the form fields, and clicks the button you would have clicked. It uses the same Gmail account you check every morning, the same HubSpot workspace your contacts live in, the same QuickBooks file your accountant uses. The instruction lives in a plain text file you own. Clone's architecture.tsx labels this layer the 'Clone Computer Agent' with the sublabel 'Reads the screen, clicks, types, scrolls.'

Two big differences. First, the trigger surface. A Zap needs a clean event that fires on an API webhook (a button click, a calendar event, a Stripe payment). Screen-driving can fire on content (a phrase in a Gmail thread, a number in a Zoom transcript, a paragraph in a SOW). Most consulting workflow events are content events, not API events; that's why Zaps tend to break on the most useful triggers. Second, the daily surface. A Zapier graph asks you to log into Zapier when something breaks. A screen-driving agent has no separate dashboard you have to learn. The 'config' is a markdown file in a folder on your machine.

Three places. (1) Your data lives in your apps, not Clone's database. There is no Clone database. The instruction files live in a folder on your machine (~/.clone/memory/) and you can delete them or read them in TextEdit. (2) Your accounts are your accounts. Clone signs in to Gmail, HubSpot, and QuickBooks the same way you do, with your credentials, in your browser session. Cancel Clone tomorrow and your accounts still have everything: contacts, notes, invoices, threads. (3) The architecture file labels the legend explicitly. Three layers (Planner, Computer Agent, Memory) are tinted as 'Clone layer (removable).' Three layers (You, Your Apps, Your Business) are tinted as 'Your existing stack.' The diagram is what ships on the homepage.

You want them where they exist and work. Screen-driving doesn't reject APIs. It uses them when they're cleaner (a Stripe webhook on payment is fine; a HubSpot deal stage move is fine). It falls back to the screen when the API can't see what you can. Most consulting events are in the latter category: a milestone signoff phrase appears in an email, a proposed amount is mentioned in a Zoom transcript, a SOW expected number is in a Drive doc. APIs don't see those. The screen does. The honest line is: prefer the API when it works, and have a screen-driving fallback for the events your APIs miss.

Yes. This is the row in Clone's comparison table that quietly fails on iPaaS: 'Works with custom or legacy apps.' Zapier needs a published API. So does Make, so does n8n. If your client has a 2014-era practice management portal, an internal Salesforce instance with custom objects, a niche bookkeeping tool with no public API, or any browser-based app at all, an iPaaS can't reach it. Screen-driving can. The agent treats every app the same way: it reads the screen, types into fields, clicks buttons. Custom and legacy apps look exactly the same to it as Gmail does.

Realistic timeline: install Day 1, one instruction file Day 2, watch it run on Day 3, edit the file as your style changes from Day 4 onward. The first instruction file most consultants write is post-call admin: when a Zoom call ends, summarize the transcript, log the contact in HubSpot, draft a follow-up email in Gmail. That single file pays back inside the first week. By week four, most consultants have four or five files, each closing one recurring loop. None of those days involve learning a new dashboard, migrating any data, or signing into a new tool other than the Clone background app itself.

Clone is $49/month for solo, $129/seat for boutique firms, free 14-day trial without a credit card. Zapier is $49 to $599/month depending on volume and apps. HoneyBook is $39 to $129/month and replaces pieces of your stack you didn't ask to replace. A part-time virtual assistant is $3,000 to $6,000/month and works on their clock, not yours. The cost compounds differently: with iPaaS or a suite, you're paying for a tool you log into. With screen-driving, you're paying for a background process. The marginal hour cost on the four or five fuzzy-trigger loops in a typical practice is roughly 50x lower than a VA, and the daily friction is roughly zero, since there's no new daily surface to learn.

Pick one recurring task that has been costing you time, then write one plain English instruction file for it. Post-call admin is the canonical first one because it fires several times a day and the win is visible inside 24 hours. The instruction file looks like a memo: 'When a Zoom call ends, read the transcript. Find the action items. Log the contact note in HubSpot. Draft a follow-up in Gmail using my voice from the last five emails I sent to this person. Send me a Slack DM with the draft.' Save the file. The next call closes the loop end to end without you opening a tab you weren't already going to open.