Matthew Diakonov

Published April 19, 202611 min read

Consulting business software, from inside the source

The consulting business software category is organized by tool. Your practice runs by client.

Every first-page guide lists 10 to 20 tools across 7 software categories: CRM, invoicing, project management, scheduling, transcription, docs, dashboards. None of them trace a single client from discovery call to paid invoice. Clone is the operator layer that runs that lifecycle out of one markdown file at memory/rituals/new-client.md, at $49/mo on Solo. The stack you already pay for stays where it is.

$49/mo on Solo. One file, one operator, the apps you already use.

4.9from 127 solo + boutique consultants

One operator across the 6 consulting functions in features.tsx

Reads memory/rituals/new-client.md for the full lifecycle

Drives QuickBooks, HubSpot, Gmail, Zoom, Sheets, Calendly

$49/mo on Solo. 21-day trial. No integration build.

Every "consulting business software" guide is a category grid

Flowlu's 12 picks. BigTime's 10 picks. Paperbell's 20 picks. Bonsai's 12 picks. Productive's 10+ picks. Teamwork's 10 picks. Wispa's roundup. BigContacts' 10 picks. Every one of them sorts consulting business software by category row: CRM here, invoicing there, proposals in the next section, scheduling after that. The reader is implicitly asked to buy one tool per row. A typical recommended stack lands at $300 to $1,000 per month depending on team size.

The unspoken assumption: you, the consultant, are the integration layer. You take the discovery-call notes out of Fireflies and paste them into a Google Doc to draft the SOW. You copy the fields from the SOW into PandaDoc. You create the HubSpot deal and link the envelope. You open QuickBooks and draft the deposit invoice. You open Gmail and write the kickoff note. The tools generate. The handoffs between them are your hands.

Clone is the missing row in that grid. Not a new consulting business software category, but the operator that drives all of them from one ritual file.

The category grid every "consulting business software" list repeats

CRM (HubSpot, Pipedrive)Invoicing (QuickBooks, FreshBooks)Proposals (PandaDoc, Qwilr, Bonsai)Scheduling (Calendly, Cal.com)Transcription (Fireflies, Otter, tl;dv)Project Mgmt (Asana, ClickUp, Teamwork)Docs (Notion, Google Drive)Dashboards (Sheets, Databox)Time tracking (Toggl, Harvest, Timely)Follow-ups (Mailchimp, Instantly)Client portal (HoneyBook, Copilot, Dubsado)Automation glue (Zapier, Make, n8n)

12 software rows. 7+ subscriptions. No single place that covers one client from discovery to deposit.

The anchor fact

Clone's source enumerates exactly 6 consulting functions

Open src/components/features.tsx in the website repo. Lines 13 through 62 define an array of six feature objects, one per consulting function: Receipt (Invoicing on autopilot), Users (Client onboarding in minutes), Microphone (Zoom calls to CRM, automatically), EnvelopeOpen (Follow-ups that feel personal), ChartLineUp (A dashboard you never had to build), Clock (Hours back every week).

Six functions. Every SERP "consulting business software" article maps each one of those six to a separate software category with a separate subscription: QuickBooks + HubSpot + Fireflies + Mailchimp or HoneyBook + Notion or Sheets + Toggl. Clone collapses all six into prompts against one ritual file at memory/rituals/new-client.md, driven by the Computer Agent layer defined in src/components/architecture.tsx lines 18 to 22 ("Reads the screen, clicks, types, scrolls").

The anchor: there is no "invoicing module" or "CRM module" inside Clone. There is one Computer Agent and one folder of markdown at memory/rituals/. The consulting functions are the contents of the ritual files, not the product's shape.

The unit that matters

A new client, traced across the whole lifecycle

The SERP lists stop at category comparison. Here is the thing they skip: one client, moving from discovery call to paid close, across the 7 apps the category grid recommends. Clone runs every step from one markdown file.

From discovery call to paid close in one ritual file

1
Discovery call
Fireflies transcript lands. Clone pulls the pain points, proposed scope, and price signal. Saves the transcript to the prospect's folder in Drive.
2
Proposal + contract
Clone drafts the SOW in Google Docs using your past SOW voice, fills engagement fields, pushes both into a PandaDoc envelope. HubSpot deal is staged 'proposal sent' with the envelope URL.
3
Signed + kickoff
PandaDoc webhook fires. Clone flips the HubSpot deal to won, sends invoice #1 from QuickBooks (50% deposit), books kickoff on Cal.com, emails the client the calendar invite and a welcome note.
4
Delivery
Every Zoom call transcribed to the deal record. Weekly status email drafted from the last call. Task list in Notion updated from decisions made on calls. Time-tracked work rolls up to utilization.
5
Close + retain
Final invoice out, closeout call booked, testimonial request drafted, case study stubbed into the pipeline folder, follow-up cadence scheduled for 90 days out.

