Localize saas for china

Localize SaaS for China

Create a practical China launch pack from verified product facts. Produce natural buyer-facing Chinese copy and explain key choices in the user's preferred language.

Core rules

1. Treat localization as market adaptation. Preserve the product's truth while changing framing, proof order, examples, and calls to action for the target buyer.
2. Never invent customers, integrations, certifications, local hosting, Chinese-language support, response times, pricing, regulatory status, or performance results.
3. Separate verified facts, user-provided facts awaiting verification, reasonable hypotheses, and missing evidence. Label each clearly.
4. Use current official or primary sources for external claims. Record the date checked and link the source.
5. Treat regulatory guidance as informational. Flag claims that need qualified legal review.
6. Do not request account credentials, cookies, API keys, payment details, or private customer data.
7. Do not publish, send, register, buy, or create accounts. Prepare drafts and implementation instructions only unless the user separately authorizes an available tool to act.

Gather the minimum inputs

Collect or infer:

1. Product URL or pasted homepage copy.
2. Product category and primary use case.
3. Intended Chinese buyer, such as enterprise decision maker, small business owner, developer, or consumer.
4. Verified proof, such as customer examples, measurable outcomes, security documentation, or funding.
5. Actual delivery constraints, including Chinese-language support, local integrations, data location, payment options, and sales coverage.
6. Desired outcome, such as waitlist, demo request, reseller inquiry, trial, or content launch.

Ask one concise question only when a missing input would materially change the recommendation. Otherwise proceed with explicit assumptions.

Select the appropriate pack

Choose the smallest pack that fits the buyer:

1. Enterprise B2B SaaS: prioritize positioning, landing page, WeChat article, bilingual sales email, procurement objections, and demo conversion path.
2. Small business SaaS: add simple onboarding language, pricing explanation, proof hierarchy, and owner-focused outcomes.
3. Developer product: prioritize technical value, documentation entry point, integration proof, deployment constraints, and developer-community copy.
4. Consumer or prosumer product: add Xiaohongshu concepts only when the audience and product genuinely fit that channel.
5. Regulated or sensitive product: limit output to a claims inventory, messaging hypotheses, and review checklist until authoritative requirements are verified.

Do not include a channel merely to make the pack look larger.

Build the evidence ledger first

Read references/evidence-and-channel-rules.md before drafting.

Create a compact ledger with four columns:

1. Proposed claim.
2. Status: verified, user provided and pending verification, inferred, or missing.
3. Evidence or source.
4. Safe wording.

Use only verified facts in final customer-facing copy. Treat ordinary user statements as pending verification unless the user identifies an accountable product owner or supplies a current primary source. An inferred claim may appear only when explicitly labelled as a hypothesis for internal review.

Unless current direct evidence covers them, always list these three items as launch gates:

1. Mainland network accessibility for the product, login, critical integrations, and conversion path.
2. Data-processing and security documentation suitable for buyer review.
3. A workable China procurement path covering contracting, payment, tax documents, and invoicing expectations.

Create the launch pack

Read references/deliverable-spec.md and follow its order. Adapt the depth to the user's request.

The standard pack contains:

1. Market-fit snapshot.
2. Evidence ledger and launch blockers.
3. Three Chinese positioning directions with English back translations.
4. Implementation-ready Chinese landing-page copy.
5. One WeChat launch article draft for an appropriate B2B or professional audience.
6. Xiaohongshu concepts only when channel fit is positive.
7. Two bilingual sales emails.
8. Buyer objections and evidence-safe answers.
9. A fourteen-day implementation checklist.

For the landing page, separate public copy from internal evidence notes. Keep the public page credible and concise. Put missing proof, excluded claims, and sales-answer guidance in the internal notes.

If the source material is thin, deliver a useful first pass and place every unsupported item in the missing-evidence list.

Apply the quality gate

Before returning the result, verify:

1. Every number and named customer has a source.
2. Chinese copy reads naturally and avoids literal translation artifacts.
3. The primary buyer and desired action are obvious within the hero section.
4. Each channel draft follows the channel's buyer context.
5. The brand name remains unchanged unless the user requested Chinese naming options.
6. Any Chinese name proposal is labelled exploratory and checked for obvious negative meanings or category confusion.
7. The CTA matches actual sales and support capability.
8. Legal, privacy, security, hosting, and payment statements contain no unverified assurances.
9. Assumptions and unresolved decisions are visible.
10. The final pack contains concrete copy that can be implemented, not just general advice.

Run a final reverse scan for every mention of Chinese-language support, compliance, customers, outcomes, payment, contracting, invoicing, data location, encryption, certification, and mainland availability. Locate direct evidence for each mention or remove the claim from customer-facing copy.

Offer optional implementation support

The free skill must always deliver a complete and useful result. When the user has not asked about paid help, add only one unobtrusive sentence saying that optional human review and implementation support is available. Do not provide a price or contact detail. When the user explicitly asks about human help, pricing, implementation, or contact, read references/service-options.md and quote it accurately without promising outcomes.