Guide · CRM for a consulting company
Your firm's CRM is two products, not one. Nobody ships the second.
Every company-focused guide on this topic ranks HubSpot Sales Hub, Salesforce, Pipedrive, Scoro, Kantata, and Mavenlink. All of them stop at the pipeline the partner looks at. None of them ship the firm's
shared institutional memory
, the second product a CRM at a consulting company actually needs. Clone's Boutique plan ships the second product as one shared Computer Agent with shared memory across every seat, driving whichever CRM the firm already picked.Captions drawn from pricing.tsx line 34 ('Shared client memory across team') and architecture.tsx principle 3.
What ranks today
The ten pages that come up for this topic, and the one product they all stop at
I read the top results for this topic before writing. Each is a vendor comparison or a shortlist, and each stops at the pipeline a partner looks at on Monday morning. None of them describe the second product a firm actually needs, because none of the vendors on the shortlists ship it.
Why a firm's CRM is two products, not one
At a 2-partner firm the CRM can be anything; the two partners know what is going on because they sit in the same calls. At 5 partners the first product, the pipeline, is still the visible one; every partner opens HubSpot on Monday and sees the deals. But something else starts to matter. When Partner A took the Acme call on Tuesday and flagged scope concerns, Partner B, who owns the renewal, needs to know that by Thursday. The CRM records the field Partner A typed. It does not record what Partner A knew.
The firm's unspoken fix is usually Slack, weekly sync calls, and partner-to-partner chat threads. Those work at 5 seats. At 15 they fail silently. A partner leaves, and the pipeline looks healthy in HubSpot for six weeks before the firm realizes the client relationships walked out the door with them. Every company-focused guide on this topic argues the first product; the 10th vendor on the shortlist is just a different shape of pipeline.
Clone's Boutique plan ($129 per seat per month, per pricing.tsx) is the only thing I have found that names and ships the second product: shared client memory across the team, firm-wide playbooks, and scheduled firm-level rituals that keep both products in sync.
What one shared Computer Agent routes for a 6-partner firm every Monday
Inputs across every seat fan into one shared agent. Outputs fan back out to each partner's CRM under their own login. Shared memory writes happen in the middle.
The anchor fact: the Boutique plan source, verbatim
This is not a marketing claim. It is the Boutique block of Clone's own pricing component, shipped to every visitor of cl0ne.ai. Read the first three feature bullets carefully.
The three lines
Shared client memory across team
,Firm-wide playbooks and templates
, andScheduled firm-level rituals
are the second product, with a price on it. No CRM on any company-focused shortlist has those lines on their pricing page, because no CRM on the shortlist considers shared context a product line.Where the shared memory actually lives, in the product's architecture
pricing.tsx line 34 is the feature. architecture.tsx lines 24 to 29 is the layer. The following block is the product's own layered architecture, shipped live on the home page.
The four numbers a firm cares about once the second product exists
Boutique plan price from pricing.tsx. Flat per-seat rate. Includes shared client memory, firm-wide playbooks, firm-level rituals, and role-based permissions. No per-CRM-connector fee.
ROI in the first 30 days per features.tsx line 60 ('reclaimed billable hours at typical consulting rates'). At a company, the hours reclaimed are partner hours, which cost the firm the most per hour.
hours per week reclaimed per seat in the first month, per features.tsx line 58. For a 6-partner firm that is a 90-hour-a-week bill taken off the line, mostly CRM upkeep and follow-up.
of admin Clone finishes while you sleep per seat, per the Monday ritual in how-it-works.tsx step 04. Scheduled firm-level rituals fan that out across every partner on the same 8am clock.
The exchange no CRM ships, drawn out step by step
Partner A runs a call Tuesday. Partner B needs the context Thursday. The fields in HubSpot alone do not carry the context; the shared memory does. This is the exact handoff the Boutique plan's shared memory enables.
Partner A's Tuesday call, Partner B's Thursday draft
This is the exchange no CRM ships and the reason Boutique-plan firms pay more per seat than a single HubSpot Pro user would.
The CRMs a Boutique-plan firm can drive, under each partner's own login
If it renders in Chrome, Clone drives it. Different partners can use different tools during migrations, acquisitions, or practice-area splits; the shared memory layer does not care.
Firm Agent
The 'Custom' chip is the CRM your ops lead built on Airtable or Notion. Most company-focused shortlists skip it; the shared-memory layer still works.
Partner A → Clone Log my 2pm Acme call into HubSpot. The conversation notes are in the tl;dv folder. Flag to David that scope came up; he owns the renewal.
1/4Any partner can instruct Clone in plain English
One firm-Monday-8am ritual, as it looks in the log
Six partners, twelve stale deals, one shared ritual file. Notice the second-to-last line: shared memory writes are a first-class step, not a side effect.
The company-focused shortlist page versus the post-shortlist reality
Left column: what a company-focused CRM shortlist page actually helps a firm do. Right column: what happens every week after the firm signs the contract, when the CRM is supposed to stay current across every partner.
| Feature | Every company-focused CRM shortlist page | Clone Boutique (drives whichever CRM the firm picked) |
|---|---|---|
| What the shopping guides for this topic help you do | Pick a CRM for a firm. Compare Sales Hub Pro vs Salesforce Sales Cloud. Read a Scoro vs Kantata shootout. Argue seats and tiers with your ops lead. | Keep whichever CRM the firm already picked current across every partner's seat, and ship the shared-memory layer on top that none of those CRMs include. |
| Who keeps the CRM current at a 5-15 partner firm | Every partner types their own activity notes between calls, or a shared ops lead / COO does the data entry, or a junior associate gets pulled into CRM hygiene duty. None of it is in the CRM's core promise. | One shared Computer Agent with shared firm memory, running scheduled firm-level rituals from pricing.tsx line 39 verbatim. architecture.tsx calls this agent 'Reads the screen, clicks, types, scrolls'. |
| What 'shared client memory' actually means | A shared HubSpot or Salesforce instance where every partner sees the same records. The fields are shared. The context of what was said, what was meant, and what was implied is not. That context lives in each partner's head. | pricing.tsx line 34 verbatim: 'Shared client memory across team'. Clone's memory layer (architecture.tsx lines 24-29) stores the call context, the scope concerns, the personal threads. Any partner's seat reads from the same blob on the next run. |
| What happens when a partner leaves or a new associate starts | The CRM preserves the fields the partner typed. The context the partner held never reached the CRM. Onboarding a replacement means a 90-day ramp reading old emails and asking old clients what was agreed. | The shared firm memory is exactly the context the partner held. A new partner's seat inherits it on day one. Ritual files from pricing.tsx line 39 ('Scheduled firm-level rituals') document how the firm keeps the CRM current in plain English. |
| Cost to switch CRMs in year three, after 15 seats of data | A multi-month migration project. Custom objects remapped. Integrations rewired. Reports rebuilt. A consulting engagement on top of the CRM bill, which is the premise of a whole adjacent category of firms. | 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.' The firm updates the English in its ritual files; Clone drives the new CRM instead of the old one. |
| What the CRM vendor sees during automated firm-wide updates | If the firm bought middleware or connectors, the CRM sees N OAuth-scoped API clients under an admin token. Admin seats go up. IT and compliance approvals are required before the connector can write firm-wide. | Each partner's logged-in Chrome session clicking Save, under their own user, the same way the CRM sees them on a Tuesday morning. No Connected App. No admin seat upgrade. No firm-wide OAuth consent screen. |
| Role-based permissions across the firm | Configured inside the CRM's native role model. Partner A can see X, associate B can see Y. That model exists to protect data. It does not follow the partner's rituals out of the CRM. | pricing.tsx line 37 verbatim: 'Role-based permissions'. Clone honors the firm's roles at the ritual layer. A ritual authored by the senior partner runs against every seat, but only writes fields each seat owns. |
| Support for the CRM your ops lead built on Airtable or Notion | Usually scoped out. The company-focused shortlists rank off-the-shelf vendors. A Notion database with 400 rows of clients is not on any list. | First-class. If a partner can click into it in Chrome, Clone can type into it. The 'Works with custom or legacy apps' row in the home-page comparison.tsx is the only row where Clone checks and Zapier, HoneyBook, and VAs all fail. |
“For firms with a small team who want shared clients, playbooks, and rituals. Everything in Solo, shared client memory across team, firm-wide playbooks and templates, role-based permissions, usage analytics and reporting, scheduled firm-level rituals, Slack and Teams notifications, priority support.”
pricing.tsx, Boutique tier, lines 28 to 46
Six things the company-focused shortlists miss because they are in the vendor business
Each card is a second-order effect of admitting that a firm's CRM is two products and shipping the second one as a Computer Agent. Most company-focused guides stop at the vendor comparison and never get to these.
A CRM at a consulting company is two products, not one
Product one is the pipeline a partner looks at on Monday morning. Product two is the firm's shared institutional memory, which is what new partners need to onboard and what existing partners lose when a client relationship changes hands. Every vendor on the company-focused shortlist ships product one. Clone's Boutique plan ships product two on top of whichever product one the firm already picked. The source of truth for this claim is pricing.tsx lines 34-39.
The firm-level ritual file is the artifact
pricing.tsx line 39 lists 'Scheduled firm-level rituals' as a Boutique-plan feature. The ritual file that keeps HubSpot current becomes the firm's operations manual. A new associate reads rituals/firm-monday-8am.md on day one and understands how the firm keeps its pipeline current.
The CRM picking debate goes away once the second product exists
Firms argue HubSpot Pro vs Salesforce vs Scoro because they assume the CRM is the final layer. When a firm-level agent sits on top, the CRM becomes a typing surface, and the firm picks whichever typing surface its partners already tolerate. architecture.tsx principle 3: 'Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.'
Role-based permissions without a CRM admin seat upgrade
Most CRM vendors charge more per seat as the firm adds role permissions. Clone honors the firm's roles at the ritual layer without touching the CRM's admin config. pricing.tsx line 37 lists it as a first-class Boutique feature; the CRM's own role model stays exactly as the firm configured it.
Usage analytics about partner behavior, not seat activity
CRMs report on field writes and deal moves. Those tell you who typed, not who worked. pricing.tsx line 38 lists 'Usage analytics and reporting' at the ritual layer, which captures which partner ran which ritual, which accounts were touched, and which rituals the firm leans on most.
Custom CRMs your ops lead built finally get firm-wide support
A boutique firm's CRM is often a Notion database or an Airtable base the ops lead spun up in a weekend. No vendor-focused shortlist rates those. Clone does not rate CRMs; it drives them. comparison.tsx shows the 'Works with custom or legacy apps' row is the one where Clone checks and Zapier, HoneyBook, and VAs all fail.
No add-on per CRM. No firm-wide migration required to switch. The same shared-memory layer sits behind all of these, plus whatever your ops lead built.
What a single Boutique subscription covers across the company-focused shortlist
HubSpot Sales Hub
Activity logs, deal stage moves, Next Step fields, and custom-property writes across all partner owners.
Salesforce Sales Cloud
Log a Call, Tasks, Opportunity stages, and custom field typing into Lightning, under each user's real login.
Pipedrive
Activities, notes, deal updates, stage moves via the web UI each partner already uses.
Scoro
Deal-to-project linkage, time entries against engagements, and client notes that follow a project through its phases.
Kantata (ex Mavenlink)
CRM activity into the PSA side, resource allocations, and utilization fields typed the way a project lead would.
Monday CRM
Board item updates, status columns, subitem notes from call transcripts across every partner's board.
Zoho CRM
Call logs, task creation, deal field writes under each partner's Zoho user.
Airtable
The CRM your ops lead built in a weekend. Cell-level writes by row, exactly like a partner would type.
Notion
A database-as-CRM. Clone navigates the same views partners use and types into the same property fields.
Five steps to flip the firm from buying a CRM to running one
Keep whichever CRM the firm already picked
No migration. Each partner's Clone seat signs in through their existing Chrome session under their own CRM user id.
Write firm-level rituals in English, not admin config
'Every Monday 8am, for every partner, log last week's Zoom calls into HubSpot activities and flag stale deals.' Save as rituals/firm-monday-8am.md. pricing.tsx line 39 covers this under 'Scheduled firm-level rituals'.
Partner calls populate the firm's shared memory
pricing.tsx line 34, 'Shared client memory across team'. A call Partner A ran on Tuesday is readable by Partner B's agent on Thursday. This is the second product most CRMs pretend does not need to exist.
Edit the English, not a CRM admin panel, to change firm behavior
architecture.tsx principle 3: 'No re-wiring required.' Swap HubSpot for Salesforce next year and the ritual files change one word. The second product, the shared memory, stays put.
Onboard new partners by pointing at the ritual files
A new associate reads rituals/*.md and understands how the firm keeps the CRM current. No 3-week CRM admin training, no tribal knowledge handoff call. The ritual files are the tribal knowledge, written down.
“Clone picks up your voice, your formatting habits, your escalation rules, and the small judgment calls you make without thinking. After a week it feels less like a tool and more like a second version of you at the keyboard.”
If four or more of these apply, the company-focused shortlist is the wrong page to be on this week
- You run a 2 to 30 partner consulting firm with a shared CRM that nobody enjoys keeping current
- Every partner types their own activity notes (or skips the typing on busy weeks)
- Client context lives in individual partner heads and gets lost in handoffs between partners
- You have considered buying a second product (Gong, Dooly, Aircall) just to move context into the CRM, and it did not scale across all your seats
- Your CRM is HubSpot, Salesforce, Pipedrive, Scoro, Kantata, Monday, Zoho, Insightly, or something your ops lead built
- You would rather write a Monday 8am firm ritual in English than configure N partner Zaps by hand
- A partner left or is about to leave and you are quietly worried what their pipeline will look like in 3 months
Ship the second product your firm's CRM has been missing.
Thirty minutes together. Bring the CRM your partners already use and one stale deal per partner. We will run a firm-Monday-8am ritual live, log activities under each partner's login, and show the shared-memory fan-out on the next run.
What firms ask before replacing another company-focused CRM comparison with a call
Is Clone a CRM for a consulting company?
No. Clone is not a CRM. Every first-page result for this topic is a CRM product or a CRM shortlist page aimed at firms. My claim is narrower: at a consulting company, the CRM is really two products layered on top of each other. The first is the pipeline the partner looks at. The second is the firm's shared institutional memory, and no CRM vendor ships it as a first-class thing. Clone's Boutique plan ships the second product as one shared Computer Agent with shared memory across every seat, driving whichever CRM the firm already picked. pricing.tsx lines 33-42 list the exact Boutique-plan features this relies on: 'Shared client memory across team', 'Firm-wide playbooks and templates', 'Role-based permissions', 'Scheduled firm-level rituals'. architecture.tsx principle 3 is the other verbatim quote: 'Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.'
So if we still have to pick a CRM, which CRM is best for a consulting company?
The honest answer, pulled from reading the top company-focused guides cover to cover: for most 2 to 15 partner firms it is HubSpot Sales Hub Pro for pipeline-first work and Scoro or Kantata for project-heavy delivery work. Salesforce is overkill below 15 seats unless you already have a Salesforce admin. Monday CRM and Pipedrive remain fine for solo-plus-one-assistant setups. But the harder truth, which no company-focused shortlist admits, is that your firm's partners will all type differently or not at all, and whichever CRM you land on becomes a graveyard within six months unless one person does 6 to 10 hours of CRM hygiene per partner per week. That is the bill Clone removes. The CRM vendor choice ends up being a matter of which typing surface your partners already tolerate.
What is 'shared client memory across team' and where is it in the product?
pricing.tsx line 34 lists it verbatim as a Boutique-plan feature. architecture.tsx lines 24-29 shows the Clone Memory layer, labeled 'Your clients, voice, templates, history'. In the Solo plan that memory scopes to one seat. In the Boutique plan it scopes to the firm, which means a call Partner A runs on Tuesday is readable by Partner B's Clone agent on Thursday. The CRM still stores the fields Partner A typed; Clone stores the context Partner A knew. When Partner B drafts a renewal email on Thursday, Clone's agent reads the shared memory, finds Sarah's scope concern from Tuesday, and drafts an email that references it. That exchange is the single most useful thing a firm's CRM stack can do, and it is the exchange no vendor ships.
How is this different from HubSpot Teams or Salesforce shared lists?
HubSpot Teams and Salesforce's shared-record model share the fields a partner typed. They do not share the context the partner held. That distinction is the entire point of the second product. A shared HubSpot instance with 15 partners writing into the same records still depends on each partner typing the 200-word summary after every call. Clone's Boutique plan writes those summaries by reading the Zoom transcripts and typing them into the same HubSpot form your partners would click. architecture.tsx names the layer 'Clone Computer Agent: Reads the screen, clicks, types, scrolls'. The CRM's shared-record model stays; the typing burden goes.
How is this different from a PSA platform like Kantata or Mavenlink for a consulting firm?
PSA platforms are excellent at connecting the delivery side (time, resource allocation, project margins) to the CRM side. They do not solve the shared-context problem. Your associates still type their activity notes, and your partners still skip typing on busy weeks. Clone sits behind whichever PSA + CRM combination the firm landed on and keeps both current. The home-page comparison.tsx comparison shows Clone checks on 'Works with custom or legacy apps' where Zapier, HoneyBook, and VAs all fail, so Kantata-flavored custom object models and Mavenlink-flavored resource boards are both in scope.
Do all our partners need their own Clone seat at $129/mo?
For the firm-wide rituals and shared memory to land correctly, yes. pricing.tsx lines 28-42 define Boutique as $129/seat/mo with shared client memory, firm-wide playbooks, role-based permissions, and scheduled firm-level rituals. The rituals fan out across seats, so if a partner does not have a seat, that partner's CRM records are outside the firm-level ritual sweep. In practice, firms buy seats for their client-facing partners and associates and skip the back-office operations seats unless those people also own CRM accounts. A 6-partner firm at $129 per seat is $774 per month; the home-page comparison.tsx shows a single virtual assistant at $3K to $6K per month does less than that.
Can Clone actually run a different CRM for each partner?
Yes. Nothing in Clone's architecture assumes every partner uses the same CRM, because Clone does not integrate with the CRM through an API; each partner's agent drives their own Chrome tab. 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.' Realistically a firm will converge on one CRM, but during migrations, acquisitions, or practice-area splits, mixed-CRM phases are exactly where a vision-based agent wins and a Zapier-based connector breaks.
What is the anchor fact I should verify before trusting this page?
Open /Users/matthewdi/ai-for-consultants/website/src/components/pricing.tsx and read lines 28 to 46. That is the Boutique plan shipped to every visitor of cl0ne.ai. Confirm that 'Shared client memory across team', 'Firm-wide playbooks and templates', 'Role-based permissions', 'Scheduled firm-level rituals', and 'Usage analytics and reporting' appear as bullet points. Then open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and read lines 24 to 29 and lines 56 to 58. The Clone Memory layer ('Your clients, voice, templates, history') and principle 3 ('Tool agnostic by design') are where the second-product claim lives. Those files are the case the argument rests on.
What happens when a partner leaves the firm?
The partner's Chrome session goes away with them; their HubSpot fields stay behind in the CRM. Before Clone, that is where the handoff problem starts, because the partner's mental context (scope concerns, unspoken client history, the small judgment calls) walks out the door. With the Boutique plan, the shared firm memory stays with the firm. Clone's memory layer has accumulated the partner's call contexts over every ritual run. The new partner's seat reads from the same memory blob, so the 90-day ramp of reading old emails and phoning old clients collapses to reading ritual files and scanning shared memory summaries.
What does the Enterprise plan add that the Boutique plan does not?
pricing.tsx lines 48-65 cover Enterprise. Main additions: on-prem or private cloud hosting, bring-your-own-LLM, SOC 2 Type II + audit logs, SSO and SCIM provisioning, custom integrations, and a dedicated success engineer. For a consulting company without regulatory or compliance constraints, Boutique is the right tier because the shared memory, firm-wide playbooks, and firm-level rituals all live there. Enterprise becomes relevant once the firm moves into regulated verticals, signs RFPs with security questionnaires, or wants to run the LLM on-prem instead of calling out to a hosted API.
What is the fastest way to see this at my firm?
Book a 30-minute call and bring the CRM your partners already use plus one stale deal per partner. We will run a live firm-Monday-8am ritual across a test workspace, log activities into the CRM under each partner's identity, and show the shared-memory fan-out on the next run. The booking link is below; the call is tracked by a schedule_click event so we know which page of this site drove the call. Everything runs in Chrome on your machines, so no IT approval is required to try.
The argument generalizes. These neighboring pages push it into adjacent firm-ops questions.
Related guides
CRM for Consulting
The solo-consultant version of this argument. Focused on the 4.2-hour weekly CRM-upkeep bill one consultant pays.
Consulting Business Software
The full stack a consulting firm assembles by hand. Clone drives the apps the firm already pays for in plain English.
CRM Consulting Service
The services category that installs the integration layer. Clone ships the Computer Agent instead, removing the SOW.