Twelve consultants. The same CRM. Twelve different shapes of activity log.

No. Clone is not a CRM and we do not position it as one. Every shortlist that currently ranks for this topic recommends a vendor: Salesforce, HubSpot, Pipedrive, Insightly, Zoho, Scoro, Monday, Dynamics. Our position is that the choice between those is real but secondary at firm scale. Once the firm has bought one (or three, across practices), the failure that compounds over 18 months is dialect drift across consultants. Clone's Boutique tier sits on top of whichever CRM the firm already picked and ships shared client memory, firm-wide playbooks, and scheduled firm-level rituals (pricing.tsx lines 35, 36, 39 verbatim). The CRM still belongs to Salesforce or HubSpot. The hygiene layer belongs to the firm's playbook file.

It depends more on the practice mix than the vendor capabilities. Salesforce wins for firms with 25-plus seats, complex pipeline geometry, and an admin willing to maintain Lightning. HubSpot wins for 5 to 25 seats that want to start free and grow into Sales Hub. Pipedrive wins for boutique firms whose work is genuinely pipeline-shaped. Scoro and Insightly win when project management is welded to CRM. Dynamics 365 wins inside Microsoft-aligned shops with existing E5 licenses. The honest part the shortlist pages do not write: every one of these becomes a graveyard within twelve months in a firm where consultants type differently and nobody enforces shape. Clone is the layer that closes the gap on whichever vendor wins for your firm.

Pricing.tsx lines 28-46 lists it verbatim: $129 per seat per month, everything in the Solo tier plus shared client memory across the team (line 35), firm-wide playbooks and templates (line 36), role-based permissions (line 37), usage analytics and reporting (line 38), scheduled firm-level rituals (line 39), Slack and Teams notifications (line 40), and priority support (line 41). The relevant trio for the topic of this page is line 35, line 36, and line 39: shared memory, the playbook, and the schedule. Together they are the mechanism that makes 12 consultants on the same CRM produce the same shape of record.

Open /Users/matthewdi/ai-for-consultants/website/src/components/pricing.tsx and read lines 28 through 46. That is the Boutique tier definition, in the product source. Then open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and read lines 60 through 64. That is principle 4, 'Always reviewable', verbatim: 'Every action Clone takes is logged and reversible. Preview drafts before they send. See every file it touched. Roll back an entire morning of work with one click if you need to.' Those two blocks are the whole argument. The Boutique tier provides the mechanism (shared memory, playbook, schedule). Principle 4 provides the governance (logged, reversible, auditable per seat). Together they answer the question every vendor shortlist page does not name: how does a 12-seat consulting firm produce one shape of CRM record across all 12 seats.

Yes, and this is exactly the case the playbook architecture is built for. The ritual file is plain English, not vendor-specific. It says: 'open the deal record in our CRM, log a Call activity with these fields, set the stage gate to one of these enums.' On the 8 HubSpot seats, the agent focuses HubSpot in Chrome and types into HubSpot's Activity panel. On the 4 Salesforce seats, the agent focuses Salesforce Lightning and types into Log a Call. The shape of the record is identical because the spec is identical. The pipeline review query joins HubSpot and Salesforce data in whichever BI tool the firm uses (Sheets, Notion, Airtable) and the shape lines up. architecture.tsx principle 3 names exactly this: 'Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.'

The SOP is the same idea. The enforcement mechanism is the difference. A traditional CRM consulting engagement produces a beautiful SOP document, a Salesforce admin builds Validation Rules and Flow Builder logic to enforce parts of it, and the consultants on the firm follow the rest by hand. The hand-followed parts drift within a quarter. With Clone's Boutique tier, the SOP is the executable playbook. There is no 'consultants follow this by hand' step. The agent reads the transcript, opens the CRM, and types into the form fields the way the playbook says, every time. The rollback is logged. The audit is automatic. There is no enforcement gap.

It handles whatever you specify, because the playbook is plain English. The example file in this guide tells the agent to populate a custom field called 'stage gate' with one of five enums (pricing, scope, legal, exec-buy-in, signed). The agent will set that field on every record the firm produces. If next quarter the firm adds a sixth enum or a second custom field, the partner edits the markdown file and the next run follows the new spec. The agent does not depend on a vendor-specific schema; it reads the form fields visible in the CRM UI and types into them.

architecture.tsx principle 4 is the governance line. Every action is logged with the exact fields written and the exact tab focused. The managing partner (or any seat with the right role permission per pricing.tsx line 37) can preview the draft, see the file it touched, and roll back the entire morning if needed. In a vendor shortlist world, the equivalent would be a Salesforce Setup audit trail plus a manual revert by an admin. With the Boutique tier, the rollback is a one-click action against an action log the firm owns.

Probably yes, and pricing.tsx lines 47-66 names what changes: on-prem or private cloud deployment, bring-your-own-LLM (local or private), SOC 2 Type II and audit logs, SSO and SCIM provisioning, custom integrations, a dedicated success engineer, and procurement and security reviews. The Boutique playbook architecture is the same. The deployment shape and the security posture is what changes. For a regulated 30-seat firm with sensitive client data, the Enterprise tier is built for procurement to approve and for InfoSec to sign off. The CRM hygiene mechanism described in this guide is identical at both tiers; the firm just decides whether the agent runs in shared cloud or in their own VPC.

The CRMs the firm already owns. The records that were typed in. The ritual file (it is just markdown, the firm authored it). The audit log up to cancellation. What stops happening is the agent runs. The firm reverts to the original failure mode where 12 consultants type 12 different shapes of activity log into the same CRM, but the data accumulated up to that point stays clean. There is no vendor lock-in beyond the months Clone was running.