A CRM fails in a small Japanese business for the same few reasons almost every time. The company bought the tool before it agreed how sales actually work, the setup grew more complicated than the team could maintain, the people entering data were never asked what they needed, and nobody was given the job of keeping it accurate. The software is rarely the real problem.

I see the result often when I review a company’s systems in a Diagnostics engagement. A CRM was purchased two or three years ago and configured by whoever was most comfortable with software at the time. The sales team used it for a few months. Then a shared Excel file or Google Sheet quietly took over, and the CRM kept renewing every month with nobody logging in.

That outcome is predictable, which means it is also preventable.

Why do CRM projects fail in small companies?

The tool arrived before the sales process

A CRM records a sales process. If the business has never written down its deal stages, who owns each one, and what has to be true before a deal moves forward, the CRM has nothing to record. Staff are asked to fill in fields for a workflow that does not exist, so they stop filling them in, and the reports become fiction.

Before opening any CRM, write the process on one page. List the stages from first contact to signed contract. Name the person responsible at each stage. Note the information you need before moving to the next one, and agree what counts as a won or lost deal. If the team cannot agree on that page, a CRM will not settle the argument for them.

The setup was built for the vendor, not the team

Large implementations earn the vendor or integrator more in professional services, and heavy customization makes a system harder to leave. In a 15-person company, the result is often dozens of custom fields nobody understands, eight clicks to log a phone call, and dashboards that only the original consultant could read.

If recording a visit takes longer in the CRM than in the spreadsheet it replaced, the spreadsheet will win.

The people doing the work were not involved

Salespeople decide whether a CRM lives or dies, because they are the ones entering the data. When management chooses a tool and hands it over without asking what the team needs from it, the team finds workarounds. The system is technically deployed and practically unused.

Involve two or three people who will use it daily in choosing and testing the tool. Ask what they currently track, where, and why. Their existing spreadsheet usually shows you the fields that actually matter.

Nobody owns it after launch

A CRM decays without maintenance. Contacts go stale, stage names stop matching how the business sells, duplicate companies multiply, and reports drift away from reality. In most small companies this job belongs to nobody, so nobody does it.

Which CRM should a Japanese SME use?

Choose the tool after the process is written down, and choose the simplest one that supports it. These are the options I see most often in small and mid-sized companies in Japan.

HubSpot’s free CRM is a sensible starting point when the business has no working CRM yet. The free tier covers contacts, companies, a deal pipeline, email logging and basic reporting, which is enough for a small team to prove it will use a CRM at all. Paid hubs can wait until you know exactly which feature you are missing.

Pipedrive suits teams whose work is mostly moving deals through a pipeline. It is more opinionated than HubSpot, which helps when you want everyone working the same way. Its Japanese interface is serviceable, and it fits companies with some international work.

kintone from Cybozu is common in Japanese companies because it is flexible, fully Japanese and familiar to many local staff and IT vendors. That flexibility cuts both ways: a kintone CRM is only as good as the app someone designs in it. I compare it with Salesforce in kintone vs Salesforce.

Japanese sales tools such as Mazrica Sales (formerly Senses) and eセールスマネージャー are worth a look when the whole team works in Japanese and sells mainly to Japanese customers. Support, training and invoicing all happen in Japanese, which matters more than a feature list for some teams.

Salesforce is rarely the right first CRM for a small company. The per-user license is only part of the cost. A real deployment usually needs an implementation partner and someone who administers the system afterwards. It makes sense for larger sales operations with complex processes and a dedicated administrator. If a vendor recommends it for a 15-person team, ask them to explain what the smaller tools cannot do.

For a broader comparison, see the guides to choosing a CRM for a Japan SME and affordable CRM options for startups in Japan.

How to roll out a CRM your team will use

Write the process first. Agree the stages, owners, qualification rules and a realistic timeline for a typical deal. This is most of the work, and it is useful even if you never buy software.

Configure the minimum. Set up the standard deal stages, five to ten custom fields that the process genuinely needs, and one report that shows the pipeline. Import only the contacts and open deals you will actually work on. Add more later when someone can explain why they need it. If most contacts still arrive on paper meishi, decide how those cards get into the CRM before launch.

Test with real deals. Have two or three salespeople run their current deals through the system for two weeks. Fix whatever slows them down before asking everyone else to switch.

Retire the spreadsheet. Pick a date after which the old file becomes read-only. Two systems of record means neither one is trusted.

Give it an owner. Name one person who cleans up duplicates each month, updates stages when the process changes and answers colleagues’ questions. For a small team this is usually a few hours a month, but it has to be part of someone’s job.

Do you need a CRM at all?

The goal is a clear, current picture of your pipeline: who is in it, what stage they are at, what they need next and when you expect to close. If a shared spreadsheet gives you that and the team keeps it accurate, a CRM is not urgent.

A CRM becomes worth the effort when deals slip through gaps, when a salesperson leaving would take the customer history with them, when managers cannot see the pipeline without asking around, or when you need follow-up emails and tasks to happen automatically.

Fixing a CRM that already failed

An abandoned CRM does not always need replacing. Often the fastest route is to strip the configuration back to the stages and fields the team really uses, clean the data, connect it to the email and calendar tools people already have, and give it an owner. Sometimes the honest answer is to cancel the subscription and run a disciplined spreadsheet until the process is settled.

If you are sitting on a CRM nobody opens, a Diagnostics review will show how sales information actually moves through the business and what to keep. If you already know what needs to change, I can plan and carry out the rebuild with your team. You can also tell me about your situation.

Further reading: what belongs in a Japan SME technology stack · reviewing the subscriptions your business still needs · what to do with the business cards you collect