Integration Audit
We review your website, CRM, email platform, payment gateways, and any operational tools such as Kintone that are part of your business workflow. We document what is connected, what is broken, what data is being lost between systems, and what APPI-related compliance considerations apply to your current data flows. The audit produces a complete picture of your integration landscape before any build work begins.
Integration Specification
We produce a written specification in both Japanese and English for each integration required, covering the data that moves between systems, the direction and trigger conditions for each transfer, and the field mappings required. The specification is detailed enough for any competent developer to implement and serves as the authoritative reference for your integration architecture going forward.
CRM Field Mapping
We map every data point your website and payment platforms generate to the corresponding fields in Salesforce Japan, HubSpot Japan, or Kintone. For Japanese CRM setups, this includes mapping fields for furigana name input, company name in kanji and kana, Japanese address structure, and any custom fields specific to your business process. Where field types or character set handling create mismatches, we resolve them in the specification before the build.
API and Webhook Setup
We build the connections between your website and your target systems using the appropriate API and webhook mechanisms for each platform. For Salesforce Japan and HubSpot Japan, this uses their native APIs. For Kintone, this uses Cybozu's REST API. For GMO Payment Gateway and Stripe Japan, webhook events trigger CRM updates and email platform flows. Every connection is tested before handover.
Form-to-CRM Flow
We configure each website form to submit data directly to your CRM in real time, with full field mapping, UTM parameter capture, and any conditional routing logic required. For Japanese-language forms, we ensure that field mapping handles full-width and half-width character inputs correctly, and that furigana or kana-required fields map to the correct CRM properties.
Data Quality Checks
We configure deduplication rules, validation logic, and data cleansing processes to prevent duplicate or malformed records from entering your CRM. For Japanese data, this includes handling the common case where a contact submits once in kanji and once in romaji, creating duplicate records that standard Latin-character deduplication does not catch. We build deduplication logic suited to Japanese name and company data.
Automation Setup
We build the lead routing rules, assignment logic, notification triggers, and lifecycle stage transitions your CRM requires. For Japanese business contexts, this includes routing by industry, region, or deal size, and configuring notification formats and escalation paths that align with your internal communication conventions. Automation is configured in both Japanese and English interface languages as required by your team.
Testing
We test every integration end to end with real and synthetic data, including Japanese character input in all relevant fields. We test UTM parameter pass-through, payment event CRM updates, automation trigger firing, deduplication logic, and edge cases for incomplete or duplicate submissions. Test results are documented and reviewed with you before any connection goes live.
Documentation
We produce written documentation for every integration, in both Japanese and English where required, covering what each connection does, how it was built, where the relevant settings live in each platform, and what to check if something stops working. Documentation is written for your internal team or IT department to manage and maintain without depending on us.
