Some businesses win customers with a price list. Others win them by being the people a customer trusts. If you’re in the second group, with long conversations, repeat customers, referrals and an account manager who knows everyone by name, you need a CRM that backs that up, not one that turns it into a production line.
A lot of CRMs are built around a funnel. Leads go in at the top, deals fall out of the bottom, and the system measures volume and speed. That suits high-volume selling. It’s a poor fit for a business whose sales depend on remembering that a customer’s contract is up in October, or that they’d rather have a phone call than an email.
What selling on trust involves
Fewer, longer conversations, for one thing, and a sale that can take months. Several people at one customer, since the person who signs isn’t always the person you talk to. Repeat and referral business, so the relationship carries on after the first sale. Details that matter, such as preferences, history and promises made. And continuity: if one person leaves or is away, the customer shouldn’t notice.
So a CRM for this kind of selling is really a memory for your business. Its job is to make sure everything the team knows about a customer is there for whoever speaks to them next.
What to look for
Start with one complete record per customer. Every contact at the company, every conversation, every deal and every document in a single place. If you have to check three places to understand a relationship, the CRM isn’t doing its job. In Henkan CRM that’s the lead profile, which holds contact details, source, deals, notes, tasks, the proposals you’ve sent and your own custom fields, with a full history of everything that’s happened. Pinned notes sit at the top, and you can add as many contacts as you deal with, marking one as primary.
Several contacts per company matters more than it sounds. If the CRM treats a company as a single person you end up with notes like “ask for Sarah, not John”. You want to record the owner, the person who pays, the person who uses the product and whoever has to sign it off.
Then there’s the history itself: calls, emails, notes and tasks in date order, written by named people, and quick to scan before a call. If it takes ten minutes to read the log, nobody will. Our post on how to keep track of customer relationships when you sell on trust covers what to record and where.
Your own fields come next. The details that matter differ in every business. A fuel card supplier cares about fleet size and renewal month. An accountant might want a year-end date. A good CRM lets you create fields for what matters to you, and avoid systems where you’re stuck with whatever the supplier decided.
Communication from the record is another. Email and text should be sent from the customer’s page and logged there automatically, so nobody copies and pastes. In Henkan CRM you can connect your own Gmail or Outlook mailbox, so emails go from your usual address and replies from known contacts are logged on the lead, and texts work through your own Twilio account. See email and SMS.
Relationships also need maintaining, so the CRM should help you remember to follow up after a quote, check in after a sale or ring ahead of a renewal. That’s tasks and callbacks landing on the right person’s list on the right day. If your team lives on the phone, calls should appear on the record without anybody logging each one by hand. Phone system integration matches calls to leads by number and puts them on the timeline.
Finally, control over who sees what. Customer records include sensitive details, and managers and owners need an overview while reps see what they need.
What to be wary of
Funnel-only thinking, where a CRM measures only conversion and speed and nudges your team towards habits that damage relationships. Automation that sounds like a robot: sequences have a place for routine follow-up, but a customer used to talking to a person shouldn’t get a stream of generic messages. Use automation for the routine and keep the personal contact personal. (There’s more on where to draw that line in follow-up emails and sequences.) Too much data entry, because if recording a conversation takes longer than the conversation, people stop. Complicated set-up, since relationship-based teams are often small with no administrator. And any tool that buries the history, where it takes many clicks to find what was said last time.
Does that mean no automation at all? No. Just don’t automate the conversations.
A practical test
When you see a demo, ask the supplier to show you a few things. Open a customer you haven’t spoken to for six months and find out what was last discussed, and see how quickly. Add a second contact at the company. Take a call and record it, and time it. Set a reminder to call back in three weeks and see where it appears and who sees it. Hand the customer to a colleague and see what they get. If all of that is quick and obvious, the system suits relationship selling.
Why we built Henkan CRM this way
We built Henkan CRM for teams who follow up leads and send proposals. Our founder, Dominic Dysart, has spent ten years in marketing, and our view is that a CRM should serve the way a business already sells, not the other way round. You can read more on Why Henkan, and see what managers and owners get on the for who pages.
Bringing your history across
If you’re switching from another system, ask early what comes with you. For a relationship business the most valuable material is the last year or so of notes and key dates for each customer, along with every contact at the company. A short summary on each live customer is often more useful than a pile of old entries nobody will read. Ask the supplier who does the import and how they handle notes, because it’s the sort of detail that decides whether your team trusts the new system in week one.
Once you’ve got the record right, what to record after every sales call is the next habit to build. If you sell on trust and want a CRM that respects that, book a demo.




