The CRM you pick is not the bottleneck. The 4.2 hours a week nobody types are.

No. Clone is not a CRM and I did not try to position it as one. Every first-page result for this keyword is a CRM product or a CRM shortlist page. My claim is more specific: the CRM choice itself is not your bottleneck as a solo consultant or boutique firm. Keeping any CRM current is. Clone's Computer Agent operates whichever CRM you already picked (HubSpot, Salesforce, Pipedrive, Monday, Scoro, Insightly, OnePageCRM, Zoho, or even an Airtable base you built in a weekend) by reading the screen and typing into the form fields a human would type into. architecture.tsx principle 3 is literal: 'Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.'

The honest answer, pulled from reading the top 10 SERP results cover to cover: it barely matters for a solo or boutique consultant, and it matters a lot more what your client workflow looks like. HubSpot's free tier is the safe default for most. Pipedrive is lighter and pipeline-first. Monday and Scoro are better if you need project management welded to CRM. Salesforce is overkill below 10 seats. OnePageCRM is the tightest single-consultant tool. Here is the part none of the shortlist pages admit: every one of them becomes a graveyard within 6 months if no one keeps it current, and 'no one keeps it current' is the default mode for solo consultants working 40+ hours of billable time a week. Clone is the layer that closes that gap, whichever CRM you land on.

Zapier needs you to configure triggers and branches ahead of time, and the connector has to exist; custom or legacy CRMs are usually scoped out. Zapier also sees your CRM as an API and breaks when the vendor renames a field. Clone does not build a Zap. It reads the CRM's UI with vision and types into the same form fields a human would type into. When HubSpot rearranges the Activity panel next month, the Zap breaks and a developer gets paged. Clone re-reads the screen on the next run; a moved button is still labeled Save. The differentiator is in the product's own comparison table: the row 'Works with custom or legacy apps' is checked for Clone and not checked for Zapier.

Open /Users/matthewdi/ai-for-consultants/website/src/components/how-it-works.tsx and read lines 61 through 76. You will see the exact recurring Monday 8am ritual that Clone runs in the product: Timely hours pulled, 6 QuickBooks invoices generated, emails sent, outreach logged in HubSpot, Friday retro drafted in Notion, 4.2 hours of admin completed while you were asleep. 'Logged outreach in HubSpot' is the CRM write every 'CRM for consulting' listicle pretends will happen on its own once you pick the right tool. Then read architecture.tsx lines 56 to 59 for principle 3 'Tool agnostic by design'. Those two blocks are the product's own case against the shortlist framing.

HubSpot has a call-logging feature that works well when the call is placed from HubSpot's own dialer or routed through their Zoom integration with specific setup. In practice, solo consultants use whatever dial method the client prefers and end up with transcripts in their Zoom cloud, a tl;dv folder, an Otter workspace, or a Fireflies account. features.tsx line 36 is specific: Clone integrates with tl;dv, Fireflies, Otter, or native Zoom transcripts, summarizes each call by outcome, tags by project, and logs the summary against the right CRM contact. None of the CRMs on the shortlist read an arbitrary Zoom transcript folder without a connector configured in advance. Clone reads the folder the way you would.

You update the English sentence and the tab Clone focuses. That is the entire migration. architecture.tsx principle 3 verbatim: 'Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.' In the 'CRM for consulting' category, this is the feature none of the shortlist pages can offer because the shortlist pages are about picking a vendor. Clone is about keeping whichever vendor current.

Yes. The 'Works with custom or legacy apps' row in the home-page comparison table is the one row where Clone checks and Zapier, HoneyBook, and most VAs all fail. Clone treats any app you render in Chrome as a valid target. An Airtable base is a list of cells; Clone reads the cells and types into the cells. Your 2014 internal CRM with no API is, to Clone, the same shape of target as Salesforce Lightning. The shortlist pages silently exclude these because the shortlists rank off-the-shelf vendors.

Pricing.tsx line 18 lists 'CRM + invoicing integrations' as a Solo feature, but the literal behavior is broader. The $49 covers unlimited plain-English tasks, the Computer Agent that drives whatever CRM you already have, voice learning from your past emails so Clone's updates match your tone, and scheduled recurring rituals so the Monday 8am run happens without you. There is no CRM module to unlock and no per-CRM-connector fee; the subscription pays for one agent that drives whatever app is in front of it.

Yes, on the Boutique plan ($129/seat/mo). Pricing.tsx line 34-42 covers shared client memory, firm-wide playbooks, role-based permissions, and usage analytics. The ritual file for CRM hygiene becomes a team artifact: everyone's Monday morning runs the same shape of update, against the same CRM, with the same Next Step conventions. The fix for a consulting firm's 'our CRM is a graveyard' problem is not to buy a better CRM; it is to buy back the hours that were supposed to maintain the current one.