The ritual file behind the lifecycle

Below is a copy-paste-ready memory/rituals/new-client.md. Roughly 36 lines. Trigger, apps_this_quarter mapping, engagement_fields (rate_model, default_rate, deposit_split), voice_examples pointing at two past SOWs and a kickoff email, and two action blocks: one for when the discovery call ends, one for when the contract is signed. Edit apps_this_quarter to match the tools you already pay for.

memory/rituals/new-client.md

One discovery-call trigger, six apps touched

The chat instruction that runs the new-client pass

One sentence into Clone. The Planner reads the ritual. The Computer Agent opens each app window in order. Six artifacts staged for review in about four minutes. Nothing sends until you approve.

Clone chat, after Acme discovery call

The handoffs the category grid never draws

Fireflies, HubSpot, PandaDoc, QuickBooks. Each row in a SERP list is a column here. The work is not the tools. The work is the messages between them.

End-to-end: discovery call to deposit invoice

Category stack vs. one operator on one ritual file

Same consulting engagement, two shapes for how it gets run.

A typical 'best consulting business software' article lists 10-20 tools grouped by software category. HubSpot for CRM. QuickBooks for invoicing. HoneyBook or Dubsado for proposals and portal. Calendly for scheduling. Fireflies for transcription. Notion for docs. Asana for PM. Zapier to glue the 7 above. Baseline monthly cost lands between $200 and $500 before you have run one client through the stack. The article never shows you a single Acme moving from discovery call to paid deposit. The handoffs between those 7 apps are the work, and the grid does not price them.

7 to 10 separate subscriptions organized by software category
$200 to $500/mo before any one client moves through the stack
Zapier or Make required to stitch category to category
The per-client handoffs (who retypes what into which app) are invisible

The 6 consulting functions, each a prompt

Every row below is a feature object from features.tsx. Every SERP article maps it to a separate software category and subscription. Clone runs it as a prompt against the ritual file.

Invoicing on autopilot

Clone reads your time tracker, applies the right rate per engagement, generates branded invoices in QuickBooks or FreshBooks, chases late payments with polite follow-ups you approve once. Works across hourly, retainer, and fixed-fee models. Handles late fees, partial payments, and multi-currency (features.tsx lines 15-20).

Client onboarding in minutes

Drop a signed proposal into a folder. Clone provisions the workspace, drafts the kickoff agenda, books the call, sends the welcome email, files everything in your CRM (features.tsx lines 22-28).

Zoom calls to CRM, automatically

Every client call gets transcribed, summarized, tagged by project, logged against the right contact. Integrates with tl;dv, Fireflies, Otter, or native Zoom (features.tsx lines 30-36).

Follow-ups in your voice

Clone drafts follow-ups using your voice and the context of the last conversation. Learns tone from past emails. Respects opt-outs and do-not-contact (features.tsx lines 38-44).

A dashboard you never had to build

Ask for a client health board and Clone assembles it from Sheets, CRM, and invoicing. Pipeline, utilization, outstanding invoices, upcoming renewals. Refreshed every morning (features.tsx lines 46-52).

36 lines

“I priced the 'best consulting business software' recommendation at $412/mo across 8 subscriptions. The actual consulting work was still me retyping the same client name and scope into each of them. Clone was $49/mo, one ritual file, and the retype stopped.”

paraphrased from a solo consultant's evaluation notes

Switching a tool in the stack is a one-line edit

apps_this_quarter is the only place Clone looks for which window to open. Switching from QuickBooks to FreshBooks (or Calendly to Cal.com, or HubSpot to Pipedrive) is a single line of markdown. No re-build inside a Zap. No re-onboarding of a new vendor inside Clone, because the vendor is not inside Clone.

Edit one line, next engagement uses the new tool

Clone vs. the consulting business software category

The category-grid articles are written for someone choosing between tools within a row. This table is written for someone deciding whether to add one more tool or to replace the glue between the tools they already have.

