A post-sale-first bet on the consulting stack
Consulting workflow automation starts at "deal won," not at "cold click."
Every other playbook for this topic opens with cold outbound: Apollo, Clay, Instantly, Expandi, Lemlist. Clone ships six feature cards, and a case-insensitive grep for prospect, lead, outreach, outbound, cold, linkedin, or sales across the file those cards live in returns zero. The product is a deliberate bet that the consulting workflow you actually want automated is the half that runs after a proposal is signed.
The argument in one paragraph
The automation you actually need
runs after the contract is signed.
For a solo consultant, a week has two halves. The first half is finding clients: LinkedIn posts, cold email sequences, intro calls, discovery calls, proposals. The second half is delivering to clients you have already signed: invoicing them, logging their calls, drafting status updates, assembling dashboards, writing retros, chasing Net 30 that went Net 45.
The public playbooks for this topic almost all front-load the first half. They open with Apollo for databases, Clay for enrichment, Instantly or Lemlist for cadences, Expandi for LinkedIn. Those tools are genuinely good. They are also built around a prospect who has not paid you yet.
Clone is built for the other half. Every feature on the marketing site runs against a client who is already under contract. The next section is a grep you can reproduce in ten seconds that proves it.
The pre-sale stack Clone is not trying to replace
Twenty outbound products, zero of which Clone duplicates.
Every tool below is an excellent pre-sale specialist. The ones you are already paying for should stay in your stack. Clone runs on the other side of the signature page. A signed proposal is the event where the outbound stack hands off and Clone picks up.
The uncopyable detail
A grep of features.tsx for prospect, lead, outreach, cold, or linkedin returns zero matches.
Open src/components/features.tsx on the cl0ne.ai repo. Run the command below. Count the result. Zero. Now list the titles of the six feature cards (lines 16, 24, 32, 40, 48, 56). Every one of them is a ritual that runs against a client who has already signed. The product is not accidentally missing a lead-gen module; it is scoped on purpose.
The full feature array, with the post-sale tag on each card, makes the design stance explicit. If you want cold outbound, keep the tool you already use. Clone owns the six lines below.
The stat the whole argument rests on
0 pre-sale keywords in six feature cards.
Reproducible in ten seconds. Open src/components/features.tsx on the cl0ne.ai repo. Run the grep. The result is zero. The product is not a general consulting workflow automation tool aimed at the full funnel; it is a post-sale specialist that picks up at "deal won."
The six cards, expanded
Every feature Clone ships. Every one of them downstream of a signed proposal.
The two widest cards are the two heaviest ones in a typical practice: invoicing and the outcome metric. The four inner cards are the rituals between them. Read each one with a single question in mind: could this run against someone who has not paid me yet? The answer is no in every card.
Invoicing on autopilot
features.tsx line 16. Clone reads your time tracker, applies the right rate per engagement, generates branded invoices in QuickBooks or FreshBooks, and chases late payments with polite follow-ups you approve once. Handles hourly, retainer, and fixed-fee. Handles late fees, partial payments, multi-currency. Starts when a client has already signed.
Client onboarding in minutes
features.tsx line 24. Drop a signed proposal into a folder. Clone provisions the shared workspace, drafts the kickoff agenda, books the call on your calendar, sends the welcome email, and files everything in your CRM before your coffee is done brewing. The trigger is the signed proposal, not a cold lead.
Zoom calls to CRM, automatically
features.tsx line 32. Every client call gets transcribed, summarized by outcome, tagged by project, and logged against the right contact. Integrates with tl;dv, Fireflies, Otter, or native Zoom transcripts. The client is already on the call; the automation is the post-call write-up.
Follow-ups that feel personal
features.tsx line 40. Clone drafts follow-up emails for every active engagement using your voice and the context of the last conversation. Learns your tone from past sent mail. Respects your opt-outs and do-not-contact list. This is client retention writing, not cold outbound drip.
A dashboard you never had to build
features.tsx line 48. Ask for a client health board and Clone assembles it from your Sheets, CRM, and invoicing tool. Pipeline of active work, utilization, outstanding invoices, upcoming renewals, refreshed every morning. Reports live in Google Sheets or Notion.
Hours back every week
features.tsx line 56. Solo consultants report reclaiming 10 to 15 hours a week within the first month. Not because prospecting got faster; because the back office stopped eating the afternoon. Average ROI in the first 30 days: 11x based on reclaimed billable hours at typical consulting rates.
Where Clone sits in the consulting lifecycle
Inputs on the left. Same apps on the right. Clone in the middle, downstream of the signed proposal.
Each source on the left is either a committed client artifact (signed proposal, meeting transcript) or a signal about already- won revenue (accruing hours, live dashboards). The destinations on the right are the same apps you already use, updated on the same client who already signed. Clone is the middle layer that reads, writes, clicks, and summarizes across all of them.
Post-sale inputs, post-sale outputs, one chat in the middle
Four numbers, all sourced from the shipped code
The scope, stated in numbers.
Same Tuesday, two shapes
A Tuesday morning built on pre-sale automation versus a Tuesday morning built on post-sale automation.
Tuesday, 08:00 to 09:00. Same consultant. Two different stacks.
You open the laptop. Apollo is loading a 400-row prospect list. Lemlist is showing three bounces from yesterday's cadence. Expandi wants to know if you approved this morning's connection template. You spend 25 minutes on deliverability, 10 on a new variant, and 15 on a LinkedIn reply from a warm contact who never actually booked. At 09:00, your three active clients whose hours need invoicing are all still waiting, because you have not looked at that side of the business since 06:00.
- Deliverability dashboards open
- Three bounces to investigate
- A new variant to A/B
- Three active clients still not invoiced
- Billable hours lost to cold strangers
Minute by minute
What the post-sale half of a Tuesday looks like from 07:55 to 08:10.
The clock numbers below are the actual cadence. Every step is a concrete action against a client who already signed. Nothing in this list is a cold prospect; nothing in this list requires you to have loaded an outreach list first.
07:55 - Clients you already have, folder you already opened
Before the laptop is awake, you have three active engagements whose Friday hours landed in Timely overnight. No prospecting step. No LinkedIn tab. The list of clients is finite, signed, and on your disk.
08:00 - One sentence, no cold targets
You type into Clone: 'invoice all clients whose reconciled hours cover last week, log the send in HubSpot, draft a one-line thank-you in Gmail.' Three verbs, three tabs, zero prospects anywhere in the sentence.
08:02 - QuickBooks drafts three invoices
Clone drives your existing QuickBooks session, in the tab you already had logged in. It uses your rates, your templates, your branding. The drafts land in a review queue on your Mac, not in a vendor cloud.
08:04 - HubSpot notes, Gmail drafts
For each of the three invoices, Clone writes a HubSpot note against the right contact and drafts a Gmail thank-you in your voice. You approve, you send, it commits. architecture.tsx line 61, principle four: 'Always reviewable.'
08:06 - A Notion retro you did not schedule
The same ritual writes a Monday retro for each engagement in Notion. Hours delivered, open deliverables, the call you owe them this week. No new app opened. No outbound touched at any point in the ten minutes.
08:10 - You return to the work that actually bills
Ten minutes after 08:00, the entire post-sale admin block for three engagements is done. You open the slide deck that is due at 11:00 and start drawing. That is the bet this page is built on: the hours won come from the post-sale half of the workflow, not from automating strangers.
The onboarding ritual, step by step
One signed PDF triggers three staged actions, zero cold contacts in the loop.
The sequence below is the onboarding feature card (features.tsx line 24), drawn end-to-end. A signed proposal lands in a folder. Clone picks up the file event. Three staged actions land in your review queue. You approve. Every arrow below runs against a client who is already paying.
onboarding ritual: signed proposal to first welcome email
What three English sentences buy you
Three post-sale rituals, saved in under a minute of typing.
The session below is real, abbreviated. Three plain-English sentences save three rituals to local markdown files at ~/.clone/memory/rituals/. Each ritual fires on its own trigger: a file landing in a folder, a weekly clock, a weekly clock. No cold contact list is referenced anywhere.
Pre-sale-first category versus post-sale-first product
The two shapes of consulting workflow automation, row by row
Every row below is the same solo consultant, measured through two different tools on the same Tuesday.
| Feature | Pre-sale stack (Apollo / Clay / Lemlist / Expandi) | Clone (post-sale) |
|---|---|---|
| Where the automation starts | At 'a stranger opens an email.' Cold click, cold reply, cold call, cold LinkedIn accept. The first thirty days of any onboarding is spent loading prospect lists, writing sequences, and warming up domains. | At 'a signed proposal lands in a folder.' features.tsx line 24. The trigger is a paying client, not a stranger. The first ritual fires in the first five minutes. |
| What the tool holds in memory | A database of cold contacts, firmographic signals, email open/reply history, cadences by persona. Every row is someone who has not yet paid you. | Clients you already have. Their voice patterns, their templates, their SOW terms, their Zoom transcripts. architecture.tsx line 25: 'Clone Memory: your clients, voice, templates, history.' Every row is a relationship. |
| The dollar-value of one run | A reply. A booked discovery call. A cold reach that might convert someday. Revenue is probabilistic: thousands of sends for a handful of conversations. | One invoice sent, one onboarding ritual completed, one retro written. Every run closes a loop on revenue you already won. No probability tree between action and paid work. |
| What breaks when you switch apps | Your entire cadence graph. Every sequence, every variable, every trigger is re-wired when you swap Apollo for Smartlead or Lemlist for Woodpecker. | Nothing. architecture.tsx line 58: 'Clone adapts in the same conversation. No re-wiring required.' You can swap QuickBooks for FreshBooks mid-engagement; the next ritual just drives the new tab. |
| Where the client data lives | In the vendor cloud. Every cold email platform keeps a mirror of your prospects on their side for deliverability, scoring, and reporting. Any NDA'd engagement is a problem. | On your disk. architecture.tsx line 46: 'client files, emails, contracts, and transcripts never leave your computer.' Compatible with strict NDAs out of the box. |
| Typical monthly cost | $49 Apollo Basic, plus $30 Instantly, plus $99 Expandi, plus $495 Clay Growth, plus $79 Taplio, plus $10 Hunter. Stacked, a pre-sale-heavy automation practice runs $500 to $900 a month for one solo consultant. | $49 on Solo, flat. comparison.tsx line 179. Covers the six post-sale cards. No per-seat math, no per-prospect pricing. |
What is, and is not, in scope
The boundary drawn explicitly.
Every green item is a ritual Clone owns, anchored to a line in features.tsx. Every red item is deliberately out of scope; for those, use Apollo, Clay, Lemlist, Expandi, Taplio, or whatever you already pay for on the pre-sale side. Clone does not pretend to do both halves.
post-sale is in scope. pre-sale is not.
- Invoicing clients you have already signed (features.tsx line 16)
- Onboarding signed proposals into your workspace (line 24)
- Transcribing and logging post-sale Zoom calls to CRM (line 32)
- Drafting in-engagement and renewal follow-ups (line 40)
- Assembling a client health dashboard in Sheets or Notion (line 48)
- Compiling weekly retros per active client
- Writing audit log entries to markdown on your disk
- Cold email sequences, reply loops, domain warm-up
- LinkedIn outreach, connection drip, comment automation
- Lead scoring, enrichment waterfalls, firmographic lookups
- Meeting booking for cold discovery calls
- Territory management, account-based-marketing signal routing
Want the post-sale half of your Tuesday walked through on your actual stack?
30 minutes with the Clone team. Bring the two or three active engagements that eat the most admin hours and we will sketch the first three rituals on them live.
Questions from Reddit readers evaluating the post-sale-first bet
What is consulting workflow automation, phrased in one sentence?
Consulting workflow automation is the set of recurring tasks that move a signed client through engagement, delivery, reporting, and renewal without you clicking through six different SaaS dashboards. Most guides on this topic also drag in cold email and LinkedIn prospecting. Clone draws the line differently: the workflow starts when a proposal is signed. Everything before that, the prospect list, the cold cadence, the enrichment waterfall, is out of scope by design. The six feature cards in src/components/features.tsx are the whole product surface, and every one of them is a post-sale ritual.
Where can I verify the 'zero prospect, lead, outreach, cold, linkedin, or sales matches' claim?
Clone the website repo at github.com/ai-for-consultants (or open src/components/features.tsx on the shipped site), and run: grep -ciE 'prospect|lead|outreach|outbound|cold|linkedin|sales' src/components/features.tsx. The answer is 0. Every feature title is a post-sale ritual: Invoicing on autopilot, Client onboarding in minutes, Zoom calls to CRM automatically, Follow-ups that feel personal, A dashboard you never had to build, Hours back every week. The six lines where each title lives are 16, 24, 32, 40, 48, and 56.
Why is Clone not a workflow builder like Zapier, Make, or n8n?
Clone's how-it-works.tsx step 1 says it verbatim at line 20: 'No workflow builder. No drag-and-drop automations. Just type what you want, the way you'd ask a junior employee. Clone figures out which apps to open, which files to touch, and which data to pull.' That is the architectural difference. Zapier and Make ship a canvas where you wire triggers, branches, and fallbacks yourself. Clone ships a chat window where you describe the outcome. The Planner picks the apps per run, the Computer Agent drives them, and the Memory layer carries state between runs. You own no graph.
Why exclude pre-sale automation entirely? Isn't that half the consulting workflow?
It is half the reading list, not half the billable time. For a solo consultant with 25 billable hours a week (the number in the consulting-business-workflow.md revenue math, section 'Revenue Math (Solo Consultant)'), the hours that get consumed by admin are almost entirely post-sale: reconciling Timely to QuickBooks, pushing Zoom transcripts into HubSpot, drafting the weekly status update, chasing Net 30 invoices that went to Net 45. Those are the hours features.tsx line 56 promises back. Pre-sale is a different problem, solved by different tools (Apollo, Clay, Instantly, Expandi, Lemlist), and those tools are already good at it. Clone does not duplicate them.
Does this mean I have to use a separate tool for prospecting if I buy Clone?
Yes. Clone is deliberately silent on outbound. If you already run Apollo, Lemlist, or Taplio, keep them. If you run outbound by hand in a personal Gmail draft, keep doing that. Clone sits in the post-sale half of your stack. The moment a proposal is signed and lands in a folder, Clone picks up. Until then, your prospecting motion is unchanged. This is the same design stance as principle three on architecture.tsx line 56, 'Tool agnostic by design,' applied to the outbound half of the stack: keep the tool you chose for that job.
What happens the first time a new client signs?
The onboarding feature card at features.tsx line 24 is the first ritual. You drop the signed proposal PDF into a folder (Dropbox or Drive). Clone detects the file event, reads the proposal, and stages four actions: provision the shared workspace with your standard folder tree, draft the kickoff agenda in Docs, book the kickoff call on your calendar from the client's availability, and draft the welcome email in Gmail with your voice and your standard opening. All four staged actions land in a review queue on your Mac, not in a vendor cloud. You click approve; they commit. The trigger was a signed contract, not a cold stranger.
How does the dashboard feature work without me configuring a workflow?
features.tsx line 48 is the dashboard card. In plain English you ask Clone for a client health board. Clone reads your Sheets, your CRM (HubSpot, Pipedrive, Folk, whichever is open in your browser), and your invoicing tool (QuickBooks, FreshBooks, Wave), then assembles a grid in Google Sheets with one row per active engagement: hours delivered this week, pipeline stage, outstanding invoice balance, upcoming renewal date. It refreshes every morning via a ritual on a Monday 07:30 trigger. No workflow builder, no JSON schema, no per-column formula rule. You get one URL; pin it to your bookmarks bar.
Why is 'Follow-ups that feel personal' a post-sale feature instead of a pre-sale feature?
Reading features.tsx line 40 carefully: 'Clone drafts follow-up emails for every client using your voice and the context of your last conversation.' The word is 'client,' not 'prospect.' The context is 'last conversation,' which is a call that has already happened with someone who has already signed. This is in-engagement and post-engagement follow-up: after a status call, after a milestone, after a project close, before a renewal. It is not cold drip. The detail line on line 44 even names the behavior that confirms it: 'Respects your opt-outs and do-not-contact list.' That is relationship-management vocabulary, not outbound-campaign vocabulary.
How does this compare to a virtual assistant handling the post-sale work?
comparison.tsx line 188 prints the VA number verbatim: $3,000 to $6,000 a month, and that is for business-hours coverage only. A VA runs the same post-sale list that Clone runs (invoices, onboarding paperwork, CRM notes, retros) but pauses on weekends, sleeps overnight, and adds a human to the NDA circle of every engagement. Clone runs the same list on a trigger, on your Mac, for $49 a month on Solo. Also, the VA typically owns none of the six feature behaviors at the level of specificity Clone does (voice pattern learned from your sent mail, roll-back of an entire morning, dashboards assembled from your live Sheets). The VA is a general human; Clone is a post-sale specialist.
What if my consulting practice really does need pre-sale automation baked in?
Then pair Clone with a dedicated outbound tool and keep the two concerns separated. Apollo for the prospect database, Lemlist or Instantly for the cadence, Clay for enrichment, Taplio for LinkedIn content. Clone stays on the post-sale side. The handoff is the signed proposal that lands in your folder. That is the moment the responsibility crosses from your outbound stack to Clone. Keeping the two concerns separate is a feature, not a gap, because the memory model, the NDA surface, and the dollar-per-run math are all different between cold work and committed work.
What are the honest tradeoffs of starting automation at 'deal won'?
Three. First, if your practice is pre-product-market-fit and your bottleneck really is finding clients at all, Clone will not help with that; you need a prospecting motion first. Second, if your post-sale volume is low (fewer than three active engagements at a time), the ROI of $49 a month is real but small; the number gets big when active engagements exceed five. Third, Clone assumes you already have the back-office tools you like (QuickBooks or FreshBooks, HubSpot or Pipedrive, Notion or Google Sheets); if you are rebuilding your stack from scratch, you will want to pick those first, then drop Clone on top. None of these are dealbreakers. They are the tradeoffs of a post-sale-specialist bet.
How fast is the first post-sale ritual actually running?
Five minutes from download to first staged ritual. Install the .dmg, point Clone at an inference source (cloud LLM or a local Llama on an M-series Mac), type one English sentence, approve the first run. The onboarding ritual fires the next time a signed file lands in your folder. The Tuesday invoicing ritual fires next Tuesday at 08:00. The Friday retro ritual fires next Friday at 17:00. No OAuth carousel, no integration marketplace to wait on, no workflow canvas to paint.
Other angles on the same question
Adjacent guides for a consulting practice on the post-sale side
AI Tools for Consultants: Don't Grow the Stack, Operate the Stack
The operator-layer argument applied to the broader consulting stack. Read this for the grep-the-marketing-site flavor of the argument on this page.
Consulting Client Follow-Up Automation That Quotes Your Last Call
A deeper dive on the follow-ups feature card (features.tsx line 40), including how the voice pattern is learned from your sent mail.
Automation Consulting Services Ship Irreversible Work. Clone's Fourth Principle Is a One-Click Rollback.
The sibling page on Clone's fourth founding principle: Always reviewable. Read if you are comparing Clone to a traditional RPA engagement.