Kintone vs Salesforce for Japan SMEs

At a glance

Prices shown are publicly listed starting prices in Japan as of 2026-04-22. Actual deployment cost depends on user count, add-ons, and negotiated discounts. Both vendors negotiate on volume.

Pricing in Japan (real numbers)

The sticker price is not the deployment cost. Both vendors have hidden costs that only surface once you're past the purchase decision. Here's the full picture.

Kintone: straightforward economics

Kintone's pricing is simple by SaaS standards. Three tiers, per-user monthly billing, annual contracts standard.

• Light Course: ¥780/user/month — limited app count, no plug-ins, no API. Usually not enough.
• Standard Course: ¥1,500/user/month — full app count, plug-ins, API access. This is the tier most businesses actually need.
• Wide Course: ¥3,000/user/month — for 1,000+ user deployments with governance needs.
• Minimum contract: 5 users.
• Hidden costs: Paid plug-ins from the Cybozu ecosystem (¥500–¥5,000/month each), occasional consultant fees for complex app builds.

For a 15-person business on Standard, you're looking at about ¥270,000/year (~USD $1,800) in license costs. Most businesses add ¥300,000–¥600,000 of plug-in and consultant spend in year one, then settle to ¥100,000–¥200,000 in ongoing additional spend.

Salesforce: pricing that looks similar but isn't

Salesforce is priced per user per month in dollars, with Japan list prices following the US pricing with a modest premium.

• Starter Suite: ~$25/user/month (~¥3,750) — very limited.
• Pro Suite: ~$100/user/month (~¥15,000) — real CRM functionality.
• Enterprise: ~$165/user/month (~¥25,000) — customization and automation.
• Unlimited: ~$330/user/month (~¥50,000) — full platform.
• Minimum contract: Annual, typically with 10-user minimum for Pro Suite and above.
• Hidden costs: Implementation partner fees (¥1–5M typical), AppExchange apps (¥5,000–¥50,000/user/month each), Apex developer costs, ongoing admin.

For a 15-person business on Pro Suite, you're looking at about ¥2.7M/year (~USD $18,000) in license costs alone — 10x the Kintone equivalent. Add ¥1–3M in first-year implementation costs and the true year-one spend is ¥4–6M.

The long-term cost divergence

Both platforms have compounding costs, but the direction differs. Kintone's costs stay relatively flat per user over time. Salesforce's costs tend to compound: more AppExchange apps, more admin time, more Apex custom code, more implementation partner engagements when upgrading. A five-year cost comparison typically shows Salesforce running 5–8x more expensive than Kintone for an equivalent deployment at SME scale.

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. 3–5x cheaper in licenses, minimal or zero implementation cost, low 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 aren't required. Typical consultant engagement is ¥300,000–¥800,000 for a full setup.

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. Partner costs run ¥1M–¥5M. 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 CRM for Japan SMEs: Why Most Deployments Fail.

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 Stack Audit actually earns its keep.

Frequently asked questions