CRM for a ten-person sales team: what actually matters

Three people can run a pipeline out of a spreadsheet and a good memory. Thirty people cannot, and everyone knows it. Ten is the awkward middle: large enough that the memory approach has already failed, small enough that nobody wants to admit it and put in process.

At this size the CRM stops being a shared address book and becomes an instrument someone manages by. That changes what you are choosing for. The features that matter are not the ones on the comparison table; they are the ones that survive contact with ten people who each have their own way of working.

Ten is a different problem from three

• There is now a manager who does not carry a quota but has to answer for the number.
• Leads have to be routed, because "whoever gets to it first" produces both duplicate calls and ignored enquiries.
• Two people will touch the same account, and one of them will not know.
• Somebody will leave, and their pipeline has to be workable by whoever inherits it, without a handover meeting that never happened.
• The forecast is read by someone outside sales, which means it has to be defensible, not just optimistic.

Design the pipeline before you configure anything

The single highest-leverage decision is what the stages are, and most teams get it wrong the same way: they name stages after what the seller has done rather than what the buyer has done. "Proposal sent" is an activity. "Budget confirmed" is a fact about the buyer. Stages built out of seller activity always look healthy, because you can move a deal forward by doing something rather than by learning something.

1. Five to seven stages. More than that and people guess; fewer and the forecast carries no information.
2. Every stage needs an exit criterion you can state in one sentence, and it should be something the buyer did or said.
3. One stage should be allowed to mean "not now" without meaning "lost". Otherwise deals sit in the pipeline forever to avoid an unpleasant entry.
4. Write the criteria down in one place the team can open. If they live in a manager's head, they are not criteria.

Three mandatory fields, and nothing else

Required fields are a tax on entry and every one you add reduces the chance that the record exists at all. For a team of ten, make three things compulsory and let everything else be optional:

• A next step with a date. A deal without one is not a deal, it is a hope.
• An amount, even a rough one. A pipeline you cannot add up is a to-do list.
• A stage that matches the written criteria.

Every mandatory field is a bet that the information is worth more than the record you will not get. At ten people you can afford about three of those bets.

Routing and ownership

Decide before go-live how an inbound enquiry gets an owner, what happens when the owner does not respond within a stated time, and who owns an account that two people have worked. Round-robin, territory, product line or named-account lists all work; what does not work is leaving it implicit. The rule matters less than the fact that it is written down and the tool enforces it.

The report the manager actually uses

Not the dashboard. Three lists, reviewed weekly, in this order:

1. Deals with no next step. This is the only genuine leading indicator a small team has.
2. Deals whose close date has moved more than once. Movement is information; repeated movement is usually a deal that is already dead.
3. Stage age. A deal that has been in one stage for three times the normal dwell time is telling you something the owner is not.

A weekly review built on those three lists takes twenty minutes and changes behaviour. A dashboard of pie charts takes longer to build and changes nothing.

What to check in the product itself

• Required-field enforcement per stage, not globally — that is what lets you keep entry cheap and exit disciplined.
• Bulk edit and merge. You will need both in the first month, on your own imported data.
• Duplicate detection on company and email, ideally with a company lookup from a NIP so addresses come from the register.
• A permission model that lets a person see their own deals and the manager see everything, without an enterprise plan.
• Two-way mail and calendar sync through a native plug-in, not IMAP polling.
• A path from a won deal into invoicing, so nobody retypes a tax number.
• An API and webhooks, because at this size something will need to talk to something else within a year.

A four-week rollout

1. Week one: stages, criteria and fields agreed by the manager and two sellers. No configuration yet.
2. Week two: import, de-duplicate, and configure. Do the import badly on purpose once in a sandbox so you know what a bad import looks like.
3. Week three: the whole team works only in the CRM. The spreadsheet is read-only. One person is on call for questions.
4. Week four: run the first weekly review off the three lists, and fix whatever the review exposes rather than adding features.

Where to start looking

Pipedrive is built around the pipeline view and gets out of the way, which is most of the battle at this size. Livespace is Polish-built and organised around a structured B2B sales process with stage automation, which suits a team that already has a methodology and wants the tool to enforce it. HubSpot starts free and scales into marketing, with a price step that arrives faster than people expect. monday.com is worth a look if you would rather run sales on the same configurable boards as the rest of the business.

If you are earlier in the process, start with how to choose a CRM for a small Polish company and the CRM category.