What does 'marketing automation consulting' usually deliver, and how is Clone different?+
A traditional marketing automation consulting engagement hands you a workflow configured inside a vendor's UI. A Marketo smart campaign. A HubSpot workflow. A Pardot engagement studio graph. An ActiveCampaign automation. The consultant writes a runbook PDF that describes what they built, walks the ops team through it, and then leaves. The spec lives behind the vendor login. If you can't open Marketo Admin, you can't read the deliverable. Clone changes the deliverable shape. The consultant writes a ~25-line markdown file at memory/rituals/marketing/<ritual>.md that describes the segment, the emails, the branch logic, the CRM mapping, and the schedule in plain English. Clone's Computer Agent (architecture.tsx lines 18-22) executes that markdown by driving Marketo or HubSpot or Pardot through the UI the same way a human operator would. The runbook IS the ritual file. The consultant can leave and any ops team member who can open a text editor can read the entire campaign.
Does this mean the consultant skips Marketo, HubSpot, or Pardot entirely?+
No. Your clients keep their existing marketing automation platform. Clone drives it. The Computer Agent layer in architecture.tsx lines 18-22 reads 'Reads the screen, clicks, types, scrolls'. It opens Marketo the same way a marketing ops person does, builds the smart list, drafts the email, saves to the program. The ritual file's 'tool: marketo' line tells Clone which vendor to drive. Your Marketo subscription, your templates, your program history, your SFDC sync, all stay in place. Clone does not replace Marketo. It replaces the irreproducible human knowledge about what is supposed to happen every Monday at 09:00.
What is in memory/rituals/marketing/<ritual>.md, exactly?+
About 25 lines of plain markdown per campaign. The shape is a ritual name, an owner, a schedule line (e.g. 'schedule: monday 09:00 PST'), a chrome_profile line, a segment block with the filter rule in readable boolean form, one block per email (template, subject, voice reference), branch conditions (email_2_if_opened, email_2_if_not_opened), an on_click block with the CRM campaign and status update, and an actions block in plain English. A reactivation campaign, a lifecycle program, a lead-scoring redesign, a weekly report ritual all fit this shape. The Q2 reactivation example on this page is copy-paste-ready. The handoff deliverable at the end of a 12-week engagement is a folder of 5 to 10 of these files.
Who actually writes the ritual file, the client's marketing ops team or the consultant?+
The consultant writes the first draft during discovery. That's the whole point of being a marketing automation consultant: they know what a reactivation sequence looks like, which thresholds work, which vendor quirks to avoid. The difference is the artifact they leave behind. Instead of a locked Marketo smart campaign plus a 40-page PDF, they leave a 25-line markdown file the ops team can read in five minutes. The ops team owns it from day one. Once the retainer ends, they edit it themselves, add the next campaign by copying an existing file, and the consultant's agency is not a dependency for minor changes.
How does this handle Marketo tokens, custom fields, and SFDC sync quirks?+
The ritual file names them explicitly. Every token the campaign uses (e.g. {{company.name}}) is listed in the email block. Every custom SFDC field the campaign depends on is named in the on_click block. Clone's Computer Agent reads those references and drives the Marketo UI to set them up. If the token fails silently because a lead has no company, the ritual file has a 'token: fallback' line and the behavior is explicit in text instead of buried in a flow step. The anti-pattern this solves is the 'consultant left and nobody knew that mkto_last_engaged_c existed' problem.
What happens if the business switches from Marketo to HubSpot (or any vendor swap)?+
Architecture principle 3 in architecture.tsx lines 55-58 is literal: Clone is tool agnostic by design. You edit one line per ritual file: 'tool: marketo' becomes 'tool: hubspot'. Log the shared Chrome profile into HubSpot. Re-run. The Computer Agent now drives HubSpot workflows instead of Marketo smart campaigns. The segment logic, email content, voice references, branch conditions, and CRM mapping in the ritual file are unchanged. The usual six-figure re-platforming quote for 5 campaigns becomes a 5-line edit across 5 files, plus the one-time Chrome profile login.
How is the marketing automation consulting engagement priced when the deliverable is markdown?+
Same hourly or retainer pricing the consultant already uses. $150 to $300/hr, 12-week engagements at mid-market, six figures all-in. The consultant's hourly rate reflects judgment, campaign design experience, vendor expertise, and accountability for outcomes. None of that changes. What changes is the unit-economics of the handoff. A ritual file is faster to write than a Marketo smart campaign + a 40-page runbook PDF, because the runbook IS the ritual file. Consultants who move to this shape report delivering more campaigns per retainer week.
What is the role of the $49/mo Clone subscription in the engagement?+
Clone is the runtime that executes the ritual files. The consultant designs the campaigns and writes the ritual files. The client pays $49/mo on Solo (or an appropriate team tier for multiple operators) for Clone to fire the rituals on their Mac. Your existing Marketo, HubSpot, Pardot, or ActiveCampaign subscription stays on its own tier. Clone does not replace any of them. It is the scheduler plus Computer Agent that reads the markdown file and drives the vendor UI. Comparable in role to a Marketo program scheduler, except the program definition lives on your disk.
Does Clone need API access or OAuth scopes into Marketo, HubSpot, or Salesforce?+
No. The Computer Agent drives the visible UI. It does not call Marketo's REST API, does not request a HubSpot developer scope, does not need a Salesforce Connected App with custom OAuth. It uses each tool the same way the marketing ops team uses it, through the logged-in browser tabs in the shared Chrome profile. This is why ritual files work for clients on legacy Marketo accounts with deprecated API tiers, for clients on SFDC orgs with locked-down Connected Apps, and for clients using niche CRMs with no public integration. If you can open it in a Chrome tab, Clone can drive it.
How does this compare to hiring a HubSpot Platinum Partner or a Marketo Engage Partner?+
Those partnerships certify the consultant on a single vendor. The engagement is good while the client stays on that vendor, and it encodes every campaign inside that vendor's UI. The partner's value is expertise in one stack. Clone does not replace the partner. It changes the artifact the partner ships. A HubSpot Partner engagement that ends with a folder of ritual files instead of a vendor-locked workflow graph makes the client less dependent on any future HubSpot Partner (including the one they just hired). Some partners see that as a risk to their renewal pipeline. Others see it as a sharper sales pitch: 'the work I ship is readable, portable, and survives a platform swap'.
What happens on day 91 when the retainer ends?+
The ops team opens memory/rituals/marketing/ in their text editor. Every campaign is one file they can read in five minutes. They change a subject line. They edit a wait step from 3 days to 2. They copy q2-reactivation.md as q3-reactivation.md and change the segment rule. Monday 09:00 arrives and Clone fires the edited ritual. No agency ticket. No runbook-PDF scavenger hunt. No Marketo Admin role required to see what the consultant built. The spec is on your disk, in text, and the Clone runtime that executes it is $49/mo flat.
Does this apply only to email, or to social, paid, SEO, and analytics too?+
The ritual file's 'tool:' line is arbitrary. The Q2 Reactivation example uses tool: marketo. A social posting ritual can use tool: buffer or tool: sproutsocial. A paid ads budget review ritual can use tool: google-ads or tool: meta-ads-manager. An SEO reporting ritual can use tool: ahrefs and tool: ga4. The rule is: if the tool opens in a browser tab, Clone can drive it, and the consultant can ship the ritual as markdown. One marketing automation consulting engagement typically touches email + social + attribution + reporting. The handoff is still one folder.
Is everything staged as drafts, or does Clone auto-send on the client's behalf?+
Drafts by default. The review_before_send: true line in every ritual file defaults to true. 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. Clone builds the Marketo smart list, drafts the email, stages the SFDC sync, appends the stats row. Nothing sends until the named reviewer in the ritual clicks Approve inside Marketo. A specific campaign can be opted into auto-send if the client trusts it (e.g. weekly internal report emails), but the default is human-in-the-loop.
Where does the marketing data actually live? Is Clone a system of record?+
No. Every campaign's data lives in its original vendor. Marketo leads in Marketo. HubSpot contacts in HubSpot. Salesforce records in Salesforce. Gmail sent items in Gmail. Architecture principle 1 (architecture.tsx lines 46-50) is literal: Clone runs on your machine, client files and emails and transcripts never leave your computer. The ritual files are on your disk. The voice folder is in your Drive. Clone does not host a copy of any campaign data. Uninstall Clone and every vendor and every piece of client data is still where it was. The ritual folder is the only thing that leaves with the consultant at the end of the engagement, and it leaves with you, not with them.