Pick the simplest stack that fits, then stop shopping

The right RevOps stack is the smallest one that runs your revenue, and you stop the moment it does

The biggest threat to a lean team's RevOps is not picking the wrong tool. It is never stopping. Pick a spine that fits, set it up well, and resist every shiny add-on until the spine is genuinely the bottleneck.

When you are choosing a crm for b2b revops, the temptation is to evaluate everything. There are dozens of CRMs, hundreds of integrations, and a marketplace designed to make you feel under-equipped. For a company of five to fifty people, almost none of that matters. What matters is that one tool holds your contacts, companies, deals and activity in one model, automates the obvious work, and reports a number you trust. Most mid-market CRMs do this. The differentiator is not features, it is whether you will actually configure and live in it.

Why HubSpot is the spine I reach for

I build lean B2B RevOps on HubSpot because the free tier is genuinely usable, the upgrade path is smooth as you grow, and the data model, contacts, companies, deals and a clean association layer, is the right shape for revenue out of the box. You can run a real pipeline on the free CRM, then add Sales Hub or Marketing Hub features only when a specific need appears. That matters for a small team because you are never paying for capability you have not grown into, and you are never re-platforming mid-flight.

This is not a claim that HubSpot is the only correct choice. A team already living in another solid CRM should not rip it out to follow a playbook. The point is the spine, one tool that owns the revenue model, and the discipline, configure it deeply before you bolt anything on.

What the stack needs on day one

Strip it back. A lean RevOps stack on day one is smaller than you think:

1. The CRM spine holding contacts, companies and deals with associations. This is non-negotiable and it is HubSpot in this playbook.
2. A way to capture demand into it, usually a form on your site and a tracked email inbox, so leads land in the CRM automatically rather than by copy-paste.
3. A scheduling link so booked calls become CRM activity without manual logging.
4. One reporting view you check weekly, even if it starts as a single default dashboard.

That is the whole day-one stack. Notice what is absent: no sequencing tool yet, no enrichment vendor, no data warehouse, no second automation platform. Each of those is a real tool with a real job, and each is also a way to avoid configuring the spine. Add them when the spine is working and a clear gap appears, never before.

The exact steps to choose and stop

1. Confirm the spine. If you have HubSpot, you are done choosing; open it. If you have nothing, start a free HubSpot account today.
2. Write a one-line job description for every tool currently in your revenue stack. Any tool whose job overlaps the spine is a candidate to cut.
3. Set a rule: no new revenue tool enters the stack until the spine is fully configured and a named, repeated pain proves the gap. Write the rule down.
4. Diarise a review date three months out. Tool decisions get made on the calendar, not on impulse.

A worked example

A 22-person B2B agency had accumulated six overlapping tools, two CRMs, a separate pipeline app, two automation platforms and a standalone email tool, none of them fully set up. Challenge: revenue data was split across all six, so no single view of the pipeline existed and onboarding a new salesperson took a fortnight of tool training. Approach: they named HubSpot the single spine, migrated deals and contacts into it, and shut down the other five over a month, applying the day-one-stack discipline above. Result: tool spend dropped by 1,100 EUR a month, new-hire ramp on the CRM fell from two weeks to two days, and for the first time the founder could open one screen and see every deal. The fix was subtraction, not a seventh tool.

Pitfalls

• Tool-shopping as procrastination. Evaluating a fifth option is easier than configuring the one you have. Stop evaluating; start configuring.
• Paying for hubs you have not grown into. Start on the free CRM and upgrade against a specific need, not a fear of missing out.
• Letting two CRMs coexist "for now". Two spines is no spine. Pick one and migrate; a parallel system always wins back its old users.

With the spine chosen and the shopping closed, the next step is the part most teams skip: the data model. The next chapter models companies, contacts and deals as one revenue object so your reporting can ever work.