# Choosing a CRM for a SaaS company

> A CRM selection process for SaaS teams: object model for trials and expansion, real seat costs, migration effort, and when switching platforms is worth it.

Source: https://saas-marketing.net/guides/crm-for-saas-companies/
Topic: SaaS Marketing Tools
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/crm-for-saas-companies/

## Short answer

For SaaS companies, CRM selection should be decided by the object model rather than the interface. A SaaS CRM has to hold self serve signups that arrive without an account, product qualified leads scored on usage, seat and workspace expansion on an existing customer record, and a single agreed source of truth for ARR and lifecycle stage. Attio or Pipedrive fit pre Series A, HubSpot fits most companies to roughly 100 million in ARR, and Salesforce earns its admin cost only when the process complexity is real.

## Key takeaways

- Pick a CRM on how it models trials, workspaces and expansion, because that decides which marketing numbers you can defend later.
- Self serve signups break the lead and account model in every default CRM configuration, so fix that before importing a single record.
- HubSpot seats run roughly 100 to 150 dollars a month at Professional tier, Salesforce Sales Cloud Enterprise lists at 165 dollars per user per month.
- Salesforce typically needs 0.5 to 1 admin per 30 to 50 sales seats, which is a real line item most selection spreadsheets omit.
- Add a self reported attribution field on the signup form before you spend a quarter arguing about multi touch models.
- Switch CRM when the object model blocks reporting you need, never because the sales team dislikes the interface.

---

Every marketing number you will ever be asked to defend in a board meeting comes out of the CRM. Pipeline sourced, win rate by channel, payback by segment, the lot. So the selection question is not which interface reps prefer. It's whether the system can hold the shape of your business without three custom objects and a nightly script holding it together.

Most SaaS teams get this backwards. They run a demo bake off, the reps like the one with the nicer inbox, and eighteen months later nobody can answer what a self serve trial is worth because trials were never attached to accounts in the first place.

## Why default CRM objects break on SaaS

Standard CRM design assumes a salesperson creates a record for a company, works it, and closes it once. SaaS violates that assumption in four specific ways, and each one causes a different reporting failure.

Self serve signups arrive with no company. Someone signs up with a Gmail address, gets to value, and then twelve colleagues appear over the next month. If those twelve are twelve unrelated contacts, your CRM thinks you have twelve leads instead of one account with thirteen users. Domain based account matching is the fix, plus a rule for what happens with free mail domains. Decide it before launch, because retrofitting is painful.

Product qualified leads need a score the CRM did not calculate. Usage lives in Amplitude, Mixpanel, PostHog or your warehouse, not in the CRM. The mistake is syncing everything. Push four fields: PQL score, the event that triggered it, the workspace id, and the timestamp. A rep needs to know why this account lit up and what to open with.

Expansion is not a new company. If the same customer buys 40 more seats, that is a second opportunity on the same account with a type of expansion, not a fresh account. Get this wrong and your net revenue retention calculation quietly includes new logos.

Multi workspace customers break hierarchy. One enterprise buyer might run six workspaces across three business units, each with its own admin and its own bill. You need a parent and child account relationship, and you need to decide which level ARR rolls up to. Notion, Figma and Slack all sell this way, and all three had to solve it internally before their revenue reporting made sense.

Trials created as Opportunities. It feels tidy, then your win rate drops to 3 percent because 97 percent of self serve trials never talk to a human, and sales leadership spends a quarter explaining the number instead of fixing the model. Keep self serve trials as a lifecycle stage on the contact and account, and create opportunities only when a human is working the deal.

## The four realistic choices by stage

You are not really choosing from thirty vendors. You are choosing from four archetypes, and the stage you are at narrows it to two. This sits inside the wider [SaaS marketing stack](/saas-marketing-tools/) decision, and the CRM is the one component you should expect to keep for five years.

Attio deserves a specific note. It models flexible objects natively, which means workspaces, trials and expansion fit without custom object gymnastics, and teams migrating off spreadsheets tend to be live in a week. The tradeoff is a thinner ecosystem. If you need a niche integration, you may be writing it yourself.