Feature	SERP category grid (HubSpot + QuickBooks + PandaDoc + Cal.com + Fireflies + Notion + Asana + Zapier)	Clone
How the list is organized	By software category. A row for CRM, a row for invoicing, a row for scheduling. Each row is a purchase decision. You're expected to buy one per row.	By client lifecycle. One memory/rituals/new-client.md file. Discovery -> proposal -> signed -> kickoff -> delivery -> close. No category, just a trajectory.
What happens between categories	Nothing automatic. The grid articles never describe it. In practice, a human retypes client name and scope into the CRM, the invoicing app, the proposal tool, and the docs folder. That retype is the consulting admin tax.	architecture.tsx lines 18-22: 'Reads the screen, clicks, types, scrolls'. The Computer Agent opens each app window in sequence and types the same fields across them. The retype is the machine's job now.
Number of subscriptions to evaluate	7 to 12 separate tools in a typical 'consulting business software' article (CRM + invoicing + proposals + scheduling + transcription + PM + docs + dashboards + portal + automation).	1. Clone. $49/mo on Solo. The 7-12 tools you already pay for stay where they are. Clone adds the operator, not another silo.
Cost baseline	$200 to $500/mo for the stack before you count Zapier/Make and any premium tiers. A small consulting firm often pays $300-$1,000/mo across the stack.	$49/mo on Solo. No per-task fees. No integration tier. Your existing stack is billed separately and unchanged.
What happens when you swap a tool	Re-onboard, re-build templates, re-export contacts, re-wire every Zap that pointed at the old tool. Weeks of work for any one swap.	Edit one line of apps_this_quarter in memory/rituals/new-client.md. 'invoicing: quickbooks' -> 'invoicing: freshbooks'. Next engagement uses the new tool.
Where engagement data lives	Spread across 7 to 12 apps, each with its own export format. Reporting requires stitching. A closed engagement has artifacts in HubSpot, QuickBooks, PandaDoc, Google Docs, Drive, Gmail, and Fireflies.	All artifacts still live in those apps. What Clone adds is the Memory layer (architecture.tsx lines 25-29) that logs which artifact came from which engagement, so a dashboard prompt assembles the client-by-client view across them.
Review and rollback	Depends on each tool. Most schedulers auto-send. PandaDoc sends on your click. Any misfire is a per-tool cleanup.	architecture.tsx lines 61-63: every action is logged and reversible, drafts staged before they send, roll back an entire morning of work with one click.
Versus a virtual assistant	A consulting VA runs $3,000 to $6,000/mo and works business hours. Ramp time is 2 to 6 weeks. A sick day or a resignation is an SOP transfer.	$49/mo, always on. Ramp is the time it takes to write a 36-line markdown file. Voice_examples inherit your habits. No SOP document needed because the ritual file is the SOP.
Versus Zapier, Make, n8n	Recipe builders for single-hop reflex automations. Require APIs/connectors on both ends and a graph of triggers and branches you build in their UI. Brittle when a vendor renames a field.	Plain English in chat, plain markdown for config, the apps' own UIs as the action surface. A Zap is 'when X then Y'. A Clone ritual is the whole new-client pass in one readable file.

From signup to a new client running through the ritual, in one afternoon

Paste the 36-line new-client.md into memory/rituals/

This page has the full file. Schedule, apps_this_quarter mapping, engagement_fields, voice_examples, and two action blocks (on-discovery-call, on-signed-contract). Edit the apps_this_quarter values for the tools you already pay for.

No schema, no GUI. If it reads like instructions to a human contractor, Clone runs it.

Drop 2 past SOWs and 1 kickoff email into /Drive/proposals/sent/

These are voice_examples. Two sent SOWs is enough to anchor tone, paragraph shape, and the fields you always fill. One kickoff email anchors your onboarding cadence.

Docx, markdown, or plain text. Clone reads what you give it.

Run the ritual on your next discovery call

Paste the chat instruction into Clone. Watch it open Fireflies, then Google Docs, then PandaDoc, then HubSpot, then QuickBooks, then Gmail. Approve each artifact.

First-run drift is normal. Fix the wrong stage name or the wrong folder path once in the ritual file, save, re-run.

Add on-signed-contract as a webhook and let the rest run

Once the PandaDoc webhook fires, the second action block runs: HubSpot deal to won, QuickBooks deposit invoice sent, Cal.com kickoff booked, client folder created. The lifecycle now moves without you.

Review gates on each send are on by default. Turn them off per-action when you trust the output.

0consulting functions in features.tsx, covered by one ritual file

0lines in memory/rituals/new-client.md, the whole lifecycle

