Sansan

Name: Sansan
Brand: Sansan
Rating: 4.5 (20 reviews)

Leader

Sansan provides AI- and OCR-driven solutions for DX in companies and for contact, invoice, and contract management.

Est 2007|Valuation $1.7B|Raised $177.8M

LinkedIn 8K|Website|Web traffic 663K|FTEs 3,159|HQ Tokyo, Japan

MarketsLead Tracking & Intelligence

Published Oct 22, 2026

01Common complaints

Small teams that prioritize rapid procurement and minimal rollout over centralized governance and operational controls; self-serve digital card tools may be faster and less expensive to start.
Organizations that rarely use physical business cards; digitization workflows may add unnecessary overhead.
Organizations requiring full identity automation (SCIM provisioning/deprovisioning and IdP-driven lifecycle automation) unless the vendor confirms support and operational details.
CRM-first organizations aiming to avoid additional systems and integration complexity; consider CRM-native capture solutions.
Budget-constrained teams for which quote-based pricing, scanner hardware, and onboarding services are cost-prohibitive.

- Small teams that prioritize rapid procurement and minimal rollout over centralized governance and operational controls; self-serve digital card tools may be faster and less expensive to start. - Organizations that rarely use physical business cards; digitization workflows may add unnecessary overhead. - Organizations requiring full identity automation (SCIM provisioning/deprovisioning and IdP-driven lifecycle automation) unless the vendor confirms support and operational details. - CRM-first organizations aiming to avoid additional systems and integration complexity; consider CRM-native capture solutions. - Budget-constrained teams for which quote-based pricing, scanner hardware, and onboarding services are cost-prohibitive.

Disqualifiers (poor fit)

Teams seeking low-cost, self-serve solutions with transparent monthly pricing.
Organizations that have largely moved to digital-only contact exchange (NFC/QR) and have minimal physical-card workflows.
Organizations that require automated SCIM provisioning and strict IdP-driven lifecycle controls without compromise (document SAML constraints and verify provisioning capabilities prior to purchase).
CRM-first organizations that prefer to keep contact capture entirely within the CRM to minimize separate systems and integration risk.

- Teams seeking low-cost, self-serve solutions with transparent monthly pricing. - Organizations that have largely moved to digital-only contact exchange (NFC/QR) and have minimal physical-card workflows. - Organizations that require automated SCIM provisioning and strict IdP-driven lifecycle controls without compromise (document SAML constraints and verify provisioning capabilities prior to purchase). - CRM-first organizations that prefer to keep contact capture entirely within the CRM to minimize separate systems and integration risk.

Limitations documented in vendor materials

SAML authentication constraints: SAML is a paid option in published help materials. The help article notes that 2FA cannot be used concurrently with SAML in that documented configuration and that user lifecycle events from the identity provider are not automatically reflected in the application.

Operational limitations observed in reviews and case materials

Hardware/scanner dependence for bulk or professional workflows, which introduces procurement and logistical considerations.
Duplicate creation risk during CRM synchronization; vendor case materials describe deduplication procedures and the need for mapping rules.
Limited transparent pricing in public materials, which can lengthen procurement cycles.

Roadmap visibility

Public sources did not include a detailed public roadmap with dated commitments. Procurement teams should request roadmap items and timelines in written form during contracting.

02Why they buy

(Neutral, evidence-focused framing)

Product attributes supported by evidence or repeated claims

Enterprise-wide shared contact visibility: Vendor materials and some third-party anecdotes indicate functionality that allows organizations to share scanned contacts across teams to support internal introductions and knowledge retention.
Operational workflow for bulk digitization: The product offering includes scanner hardware and administrative scanning workflows designed for high-volume ingestion scenarios rather than occasional single-card scanning.
CRM augmentation: Vendor case materials describe use of the product to increase contact population in CRM systems; these materials report outcomes but generally lack independent validation.

- Enterprise-wide shared contact visibility: Vendor materials and some third-party anecdotes indicate functionality that allows organizations to share scanned contacts across teams to support internal introductions and knowledge retention. - Operational workflow for bulk digitization: The product offering includes scanner hardware and administrative scanning workflows designed for high-volume ingestion scenarios rather than occasional single-card scanning. - CRM augmentation: Vendor case materials describe use of the product to increase contact population in CRM systems; these materials report outcomes but generally lack independent validation.

Claims that require verification during procurement

Accuracy metrics for digitization (examples of marketplace claims include high-percentage accuracy). Prospective customers should request measured field-level accuracy by language and script, error rates, and SLAs for correction workflows.

03Field reports

Review-platform sentiment (G2, Capterra)

G2 listing (limited review sample) shows generally positive ratings for scanning and contact findability, with reviewers noting costs and hardware as concerns. The English-language review coverage is limited and should not be considered a definitive measure of global satisfaction.
Capterra listing contains a small number of reviews and references marketplace/vendor claims (e.g., corporate client counts and scanning accuracy claims) that should be verified with the vendor.

Interpretation: English-language review coverage is limited; localized reviews in Japan may provide additional signal and should be considered in a broader evaluation.