HubSpot is the default recommendation for most B2B SaaS companies between Series A and Series C, for one reason: marketing contacts and sales records share an object graph, so lifecycle reporting doesn't require a sync layer. The catch is contact tier pricing. Every self serve signup counts as a marketing contact, and a product with 400,000 free users will produce a bill that shocks the CFO. Mark non marketable contacts aggressively. Our [HubSpot vs Salesforce for SaaS](/comparisons/hubspot-vs-salesforce-for-saas/) breakdown goes deeper on where each one stops fitting, and the [HubSpot for SaaS companies](/guides/hubspot-for-saas/) guide covers the configuration specifics.

Salesforce is the right answer less often than its market share implies. Buy it when the process complexity is genuine: split credit across overlays, deal registration with resellers, revenue across multiple legal entities, a quoting process with approval matrices. Buy it for none of those and you have purchased a platform plus a permanent staffing commitment.

## The fields marketing needs before anything else

Build these before you import records. Retrofitting fields onto 40,000 existing records is a data project, not a config change.

**Minimum viable marketing fields**

Self reported attribution is the one people skip and regret. Platform attribution will credit the last click, which for most SaaS companies is a branded search that tells you nothing. Asking the human directly returns a different and more useful answer, particularly for podcast, community and word of mouth, none of which show up in any analytics tool. Run both and report the gap honestly rather than pretending one of them is the truth.

Lifecycle stage definitions cause more inter team friction than any other field. Write down what makes a contact an MQL, in a sentence a new hire could apply, and put it in the [sales and marketing SLA](/templates/sales-marketing-sla-template/) rather than in someone's head. Then audit it quarterly, because it drifts.

**21%** Salesforce share of the worldwide CRM applications market, the largest of any vendor and roughly double the next

## What the SaaS CRM market looks like and why you should care

CRM is the largest single category in enterprise software, worth north of 90 billion dollars a year, and it keeps consolidating. Salesforce holds roughly a fifth of it, with Microsoft, Oracle, SAP, HubSpot, Adobe and Zoho splitting most of the rest and a long tail underneath.

That matters for vendor risk in a practical way. A tool in the long tail can get acquired and sunset, or get repriced when a private equity buyer arrives. That has happened repeatedly in adjacent marketing categories. If you are betting a five year data foundation on a Series A vendor, check their funding, their logo churn and whether the API has a documented deprecation policy. The wider [SaaS market by vertical](/research/saas-market-by-vertical/) picture and the [marketing SaaS vendor map](/guides/top-marketing-saas-companies/) are worth a scan before signing a three year term.

The other consolidation pattern to watch is bundling. Every major CRM now ships AI features as part of a higher tier rather than as a separate purchase. Price your renewal assuming the tier you are on today gets squeezed upward.

## Migration: what it really takes

Migration cost is almost never the record import. Here's what a 40 seat B2B SaaS company actually spent, in weeks of effort rather than dollars, on a HubSpot to Salesforce move.

| Workstream | Effort | Who does it |
| --- | --- | --- |
| Object and field mapping | 2 weeks | Ops lead plus a sales manager |
| Data cleanup and dedupe before export | 2 to 3 weeks | Ops, often with a contractor |
| Rebuilding routing and assignment rules | 1 week | Ops |
| Rebuilding sequences and email templates | 2 weeks | Sales enablement |
| Integrations that wrote into the old CRM | 2 to 4 weeks | Engineering or a partner |
| Dashboards and historical reporting | 2 weeks | Ops or analytics |
| Parallel run and rep training | 3 to 4 weeks | Everyone |

**A migration sequence that survives contact with reality**

## When switching is genuinely worth it, and when it isn't

Switch when the object model blocks reporting the business needs and the vendor has no path to it. That is the only clean trigger. Everything else is expensive theatre.