0operator, instead of 7 to 12 category-listed software subscriptions

$0per month on Solo, vs. $200-$500/mo for the category stack

The numbers that matter for a consulting practice

Not vendor benchmarks. Counts you can verify in your own account and dollar deltas you can verify on your own bank statement.

functions in features.tsx, covered by one ritual

lines in memory/rituals/new-client.md

per month on Solo (pricing.tsx line 9)

avg ROI in first 30 days (features.tsx line 60)

“Every guide told me to buy another consulting business software. The reality was I already owned 9 of them. What I didn't own was the layer that could open Fireflies, then Docs, then PandaDoc, then HubSpot, then QuickBooks, then Gmail, in order, for one client. Clone was the only thing I bought in 2026 that reduced my stack instead of adding to it.”

Solo consultant, fractional-CMO practice

paraphrased from an onboarding interview

Bring your current consulting stack

Show us the 7 tabs your current client lives in. We'll write the ritual file live.

Pick the consulting business software you already pay for. On a 30-minute call we write your memory/rituals/new-client.md together, plug it into Clone, and watch the first artifacts stage in your real HubSpot, QuickBooks, PandaDoc, Cal.com, and Gmail. No roadmap slide, no upsell to another category tool.

Book a 30-minute call

The category every SERP grid skips. We name it on the call.

Twenty minutes together. We walk the consulting-software grid row by row and add the one category (local operator) every list forgets.

Frequently asked questions

Why do every 'consulting business software' list and this page disagree on the basic unit?

The SERP articles (Flowlu, BigTime, Bonsai, Paperbell, Productive, Teamwork, Wispa, BigContacts, Hello Bonsai, and others) organize around software category: CRM, invoicing, project management, scheduling, transcription, docs, dashboards, portal, automation. The grid has 10-20 rows and each row is a purchase decision. A consulting business, in practice, runs around one unit: a client engagement moving from discovery call to paid close. Clone is built around that unit. The configuration surface is one markdown file per ritual, not one subscription per category. That is why a page about consulting business software, written from inside the product source, ends up looking different from a listicle written from a reviewer seat.

What exactly does memory/rituals/new-client.md contain?

Roughly 36 lines of plain markdown. Shape: a trigger line (e.g., 'schedule: on-trigger (discovery call ends)'), an apps_this_quarter block mapping each function to whatever tool you currently use (calendar: cal.com, transcripts: fireflies, invoicing: quickbooks, and so on), an engagement_fields block (rate_model, default_rate, deposit_split), a voice_examples block pointing at 2 past SOWs and 1 kickoff email, and two actions blocks: actions_on_discovery_call (6 items) and actions_on_signed_contract (5 items). The full file is on this page, copy-paste ready. The same shape works for milestone rituals, renewal rituals, quarterly-review rituals, just different apps and actions.

Does Clone replace HubSpot, QuickBooks, PandaDoc, Cal.com, or Fireflies?

No. The Computer Agent layer in src/components/architecture.tsx lines 18-22 is described as 'Reads the screen, clicks, types, scrolls'. That layer opens each app the same way you do and types into the visible fields. Your HubSpot records, QuickBooks invoices, PandaDoc envelopes, Cal.com event types, and Fireflies notebooks all stay where they are. If you uninstall Clone, every one of those tools keeps running. Clone owns no client data. It is the operator, not the system of record.

How is this different from Zapier, Make, n8n, or Gumloop?

Zapier, Make, n8n, and Gumloop are recipe builders. You pick a trigger in tool A and configure one or more actions in tools B-Z through their UIs. They require an API or pre-built connector on each tool in the chain. They are strong for simple reflex automations ('when a new PandaDoc signs, post to Slack'). Clone is a different shape: plain English in chat, plain markdown for config, the apps' actual UIs as the action surface. Where a Zap is 'when X then Y', a Clone ritual is the whole new-client lifecycle in one readable file. Many consulting businesses run both: Zaps for simple A-to-B reflexes, Clone for the multi-app rituals that need judgment.

Does Clone replace a HoneyBook or Dubsado all-in-one?

No. HoneyBook and Dubsado are all-in-one client portals: they try to replace your CRM, invoicing, proposal, scheduling, and portal with one subscription. If you already use QuickBooks for tax-grade bookkeeping, PandaDoc for legally-reviewed contracts, HubSpot for pipeline, and Cal.com for scheduling, migrating into HoneyBook means re-exporting and re-onboarding all of them. Clone does the opposite: it leaves the best-of-breed tools in place and runs across them. If you run HoneyBook today, Clone can drive HoneyBook. If you run the separate-tools stack, Clone can drive the separate-tools stack. The choice of portal stays yours.

How is $49/mo possible when the SERP stack is $200-$500/mo and a VA is $3,000-$6,000/mo?

Clone is not replacing the stack. The $200-$500/mo category stack is yours, and you keep paying it. Clone is the single operator added on top. Pricing from the product's src/components/pricing.tsx: Solo $49/mo, Boutique $129/seat/mo, Enterprise custom. Solo is unlimited tasks, unlimited apps driven, local by default, with a 21-day free trial. Unlike a VA at $3-6K/mo, Clone runs 24/7 and does not need weeks of onboarding. Unlike adding a 12th category tool, Clone does not add a silo; it makes the 11 you have talk to each other.

Which tools does Clone drive well today?

Anything your Mac or PC can open a window for. Clone has been validated driving QuickBooks, FreshBooks, HubSpot, Pipedrive, Calendly, Cal.com, PandaDoc, DocuSign, Google Docs/Sheets/Drive/Gmail, Zoom with tl;dv/Fireflies/Otter, Notion, Slack. Because the Computer Agent uses screens and not APIs, tools with legacy UIs, custom Airtable bases, internal CMSes, or no public API work the same way. The limit is 'can you open it in a window and click through it'. The ritual file names the tool, Clone does the rest.

Where does the client data go? Is it sent anywhere?

Architecture principle 1 (architecture.tsx lines 46-50) is literal: Clone operates your desktop apps from your desktop, client files, emails, contracts, and transcripts never leave your computer, your engagements stay confidential by default. The HubSpot deal stays in HubSpot. The QuickBooks invoice stays in QuickBooks. The SOW PDF stays in your Drive. The Fireflies transcript stays in Fireflies. Clone does not host copies. The Planner layer may call a model to interpret your English instruction, but attached engagement content is not sent along with that call. Uninstalling Clone leaves every other tool intact.

What if I have a boutique team, not a solo practice?

src/components/pricing.tsx defines Boutique at $129/seat/mo. Shared client memory across the team, firm-wide playbooks and templates, role-based permissions, scheduled firm-level rituals, Slack/Teams notifications, priority support. The rituals become firm-wide shared files rather than per-person files. A partner writes the new-client.md ritual once; every associate uses it on their engagements. Team-level reporting rolls up across everyone's runs.

What exactly does 'review before send' look like for a consulting engagement?

review_before_send: true in the ritual file. When Clone runs the discovery-call actions, the SOW is a draft in Google Docs (not shared), the PandaDoc envelope is created but not sent, the HubSpot deal is at stage 'proposal sent' but the envelope url is attached for you to audit, the QuickBooks invoice is a draft (not emailed), and the kickoff email is a Gmail draft (not sent). You open each one, read it, edit, hit send or approve. Architecture principle 4 (architecture.tsx lines 61-63) is the backbone: every action is logged and reversible, preview drafts before they send, see every file touched, roll back an entire morning with one click.

What's the ROI a consulting practice actually sees in the first 30 days?

features.tsx lines 58-60 state it directly: solo consultants report reclaiming 10 to 15 hours a week within the first month, and the in-product average is 11x ROI in the first 30 days based on reclaimed billable hours at typical consulting rates. The reclaim is concentrated in the per-client handoffs the SERP grid skips: transcript -> SOW draft -> contract envelope -> CRM deal -> deposit invoice -> kickoff email -> welcome folder. That's 20-40 minutes of re-typing per new client, turned into 3-5 minutes of review.

Can I try this without committing to $49/mo?

Yes. Every plan starts with a 21-day free trial on Solo (pricing.tsx). Download Clone, paste the new-client.md ritual from this page into memory/rituals/, drop two past SOWs into your Drive, run it on your next discovery call. If the reclaimed time in the trial period isn't worth $49/mo, don't subscribe. The ritual file stays on your disk regardless.

One ritual file. One operator. The consulting stack you already have.

Copy the 36-line new-client.md from this page, edit apps_this_quarter for the tools you already use, drop two past SOWs into Drive, and run it on your next discovery call. $49/mo on Solo. 21-day trial. Your HubSpot, QuickBooks, PandaDoc, Cal.com, Fireflies, and Drive stay exactly where they are.

See pricing

One ritual file, your existing consulting stack. 21-day trial, $49/mo.

Book a call