kintone vs Salesforce for a Japan business

At a glance

Both vendors publish current plans and prices on their own pricing pages, linked at the end of this comparison. Check them, and ask about volume discounts, before you set a budget.

How the pricing works

The subscription is rarely the largest cost. Both platforms charge per user per month, but the spending that follows the purchase is shaped very differently. Budget for the whole first year, not the license line.

kintone: predictable per-user courses

kintone is sold in a small number of courses, billed per user with a five-user minimum. The entry course limits the number of apps and leaves out plug-ins and the API, so most businesses that plan to connect kintone to anything else end up on the Standard Course. A larger course exists for very big deployments.

• License: per user, per month, on the course you choose.
• Plug-ins: many useful extensions come from Cybozu partners and are billed separately, usually monthly.
• Setup help: optional. A partner can build the first apps, but an internal administrator often can.

Salesforce: the edition decides the bill

Salesforce sells editions that step up sharply in capability and price. The entry edition is designed for very small teams and leaves out much of what makes Salesforce worth choosing. Automation, customization and serious reporting sit in the higher editions, which are billed per user on annual contracts.

• License: per user, per month, by edition, usually committed for a year.
• Implementation partner: most deployments use one, and their fees often exceed the first year of licenses.
• AppExchange apps and admin time: each added app has its own subscription, and someone has to administer the configuration.

How the costs develop over time

kintone costs tend to stay flat per user once the apps are built. Salesforce costs tend to grow as the deployment matures: more apps, more custom code, more partner work at each upgrade. At SME scale, Salesforce is almost always the more expensive platform over several years. That is fine when its sales features earn the difference, and wasteful when they do not.

Use case fit

The cleanest way to think about this: Salesforce is a CRM that can be configured for other things. kintone is a platform that can be configured as a CRM. The difference matters.

If your primary need is managing a B2B sales pipeline with opportunities, forecasts, and quota tracking, Salesforce is purpose-built for this. The out-of-the-box workflow fits the job. You get best-practice defaults from 25 years of sales ops experience baked into the product.

If your primary need is anything else (project tracking, inventory, approvals, HR workflows, customer success, operations), kintone is purpose-built for that flexibility. You build apps that match how your business actually works, not a generic template you have to bend your workflow around.

The mistake most SMEs make is treating a sales CRM decision as a platform decision, and vice versa. A business with a 3-person sales team and 15 operations people needs a platform, not a sales CRM. A business with a 20-person sales team and 3 operations people needs a sales CRM, not a platform.

When kintone is the right call

• Japanese business with Japanese-first team. The language, the workflow assumptions, the vendor relationship - all native. No translation friction.
• Internal workflow needs beyond sales. Approvals, inventory, project tracking, HR, expense management, customer success. kintone handles these as first-class use cases.
• Budget sensitivity. Lower license costs, little or no implementation spend, and a light ongoing admin burden.
• Desire for internal ownership. A non-engineer operations person can own and extend kintone over time. Salesforce typically requires a dedicated admin or ongoing partner relationship.
• SME scale (5-200 people). kintone's pricing and complexity model is tuned for this range.
• Multi-app, not single-CRM, use case. If you want one platform replacing 3-5 different tools, kintone consolidates better than Salesforce does.

When Salesforce is the right call

• Dedicated sales organization with 10+ people. At that scale, sales-specific CRM features start earning their keep. Territory management, forecasting, quota tracking, deal reviews - all out of the box.
• Complex revenue operations. Multi-currency deals, subscription management, CPQ, renewal pipelines. These are table stakes in Salesforce and major custom builds in kintone.
• Parent company ecosystem. If your global HQ runs Salesforce and expects the Japan entity to integrate, resistance is usually more expensive than compliance.
• AppExchange dependency. Specific industry-vertical apps (Veeva for life sciences, nCino for banking, etc.) that only exist on Salesforce.
• Marketing automation integration. Pardot / Marketing Cloud integrations are tighter on Salesforce. If you're running heavy outbound or nurture campaigns and need tight sales-marketing feedback loops, Salesforce wins on integration depth.
• Investor / acquirer readiness. For venture-backed businesses heading toward acquisition, Salesforce is a more familiar stack to diligence teams. This is a soft factor but it matters.

Implementation reality

Both platforms can be set up well, poorly, or halfway. Most failed CRM deployments I've seen weren't caused by the tool : they were caused by treating implementation as a project to finish rather than a practice to build. That said, the two platforms have genuinely different implementation shapes.

kintone implementation

A typical first kintone deployment looks like this:

• Week 1: Scope the app. What problem does this CRM solve? Who uses it? What data matters?
• Week 2-3: Build the app. Fields, views, permissions, basic workflows. This can be done by an internal admin with 4-8 hours of focused time.
• Week 4: Test with 2-3 users. Fix the things they break.
• Week 5-6: Roll out. Training is usually 30-60 minutes per user.

External consultants help but are not required.

Salesforce implementation

A typical first Salesforce deployment looks like this:

• Weeks 1-2: Requirements gathering. Often with a certified partner consultant.
• Weeks 3-6: Configuration. Objects, fields, validation rules, workflow rules, process builder / flows.
• Weeks 7-10: Data migration and integration work. Bringing in existing data, setting up syncs with other tools.
• Weeks 11-14: User training and pilot. Sales teams often require multiple training sessions and structured onboarding.
• Weeks 15-16: Full rollout, followed by 60-90 days of stabilization.

External consultant engagement is basically required for most deployments. Skip this and you end up with a half-working deployment that nobody trusts.

The "consultant-dependent" problem

A side effect of Salesforce's complexity: many SMEs end up in a permanent dependency on their implementation partner for any change. This is a cost that doesn't show up on the Salesforce invoice but shows up on every partner invoice forever.

kintone's lower complexity usually breaks this cycle. After a 3-6 month learning curve, an operations person can usually handle 80% of changes without external help.

Japan-specific factors

Beyond the product comparison, there are three Japan-specific factors that matter for the decision.

Vendor relationship and language

Cybozu is a Japanese company. Customer support is native Japanese. Documentation is primarily Japanese. The product design reflects Japanese business workflow assumptions : approval hierarchies, team-based ownership, document-centric processes.

Salesforce Japan provides Japanese support and localized interface, but the product's center of gravity is in the US. Decisions about roadmap, product changes, and pricing are made in San Francisco. Japanese partner ecosystem exists but is smaller and more expensive per hour than the US equivalent.

Integration with Japanese SaaS

kintone has native integrations with Japanese accounting (freee, Money Forward), HR (SmartHR, KING OF TIME), and communication (Chatwork) tools. Salesforce has integrations with some of these through partner apps but they're generally less polished than the kintone equivalents.

Salesforce has stronger integrations with global tools (Slack is now owned by Salesforce, tight HubSpot sync, deep Google Workspace and Microsoft 365 integration).

For a Japan SME mostly using Japanese SaaS: kintone wins. For a Japan entity of a global company using international SaaS: Salesforce wins.

Data residency and compliance

kintone hosts data in Japan by default (AWS Tokyo region). For businesses with data residency requirements - government contracts, healthcare, financial services - this matters. Salesforce hosts Japan customer data in Japanese data centers as well, but the configuration and compliance documentation is more complex to navigate.

Alternatives worth considering

kintone and Salesforce are the most common framing, but neither is universally right. Three alternatives that should be on your shortlist depending on the situation:

• HubSpot - Best for foreign-owned Japan SMEs with inbound marketing and sales motion. Free tier for small teams, strong Japanese support, cleaner UX than Salesforce. Scales reasonably to 50+ person sales orgs. The main weakness is workflow flexibility - it's a CRM, not a platform.
• Zoho CRM - Cheapest of the major CRMs. Adequate Japanese support but weaker market presence than Salesforce or HubSpot. Good for budget-constrained deployments where HubSpot's free tier runs out.
• A spreadsheet - Not a joke. For businesses under 10 people with simple pipelines, a well-maintained Google Sheet outperforms a poorly-maintained CRM every time. The question isn't "should we have a CRM" but "is our pipeline complex enough that a CRM will actually pay for itself." Often the answer is no.

For the full context on why most CRM deployments fail, see Why CRM rollouts fail at Japanese SMEs, and what works.

A simple decision framework

Work through these in order. First answer that fits determines your choice.

1. Do you have 10+ dedicated sales staff? Yes → Salesforce. No → continue.
2. Does a parent company or acquirer require Salesforce? Yes → Salesforce. No → continue.
3. Is your primary need sales pipeline management only? Yes → HubSpot (probably), Zoho (if cheap), or Salesforce (only if complex). No → continue.
4. Do you need more than one tool - CRM plus project tracking, or CRM plus inventory, or CRM plus something else? Yes → kintone. No → continue.
5. Is your sales pipeline under 10 active deals at a time? Yes → Just use a spreadsheet until you grow out of it. No → kintone.

This framework gets 90% of SMEs to the right answer. The remaining 10% are the interesting cases where a Diagnostics actually earns its keep.

Frequently asked questions