Reps disliking the interface is not a reason. Reps dislike every CRM, and adoption problems are almost always process problems wearing a software costume. If activity logging is poor, the fix is usually automatic capture from email and calendar plus a manager who inspects it, not a new platform.

A new VP of Sales who used Salesforce at their last company is also not a reason, though it is the most common one in practice. Make them write down the three reports they cannot get today. If ops can build those in the existing system in a fortnight, the answer is no.

A mid market company we would describe as typical spent about 9 months and the equivalent of two full time roles moving CRM, and emerged with the same win rate, the same pipeline coverage and worse historical reporting than it started with. The thing that had been broken was lifecycle stage definitions, which cost nothing to fix and were never the platform's fault.

There is a real counter case. If you sell through partners, quote complex configurations, or operate across multiple legal entities, staying on a simpler CRM has a compounding cost: spreadsheets appear beside the system, and within a year the spreadsheets are the truth. That is the point to move, and moving earlier is cheaper than moving later.

## What to do this week

Open your CRM and answer three questions. Can you report on self serve signups that later became sales assisted deals? Does expansion revenue sit on the parent account? Is there one system everyone agrees holds ARR?

If all three are yes, you don't have a CRM problem and you should spend the money on demand instead, whether that is content or [paid](/saas-ppc/). If one is no, fix the model in the system you have. If all three are no and the vendor has no route to yes, start the selection process properly, with the object diagram first and the demos last. Teams running this at scale should read the [mid market SaaS marketing playbook](/playbooks/mid-market-saas-marketing/) alongside it, and if an external partner is doing the implementation, run them through a proper [RFP and scorecard](/templates/marketing-agency-rfp-template/) rather than a reference call.

## Frequently asked questions

### What is the best CRM for a SaaS company?

There is no single best one. Under roughly 2 million in ARR, Attio or Pipedrive give you speed and a low admin burden. Between 2 and 100 million, HubSpot usually wins on marketing and sales sitting in one object graph. Above that, or with heavy quoting, partner and territory logic, Salesforce is the defensible choice despite the cost.

### How much does a SaaS CRM actually cost per year?

Budget seat cost plus roughly the same again in admin, integration and data work. Twenty sales seats on HubSpot Sales Professional is about 24,000 dollars a year in licences, then add an operations contractor or a portion of a full time role. Salesforce at the same seat count lists higher and almost always adds a named admin, so a 40,000 dollar licence line becomes 120,000 dollars all in.

### How do you model product qualified leads in a CRM?

Keep the usage data in your product analytics or warehouse and push a small number of fields into the CRM: a PQL score, the triggering event, the workspace id and the date it fired. Do not sync raw event streams into CRM objects. Sales needs to know why this account got flagged and what to say, not every click the user made.

### When should a SaaS company migrate off HubSpot to Salesforce?

When the object model blocks something the business needs, not when the company hits a revenue number. Real triggers include multi entity revenue recognition, complex territory and split credit rules, a partner channel with deal registration, or a quoting process HubSpot cannot express. If none of those apply, migration mostly buys you a year of operations work.

### How long does a CRM migration take?

Plan 8 to 16 weeks for a company with under 50 sales seats and a clean data set, longer if reporting history has to be preserved. The work is rarely the record import. It is rebuilding routing, sequences, lifecycle definitions, dashboards and every integration that wrote into the old system, then running both in parallel for a few weeks.

### Should marketing or sales own the CRM?

Revenue operations should own it, reporting to whoever owns the number. If you have no operations function, marketing usually ends up as the reluctant admin because lifecycle stages and attribution fields live there. That works up to about 20 seats. Past that, an unowned CRM decays fast and the reporting becomes unusable within two quarters.

### Do you need a separate marketing automation tool alongside the CRM?

Only if the CRM's native email and workflow tooling cannot do the job. HubSpot and Attio cover most SaaS needs without a second system. Salesforce customers almost always add one, whether that is Marketing Cloud Account Engagement, Customer.io or Braze, which adds a sync layer and another place lifecycle stage can drift out of agreement.