- G2 listing (limited review sample) shows generally positive ratings for scanning and contact findability, with reviewers noting costs and hardware as concerns. The English-language review coverage is limited and should not be considered a definitive measure of global satisfaction. - Capterra listing contains a small number of reviews and references marketplace/vendor claims (e.g., corporate client counts and scanning accuracy claims) that should be verified with the vendor. Interpretation: English-language review coverage is limited; localized reviews in Japan may provide additional signal and should be considered in a broader evaluation.

App store signal

The Sansan mobile app is available in app stores; app ratings and reviews can provide qualitative feedback about mobile user experience but were not exhaustively analyzed here.

Community/social feedback

Sansan is not widely discussed in mainstream English-speaking technical communities. Anecdotal mentions in region-specific forums indicate that the product can provide value in organizations that share scanned cards centrally.

Why customers choose Sansan (based on case studies and reviews)

Common selection factors reported across vendor and third-party materials include:

Organization-wide sharing of relationship data to support internal introductions and cross-team prospecting
Vendor-described digitization accuracy using a combination of OCR and human review
Preservation of contact records as institutional assets to mitigate turnover risk
Use of Sansan to augment CRM contact coverage rather than replace CRM systems

Why customers may leave or experience dissatisfaction (observed signals)

Reported reasons that can contribute to churn include:

Cost, particularly as user count or contact volume scales
Hardware dependence for bulk workflows (scanner purchase and logistics)
Integration issues and duplicate records when syncing with CRMs
Identity and authentication trade-offs (SSO without automatic provisioning and possible incompatibility between SAML and 2FA)

1) Midtrans (vendor-published case study)

Sansan published a case study describing Midtrans (Indonesia) using the platform to support sales efficiency. The case cites estimated adoption rates and operational changes such as regular periodic card entry processes and bulk scanning by administrative staff.

Critical evaluation: Outcomes are qualitative and self-reported; the case lacks independently measured ROI, pipeline lift, or conversion metrics.

2) Lenovo Japan (vendor-hosted user story)

Critical evaluation: The reported increase is a notable metric but lacks documented methodology (baseline definition, deduplication approach). The acknowledgment of duplicate records is a realistic integration concern and illustrates the need for rules and validation when integrating with CRM systems.

A vendor-hosted story describes a multi-month pilot with several hundred staff and reports a notable increase in key contacts added to Salesforce. The case also documents duplicate contact creation during integration and describes steps taken to mitigate duplicates. Critical evaluation: The reported increase is a notable metric but lacks documented methodology (baseline definition, deduplication approach). The acknowledgment of duplicate records is a realistic integration concern and illustrates the need for rules and validation when integrating with CRM systems.

3) DBJ Americas (vendor customer story)

Vendor-hosted content indicates use beyond Japan, including DBJ Americas. Public excerpts in this report did not present detailed quantitative outcomes.

Critical evaluation: These vendor-provided customer stories illustrate typical adoption patterns but should be corroborated with independent metrics and procurement-level references where possible.

04Best fit

Company sizes

Mid-market to enterprise organizations with structured sales organizations and cross-team selling needs.
Small and medium teams that require team-level sharing may evaluate a related smaller offering from the vendor.

Industries

B2B sales-heavy industries such as IT services, telecommunications, manufacturing, trading/wholesale, professional services, and finance subsidiaries.

Roles and personas

Decision makers: Sales leadership, RevOps/Sales Ops, IT/security, and regional operations managers.
End users: Field sales, account managers, marketing operations, executives and executive assistants handling contact workflows.

Qualification criteria (good fit)

Organizations that regularly exchange physical business cards.
Organizations that benefit from cross-team introductions and centralized visibility into relationships.
Organizations that wish to preserve contact records as institutional knowledge.
Organizations that require controlled sharing and permissioning for contact data.

05The pitch

What the product does (objective core value proposition)

A key design goal is to convert individual employee contact collections into an organizational contact repository that persists when employees change roles or leave the company.

Sansan is a B2B cloud contact and business-card–centric sales enablement platform. It digitizes business cards (via mobile capture and/or dedicated scanners), enriches and organizes contact and company information, and makes contact records searchable and shareable across an organization to support prospecting, account handoffs, and cross-sell / warm introductions. A key design goal is to convert individual employee contact collections into an organizational contact repository that persists when employees change roles or leave the company.

Target market and market positioning

Primary market: Mid-market and enterprise organizations (especially in Japan and APAC) that continue to exchange physical business cards, and multinational teams that require centralized contact intelligence.
Positioning: Marketed as a centralized contact repository with emphasis on vendor-stated digitization accuracy and organizational sharing/governance (permissions, admin controls). It is positioned as complementary to — rather than a full replacement for — full CRM systems.
Typical buyer personas: Sales operations, revenue operations, IT, sales leadership, and, in Japan, administrative functions that handle bulk card entry.

- Primary market: Mid-market and enterprise organizations (especially in Japan and APAC) that continue to exchange physical business cards, and multinational teams that require centralized contact intelligence. - Positioning: Marketed as a centralized contact repository with emphasis on vendor-stated digitization accuracy and organizational sharing/governance (permissions, admin controls). It is positioned as complementary to — rather than a full replacement for — full CRM systems. - Typical buyer personas: Sales operations, revenue operations, IT, sales leadership, and, in Japan, administrative functions that handle bulk card entry.

Get a comprehensive analysis of Sansan including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →