Plenty of CRMs are designed with a big sales organisation in mind: departments, territories, approval layers and somebody whose whole job is administering the system. Put one in front of a team of five and what usually happens is that nobody uses it.
A small team needs something different. Not a shrunken version of the big system, but a tool that does fewer things, does them well, and can be picked up by everyone in the first week. Here’s what we think that means in practice, so you can judge any CRM on it, ours included.
Begin with what’s going wrong
Before you look at software, spend twenty minutes writing down what actually goes wrong today. For most small teams the list is short. Leads aren’t followed up on time. Nobody can see what was said to a customer before. Quotes get chased by hand. The owner can’t see how sales are going without asking. And half of what everyone knows lives in one person’s head or one person’s spreadsheet.
A good CRM for a small team fixes those and not a great deal more. If a system’s main selling point is a long feature list, ask which of those features solves one of your five problems.
What a small team uses every day
One page per lead, holding the whole story, is the foundation. Contact details, where it came from, deals, notes, tasks and the history of every call and email, so anyone can open it and know where things stand. In Henkan CRM that’s the lead profile.
Then comes follow-up, which is the most valuable thing a CRM does for a small team: making sure the next step happens. That means tasks and callback dates tied to a lead and shown on the right person’s list on the day, as in tasks and callbacks.
You’ll want a pipeline that matches how you sell, laid out by stage, with stages that are yours and not a template you have to bend to. We explain how to design one in how to set up a sales pipeline your team will follow, and the product page is the sales pipeline.
You need easy ways to get leads in, without endless copying and pasting: web forms, a way to receive leads from tools like Zapier or Make, and bulk import. That’s capture. If you send quotes, being able to build, send and sign them from the lead saves a lot of chasing, and that’s proposals and e-signature. A manager needs a handful of reports they can read without a project, which is reports and forecasting. And even in a team of four, reps should see their own work while managers see the team and an admin looks after the settings.
What you can usually skip
Every feature has a cost, in things to learn and things to pay for. For a small team we’d be cautious about territory management and elaborate hierarchies, since you don’t have territories, you have a few people. Approval chains, too: if your discount policy is “ask the boss”, you don’t need workflow software for it. Dozens of reports you’ll never open, when a few good ones beat a library. Marketing automation suites that duplicate a tool you already pay for. And heavy customisation that needs a consultant, because if you can’t change a field without outside help, the system will drift away from how you work.
None of that is bad. It’s built for different businesses.
The test that matters
A CRM is only worth having if the whole team uses it. The commonest reason small teams abandon one isn’t a missing feature. It’s that the system is so complicated only one person understands it, and everyone else keeps their own notes on the side.
So ask for a demo using your own sales process, and watch whether the person showing it can find things quickly. Then ask yourself whether your least technical rep could do the same. What happens after the demo is covered in getting your whole team to use the CRM.
Questions for any supplier
Who sets it up, and how long does it take? How does my existing data come across, and does the supplier do the import? How do you charge, and what’s included? Can I use my own fields and stages? Where’s my data held, and who can see it? Can I get it back out? Get the answers in writing. We go further in how to choose a CRM for a team of 3 to 15.
Where Henkan CRM sits
We built Henkan CRM for small and medium-sized sales teams that follow up leads and send proposals, and we’ve tried hard to keep it simple. You set your own deal types, stages and fields, and reps, managers and owners each see what they need, which you can browse on our for who pages. There’s no self-serve sign-up. After a demo we set it up with you, and our team imports your data from a spreadsheet or another CRM.
If you’re comparing us with others, Henkan CRM vs other CRMs sets out the questions we think matter. And if you’re not sure whether you need a CRM at all yet, spreadsheet vs CRM is an honest look at that.
How big is “small”?
There’s no hard line, but we think of it as a team of a few people up to around fifteen, where one person can still understand how the whole thing works. Past that you start to need layers: team leaders, separate pipelines and more careful permissions. Below it, the main enemy is complexity.
Your least technical rep sets the bar, not your most enthusiastic one. If they can find a lead, log a call and set a callback without help in their first week, the system suits you. If they can’t, it doesn’t matter how good it looks in a demo.
Thinking about cost
We don’t think you should accept a price you can’t explain. Ask how a supplier charges, whether it’s per user or a fixed rate, and what’s included, and get it in writing. Watch for features sold as extras that you’d need on day one, such as proposals or reporting. Remember too that the subscription isn’t the whole cost: there’s the time to set it up, the time to move your data and the time your team spends learning it. A system that’s cheap to buy and slow to learn can cost more than one that’s the reverse.
A sensible first month
Don’t switch everything on at once. In the first week get your leads in and make sure everyone’s using tasks and callbacks, because that’s where the value shows quickest. In the second, settle your pipeline stages and start running the weekly meeting from the board. After that, add proposals, reports or automation as real needs appear, one at a time. Somebody should own it throughout, usually a manager or the owner, even if that only takes an hour a week. A system with no owner slowly drifts away from how the team sells.
If you want the wider picture first, CRM software explained covers the category, the best CRM for a small business looks at what to look for, and how CRM pricing works lists what to ask about cost.
Want to see it set up around the way your team sells? Book a demo.




