Freelance marketing automation is one folder per client, not one Zapier graph and not a specialist to hire.

No. The SERP for freelance marketing automation is dominated by marketplaces (Upwork, Toptal, Fiverr, Truelancer) that sell you a $40 to $90/hr freelancer whose job is to build Zaps, Dubsado workflows, or ActiveCampaign automations for you. Clone is the opposite shape: a single $49/mo desktop app the freelance marketer uses themselves, which drives whatever marketing tools each of their clients already pays for. If you are looking for a body to hire, the SERP marketplaces are the right tool. If you are the freelance marketer and you want to stop re-building per-client integrations, Clone is the missing primitive.

It is the convention for a per-client marketing ritual file. About 23 lines of plain markdown per client. Each file has a client name, a schedule line (e.g., 'schedule: monday 09:00'), a chrome_profile line so Clone knows which browser profile to switch to, an apps_this_quarter block that maps each marketing function (newsletter, social_queue, visuals, campaign_log, crm, approvals_inbox) to whatever tool that specific client pays for, an audience_segments block referencing live lists in that client's CRM and email tool, a voice_examples block pointing at that client's past sends in your Drive, and an actions block listing what Clone should do every run. The Acme Roastery and Nexora SaaS examples on this page are copy-paste-ready starters. Same shape, five different client outputs.

Two layers of isolation. First, each client has a dedicated Chrome profile (the chrome_profile: line in the ritual file). Profiles have independent cookies, logins, extensions, and local storage. When Clone's Computer Agent switches from the acme-roastery profile to the nexora-saas profile, it has zero access to Acme's Mailchimp because that tab is not logged in. Second, the scope of every ritual run is the single client folder named in the chat instruction. Clone reads that folder's voice_examples, that folder's audience_segments, and logs every action against that folder's scope. Architecture principle 1 (architecture.tsx lines 46-50) is literal: Clone operates your desktop apps from your desktop, and confidentiality is the default. A misfire can't send Acme's newsletter copy to Nexora's list because the Computer Agent never had Nexora's Mailchimp in the active window.

No. It drives them. The Computer Agent layer in src/components/architecture.tsx lines 18-22 is literally described as 'Reads the screen, clicks, types, scrolls'. That layer opens each client's actual Mailchimp, types in the campaign editor, saves a draft. It does the same for Klaviyo, HubSpot, Buffer, ActiveCampaign, Later, and Canva. Your clients keep their own subscriptions, their own templates, their own segments, their own brand kits, their own historical campaign data. If a client fires you, they still have everything, and if they replace you with another freelance marketer, that marketer inherits every tool unchanged. Clone owns no marketing data. It is the operator, not the system of record.

The Upwork median rate for a marketing automation specialist is roughly $60/hr (ZipRecruiter brackets the range at $24 to $132/hr, Upwork narrows it to $40 to $90/hr). A 5-client build with per-client Zaps typically takes 20 to 40 hours upfront and 4 to 8 hours of maintenance a month per client as their tools change. That lands at $300 to $600/mo in specialist fees, plus you still own the graph inside Zapier's UI and pay Zapier's per-task tier on top. Clone is $49/mo flat regardless of client count, and the per-client configuration is a 23-line markdown file you edit yourself in under ten minutes. For a freelance marketer with 3 to 7 clients, the math almost always favors the folder-per-client shape.

No. The Computer Agent reads the screen and types into the visible UI. It does not call vendor REST APIs, does not request OAuth scopes, does not need a Klaviyo private key or a HubSpot developer app. It uses each tool the same way the client's team uses it — through the UI that's already logged into the correct Chrome profile on your Mac. That is why a client running a legacy Mailchimp account that predates the latest API tier, a custom Airtable base, or an internal CMS with no public connector all work the same way: if you can open it in a browser window, Clone can drive it.

Those are client-management CRMs built for freelancers. They replace your proposal tool, your contract signing, your client portal, your invoicing. They do not drive your client's Mailchimp or your client's HubSpot; they drive yours. They also impose their own client portal on your clients, which many freelance marketers don't want. Clone sits at a different layer: you can keep Dubsado for your own contract signing and still use Clone to operate each client's marketing stack. One freelance marketer's actual flow is often 'Dubsado for the business of freelancing + Clone for the work the business of freelancing sells'.

Copy the existing folder memory/rituals/clients/<existing>/ as memory/rituals/clients/<new-client>/. Edit the client name, the chrome_profile, the apps_this_quarter values, and the voice_examples paths. Create a new Chrome profile for that client and log them in once. Drop two past sends into their /Drive/clients/<new-client>/sent/ folder. Run the ritual once while watching. Fix any wrong segment name. Add the schedule line. Next week, client 6's drafts are waiting in their tools on the scheduled day. The 5 existing clients are untouched.

Edit one line in that client's marketing.md. apps_this_quarter.newsletter: mailchimp becomes apps_this_quarter.newsletter: klaviyo. Log that client into Klaviyo in their existing Chrome profile. Point voice_examples at any Klaviyo-sent campaigns if they exist; otherwise keep the existing voice_examples (tone is tone, not platform). Next run opens Klaviyo's campaign editor instead of Mailchimp's. The other 4 clients in the folder are not touched at all. No Zap rebuild, no re-onboarding inside a specialist's system.

The ritual file's apps_this_quarter block is arbitrary. For the Acme example on this page the functions are newsletter, social_queue, visuals, campaign_log, crm, approvals_inbox. Another client's ritual could add paid_budget: meta-ads-manager, seo_log: ahrefs, analytics: ga4, content_brief: notion. The rules are: if you can open the tool in a browser window, name a stable function for it in apps_this_quarter, and describe the action in plain English in the actions block, Clone can drive it. The ritual file is the contract. The tool list is whatever that client uses.

2 clients is already the break-even point against the SERP-recommended stack. Zapier Team ($69/mo) + Dubsado ($40/mo) + ActiveCampaign ($49/mo) = $158/mo before your time and before per-client build hours. Clone is $49/mo flat, regardless of whether you have 1 client or 10. The real lift kicks in at 3 to 5 clients, where the per-client integration rebuild cost becomes the dominant time sink and the folder-per-client shape starts compounding. New client = copy a folder, not a new Zap account.

Everything stays as a draft by default. Architecture principle 4 (architecture.tsx lines 61-63) is explicit: every action is logged and reversible, drafts are previewed before they send, you can roll back an entire morning of work with one click. The review_before_send flag in the ritual file defaults to true. Newsletter sits as a draft in that client's Mailchimp. Social posts sit as drafts in Buffer or Later. Campaign tracker rows are appended (reversible). Re-engagement emails are Gmail drafts. The client, or you on the client's behalf, approves each one. You can opt a specific low-risk action (like appending a stats row) out of the review gate if a particular client trusts it.

Each client's data stays in their own tools. Mailchimp data in Mailchimp. Klaviyo data in Klaviyo. HubSpot data in HubSpot. The voice_examples are in your own Drive inside that client's folder. The ritual file is on your own disk. Clone does not host a copy, and it does not aggregate data across clients. Architecture principle 1 (architecture.tsx lines 46-50) is literal: client files, emails, contracts, and transcripts never leave your computer. If a client asks for a data-processing agreement addendum, you can point at that principle and at the Chrome-profile isolation. Uninstalling Clone leaves every one of your clients' tools intact.