A small consulting firm has no CRM admin. The bottleneck is not the seat price. It is the partner hours every week.

Honest answer by firm size. Solo consultant: HubSpot free tier or Capsule Starter, both adequate contact databases. 2-to-5 person firm: Copper if your work lives in Gmail, Pipedrive if you want the best pipeline UI, Capsule if you want lightweight and small-firm-first, HubSpot Starter if you want the largest ecosystem. 5-to-10 person firm: Productive or BigTime if you want delivery state baked in, HubSpot Professional if you have the ops seat to configure it. None of these stick for more than 18 months on their own for a firm without a CRM admin. The firms that keep any of them alive past year two run a weekly hygiene ritual on top, whether that is Clone at $49 a month, a virtual assistant at $3K to $6K a month, or the partner's own unbilled hours.

No CRM admin seat. Every ranking page assumes someone configures the pipeline, cleans duplicates, enters activities, updates stages, and trains the team. For a 3-partner boutique, that someone is a partner billing $150 to $350 an hour. The first four weeks are fine because the partner is still enthusiastic. By week eight, they have 40 hours of billable work and a Zoom transcript folder with 30 un-logged calls. The CRM stops being current, which means it stops being useful, which means it gets opened less, which accelerates the decay. This is not a feature problem. It is a time-per-week problem, and the ranking pages do not grade on it.

Open /Users/matthewdi/ai-for-consultants/website/src/components/comparison.tsx. The rows array starts at line 6 and ends at line 77. There are 10 rows. Row 10, 'Set up in under 10 minutes', starts at line 70. Clone is marked check. Zapier is marked x. HoneyBook is marked x. Virtual VA is marked x. This is the only row in the entire file where Clone is the sole check and all three alternatives are x. Every other row has at least one other check. That means this is the single competitive claim Clone's own comparison page treats as the whole argument, and it happens to be the one row that matters most for a firm of 1 to 5 people with no ops seat.

No. Clone is not a CRM, does not have a contact database, does not have pipeline stages, and does not try to replace any CRM you are currently evaluating. Clone is a Computer Agent, per architecture.tsx line 19: 'Reads the screen, clicks, types, scrolls.' It operates whichever CRM you already picked. This guide exists because every ranking page for this topic answers the seat-price question for a small firm, and none of them answer the hygiene-hours question the small firm should actually be asking.

A four-sentence markdown file at rituals/crm-keepalive.md. The sentences are English, not YAML. Example, verbatim: 'Every Monday at 9 AM, read the transcripts folder for last week's calls. Match each transcript to the right engagement by calendar and email. For each match, write a 200-word outcome summary and a real next step in Capsule. Then rebuild the client-health board in Sheets from Capsule, Timely, and QuickBooks.' That is the whole configuration. Change the CRM name to switch targets. There is no pipeline stage wizard, no custom field mapping, no trigger-action grid, no OAuth consent carousel. comparison.tsx row 10 is an engineering claim and the ritual file is how it is cashed out.

Pricing first. Virtual VA: $3,000 to $6,000 a month, per comparison.tsx monthly cost row, which is typical for a US-based part-time VA doing CRM work. Clone Solo: $49 a month. That is a 60x to 120x cost delta, with two operational differences. First, the VA takes weekends off and goes on vacation; Clone runs on whatever schedule the ritual file describes, including Saturday mornings. Second, the VA requires SOPs written in a Google Doc, onboarding time, and ongoing quality review; Clone's SOP is the four-sentence markdown file above, which is also the whole config. Neither wins outright. A good VA is better at judgment calls; Clone is better at throughput and cost.

Zapier monthly cost per comparison.tsx: $49 to $599. Close to Clone on price. The difference is what the shortlist does not price: the hours a partner spends configuring the Zap. A typical 'Zoom call to Capsule activity' Zap is 11 steps: webhook trigger, filter by duration, lookup contact, format summary, create activity, create next-step task, handle errors, version the template when Capsule changes a field name. For a firm with one such Zap, fine. For a firm that needs Zoom to Capsule and tl;dv to Capsule and Otter to Capsule and Gmail to Capsule, that is four separate Zap trees. Clone's comparison.tsx row 3 ('No workflow configuration') grades this. Clone checks. Zapier x.

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 operational terms, you change the word 'Capsule' to 'Pipedrive' in the ritual file. That is the migration. The pipeline stages, custom fields, and activity types in the new CRM are whatever Pipedrive ships out of the box. Clone types against whatever is there. The ritual file is the durable artifact; the CRM tab is the replaceable one. For a small firm that changes CRM roughly every 18 to 24 months, this inverts the usual lock-in dynamic.

First-class support, per comparison.tsx row 4: 'Works with custom or legacy apps'. Clone checks. Zapier x. HoneyBook x. Any app you can render in a Chrome tab is a valid target: your 2019 Airtable pipeline base, your 'Clients.xlsx' Google Sheet, your Notion database with relation rollups, your self-hosted SuiteCRM install. Clone reads the screen and types. This is the row shortlists quietly exclude because their thesis is to rank named vendors, and 'the spreadsheet we built ourselves' is not a vendor.

Minute 1 to 3: install Clone on your Mac or PC. Minute 3 to 6: open the CRM tab in Chrome and let Clone see it once, so the Computer Agent learns the screen layout. Minute 6 to 9: write the four-sentence ritual file, save it to rituals/crm-keepalive.md. Minute 9 to 10: run clone ritual --file rituals/crm-keepalive.md once to verify it drives the CRM correctly. By minute 10, the ritual is working and scheduled. What it does not include: pipeline stage design, custom field mapping, OAuth carousels, Zap trees, virtual assistant onboarding. These are the steps every other option on comparison.tsx requires, which is why three of the four columns score x on this row.