Lead gen forms and CRM sync for Japanese data

I ship Japanese lead forms at six fields. The platform permits twelve, and the six I leave off are the reason the form gets finished on a phone on a train. The harder decision comes before that, though. A LinkedIn form prefills from the member's profile, a great many Japanese profiles are maintained in romaji, and so the lead lands as Haruka Ono while your CRM keys on the kanji name and demands a kana reading. Furigana is not a native field. Making it a custom question stops it prefilling and costs completions. That trade is a judgement made per campaign, not a rule to copy from somewhere. The form: Company, department, job title, name, business email, and one qualifying question your sales team genuinely uses. Everything beyond that is a question a seller can ask in the first minute of the first call. The qualifying question is written with your sales lead in the room, because a question nobody reads is worse than no question at all. Consent is not an afterthought: the purpose-of-use statement required under Japan's personal information protection act appears at the point of collection, in Japanese, with a separate opt-in where data passes to a distributor or a third party. The join: Company name is a poor key in Japan. The same firm arrives with the corporate suffix leading, trailing, abbreviated in a single character, and romanized as a trading name, in full-width and half-width characters, across four campaigns. Accounts are resolved on the National Tax Agency corporate number where the company can be identified, and on a deterministic cleaning rule where it cannot, then deduplicated against existing records before the lead is created rather than after. Otherwise an account owner opens a duplicate, calls a contact already inside an open opportunity, and the campaign gets the blame. The sync: Salesforce, HubSpot and Marketo accept leads natively, and I configure the field mapping, the hidden campaign fields, and an alert for when the connection drops, which it does silently and is usually noticed weeks later by someone wondering why volume fell. Japanese marketing automation is a different build: SATORI, List Finder and kintone get a webhook endpoint and a mapped payload rather than a scheduled export, so first touch happens in minutes instead of the following morning. Routing: Leads route by account, not by volume. A contact from a tier one account goes to the named owner with the campaign and the document they downloaded attached to the record. Everything else enters a nurture track. Both rules are agreed with sales in writing before launch, because routing invented in week two after the first complaint never gets revisited. Not included: CRM implementation and lifecycle stage redesign. Deduplication of the database you already have. Nurture email content. Consent management platform selection and cookie banner work. Legal review of your privacy notice; I tell you what the form must display and your counsel approves the wording. Sales training on what to do with the lead once it arrives. Who this is not for: Teams measuring this work on cost per lead alone. Dropping the kana field, cutting to four fields and widening targeting will always produce a cheaper lead, and I will not build toward that number while a sales team quietly stops calling the list. Also not for companies whose CRM is a spreadsheet one person maintains: the sync has nowhere to land, and what you need first is a CRM project rather than this one.