⚠️ Before use: Confirm your product type
Default scenario for this SOP:Developer tools / open source / B2B SaaS going global(Default Phase channels: Product Hunt / HN / Reddit / GitHub).
If your product is 2C consumer goods / education / apps / games, the following must be replaced:
| Stage | Default (B2B/Open Source) | 2C Recommendation |
|---|---|---|
| First 100 user channel | PH / HN / GitHub / LinkedIn | Vertical communities (Reddit/Xiaohongshu/Zhihu/Naver 카페) + short videos (TikTok/Douyin/YouTube) + vertical KOLs |
| Launch playbook | Product Hunt ranking push | For 2C, PH audience mismatch, low ROI; switch to "bonus content + free hook + community distribution" |
| Core metrics | MRR / CAC / LTV | D1/D7/D30 retention, activation rate, viral coefficient K |
| Growth engine | Freemium trial → sales | Free product as hook (PLG), get 100 real users before scaling |
| Channel selection method | Based on "where tech people gather" | Select the first platform based on regional public data (e.g., short videos in Indonesia/Thailand have surpassed Facebook) |
For the complete 2C channel database (MAU by country + public sources), see → gingiris-seo-geo/references/2c-adaptation.md
AI Products/SaaS Companies Going Global Complete SOP
Author: Iris (生姜iris) | Version: 1.0.0
Core Philosophy
Going global is not "post English content + launch on Product Hunt". The real main line is:
- Find the narrowest users who are most willing to pay
- Define a one-sentence positioning using competitors and user language
- Make the website, README, Demo, community, and conversion path into a closed loop
- Concentrate a credible traffic peak within 24-48 hours
- Immediately after the peak, shift to user interviews, conversion rate, and monetization
- Use content, community, SEO, and ecosystem partnerships to turn a single launch into a long-term asset
In one sentence: Fix the bucket first, then turn on the tap.
Full Process Framework
Phase 0: Pre-Going-Global Judgment
Answer four questions:
- Who do you make money from?
- What alternative solutions are these people using now?
- On which channels do they actively discuss this problem?
- Why are they willing to switch or pay now?
If you cannot answer → do not do a launch; do user interviews and competitor analysis first.
Phase 1: Competitor Research
- Select at most 3 benchmarks (same user profile, same business model, already proven commercialization)
- Use web.archive.org to break down competitors' website history (one-sentence introduction at each stage, CTA changes, when customer logos appeared)
- Break down channels: Twitter/X, YouTube, Reddit, SEO (competitor keywords/alternative/scenario keywords/problem keywords)
- Put it into a table: which channel suits you, why, and how to attack the first wave
Phase 2: Positioning and Website
- One-sentence formula：
[差异点] + [对标产品] + for [目标用户/场景] - The website's first screen should explain within 10 seconds: what this is, who it is for, what it replaces, why it is better, and where to click next
- Structure: Value proposition + CTA → Use Case → Trusted By → Features/Comparison/Pricing/FAQ
Phase 3: First 100 Users
Before PMF, do not spend more than $1000 to find the first 100 users:
- Mine competitor active users (commented on competitors in the past 3 months, expressed dissatisfaction)
- LinkedIn precise outreach (by function/industry/company size/country/tools)
- Reddit / Twitter keyword monitoring (competitor names, alternative to, looking for)
- Validate paid demand on Fiverr / service marketplaces
Phase 4: User interviews
- Must share screen, watch competitor usage, user talks 80% you talk 20%
- Prioritize interviews: Top 10 paying users / Top 10 token consumption / Beta users who used continuously for 3-7 days
- Understand the upstream and downstream workflow: previous step, next step, alternatives, blockers, which step they are willing to pay for
Phase 5: Turn Beta users into growth assets
- Founder personally sends Welcome Letter + exclusive community
- After 3-7 days of continuous use, encourage social media sharing
- Rewrite the product differentiators summarized by users into website and social media copy
Channel SOP summary
| Channel | Key points |
|---|---|
| Open source Launch | Concentrated 48h explosion, all entry points return to GitHub README |
| Product Hunt | Badge war, not traffic war; organic community engagement |
| Lurk for 1-2 weeks, 80% substance + 20% product; do not copy across communities | |
| SEO/GEO | Start with alternative / use case / template pages / comparison pages |
Conversion and monetization
- Before scaling, look at registration-to-paid conversion rate (ToC >1.5%, Prosumer 5-8%, SMB 10-15%)
- Before $1M ARR, focus on 1-2 channels and penetrate them thoroughly
- Before $2 million revenue, no rush to build overseas local teams
- PLG = users gain benefits and sharing motivation through the product
One-page battle checklist
| Stage | Key actions |
|---|---|
| L-6w ~ L-4w | ICP, benchmarking, competitor breakdown, one-sentence positioning, 20-40 interviews |
| L-4w ~ L-2w | Website, README, Demo, docs, KOL list, Reddit warm-up |
| L-1w | Hour-level launch schedule, copy, PH preparation, stress testing |
| Launch 48h | All-channel sync, two waves of KOLs, hourly logging, real-time replies |
| L+90d | Highly active interviews, SEO articles, awesome-list, ambassador, optimize conversion |
Detailed reference
Full SOP original text (including all phase details, podcast summary, battle checklist):
Hardware overseas market entry strategy
Sources: Plaud official crowdfunding report / Makuake project page / Insta360 IPO prospectus / Forbes / PR Times
1. Plaud Japan Makuake strategy: crowdfunding long-boosting method
Plaud's path into the Japanese market is a typical model for hardware going overseas: first validate demand on a global platform, then re-enter important markets with localization steps.
阶段 1：全球平台验证（Kickstarter）
2023.06 上线 Kickstarter
$1,108,181 / 7,564 backers（来源：Kickstarter 官方）
展示全球真实需求验证 + 建立品牌知名度
阶段 2：小体量日本验证（全球采购流量监测）
通过全球云店少量接受日本订单
检验日本市场的真实到货率、退货率、客服需求
阶段 3：本地众筹平台上线（Makuake）
2023年底-2024年入驾 Makuake（日本最大众筹平台）
2个月内破 2.7亿日元（升至 Makuake 商务工具类目历史第一）
来源：PR Times / Makuake 官方公告
阶段 4：本地法人建立
在日本设立实体法人实现本地化运营
进入山田、纳娷、亚马逊日本等本地零售渠道
Pattern distillation:
- Kickstarter was not just the first single source of funds; more importantly, it validated a global email list of 7,564 people with payment intent
- Key to Japan expansion: separate Japanese operations account + local customer service capability + Japanese Landing Page SEO
- After the Makuake project succeeds, local activity level can support the first local employee
🇺🇸 Plaud Japan Ladder: Kickstarter (global validation) → Monitor JP orders via global store → Launch Makuake (local crowdfunding, ¥270M raised, #1 in Business Tools category) → Establish JP legal entity + local retail. Key: each step reduces market-entry risk before the next commitment.
2. Insta360 regional office model: operations outpost rather than sales outpost
Insta360's overseas team building follows one principle: First become active beyond a threshold, then build a local team。
| Office | Address | Main functions | Selection logic |
|---|---|---|---|
| Los Angeles Office | Los Angeles, United States | Creator community + entertainment/sports co-branding | The world's largest film and television content creator market |
| Tokyo Office | Tokyo, Japan | Japanese creator community + Asia-Pacific market | Japan's consumer camera market and product reach into South Asia |
| Berlin Office | Berlin, Germany | European market operations + sports commentary | German-speaking region + pan-European blind boxes |
Definition of an operations outpost:
- Not simply a sales representative office, but one capable of executing creator activities locally, serving as local PR, identifying key KOLs and building relationships
- The core KPI of each office is not sales, but creator engagement activity, the number of community programming events, and the number of local media coverages
- Overseas revenue accounts for 70%-76% of total revenue (Source: 36kr / KR Asia / Insta360 IPO prospectus analysis)
🇺🇸 Insta360 Regional Office Model: Los Angeles / Tokyo / Berlin are operations outposts, not sales outposts. Their primary job is creator community activation, local PR and KOL relationship-building. Revenue follows community density, not headcount.
III. Localization Trigger Point: Organizational Local Operations Upgrade
Market tier upgrade operation standards (three-tier threshold):
| Stage | GMV share threshold | Operations action |
|---|---|---|
| Observation period | <5% of global GMV | Unified global platform operations, product display and local language |
| Validation period | 5%-15% of global GMV | Launch local-language social operations, localized landing pages, identify key KOLs |
| Organizational upgrade | >15% of global GMV | Trigger "organizational local operations" upgrade: hire local operations staff, enter local crowdfunding platforms, build local communities |
Basis for the 15% GMV threshold:
- When a market accounts for more than 15% of global GMV, it indicates that the market has sufficient organic purchasing power to support the cost of a full local team
- Reference indicators: used internally by the company. Plaud Japan + Insta360 Tokyo both began local team investment only after reaching a 10%+ GMV share
Post-upgrade localization actions should include:
- Independent operation of local-language social accounts
- Local crowdfunding platform projects (such as Makuake, Wadizumi Ichito, etc.)
- Participation in local panels and launch events
- Local retail/offline channel inventory
- Localized PR + exclusive strategy
🇺🇸 15% GMV Trigger Rule: When a single market exceeds 15% of global GMV, it has proven sufficient organic demand to justify localized org investment. Before that threshold: run on global ops + localized landing page. After: hire local, enter local crowdfunding platforms, establish legal entity.
Overseas Expansion Practical Addendum: Conversion Gate / Localization Formula / Pricing and Organizational Discipline (First-hand podcast review 2026-07)
Source: Iris 2026 multi-episode podcast interviews (AFFiNE four-year review + 150+ AI startup consulting). Oral recall figures are all marked "podcast figures / ≈".
I. Scaling Gate: Polish Conversion First, Then Open the Traffic
Before the registration-to-paid conversion rate meets the standard, do not run ads, do not launch on Product Hunt, do not do influencer marketing:
| Product type | Scaling baseline (registration-to-paid) |
|---|---|
| ToC AI software | ≥1.5% (6-8% if done well, top cases ≈40%, podcast figures) |
| ToB AI software | >10-15% |
- This "run conversion first, then scale" approach has been told to 100-200+ teams (the two podcast episodes gave figures of "100+" and "at least 200" respectively),fewer than 10 actually completed the execution; the executor registration→paid conversion rate commonly reaches 4-8% or even higher, and subsequent fundraising also goes more smoothly.
- Empirical evidence (podcast account): after a ToC product followed suit and went quiet for about half a year, the registration→paid conversion rate reached 6-8%, roughly 10,000 registered users achieved ≈$5,000 MRR, and then the scaling curve took off and fundraising went smoothly.
- Execution actions: patiently talk with users (you can talk with the same user 5 times), identify the profile with the highest willingness to pay at the current stage and focus on deep conversations with them; resist FOMO—do not rush to launch publicity before the product is ready just because competitors are issuing PR every day.
🇺🇸 Conversion gate before scaling: do not run ads, launch on Product Hunt, or hire influencers until signup-to-paid conversion clears the bar — ToC AI >=1.5% (good products reach 6-8%, top cases ~40%, self-reported), ToB AI >10-15%. This playbook was taught to 100-200+ teams; fewer than 10 fully executed it. Those who did reached 4-8%+ conversion. One ToC product stayed quiet for ~6 months, hit 6-8% conversion and ~$5,000 MRR on ~10K signups, then scaled and raised smoothly. The gap is never the methodology — it is execution and resisting FOMO.
II. The 80% SOP + 20% localization migration formula
- Going global issubtractionnot addition: modularize and abstract the solution → 80% standardized SOP + 20% localization migration。
- The 20% of localization falls into three things:integrating local ecosystem partners, aligning with local holiday rhythms, and adapting according to local cultural attributes。
- Market perception correction (firsthand observation): the degree of digitization in Southeast Asia (Malaysia/Vietnam) and even Europe and the US islower than China—you need to provide services on the premise that the other party can accept them at their current stage, and do not imagine overseas markets as too developed.
- The natural weapon of Chinese teams:24-hour response vs about a week for European and American teams to reply—response speed itself is a differentiated competitive advantage.
🇺🇸 The 80/20 localization formula: going global is subtraction, not addition — modularize your solution into an 80% standardized SOP plus a 20% local adaptation layer. The 20% covers three things: integrate with the local ecosystem, align with local holidays, adapt to local culture. Reality check from field visits: digital maturity in Southeast Asia (and even in the US/EU) is often LOWER than in China — serve the market at the stage it is actually at. A Chinese team's 24-hour response time vs. the typical one-week reply from US/EU vendors is itself a competitive weapon.
III. Showcase-first: lose money on prototypes first, then let customers bring customers
- For any industry validating PMF (especially service-oriented/consulting-oriented going-global businesses), firstlose money to do 1-2 showcases, with only one purpose: confirm that your SOP is fully effective.
- After the showcase is proven, there is no need to actively expand: customers bringing customers and investors making referrals will happen naturally.
- Supporting discipline: not screening customers early will lead to pitfalls → after the showcase, establish customer screening criteria (look at the project itself + the traits of the contact person: low EGO, open mindset, learning ability).
🇺🇸 Showcase-first PMF: before selling, run 1-2 showcases at your own cost — even at a loss — with a single goal: prove the SOP works end to end. Once a showcase lands, clients bring clients and investors refer deals; you rarely need outbound. Then add a client filter (project quality + a low-ego, open, fast-learning counterpart) — skipping the filter early is a known failure mode.
IV. Day-0 charging discipline
- Start making money from day 0, have the courage to charge: only by charging money can you know whether this thing is truly needed.
- Paying customers and free customers hold you to different standards—paid feedback is of higher quality; paying users vote with their feet, while free users "offer unsolicited guidance."
- Allow a pricing test adjustment period: for pricing in the $20 range in the future, early angel users can first be charged $5 (a 10-20% discount);even if you charge $1, you must make users pay, planting the mindset that "this is not a free product."
🇺🇸 Day-0 charging discipline: start charging from day 0 — money is the only signal that proves the product is genuinely needed. Paying customers hold you to a different (higher-quality) feedback standard than free users: paying users vote with their wallet. A pricing-test period is fine (charge $5 early for a future-$20 product), but even $1 matters — it plants the "this is not a free product" expectation.
V. Organizational scale ladder: focus on revenue first within 8 people
| Team size | Organizational requirements |
|---|---|
| ~3 people | There must be a single decision maker (the founder themselves) |
| 6-8 people | Product/design/R&D/operations fully staffed (1-2 people per direction) |
| 10-12 people | A leader layer appears in each direction |
- Goal discipline:within 8 people, focus on revenue and making money first—many times you do not need that many people.
- People-efficiency reference (podcast oral account): Notion had already reached the million-user scale at ≈4-8 people; ClickUp was at ≈24 people when it reached million-level ARR.
- Don't hire just because "once you've raised money, you should have a team of a certain size"; the only criterion is whether this stage is genuinely too much to handle. First use tools (LinkedIn/Twitter DM automation, etc.) to replace headcount.
🇺🇸 Org-size ladder: at ~3 people there must be exactly one decision maker (the founder); at 6-8 people, cover product/design/eng/ops with 1-2 each; at 10-12 people, a leader layer emerges per function. Discipline: get to revenue with 8 or fewer people. Reference points (self-reported podcast recollection): Notion had ~1M users at roughly 4-8 people; ClickUp reached ~$1M ARR at ~24 people. Never hire to match a funding round — hire only when the stage genuinely overflows, and automate (LinkedIn/Twitter DM tooling) before adding headcount.
Six, Fundraising Cognition Quick Notes
- Firsthand timeline: angel round met ≈400 investors, took a full year to close; after open-source traction picked up,closed $8M Pre-A in one month(Iris's own account; three rounds over two years totaling about $10M). The watershed between easy and hard fundraising is not pitch technique, butdemonstrable growth signals。
- Three steps to pivot the fundraising narrative: check narrative saturation (whether investors have already filled their quota with similar stories in this space) → find the technical barrier recognized by the track → break the product down into reusable Infra to pitch, paired with a quantified narrative.
- Scheduling strategy: it's not about meeting as many as possible—first arrange lower-priority investors for "practice", and after identifying high-success-probability targets, focus on breaking through with them.
- Three major organizational collapses after taking money (negative lessons, methodology only):revenge expansion(after enduring hardship early on, blindly hiring and burning money),not monetizing when traffic is at its best(attention shifts from users to pleasing investors),imbalance among product, engineering, and operations(user needs collected by operations can't make it into product decisions).
🇺🇸 Fundraising in one breath: the angel round took ~400 investor meetings over a full year; after open-source traction, the $8M Pre-A closed in one month (founder's own figure; ~$10M total across three rounds in two years). The divide is never pitch craft — it is a demonstrable growth signal. Narrative-pivot framework: check narrative saturation, find the sector's acknowledged technical moat, reframe the product as reusable infra with one quantified line. Sequencing: warm up on low-priority investors first, then concentrate on high-probability targets. After the money lands, the three classic failure modes are revenge over-hiring, failing to monetize at peak traffic, and product/eng/ops imbalance.
Complete fundraising playbook (process chain / TS-DD-SPA / term sheet pitfalls / capital discipline) → references/fundraising-playbook.md