Outcome: Shanghai WFOE with ICP filing, in-region hosting on a local cloud, PIPL-compliant Chinese notices, and a data map that passed enterprise procurement review — first Chinese enterprise contract in week 16.
The brief
The vendor sold offshore to Chinese multinationals, but their China subsidiaries could not buy: no fapiao from a foreign entity, data-residency policy, and procurement rules requiring a local contracting party. The fix was a minimal viable China presence — not a product rebuild.
What we did
- Entity + ICP: Shanghai WFOE (service scope), then ICP filing for the informational domain and evaluation of whether the commercial license (EDI/ICP) was triggered — it was not, given the licensing model.
- Hosting architecture: in-region deployment on a licensed local cloud; the offshore product stayed for global tenants — no cross-border tenant data flows in scope.
- The data map: one page — what personal data the China tenant processes, where it lives, what never leaves China. That page was the procurement team's entire data question answered.
- PIPL notices: Chinese-language privacy notices and DPA templates aligned to the notices.
- Commercial rails: fapiao issuance, local labor for the two Shanghai hires, banking with a cross-border desk for the royalty-lite structure ( Trademark license to the WFOE, royalties with TP documentation).
Lesson
Chinese enterprise deals die on procurement checkboxes, not product gaps. The entity + fapiao + data-residency + data-map package is what SaaS vendors actually sell into China — build it deliberately.
One partner for the whole journey
Zhonghui Consulting — licensed, fixed-fee, English-speaking. cross-border compliance engagements, ICPA-reviewed.
See All Services & Pricing → Free AI Entry CheckGeneral information only — not legal, tax, or immigration advice. Rules change; verify with official sources (SAMR, STA, SAFE, MOFCOM, NIA) and licensed advisors before acting.