Services Insights Knowledge Base Skills 中文 EN Get in touch

THE GROWTH FIELD GUIDE / GLOBAL GROWTH

From product launch to acquisition,
practical guidance for every step.

Built on Ginger & Iris's hands-on experience advising 80+ companies, this guide turns real project work into practical steps, templates, and examples.

Explore the knowledge base ↓

THE COMPLETE COLLECTION

Global Growth Field Guide · Complete Knowledge Base

From your first global project to steady progress

Explore demand validation, product launches, customer acquisition, B2B sales, and service business fundamentals as your project needs them.

22documents 280k+characters

Includes the three topic packs below and the OPC Starter Guide.

¥599

KNOWLEDGE BASE · CHOOSE A TOPIC

Practical resources, available by topic

Selected from the complete knowledge base, from ¥49. No duplicate purchase is needed with the complete collection.

TOPIC PACK · AVAILABLE INDIVIDUALLY

Paid Demand Validation

¥199

5 documents

Users say they want it—but will they pay?

Connect competitor research, user interviews, product testing, and pricing validation to decide what to invest in next.

  • Competitor research framework
  • User interview and testing workflows
  • Pricing and monetization validation

Selected from the complete global growth knowledge base

TOPIC PACK · AVAILABLE INDIVIDUALLY

Launch & Acquisition

¥329

11 documents

The product is ready. How do you launch and find users?

Follow practical steps, content methods, and review frameworks from launch preparation through channel operations.

  • Product launch and Launch workflows
  • KOL, UGC, and Reddit operations
  • Content distribution, community, and growth reviews

Selected from the complete global growth knowledge base

TOPIC PACK · AVAILABLE INDIVIDUALLY

B2B Business Starter

¥199

5 documents

You have interested business customers. How do you turn talks into deals?

Map the B2B journey from customer trust and requirements discovery to pricing, delivery, and collaboration.

  • B2B sales and delivery SOP
  • Pricing, SOW, and contract templates
  • Brand building and team collaboration

Selected from the complete global growth knowledge base

SERVICE BUSINESS · 1 GUIDE

OPC Starter Guide

Turn professional expertise into a service you can sell. Included in the ¥599 complete collection or available separately.

¥49

Topic packs are sold by content scope. VIP peer community, private member sessions, and lifetime updates are included with the complete collection above. The catalog dialog shows chapter titles and page numbers, not paid content.

INDEPENDENT COURSE · XIAOBOT

Global Growth System Course

A field guide for building global growth

Build a systematic understanding of global growth, from user research and product positioning to channel selection. Includes 18 core lessons and 3 special-topic lessons, with notes, audio, exercises, and a VIP peer community.

¥299

Preview on Xiaobot ↗

FAQ

Frequently asked questions

If I buy the Global Growth Field Guide · Complete Knowledge Base, should I also buy topic packs?

The Global Growth Field Guide · Complete Knowledge Base already includes Paid Demand Validation, Launch & Acquisition, B2B Business Starter, and the OPC Starter Guide. You do not need to buy them again. If you only need selected materials, you can purchase the relevant topic pack on its own.

For my first global project, should I choose the Global Growth Field Guide or the Global Growth System Course?

If you already have a project, start with the Global Growth Field Guide. Choose a topic pack to advance one task, or the Complete Knowledge Base for methods across multiple stages. If you want a structured introduction to users, products, channels, and other fundamentals, choose the independently sold Global Growth System Course on Xiaobot.

Does the Global Growth Field Guide · Complete Knowledge Base include the Global Growth System Course on Xiaobot?

No. The Global Growth System Course is a separate course sold on Xiaobot, focused on foundational knowledge and a systematic understanding. The Complete Knowledge Base provides execution steps, frameworks, templates, and cases. Purchase either or both based on what you need.

GINGIRIS / LEARN & GROW

Want to learn more about global growth?

For an introduction, recommendations, or purchasing questions, add us on WeChat: staywildgrow

The current local edition contains approximately 287,000 characters across Chinese and English, including templates and appendices. Content is updated continuously.

GINGIRIS / COMPLETE CONTENTS

Global Growth Field Guide · Complete Contents

22 documents organized by topic. Browse chapter titles and PDF page numbers; paid content is not included.

Paid Demand Validation 5 documents
User Interview Field Guide Original 15 pages · 47 entries
  1. 1. Why conduct user interviews? (p. 1)
  2. 1.1 Core value (p. 1)
  3. 1.2 Benchmark metrics (p. 1)
  4. 2. User interview workflow (p. 1)
  5. 2.1 Prepare for interviews (p. 2)
  6. Step 1: Define the interview objective (p. 2)
  7. Step 2: Select interview participants (p. 2)
  8. Step 3: Schedule participants (p. 3)
  9. 2.2 Conduct the interview (p. 3)
  10. Interview setup (p. 3)
  11. Opening the interview (5 minutes) (p. 3)
  12. 3. Core interview question framework (p. 4)
  13. 3.1 Background (required) (p. 4)
  14. 3.2 Deep dive (core questions) (p. 4)
  15. Explore the current workflow (p. 4)
  16. Compare alternatives (p. 5)
  17. Explore pain points (p. 5)
  18. Willingness to pay (p. 5)
  19. 3.3 Screen sharing (critical) (p. 6)
  20. 4. Close the interview and follow up (p. 6)
  21. 4.1 Closing the interview (5 minutes) (p. 6)
  22. 4.2 Post-interview review (required) (p. 7)
  23. 5. User persona analysis templates (p. 8)
  24. 5.1 Basic information table (p. 8)
  25. 5.2 User behavior table (p. 9)
  26. 5.3 User interview notes (p. 9)
  27. 6. User segmentation criteria (p. 10)
  28. 6.1 Segmentation dimensions (p. 10)
  29. 6.2 User tiers (p. 11)
  30. 7. Analyze and apply interview data (p. 11)
  31. 7.1 Summarize interview findings (p. 11)
  32. 7.2 Deliverables (p. 12)
  33. 8. Interview tools and resources (p. 12)
  34. 8.1 Survey tools (p. 12)
  35. 8.2 Note-taking tools (p. 12)
  36. 8.3 User management (p. 13)
  37. 8.4 Communication tools (p. 13)
  38. 9. Frequently asked questions (p. 13)
  39. Q1: What if a user declines an interview? (p. 13)
  40. Q2: What if a user feels nervous and struggles to speak? (p. 13)
  41. Q3: How do you prioritize a long list of user requests? (p. 13)
  42. Q4: How can you tell if a user is giving superficial answers? (p. 13)
  43. 10. Reference documents (p. 14)
  44. Appendix: Practical activation and retention optimization data (p. 14)
  45. Key insights into new-user behavior (p. 14)
  46. When retention should take priority over acquisition (p. 14)
  47. Close the loop from user interviews to product iteration (p. 14)
User Testing and Cold-Start Operations Methodology Original 13 pages · 30 entries
  1. 1. Beta testing design framework (p. 1)
  2. 1.1 Three layers of testing objectives (p. 1)
  3. 1.2 Principles for designing test tasks (p. 1)
  4. 1.3 Staged email onboarding sequence (p. 2)
  5. 1.4 Live test call scripts (p. 2)
  6. 1.5 Use the wait time to learn about users (p. 3)
  7. 1.6 Design feedback questions (p. 4)
  8. 2. User outreach and funnel management (p. 5)
  9. 2.1 Cold outreach funnel structure (p. 5)
  10. 2.2 Iterate on messaging (p. 5)
  11. 2.3 Multichannel outreach strategy (p. 6)
  12. 3. User segmentation and management (p. 6)
  13. 3.1 Two-tier beta user program (p. 6)
  14. 3.2 Persona categories and PMF value assessment (p. 7)
  15. 3.3 Design a user tracking sheet (p. 8)
  16. 4. Techniques for deeper user interviews (p. 8)
  17. 4.1 Compare workflows (p. 8)
  18. 4.2 Capture users' language to improve messaging (p. 8)
  19. 4.3 Ask how much users would pay (p. 9)
  20. 5. Churn analysis framework (p. 9)
  21. 5.1 Categorize churn reasons (p. 9)
  22. 5.2 Interview former users (p. 10)
  23. 6. Reusable templates (p. 10)
  24. 6.1 Beta test invitation template (p. 10)
  25. 6.2 Bug report collection template (p. 11)
  26. 6.3 Evaluate users after testing (p. 11)
  27. Appendix: Cold-start data benchmarks (p. 12)
  28. Key metrics from cold start to scale (p. 12)
  29. Channel efficiency during cold start (p. 13)
  30. Core principles for beta testing (p. 13)
Competitor Research SOP Original 24 pages · 50 entries
  1. Gingiris competitor research SOP (p. 1)
  2. 1. Core competitor research framework (p. 1)
  3. 1.1 Four-step research method (p. 1)
  4. 1.2 Tool list (p. 1)
  5. 2. Website teardown methodology (p. 2)
  6. 2.1 Analyze each version and product stage (p. 2)
  7. 2.2 Teardown framework (p. 2)
  8. 2.3 Steps and documentation template (p. 3)
  9. 3. Analyze social-channel content (p. 3)
  10. 3.1 Identify traffic sources before the teardown (p. 3)
  11. 3.2 Twitter/X teardown framework (p. 4)
  12. Account portfolio analysis (p. 4)
  13. Analyze the publishing cadence (p. 4)
  14. Content category tracking template (p. 5)
  15. KOL partnership tracking table (p. 6)
  16. Reddit teardown framework (p. 6)
  17. 3.3 YouTube teardown framework (p. 6)
  18. 3.4 Compare content strategies across platforms (p. 7)
  19. 4. Analyze the competitor's distribution flywheel (p. 8)
  20. 4.1 Core growth flywheel structure (p. 8)
  21. 4.2 Template for analyzing the flywheel's six stages (p. 8)
  22. 4.3 Assess the strength of a growth flywheel (p. 9)
  23. 4.4 Lovable flywheel case study (p. 9)
  24. 5. Analyze content distribution touchpoints (p. 10)
  25. 5.1 Four-stage distribution model (p. 10)
  26. 5.2 Quantitative template for distribution stages (p. 10)
  27. 5.3 Analyze content angles (p. 11)
  28. 5.4 Rank content types by performance, validated by Lovable data (p. 11)
  29. 5.5 Identify influential KOLs (p. 12)
  30. 5.6 Lovable's full November distribution timeline (p. 12)
  31. 6. Analyze X / Twitter distribution in depth (p. 13)
  32. 6.1 Search query templates (p. 13)
  33. 6.2 Data dimensions and calculation methods (p. 14)
  34. 6.3 Analyze a breakout post (p. 14)
  35. A. Verify basic information (p. 15)
  36. B. Break down the content (p. 15)
  37. C. Reconstruct the distribution path (p. 15)
  38. 6.4 Analyze the comment section (p. 16)
  39. 7. Synthesize key insights (p. 16)
  40. 7.1 Five-dimensional insight framework (p. 16)
  41. 7.2 Deep ICP analysis template, using Lovable as a reference (p. 17)
  42. 7.3 Pricing strategy analysis framework (p. 17)
  43. 7.4 Self-review checklist (p. 18)
  44. 8. Recommendations for Gingiris competitor research (p. 19)
  45. 8.1 Competitor tiers (p. 19)
  46. 8.2 Recommended research cadence (p. 19)
  47. 8.3 Metrics to monitor (p. 19)
  48. Appendix 1: Tools and resources (p. 20)
  49. Appendix 2: Reference documents (p. 20)
  50. Appendix 3: Competitor research report template (fillable Markdown) (p. 21)
Open-Source Product Competitor Analysis Framework Original 20 pages · 45 entries
  1. 1. Quick positioning (5 minutes) (p. 1)
  2. 2. Open-source product growth flywheel model (p. 1)
  3. 3. Diagnose README conversion (p. 2)
  4. 4. Analyze website evolution (p. 3)
  5. 5. Traffic channels and attribution (p. 3)
  6. 5.1 Overall traffic picture (p. 3)
  7. 5.2 Estimate channel contribution by stage (p. 4)
  8. 6. Deep dive into social channels (p. 4)
  9. 6.1 Twitter / X account portfolio (p. 4)
  10. 6.2 Reddit teardown (p. 5)
  11. 6.3 YouTube (p. 5)
  12. 6.4 Instagram / TikTok: short-video discovery channels (p. 6)
  13. 7. Identify the growth model (p. 6)
  14. 8. Assess content Hook effectiveness (p. 7)
  15. 8.1 High-performing Hook types validated by open-source products (p. 7)
  16. 8.2 Attribute competitor content performance (p. 7)
  17. 9. Framework for replicating a Trending launch (p. 8)
  18. T-14 to T-7: prepare conversion assets (p. 8)
  19. T-7 to T-1: prepare seed content (p. 8)
  20. T0 to T+2: publish in concentrated waves (p. 8)
  21. T+3 to T+14: amplify during the leaderboard period (p. 8)
  22. 10. Attribution instrumentation recommendations (p. 9)
  23. 11. Diagnostic report template (p. 9)
  24. Appendix A: Reference resources (p. 9)
  25. Appendix B: Open-source research tools and sites (p. 10)
  26. GitHub ecosystem data (p. 10)
  27. Downloads and package managers (p. 11)
  28. Communities and discussion platforms (p. 11)
  29. Traffic and SEO (p. 12)
  30. Product discovery and comparison (p. 12)
  31. Social and KOL monitoring (p. 13)
  32. Appendix C: Open-source competitor teardown SOP (step by step) (p. 13)
  33. Step 0: Choose research targets and objectives (10 minutes) (p. 13)
  34. Step 1: Collect GitHub repository basics (15 minutes per competitor) (p. 14)
  35. Step 2: Analyze README and repository conversion (15 minutes per competitor) (p. 15)
  36. Step 3: Analyze website version history (20 minutes per competitor) (p. 16)
  37. Step 4: Map traffic sources and channel mix (15 minutes per competitor) (p. 16)
  38. Step 5: Analyze each social channel (30 minutes per competitor) (p. 17)
  39. 5A. Twitter/X teardown (p. 17)
  40. 5B. Reddit teardown (p. 18)
  41. 5C. YouTube teardown (p. 18)
  42. 5D. Hacker News teardown (p. 18)
  43. Step 6: Attribute growth inflection points (20 minutes per competitor) (p. 18)
  44. Step 7: Summarize the growth model and strategy (15 minutes) (p. 19)
  45. Step 8: Deliver recommended actions (p. 19)
AI Product Pricing and Commercialization Validation Guide Original 16 pages · 30 entries
  1. 1. Use cases and execution overview (p. 2)
  2. 1.1 Choose a starting point based on the problem (p. 2)
  3. 1.2 Run one cycle using a single-page log (p. 2)
  4. 2. Validate user value and willingness to pay (p. 3)
  5. 2.1 Interview workflow (p. 3)
  6. 3. Choose a charging model and pricing unit (p. 4)
  7. 3.1 Compare common models (p. 4)
  8. 3.2 Distinguish usage, deliverables, and business outcomes (p. 4)
  9. 3.3 Readiness check before outcome-based pricing (p. 5)
  10. 4. Design plans, quotas, and free trials (p. 5)
  11. 4.1 Separate self-serve and sales-led plans (p. 5)
  12. 4.2 Help users estimate their bill (p. 6)
  13. 4.3 Free trial design SOP (p. 6)
  14. Case study: ChatCut lets users judge edits with their own footage (p. 7)
  15. 4.4 Categorize failed-payment reasons (p. 8)
  16. 5. Calculate costs and run stress tests (p. 9)
  17. 5.1 Calculate the cost of one task first (p. 9)
  18. 5.2 Stress-test example (p. 9)
  19. 6. Launch acceptance and price-change communication SOP (p. 10)
  20. 6.1 Verify plan commitments (p. 10)
  21. 6.2 Explain the impact when changing prices (p. 10)
  22. 7. Commercialization experiments and retrospectives (p. 11)
  23. 7.1 Maintain just this one page (p. 11)
  24. 7.2 Make one decision after each cycle (p. 11)
  25. 8. Public case studies (p. 11)
  26. 8.1 Intercom Fin: define a verifiable billable event around solving a problem (p. 12)
  27. 8.2 Fin for Sales: charge at a point the Agent can complete and prove (p. 13)
  28. 8.3 Cursor: explain quotas, overages, and migration for existing users when repricing (p. 15)
  29. 9. Where to start and supporting resources (p. 16)
  30. Supporting resources (p. 16)
Launch & Acquisition 11 documents
Open-Source Launch Action Guide Original 22 pages · 35 entries
  1. Introduction (p. 1)
  2. Part 1: Integrated Marketing SOP (p. 1)
  3. 1.1 Pre-launch preparation (T-4 weeks to T-1 week) (p. 1)
  4. 1.1.1 Strategy and positioning (T-4 weeks) (p. 2)
  5. 1.1.2 Core asset preparation (T-3 weeks) (p. 3)
  6. 1.1.3 Channels and resources (T-2 weeks) (p. 4)
  7. 1.1.4 Team roles and budget (T-1 week) (p. 5)
  8. 1.2 Open-source launch execution (T-3 to T+7 days) (p. 5)
  9. 1.2.1 Final pre-launch sprint (T-3 days) (p. 5)
  10. 1.2.2 Launch-day checklist for the US market (T-0) (p. 6)
  11. 1.2.3 Ongoing post-launch operations (T+1 to T+7) (p. 8)
  12. 1.3 Community and contributor management (p. 9)
  13. 1.4 Data monitoring and optimization (p. 10)
  14. 1.4.1 Core metric tracking (p. 10)
  15. 1.4.2 Issue diagnosis and optimization (p. 10)
  16. Part 2: Execution TODO checklist (p. 11)
  17. 2.1 Preparation (T-30 to T-7) (p. 11)
  18. 2.2 Final pre-launch sprint (T-3) (p. 11)
  19. 2.3 Launch-day execution (T0) (p. 12)
  20. 2.4 Ongoing post-launch operations (T+1 to T+7) (p. 12)
  21. Part 3: Channel distribution and resource list (p. 13)
  22. 3.1 Twitter/X channels (p. 13)
  23. 3.1.1 KOL outreach list and strategy (p. 13)
  24. 3.1.2 AI-assisted traffic and developer account list (p. 15)
  25. 3.2 Reddit communities (p. 16)
  26. Core strategy: post from established accounts with high Karma; read community rules first and consider asking others to upvote (p. 16)
  27. 3.3 Content and open-source platforms (p. 18)
  28. 3.3.1 Content platforms (p. 18)
  29. 3.3.2 Open-source platform submission checklist (p. 19)
  30. 3.4 Paid promotion channels (p. 19)
  31. 3.4.1 Paid PR distribution (p. 19)
  32. 3.4.2 Paid newsletters (p. 20)
  33. 3.4.3 YouTube ads (p. 20)
  34. 3.5 Overseas developer communities (p. 20)
  35. 3.6 Automation tools (p. 22)
Global Product Launch Guide Original 50 pages · 68 entries
  1. Overview (p. 1)
  2. Launch timeline at a glance (p. 2)
  3. Part 1: General preparation (L-6 to L-1 weeks) (p. 3)
  4. 1.1 Strategy definition (L-6 weeks) (p. 3)
  5. 1.2 Website optimization workflow SOP (L-5 to L-2 weeks) (p. 4)
  6. 1.3 Brand and feature video production SOP (L-5 to L-1 weeks) (p. 7)
  7. 1.3.1 Launch video SOP (p. 7)
  8. 1.3.2 Feature tutorial video SOP (p. 9)
  9. 1.4 End-to-end KOL partnership SOP (L-4 to L+1 weeks) (p. 11)
  10. Step 1: Identify KOLs and build a list (L-4 weeks) (p. 11)
  11. Step 2: Request KOL rates (L-4 weeks) (p. 12)
  12. Step 3: Confirm interest and send the content package (L-3 weeks) (p. 13)
  13. Step 4: Review the KOL's content draft (L-2 weeks) (p. 15)
  14. Step 5: Payment (L-1 day to L-Day) (p. 15)
  15. Step 6: Monitor publishing and collect data (L-Day to L+1 week) (p. 16)
  16. 1.5 Reddit operations SOP (p. 16)
  17. Core idea: move from selling products to solving problems (p. 16)
  18. Reddit AI Agent workflow (p. 17)
  19. Subreddit selection guide (p. 19)
  20. Reddit post copy template, refined from AI Agent drafts (p. 20)
  21. Part 2: UGC growth engine SOP (start at L-4 weeks; ongoing) (p. 22)
  22. 2.1 UGC growth philosophy: find brand ambassadors (p. 22)
  23. 2.2 Recruit and screen ambassadors / UGC partners (L-4 to L-2 weeks) (p. 23)
  24. 2.3 Ambassador management and content strategy (p. 24)
  25. 2.4 UGC publishing plan (p. 25)
  26. 2.5 UGC workflow and practical tools (p. 26)
  27. Part 3: Official product launch — Launch Week (p. 26)
  28. 3.1 Launch Week planning principles (p. 26)
  29. 3.2 Detailed daily Launch Week timeline (p. 27)
  30. Day 1 (Monday): Main launch and product reveal (p. 27)
  31. Day 2 (Tuesday): Getting-started tutorials to lower the barrier (p. 29)
  32. Day 3 (Wednesday): Deep dive into core feature 1 (p. 31)
  33. Day 4 (Thursday): Deep dive into core feature 2 (p. 31)
  34. Day 5 (Friday): Community engagement and Launch Week recap (p. 31)
  35. 3.3 After Launch Week: build momentum (Launch+1 week to PH-1 week) (p. 32)
  36. Part 4: Product Hunt launch (p. 33)
  37. 4.1 Choosing a Product Hunt launch date (p. 33)
  38. 4.2 Product Hunt-specific preparation (PH-1 week) (p. 33)
  39. 4.3 Product Hunt launch-day schedule: a 24-hour plan (p. 35)
  40. Core principle: stay active all day, use multiple waves, keep users engaged, and respond quickly (p. 35)
  41. 4.4 After the Product Hunt launch (p. 37)
  42. Part 5: Channel content templates (p. 38)
  43. 5.1 Official Twitter/X launch post template (p. 38)
  44. 5.2 Discord / Telegram community announcement template (p. 39)
  45. 5.3 Overseas community post template (Facebook / Telegram / WhatsApp) (p. 39)
  46. 5.4 Direct-message outreach template (p. 40)
  47. 5.5 LinkedIn influencer partnership outreach template (p. 41)
  48. Part 6: Launch channel checklist (p. 42)
  49. 6.1 Core launch platforms (required) (p. 42)
  50. 6.2 Social platforms (p. 42)
  51. 6.3 Community platforms (p. 43)
  52. 6.4 Overseas messaging communities (p. 44)
  53. 6.5 Media and content platforms (p. 44)
  54. 6.6 Developer communities and events (p. 45)
  55. Part 7: Omnichannel toolkit (p. 45)
  56. 7.1 Research and analytics tools (p. 45)
  57. 7.2 KOL and UGC management tools (p. 46)
  58. 7.3 Social automation and outreach tools (p. 47)
  59. 7.4 Link tracking and analytics tools (p. 47)
  60. 7.5 Content creation tools (p. 47)
  61. 7.6 Email marketing tools (p. 48)
  62. 7.7 Community discovery tools (p. 48)
  63. 7.8 Account resources (p. 48)
  64. Part 8: Long-term growth and ongoing operations (p. 49)
  65. 8.1 Data tracking and retrospectives (p. 49)
  66. 8.2 User development and community operations (p. 49)
  67. 8.3 Long-term growth engine: SEO and content marketing (p. 49)
  68. 8.4 Continuous iteration of the UGC engine (p. 50)
Global Product Launch Guide: Case Study Edition Original 60 pages · 91 entries
  1. Core principles (p. 1)
  2. Part 1: Core strategy—four pillars of viral reach (p. 1)
  3. 1.1 Pillar 1: product value underpins every story (p. 1)
  4. 1.2 Pillar 2: narratives that evolve through emotion (p. 2)
  5. 1.3 Pillar 3: the influencer flywheel (p. 2)
  6. 1.4 Pillar 4: platforms pass the baton (p. 2)
  7. Part 2: Case studies—Manus and Devin launch timelines (p. 3)
  8. 2.1 Manus launch timeline (March 2025) (p. 3)
  9. 2.2 Devin launch timeline (March 2024) (p. 4)
  10. 2.3 Comparing the cases: validating the distribution logic (p. 5)
  11. Part 3: Launch timeline at a glance (p. 6)
  12. Part 4: General preparation (L-6 to L-1 weeks) (p. 7)
  13. 4.1 Strategy definition (p. 7)
  14. 4.2 Website optimization workflow SOP (L-5 to L-2 weeks) (p. 9)
  15. 4.3 Brand and feature video production SOP (L-5 to L-1 weeks) (p. 11)
  16. 4.3.1 Launch video SOP (p. 11)
  17. 4.3.2 Feature tutorial video SOP (p. 13)
  18. 4.4 Media, influencers, and PR strategy (starting L-4 weeks) (p. 14)
  19. 4.4.1 Choose a launch strategy (p. 14)
  20. 4.4.2 Influencer segments and value assessment (p. 14)
  21. 4.4.3 Leading AI newsletter founders (highest priority) (p. 15)
  22. 4.4.4 Industry influencers and KOLs (high-value partners) (p. 16)
  23. 4.4.5 China–US tech media and analysts (China-US Connector) (p. 17)
  24. 4.4.6 Major technology media (p. 18)
  25. 4.4.7 Media and influencer outreach timeline (p. 18)
  26. 4.5 End-to-end KOL partnership SOP (L-4 to L+1 weeks) (p. 19)
  27. Step 1: Identify KOLs and build a list (L-4 weeks) (p. 19)
  28. Step 2: Request KOL rates (L-4 weeks) (p. 21)
  29. Step 3: Confirm interest and send the content package (L-3 weeks) (p. 22)
  30. Step 4: Review the KOL's content draft (L-2 weeks) (p. 24)
  31. Step 5: Payment (L-1 day to L-Day) (p. 24)
  32. Step 6: Monitor publishing and collect data (L-Day to L+1 week) (p. 24)
  33. 4.6 UGC growth engine SOP (start at L-4 weeks; ongoing) (p. 25)
  34. 4.6.1 UGC growth philosophy: find brand ambassadors (p. 25)
  35. 4.6.2 Recruit and screen ambassadors / UGC partners (L-4 to L-2 weeks) (p. 25)
  36. 4.6.3 Creator tiers and management (p. 26)
  37. 4.6.4 Timeless Scripts (p. 26)
  38. 4.6.5 Build community culture (p. 27)
  39. 4.6.6 UGC publishing plan (p. 27)
  40. 4.6.7 UGC workflow and practical tools (p. 27)
  41. 4.7 Reddit operations SOP (start at L-4 weeks) (p. 28)
  42. Reddit AI Agent workflow (p. 28)
  43. Part 5: Official product launch—Launch Week (p. 32)
  44. 5.1 Launch Week planning principles (p. 33)
  45. 5.2 Detailed daily Launch Week timeline (p. 33)
  46. Day 1 (Monday): Main launch and product reveal (p. 33)
  47. Day 2 (Tuesday): Getting-started tutorials to lower the barrier (p. 35)
  48. Day 3 (Wednesday): Deep dive into core feature 1 (p. 36)
  49. Day 4 (Thursday): Deep dive into core feature 2 (p. 37)
  50. Day 5 (Friday): Community engagement and Launch Week recap (p. 37)
  51. 5.3 After Launch Week: build momentum (Launch+1 week to PH-1 week) (p. 38)
  52. Part 6: Product Hunt launch (p. 38)
  53. 6.1 Choose a Product Hunt launch date (p. 38)
  54. 6.2 Choose a Hunter (p. 39)
  55. 6.3 Product Hunt-specific preparation (PH-1 week) (p. 40)
  56. 6.4 Product Hunt launch-day schedule: a 24-hour plan (p. 41)
  57. 6.5 Upvote strategy and contingency plan (p. 43)
  58. Part 7: Budget allocation recommendations (p. 44)
  59. 7.1 Budget allocation principles (p. 44)
  60. 7.2 Lean $10,000 plan for an early-stage team (p. 45)
  61. 7.3 Standard $50,000 plan for a funded startup (p. 45)
  62. 7.4 Industry benchmark pricing (p. 46)
  63. Part 8: Channel content templates (p. 46)
  64. 8.1 Official Twitter/X launch post template (p. 47)
  65. 8.2 Discord / Telegram community announcement template (p. 48)
  66. 8.3 Overseas community post template (Facebook / Telegram / WhatsApp) (p. 48)
  67. 8.4 Direct-message outreach template (p. 49)
  68. 8.5 LinkedIn influencer partnership outreach template (p. 51)
  69. Part 9: Launch channel checklist (p. 52)
  70. 9.1 Core launch platforms (required) (p. 52)
  71. 9.2 Social platforms (p. 52)
  72. 9.3 Community platforms (p. 53)
  73. 9.4 Overseas messaging communities (p. 54)
  74. 9.5 Media and content platforms (p. 54)
  75. 9.6 Developer communities and events (p. 54)
  76. Part 10: Omnichannel toolkit (p. 55)
  77. 10.1 Research and analytics tools (p. 55)
  78. 10.2 KOL and UGC management tools (p. 56)
  79. 10.3 Social automation and outreach tools (p. 56)
  80. 10.4 Link tracking and analytics tools (p. 57)
  81. 10.5 Content creation tools (p. 57)
  82. 10.6 Email marketing tools (p. 57)
  83. 10.7 Community discovery tools (p. 57)
  84. 10.8 Account resources (p. 58)
  85. 10.9 Other useful tools (p. 58)
  86. Part 11: Long-term growth and ongoing operations (p. 58)
  87. 11.1 Data tracking and retrospectives (p. 58)
  88. 11.2 User development and community operations (p. 59)
  89. 11.3 Long-term growth engine: SEO and content marketing (p. 59)
  90. 11.4 Continuous iteration of the UGC engine (p. 59)
  91. Conclusion (p. 59)
Product Hunt Launch Action Guide Original 42 pages · 41 entries
  1. About launching on Product Hunt (p. 1)
  2. Overall timeline (p. 2)
  3. Part 1: Strategy preparation (PH-4 weeks) (p. 3)
  4. 1.1 Choose a launch date (p. 3)
  5. 1.2 Confirm a Hunter (p. 3)
  6. 1.3 Start KOL partnerships (PH-4 weeks) (p. 6)
  7. Part 2: Create launch assets (PH-3 to PH-2 weeks) (p. 9)
  8. 2.1 Product Hunt page asset SOP (p. 9)
  9. 2.1.1 Tagline (one-line introduction) (p. 9)
  10. 2.1.2 Description (full product overview) (p. 9)
  11. 2.1.3 Video assets (p. 10)
  12. 2.1.4 Screenshots and GIFs (5) (p. 11)
  13. 2.2 Prepare the maker comment (p. 11)
  14. 2.3 Send the KOL content package (PH-2 weeks) (p. 13)
  15. Part 3: Final confirmation (PH-1 week) (p. 16)
  16. 3.1 Final asset checklist (p. 16)
  17. 3.2 Set up the Product Hunt war room (p. 17)
  18. 3.3 Warm up the community (PH-3 to PH-1 days) (p. 18)
  19. 3.4 KOL content draft review checklist (p. 19)
  20. Part 4: Product Hunt launch day—24-hour action plan (p. 19)
  21. 4.1 The day before launch (midday China time) (p. 20)
  22. 4.2 Launch day, starting at 00:01 PST (p. 20)
  23. 4.3 Detailed upvote acquisition strategy (p. 23)
  24. 4.3.1 Organic traffic channels (p. 23)
  25. 4.3.2 Paid traffic channels (p. 26)
  26. 4.4 Live ranking monitoring and contingency plans (p. 27)
  27. 4.5 Launch-day checklist (p. 29)
  28. Part 5: Channel launch copy templates (p. 30)
  29. 5.1 Official Twitter/X launch post (p. 30)
  30. 5.2 Discord / Telegram community announcement (p. 32)
  31. 5.3 Reddit Product Hunt launch post (p. 33)
  32. 5.4 Overseas community post (Facebook / Telegram / WhatsApp) (p. 35)
  33. 5.5 Domestic WeChat group announcement (p. 35)
  34. 5.6 LinkedIn DM request for support (p. 36)
  35. 5.7 KOL thread reference template (p. 36)
  36. Part 6: Post-launch retrospective (PH+1 week) (p. 38)
  37. 6.1 Data review framework (p. 38)
  38. 6.2 Tips for a second conversion (p. 39)
  39. 6.3 User follow-up (p. 39)
  40. 6.4 Capture and redistribute content (p. 39)
  41. Appendix: Product Hunt launch toolkit (p. 40)
KOL Operations Guide Original 52 pages · 160 entries
  1. 1. Core strategy: the influencer flywheel (p. 1)
  2. Key insights (p. 1)
  3. 2. KOL segments and value assessment (p. 1)
  4. Influencer segmentation table (p. 1)
  5. 3. KOL selection criteria (p. 2)
  6. Screening dimensions (p. 2)
  7. Common screening pitfalls (p. 3)
  8. 4. KOL rate benchmarks by platform (p. 3)
  9. Rate ranges (p. 3)
  10. Negotiation strategies (p. 4)
  11. 5. End-to-end KOL partnership SOP (p. 4)
  12. Step 1: Identify KOLs and build a list (L-4 weeks) (p. 4)
  13. Step 2: Request KOL rates (L-4 weeks) (p. 4)
  14. Step 3: Send the content package (L-3 weeks) (p. 5)
  15. Step 4: Review the KOL's content draft (L-2 weeks) (p. 7)
  16. Step 5: Payment (L-1 day to L-Day) (p. 8)
  17. Step 6: Monitor publishing and collect data (L-Day to L+1 week) (p. 8)
  18. 6. Leading KOL resource directory (p. 8)
  19. Leading AI newsletter founders (highest priority) (p. 8)
  20. Industry influencers and KOLs (p. 9)
  21. China–US tech media and analysts (China-US Connector) (p. 9)
  22. Major technology media (p. 10)
  23. 7. Launch scale benchmarks (p. 10)
  24. Launch volume by platform (p. 10)
  25. 8. Case review: Manus vs. Devin (p. 11)
  26. Side-by-side case comparison (p. 11)
  27. Key takeaways (p. 11)
  28. 9. KOL management tools (p. 12)
  29. 10. Full timeline overview (p. 12)
  30. 11. Advanced KOL partnerships: a data evaluation system (p. 13)
  31. Core performance metrics (p. 13)
  32. How to calculate ROI (p. 14)
  33. Reference keywords for KOL screening (p. 14)
  34. 12. Complete KOL partnership workflow (six stages) (p. 14)
  35. Stage 1: Build a KOL contact list (p. 14)
  36. Stage 2: Make initial contact by email (p. 15)
  37. Stage 3: Discuss and confirm partnership potential (p. 15)
  38. Stage 4: Confirm the partnership and sign (p. 15)
  39. Stage 5: Review and approve content (p. 16)
  40. Stage 6: Monitor the launch and review results (p. 16)
  41. 13. KOL email template library (p. 16)
  42. Initial outreach template (p. 16)
  43. Follow-up email template (p. 17)
  44. 14. Complete content package template (p. 17)
  45. 1. Product overview (p. 17)
  46. 2. Brand assets (p. 18)
  47. 3. Key talking points (p. 18)
  48. 4. Video structure guidance (p. 18)
  49. 5. Publishing requirements (p. 19)
  50. 6. Dedicated UTM tracking links (p. 19)
  51. 15. KOL partnership incentive design (p. 20)
  52. Compensation structure (p. 20)
  53. Additional incentives (p. 20)
  54. 16. KOC partnerships: low-cost acquisition (p. 21)
  55. KOC definition and screening (p. 21)
  56. KOC partnership strategy (p. 21)
  57. KOC partnership considerations (p. 21)
  58. 17. Team roles and collaboration (p. 22)
  59. Typical team structure (p. 22)
  60. Daily workflow (p. 22)
  61. 18. Key lessons from practice (p. 22)
  62. Practical cases and strategy notes (source: Feishu Minutes) (p. 23)
  63. 1. Influencer budget and performance benchmarks (p. 23)
  64. Twitter/X promotion budget model (p. 23)
  65. Influencer campaign execution details (p. 23)
  66. Product Hunt launch costs (p. 23)
  67. GitHub Trending strategy (p. 24)
  68. 2. Influencer costs and ROI by channel (p. 24)
  69. YouTube creators (p. 24)
  70. Twitter/X influencer rate tiers (p. 24)
  71. LinkedIn campaigns (p. 24)
  72. Domestic promotion budget benchmarks (p. 24)
  73. 3. Build and manage an influencer database (p. 25)
  74. ROI evaluation formula (p. 25)
  75. Influencer quality screening (p. 25)
  76. Conversion tracking methods (p. 25)
  77. Improve outreach efficiency (p. 25)
  78. Influencer type labels and management (p. 25)
  79. 4. Build lasting influencer partnerships (p. 26)
  80. Tie rewards to conversion (p. 26)
  81. Marketing accounts vs. individual creators (p. 26)
  82. How to review an influencer database (p. 26)
  83. 5. Promote open-source projects through creators (p. 26)
  84. Distribution in overseas communities (p. 26)
  85. Acquire users through GitHub Issues and PRs (p. 27)
  86. Suggested campaign mix: a $16,000 budget example (p. 27)
  87. 19. Platform algorithms in depth (p. 27)
  88. 1. TikTok algorithm (p. 27)
  89. 1.1 Core mechanism: interest graph, not social graph (p. 27)
  90. 1.2 Three stages of For You Page (FYP) distribution (p. 28)
  91. 1.3 2026 ranking signals by influence (p. 28)
  92. 1.4 Major algorithm changes in 2025–2026 (p. 29)
  93. 1.5 Practical applications (p. 29)
  94. 2. YouTube Shorts algorithm (p. 29)
  95. 2.1 Core mechanism: a recommendation system independent of long-form video (p. 29)
  96. 2.2 Shorts recommendation flow (p. 30)
  97. 2.3 Shorts ranking signals by importance (p. 30)
  98. 2.4 2026 update: more home-feed inventory for Shorts (p. 30)
  99. 2.5 Practical applications (p. 31)
  100. 3. Instagram Reels algorithm (p. 31)
  101. 3.1 Core mechanism (p. 31)
  102. 3.2 Reels' three-tier recommendation logic (p. 31)
  103. 3.3 Reels ranking signals: 2026 update (p. 31)
  104. 3.4 Major changes in 2025–2026 (p. 32)
  105. 3.5 Practical applications (p. 32)
  106. 4. X (Twitter) algorithm (p. 33)
  107. 4.1 Core mechanism: full adoption of AI in 2026 (p. 33)
  108. 4.2 Recommendation flow: a three-stage pipeline (p. 33)
  109. 4.3 X ranking signals by influence (p. 33)
  110. 4.4 Practical applications (p. 34)
  111. 5. LinkedIn algorithm (p. 34)
  112. 5.1 Core mechanism: four distribution stages (p. 34)
  113. 5.2 LinkedIn ranking signals: 2026 update (p. 35)
  114. 5.3 2026 change: lower overall traffic, more standout content (p. 36)
  115. 5.4 Practical applications (p. 36)
  116. 6. Reddit algorithm (p. 36)
  117. 6.1 Core mechanism: community first (p. 36)
  118. 6.2 Five ranking systems (p. 36)
  119. 6.3 Hot algorithm: time decay and logarithmic voting (p. 37)
  120. 6.4 Major changes in 2026 (p. 37)
  121. 6.5 Practical applications (p. 37)
  122. 7. Xiaohongshu algorithm (p. 38)
  123. 7.1 Core mechanism: decentralized, dual-engine distribution (p. 38)
  124. 7.2 CES scoring system (p. 38)
  125. 7.3 Major algorithm upgrades in 2025–2026 (p. 38)
  126. 7.4 Traffic tiers (p. 39)
  127. 7.5 Practical applications (p. 39)
  128. 8. Platform algorithm comparison at a glance (p. 40)
  129. 9. Adapt your KOL strategy to platform algorithms (p. 41)
  130. 9.1 TikTok / Instagram Reels (p. 41)
  131. 9.2 YouTube Shorts (p. 41)
  132. 9.3 X (Twitter) threads (p. 41)
  133. 9.4 LinkedIn (p. 42)
  134. 9.5 Reddit (p. 42)
  135. 9.6 Xiaohongshu (p. 42)
  136. 20. X algorithm source-code analysis (May 2026 update) (p. 43)
  137. 1. Core architecture: a three-stage pipeline (p. 43)
  138. Architecture flow diagram (p. 43)
  139. 2. Two candidate sources: Thunder + Phoenix (p. 44)
  140. 2.1 Thunder (on-platform content) (p. 44)
  141. 2.2 Phoenix (off-platform content) (p. 44)
  142. 3. Phoenix Scorer: predict 15 dimensions of engagement (p. 45)
  143. 4. Filtering layer: rules creators should know (p. 46)
  144. Pre-scoring filters (p. 46)
  145. Post-selection filters (p. 47)
  146. 5. Author Diversity Scorer: prevent one account from dominating the feed (p. 47)
  147. 6. Major update on May 15, 2026 (p. 48)
  148. Update 1: end-to-end inference pipeline (p. 48)
  149. Update 2: pretrained Mini Phoenix model (p. 48)
  150. Update 3: Grok Content-Understanding Pipeline (new content-understanding layer) (p. 48)
  151. Update 4: Ads Blending System (p. 48)
  152. Update 5: expanded Query Hydrators (p. 49)
  153. Update 6: expanded Candidate Hydrators (p. 49)
  154. 7. Source-level design principles and creator takeaways (p. 50)
  155. Principle 1: no hand-engineered features (AI-driven) (p. 50)
  156. Principle 2: candidate isolation (p. 50)
  157. Principle 3: multi-action prediction (p. 50)
  158. 8. The strongest amplifier: author replies outperform ordinary likes by 150× (p. 50)
  159. 9. Creator action checklist based on the source logic (p. 51)
  160. 10. References (p. 52)
UGC Matrix Account Operations Guide Original 20 pages · 79 entries
  1. 1. UGC growth philosophy: think like a brand ambassador (p. 1)
  2. Three guiding principles (p. 1)
  3. How to recognize a creator with good taste (p. 1)
  4. 2. Creator recruitment channels (p. 1)
  5. Recruitment priorities (p. 2)
  6. 3. Creator tiers and management (p. 2)
  7. Two creator roles (p. 2)
  8. Content iteration path (p. 3)
  9. 4. Incentive design (p. 3)
  10. Fixed-fee benchmarks (p. 3)
  11. View-based bonus model (recommended) (p. 3)
  12. 5. AI creator account portfolios: specialized tactics (p. 4)
  13. Use cases (p. 4)
  14. Account solutions (p. 4)
  15. AI content production strategy (p. 4)
  16. 6. Launch Week publishing plan (p. 4)
  17. Launch volume benchmarks (p. 4)
  18. Content mix (p. 4)
  19. 7. How platform strategies differ (p. 5)
  20. Compare the three major platforms (p. 5)
  21. Content guidance by platform (p. 5)
  22. 8. Account operations and warm-up (p. 6)
  23. Core principles for warming up an account (p. 6)
  24. Warm-up process (about 2–4 weeks) (p. 6)
  25. 9. Management tools and workflow (p. 6)
  26. 10. Recommended cold-start path (p. 7)
  27. 11. Common mistakes (p. 7)
  28. 12. Case study: Kuse—$10M ARR in 60 days, $0 ad spend, and 70M global impressions (p. 8)
  29. Core model: an IP account and UGC portfolio flywheel (p. 8)
  30. Why Threads? (p. 8)
  31. Content strategy: two steps (p. 8)
  32. Short-form video structure: Instagram expansion (p. 9)
  33. UGC Program: organize the work from 1 to 100 (p. 9)
  34. AI UGC: move beyond human production limits (p. 10)
  35. Market priorities: where to start (p. 10)
  36. Key metrics at a glance (p. 10)
  37. 13. Content production methodology (p. 11)
  38. Analyze competitors: the most effective starting point (p. 11)
  39. Develop content sense (p. 11)
  40. Produce content at scale with AI tools (p. 12)
  41. Video production cadence (p. 12)
  42. Demo video production essentials (p. 13)
  43. 14. Platform cold-start paths (p. 13)
  44. Launch strategy by platform (p. 13)
  45. Reddit cold start (p. 13)
  46. YouTube Shorts promotion strategy (p. 13)
  47. Xiaohongshu and domestic platforms (p. 14)
  48. 15. Build a community system: the brand-friends program (p. 14)
  49. Core concept (p. 14)
  50. Incentive design (p. 14)
  51. Execution essentials (p. 14)
  52. Choose a group-chat tool (p. 15)
  53. 16. Content marketing metrics and cadence (p. 15)
  54. Core metrics (p. 15)
  55. Publishing cadence benchmarks (p. 15)
  56. 17. Key quotes from internal meetings (lessons learned) (p. 16)
  57. Practical cases and strategy notes (source: Feishu Minutes) (p. 16)
  58. 1. Low-cost UGC Program operating model (p. 16)
  59. Core metrics (p. 16)
  60. Incentive design validated in practice (p. 17)
  61. UGC Creator management SOP (p. 17)
  62. Key lesson: avoid common causes of poor conversion (p. 17)
  63. 2. Hands-on AI UGC account portfolio operations (p. 17)
  64. Three-part AI UGC video structure (p. 17)
  65. AI account portfolio operating metrics (p. 18)
  66. Account and device management (p. 18)
  67. Device scaling model tested on another project (p. 18)
  68. 3. UGC recruitment and screening (p. 18)
  69. Recruitment channels (p. 18)
  70. Screening criteria (p. 18)
  71. UGC content management workflow (p. 19)
  72. 4. Recommended market-entry sequence (p. 19)
  73. 5. Short-form video methodology for account portfolios (p. 19)
  74. A repeatable short-video structure: one video drove 2,000+ sign-ups (p. 19)
  75. Validate replication across markets (p. 19)
  76. Trends in AI-generated content (p. 20)
  77. 6. UGC growth for mobile apps (p. 20)
  78. Key differences from web growth (p. 20)
  79. ASO tools and techniques (p. 20)
In-House Team UGC Execution Guide Original 24 pages · 42 entries
  1. 1. Run a seven-day pilot first (p. 1)
  2. 2. Practical details from team discussions (p. 3)
  3. 2.1 How the Wispr team recruits, briefs, edits, and replicates effective content (p. 3)
  4. 2.1.1 Step 1: Find people who can explain the product; use a paid test shoot to assess long-term fit (p. 3)
  5. 2.1.2 Step 2: Give creators room to work—split assignments into self-chosen scenarios and reference templates (p. 4)
  6. 2.1.3 Step 3: Replace word-for-word scripts with a shoot-ready structure card (p. 5)
  7. 2.1.4 Step 4: Give timestamped, visual feedback when a cut misses the mark (p. 6)
  8. 2.1.5 Step 5: When a video performs, identify why and plan distinct versions (p. 6)
  9. 2.1.6 Step 6: Assign work to creator strengths and develop mentors for new creators (p. 7)
  10. 2.1.7 Corresponding sources (p. 8)
  11. 2.2 Higgsfield: connect assignments, submissions, and payment in one loop (p. 8)
  12. 3. Ready-to-copy operating templates (p. 9)
  13. 3.1 Recruitment DMs, screening form, and onboarding kit (p. 9)
  14. 3.2 A completed video brief using an AI transcription tool as the example (p. 9)
  15. 3.3 Portfolio tracker: at least three linked tables (p. 10)
  16. 3.4 Budget and retrospective: set the rules before reviewing results (p. 11)
  17. 4. New: turn Reddit feedback into execution checks (p. 11)
  18. 5. UGC portfolio tool list: add capabilities as needed (p. 12)
  19. 5.1 Source scope and reading boundaries for this edition (p. 14)
  20. 6. Turn internal experience into operating rules (p. 14)
  21. 6.1 Make these six changes first (p. 14)
  22. 6.2 Trials and incentives: do not combine meeting proposals into a single policy (p. 15)
  23. 6.3 Deliverables to add directly to the existing seven-day plan (p. 16)
  24. 6.4 Add tools for organizing assets and attribution first (p. 16)
  25. 7. Define what you are building first (p. 16)
  26. 8. Six key conclusions from the original video (p. 17)
  27. 9. Before launch: assign roles and define pilot boundaries (p. 18)
  28. 10. Execution: from creative gaps to ongoing partnerships (p. 19)
  29. 10.1 Audit content gaps, then recruit (p. 19)
  30. 10.2 Clarify partnership terms and compensation (p. 19)
  31. 10.3 Help creators understand the product and its users (p. 19)
  32. 10.4 Review assets and maintain test records (p. 20)
  33. 10.5 Turn weekly data reviews into creative direction (p. 20)
  34. 10.6 Decide whether to scale after settling payments (p. 20)
  35. 11. Gingiris recommendation: a 30-day launch plan (p. 20)
  36. 12. Ready-to-copy execution templates (p. 21)
  37. 12.1 Creator screening card (p. 21)
  38. 12.2 Single-video creative brief (p. 22)
  39. 12.3 Asset and test tracker (p. 22)
  40. 12.4 Weekly review and payment card (p. 22)
  41. 13. Issue handling and review (p. 23)
  42. 14. Sources and evidence notes (p. 23)
Reddit Operations SOP Original 28 pages · 64 entries
  1. 1. Why Reddit is essential (p. 1)
  2. 1.1 Key Reddit platform data (p. 1)
  3. 1.2 Why your product should be on Reddit (p. 2)
  4. 1.3 Reddit's advantages over other platforms (p. 2)
  5. 2. Account structure and ban prevention (p. 3)
  6. 2.1 Three ban types and how to respond (p. 3)
  7. 2.2 Core rules for avoiding bans (p. 3)
  8. 2.3 Multi-account portfolio strategy (p. 4)
  9. 2.4 Standard account warm-up process (p. 4)
  10. 2.5 Identify and appeal a ban (p. 5)
  11. 3. Find and classify target Subreddits (p. 6)
  12. 3.1 Discovery methods (p. 6)
  13. 3.2 Framework for classifying target Subreddits (p. 6)
  14. Core target communities (highest priority) (p. 6)
  15. Related target communities (p. 7)
  16. Broad-interest communities for user acquisition (p. 7)
  17. 3.3 Community screening criteria (p. 7)
  18. 4. Content strategy system (p. 8)
  19. 4.1 Content mix principles (p. 8)
  20. 4.2 Content types and post templates (p. 9)
  21. Type A: value-only content with no brand mention (p. 9)
  22. Type B: subtle product mention in a natural context (p. 9)
  23. Type C: genuine first-person product recommendation (p. 10)
  24. 4.3 Comment strategy: more important than posting (p. 11)
  25. 4.4 General-purpose content idea bank (p. 11)
  26. 5. Advanced content strategy: make Reddit a traffic flywheel (p. 12)
  27. 5.1 Coordinate Reddit with Product Hunt (p. 12)
  28. 5.2 Convert public traffic into owned audiences (p. 13)
  29. 5.3 Founder IP and AMA strategy (p. 13)
  30. 6. Working with service providers (p. 14)
  31. 6.1 Service provider pricing benchmarks (p. 14)
  32. 6.2 When to hire a service provider (p. 14)
  33. 6.3 Key partnership terms (p. 15)
  34. 7. Daily operations SOP (p. 15)
  35. 7.1 Daily checklist (p. 15)
  36. 7.2 Weekly operating cadence (p. 15)
  37. 7.3 Content calendar template (p. 16)
  38. 8. Data tracking and retrospectives (p. 16)
  39. 8.1 Core tracking metrics (p. 16)
  40. 8.2 Retrospective dimensions (p. 17)
  41. 8.3 A/B testing framework (p. 17)
  42. 9. General considerations for every brand (p. 18)
  43. 9.1 Content compliance guardrails (p. 18)
  44. 9.2 Seasonal content cadence (general version) (p. 18)
  45. 9.3 Differentiate content with AI and vertical expertise (p. 18)
  46. 10. Pre-launch execution checklist (p. 19)
  47. Appendix 1: Complete Subreddit list (p. 20)
  48. Core targets (p. 20)
  49. Related targets (p. 20)
  50. Appendix 2: Post template library (p. 21)
  51. Template 1: Industry trend analysis post (p. 21)
  52. Template 2: Product launch post (p. 21)
  53. Template 3: User Q&A comment (p. 22)
  54. Appendix 3: Brand case studies for reference (p. 22)
  55. Appendix 4: Special posting rules for r/MachineLearning (p. 23)
  56. Appendix 5: Reddit operations tools (p. 23)
  57. Appendix 6: Classic Reddit operations case studies (p. 24)
  58. Case 1: Adobe Reddit marketing—creative discussion drives 3× conversions (p. 24)
  59. Case 2: New Balance running culture livestream—authentic content builds brand acceptance (p. 25)
  60. Case 3: Starter Story's cold-start success—from zero to tens of thousands on Reddit (p. 25)
  61. Case 4: Base44's $80M acquisition AMA—the power of founder IP (p. 26)
  62. Case 5: AFFiNE coordinates Reddit and Product Hunt for 30K–40K qualified impressions (p. 26)
  63. Case 6: SenseNova-U1—marketing an AI product to Reddit communities (p. 27)
  64. Case 7: Self-promotion in the Reddit r/MachineLearning community (p. 28)
Product Content Distribution to Communities SOP Original 19 pages · 35 entries
  1. 1. Pre-launch checklist: pause if even one item is missing (p. 1)
  2. 2. Community screening: five criteria, all required (p. 1)
  3. 3. Find communities that match your target users (p. 2)
  4. 3.1 Five ways to find groups (p. 2)
  5. 3.2 Build and maintain a community database (p. 4)
  6. 3.3 Quick group-screening template (p. 4)
  7. 4. Three distribution paths (p. 4)
  8. Path A: paid promotion for teams with budget seeking a fast channel test (p. 4)
  9. Path B: free distribution to groups you already belong to (p. 5)
  10. Path C: DM high-quality large-group owners (p. 6)
  11. 5. Platform-specific operating guidance (p. 6)
  12. Facebook Groups (p. 6)
  13. LinkedIn Groups (p. 7)
  14. Reddit (p. 8)
  15. Telegram (p. 9)
  16. Discord (p. 9)
  17. 6. Five universal content-writing guardrails (p. 9)
  18. 7. KOL campaigns: extend reach beyond communities (p. 10)
  19. 8. Distribute your own videos in communities (p. 10)
  20. 8.1 Which videos work in communities? (p. 11)
  21. 8.2 Low-cost video production tools (p. 11)
  22. 8.3 Repurpose one video across platforms (p. 12)
  23. 8.4 How to post in groups (p. 12)
  24. 8.5 How videos spread within communities (p. 13)
  25. 9. UGC creator portfolio: a standalone growth path (p. 14)
  26. 9.1 UGC growth flywheel (p. 14)
  27. 9.2 Recruit and tier creators (p. 14)
  28. 9.3 Incentive design (p. 15)
  29. 9.4 Match UGC formats to platforms (p. 15)
  30. 9.5 Use AI UGC to supplement limited human content (p. 16)
  31. 9.6 Pre-launch safety gate (p. 16)
  32. 10. Data-hook strategy to drive community referrals (p. 17)
  33. 11. Conditions for scaling distribution (p. 17)
  34. 12. Community health benchmarks for owned groups (p. 17)
  35. 13. This week's action checklist: fill in for your situation (p. 18)
Community, Ambassador, and Community Operations Guide Original 25 pages · 55 entries
  1. Community / ambassador operations SOP: general guide (p. 1)
  2. 1. Core objectives and value proposition (p. 1)
  3. 1.1 The community's core mission (p. 1)
  4. 1.2 What is an ambassador: unpaid labor or value co-creation? (p. 1)
  5. 1.3 Align value for the three core participant groups (p. 2)
  6. 2. Prerequisites for launching an ambassador program (p. 3)
  7. 2.1 Checklist for launching an ambassador program (p. 3)
  8. 2.2 Assess your product stage (p. 4)
  9. 3. Six-step community setup SOP (p. 4)
  10. Step 1: Choose the community's purpose and platform (p. 4)
  11. Step 2: Set group announcements and community rules (p. 5)
  12. Step 3: Define community moderator standards (p. 5)
  13. Step 4: Monitor social sentiment (important) (p. 6)
  14. Step 5: Build a community knowledge base (Wiki) (p. 6)
  15. Step 6: Set baseline community operating metrics (p. 7)
  16. 4. Ambassador recruitment and management system (p. 7)
  17. 4.1 Ambassador program value proposition (p. 7)
  18. 4.2 Ambassador admission criteria: Notion requires both A and B (p. 8)
  19. 4.3 Design the ambassador application form (p. 8)
  20. 4.4 Ambassador tiers and advancement (p. 9)
  21. 4.5 Annual ambassador rewards (p. 10)
  22. 4.6 Detect and prevent ambassador attrition (p. 10)
  23. 5. Empower and support ambassadors (p. 11)
  24. 5.1 Onboard new ambassadors (p. 11)
  25. 5.2 Ambassador resource support (p. 12)
  26. 5.3 Ambassador training plan (p. 12)
  27. 5.4 The logic behind ambassador incentives: insights from Notion (p. 13)
  28. Five incentive pillars (p. 13)
  29. Notion's peer-learning mechanism for ambassadors (p. 14)
  30. Connect incentives to monetization (p. 14)
  31. 6. Community event operations SOP (p. 14)
  32. 6.1 Event categories (p. 14)
  33. 6.2 End-to-end event SOP (p. 15)
  34. Preparation: one month before the event (p. 15)
  35. During the event (p. 15)
  36. After the event: within one week (p. 16)
  37. 7. Incentivize community content creation (p. 16)
  38. 7.1 Content and incentives matrix (p. 16)
  39. 7.2 Official content amplification: a key Notion tactic (p. 17)
  40. 7.3 Monthly challenges (p. 17)
  41. 8. Community health metrics (p. 17)
  42. 8.1 Core metrics dashboard (p. 17)
  43. 8.2 Key health metrics for ambassador programs (p. 18)
  44. 9. Ambassador community governance and risk control (p. 18)
  45. 9.1 Ambassador code of conduct (p. 19)
  46. 9.2 Handle cultural conflicts (p. 19)
  47. 10. Annual operating calendar (p. 20)
  48. 11. Tools and resource directory (p. 20)
  49. Essential tools (p. 20)
  50. Reference case studies (p. 21)
  51. User research and ambassador interview templates (p. 21)
  52. Appendix 1: Ambassador recruitment copy template (p. 22)
  53. Appendix 2: Key lessons from Notion's ambassador program (Linmi interview) (p. 24)
  54. Ten key insights (p. 24)
  55. Appendix 3: Brand-specific checklist (complete before use) (p. 24)
Data Dashboard Setup Manual Original 27 pages · 78 entries
  1. Gingiris data dashboard setup manual (p. 1)
  2. §0 Foreword: why this manual exists (p. 1)
  3. §0.1 One-line positioning (p. 1)
  4. §0.2 Three dashboard types—keep them distinct (p. 1)
  5. §0.3 Four common dashboard pitfalls (read first) (p. 1)
  6. §1 Four steps to build a dashboard (p. 2)
  7. Step 1: Define the business question (week 1) (p. 2)
  8. Step 2: Define the metrics framework (weeks 1–2) (p. 2)
  9. Step 3: Choose tools and pull data (weeks 2–3) (p. 3)
  10. Step 4: Design the dashboard and reporting workflow (weeks 3–4) (p. 3)
  11. Data trust prerequisite: require sign-in (p. 4)
  12. §2 Three metric categories: product funnel, channels, and company (p. 4)
  13. §2.1 Product data funnel (p. 4)
  14. Five funnel stages: metric dictionary (p. 4)
  15. Activation definitions across product types (p. 5)
  16. Industry benchmarks and actual results (p. 6)
  17. Growth equation and metric priorities (p. 7)
  18. §2.2 Channel attribution metrics (p. 8)
  19. §2.3 Company-level metrics (p. 9)
  20. §3 Five channel attribution methods, from simple to advanced (p. 9)
  21. §3.1 UTM parameters: the basic requirement for every scenario (p. 9)
  22. §3.2 Dedicated discount codes: when UTM is not enough (p. 10)
  23. §3.3 Referral codes for China and WeChat ecosystems (p. 10)
  24. §3.4 Segment traffic with landing and signup pages (p. 11)
  25. §3.5 User research and interviews: qualitative context for quantitative data (p. 11)
  26. §4 Choose tools by use case, not by vendor (p. 11)
  27. §4.1 Traffic and impressions (p. 11)
  28. §4.2 User behavior and product analytics (p. 12)
  29. §4.3 Short links and UTM management (p. 12)
  30. §4.4 UGC and influencer dashboard (from the ASO guide) (p. 13)
  31. §4.5 Unified dashboard: bring the data together (p. 13)
  32. §5 Practical templates for different stages (p. 13)
  33. §5.1 From 0 to 1: start with three core numbers (p. 13)
  34. §5.2 From 1 to 10: add five channel metrics (p. 14)
  35. §5.3 From 10 to 100: adopt a BI tool (p. 14)
  36. §5.4 UGC stage (reference: ASO guide) (p. 14)
  37. §5.5 Growth stage (reference: weekly learnings from an AI assistant) (p. 15)
  38. §6 Common pitfalls drawn from real projects (p. 15)
  39. Pitfall 1: The data team builds a dashboard that operations cannot use (p. 15)
  40. Pitfall 2: PostHog events cannot track TikTok / Douyin (p. 15)
  41. Pitfall 3: Mixed traffic sources cannot be distinguished (p. 16)
  42. Pitfall 4: NPS sample too small to be reliable (p. 16)
  43. Pitfall 5: Data lags by t-1 or t-2 (p. 16)
  44. Pitfall 6: Different tools use inconsistent metric definitions (p. 16)
  45. Pitfall 7: Operations and product interpret metrics differently (p. 17)
  46. Pitfall 8: Hard-code the PostHog key in event tracking (p. 17)
  47. Pitfall 9: Track data inside a user's private workspace (p. 17)
  48. Pitfall 10: A UI redesign breaks the event-tracking flow (p. 17)
  49. Pitfall 11: Missing PostHog $session_id causes 0% conversion (p. 17)
  50. Weekly event-tracking health checklist (p. 18)
  51. §7 Automation and AI enhancements (p. 18)
  52. §7.1 Generate a weekly report with AI (p. 18)
  53. §7.2 Automatically alert on data anomalies (p. 18)
  54. §7.3 Use AI to choose keywords and channels (p. 19)
  55. §7.4 Use AI to draft attribution findings (p. 19)
  56. §8 Dashboard design standards (p. 19)
  57. §8.1 Design principle: keep it simple (p. 19)
  58. §8.2 Five core dashboard modules (p. 19)
  59. Detailed in-product funnel dashboard (p. 20)
  60. Funnel diagram (p. 21)
  61. §8.3 Recommended weekly cadence (p. 21)
  62. §8.4 Close the loop with action (critical) (p. 22)
  63. §9 Case studies: how real dashboards were built (p. 22)
  64. Case 1: Data Funnel Report for a knowledge-management tool (2023) (p. 22)
  65. Case 2 (p. 23)
  66. Case 3: An AI assistant tool (p. 23)
  67. Case 4: Version 1.0 dashboard for an open-source AI assistant (Aug. 6 meeting) (p. 24)
  68. §10 Quick reference: get started in five minutes (p. 24)
  69. §10.1 Five things to do now (p. 24)
  70. §10.2 Five things to do this month (p. 25)
  71. §10.3 In-product funnel implementation checklist (p. 25)
  72. P0 essentials: growth is impossible without these (p. 25)
  73. P1 improvements: complete within two weeks (p. 25)
  74. P2 advanced: complete within one month (p. 25)
  75. §10.4 A 30-minute diagnostic for the team weekly meeting (p. 25)
  76. §10.5 Nine golden rules from practice (p. 26)
  77. §10.6 Key links and practical tools (p. 26)
  78. §11 In closing: four rules to live by (p. 27)
B2B Business Starter 5 documents
AI B2B Global Product Lifecycle Growth Guide Original 33 pages · 45 entries
  1. Contents (p. 1)
  2. Part 1: The foundations—launch, user research, and community (p. 3)
  3. Chapter 1: Introduction—the new model for global AI B2B (p. 3)
  4. Chapter 2: Find your north star—deep user research and market validation (p. 4)
  5. 2.1 Case study: How HeyGen found PMF through 1,800 interviews (p. 4)
  6. 2.2 A practical user research framework: reusable interview guide (p. 4)
  7. Appendix 2.A: User interview outline template (p. 5)
  8. 2.3 Manage early users: build a golden-customer database (p. 8)
  9. Appendix 2.B: Early-access customer database template (p. 8)
  10. Chapter 3: Ignite growth—product launch and community activation (p. 9)
  11. 3.1 Product launch strategy: from private beta to public launch (p. 9)
  12. 3.2 Community-led growth (CLG): a practical guide from 0 to 1 (p. 10)
  13. Appendix 3.A: Community ambassador application and information template (p. 11)
  14. Part 1: Ambassador application form (p. 11)
  15. Part 2: Ambassador management backend (p. 12)
  16. Part 2: Build the growth engine—affiliate marketing, channel partners, and direct sales (p. 13)
  17. Chapter 4: A hybrid growth model—the PLG and SLG double helix (p. 13)
  18. Chapter 5: Affiliate marketing—use leverage to reach global markets (p. 14)
  19. 5.1 Deep dive: three common commission models (p. 14)
  20. 5.2 Six steps to build an affiliate program (p. 15)
  21. Chapter 6: Channel partner ecosystem—a multiplier for scaling from 1 to N (p. 15)
  22. 6.1 Four core channel partner roles (p. 16)
  23. 6.2 Case studies: partner ecosystems at Deel, Vercel, and AWS (p. 16)
  24. 6.3 Build and operate a partner program (p. 17)
  25. Chapter 7: Sales as the growth spearhead—build an efficient direct-sales team (p. 17)
  26. 7.1 Sales pod model: SDR + AE + SE + CSM (p. 17)
  27. 7.2 Multi-threaded enterprise sales (p. 18)
  28. Chapter 8: Communicate value—create high-converting B2B sales and marketing materials (p. 18)
  29. 8.1 Case studies: value propositions from Supabase and Vercel (p. 18)
  30. 8.2 B2B sales deck structure (p. 19)
  31. Chapter 9: Customer success stories—let data and narrative work together (p. 20)
  32. 9.1 Case study: the Vercel × Frame.io hero's journey (p. 20)
  33. 9.2 A repeatable customer case-study production process (p. 21)
  34. Part 3: Standardization and continuous improvement (p. 22)
  35. Chapter 10: Mitigate risk and protect partnerships with professional contract templates (p. 22)
  36. Appendix 10.A: Service Order Request (SOR) template (p. 23)
  37. Appendix 10.B: Statement of Work (SOW) template (p. 25)
  38. Appendix 10.C: Master Service Agreement (MSA) key clauses (p. 27)
  39. Appendix 10.D: Project Change Request (PCR) template (p. 28)
  40. Appendix 10.E: Development project quote template (p. 29)
  41. Chapter 11: Close the growth loop with data—measure, analyze, and optimize (p. 31)
  42. 11.1 Growth metrics: north-star metric and AARRR funnel (p. 31)
  43. 11.2 Tool stack and best practices (p. 32)
  44. Chapter 12: Conclusion—build a self-renewing global growth flywheel (p. 32)
  45. References (p. 33)
B2B Deal Closing and Delivery SOP Original 13 pages · 44 entries
  1. A technical team's playbook from requirements confirmation to acceptance and payment (p. 1)
  2. Complete this project brief before starting (p. 1)
  3. Chapter 1: Six steps for B2B client engagement (p. 2)
  4. Evidence to capture at every step (p. 2)
  5. Chapter 2: Project kickoff and pricing (p. 3)
  6. Four components of a complete quote (p. 3)
  7. Pricing principles (p. 3)
  8. Quote template (p. 3)
  9. Chapter 3: Contracts and SOW (p. 4)
  10. Keep the SOR and SOW separate (p. 4)
  11. Required elements in an SOW (p. 4)
  12. SOW template by section (p. 4)
  13. Chapter 4: Payment, acceptance, and collections (p. 5)
  14. Design the payment structure (p. 5)
  15. Protect the payment schedule (p. 5)
  16. Final-payment follow-up log (p. 5)
  17. Chapter 5: Change requests and CCB (p. 5)
  18. Change request template (p. 6)
  19. Chapter 6: Boundaries between private deployment, integration, and SaaS (p. 6)
  20. First understand why the client wants private deployment (p. 6)
  21. Private deployment readiness checklist (p. 7)
  22. Chapter 7: Channels and partners (p. 7)
  23. Three channel due-diligence questions (p. 7)
  24. Channel profile card (p. 7)
  25. Chapter 8: Revenue and pipeline analysis (p. 8)
  26. Pipeline dashboard (p. 9)
  27. Chapter 9: B2B content and sales narrative (p. 9)
  28. Recommended order for a customer deck (p. 9)
  29. Information to gather before closing a deal (p. 10)
  30. Appendix A: Twelve questions before signing (p. 10)
  31. Appendix B: Contract discussion checklist for legal (p. 11)
  32. Appendix C: Conversation scripts (p. 11)
  33. Clarify requirements (p. 11)
  34. Out-of-scope requests (p. 11)
  35. Concessions in stages (p. 11)
  36. Explain the quote (p. 12)
  37. Final-payment reminder (p. 12)
  38. Escalate to the decision-maker (p. 12)
  39. Appendix D: 30-day client execution plan (p. 12)
  40. Week 1: opportunity and organization (p. 12)
  41. Week 2: productized pricing (p. 12)
  42. Week 3: contract and delivery control (p. 12)
  43. Week 4: pipeline and retrospective (p. 13)
  44. Client sign-off page (p. 13)
Build an Online Brand for Developer Tools Original 21 pages · 53 entries
  1. How B2B developer tools can earn prospect trust through online content (p. 1)
  2. 1. Framework: online brand-building makes sales easier; it is not acquisition itself (p. 1)
  3. 1.1 The user's real journey (p. 1)
  4. 1.2 Priorities at each stage (p. 2)
  5. 1.3 Three layers of online branding for B2B products (p. 2)
  6. 2. Website: build a credible first screen (p. 2)
  7. 2.1 The website's single objective (p. 2)
  8. 2.2 First-screen and second-screen structure (p. 3)
  9. 2.3 Principles for product positioning and narrative (p. 3)
  10. 2.4 Customer stories: a core trust asset (p. 3)
  11. 2.4b Website comparison pages and ROI calculator (p. 4)
  12. 2.5 Documentation quality builds trust invisibly (p. 5)
  13. 3. Technical content: a compounding trust asset (p. 5)
  14. 3.1 The nature of content (p. 5)
  15. 3.2 Technical blog: a core trust asset (p. 6)
  16. 3.3 YouTube: a long-term trust asset, not an acquisition tool (p. 7)
  17. 3.4 Podcasts: an underrated B2B trust channel (p. 8)
  18. 3.5 Release updates: show that work is progressing (p. 8)
  19. 4. Community: build credibility over time (p. 8)
  20. 4.1 Community is about trust, not growth (p. 8)
  21. 4.2 GitHub: the home of developer trust (p. 9)
  22. 4.3 Discord community operations (p. 10)
  23. 4.4 Vertical communities (p. 10)
  24. 5. Founder IP: start sales conversations earlier (p. 11)
  25. 5.1 The role of founder IP (p. 11)
  26. 5.2 LinkedIn: a core channel for B2B brands (p. 11)
  27. 5.3 Twitter/X: stay visible in developer communities (p. 12)
  28. 5.4 Core principles for building content (p. 13)
  29. 6. Media proof: third-party validation builds trust best (p. 13)
  30. 6.1 Why media coverage is 10× more effective than self-promotion (p. 13)
  31. 6.2 PR strategy (p. 13)
  32. 6.3 Citations are a core asset in the GEO era (p. 14)
  33. 6.4 G2, Capterra, and developer review platforms (p. 15)
  34. 7. SEO foundations: help people find you (p. 15)
  35. 7.1 SEO is a low-cost, long-term trust-building channel (p. 15)
  36. 7.2 Keyword strategy (p. 15)
  37. 7.3 Build backlinks (p. 16)
  38. 8. User interviews: the best source of content (p. 16)
  39. 8.1 Why interviews are an underrated brand-building tool (p. 16)
  40. 8.2 Turn interview insights into brand assets (p. 17)
  41. 9. Metrics: measure trust-building (p. 17)
  42. 9.1 Brand trust metrics (p. 17)
  43. 9.2 Content influence metrics (p. 18)
  44. 9.3 Sales enablement metrics (p. 18)
  45. 10. Priorities by stage (p. 18)
  46. Stage 1: 0–1, product exists but no customers (p. 19)
  47. Stage 2: 1–10, validating PMF (p. 19)
  48. Stage 3: 10–100, scaling (p. 19)
  49. Appendix: launch-period acquisition references, outside the scope of brand trust (p. 20)
  50. A.1 Launch budget benchmarks (p. 20)
  51. A.2 GitHub Star growth cadence (p. 20)
  52. A.3 Hacker News front-page criteria (p. 21)
  53. A.4 Product Hunt key parameters (p. 21)
Product, Engineering, and Operations Collaboration SOP Original 21 pages · 46 entries
  1. Product, engineering, and operations collaboration SOP (p. 1)
  2. 1. Diagnose the core issue: why do product, engineering, and operations struggle to collaborate? (p. 1)
  3. 1.1 Three conflicts common to growing products (p. 1)
  4. 1.2 Solutions (p. 1)
  5. 1.2 Solutions (p. 2)
  6. 2. Shared collaboration hub: design the board system (p. 2)
  7. 2.1 Two-tier board structure (p. 2)
  8. 2.2 Issue intake template (general format) (p. 3)
  9. 2.3 Route bugs and feature requests separately (p. 4)
  10. 3. Design the iteration cadence (p. 5)
  11. 3.1 Choose an iteration cycle (p. 5)
  12. 3.2 Standard 10-day iteration workflow (p. 5)
  13. 3.3 Release guardrails (p. 6)
  14. 4. Alignment meetings across the three functions (p. 6)
  15. 4.1 Daily stand-up (15 minutes) (p. 6)
  16. 4.2 Iteration planning (30–60 minutes at the start) (p. 6)
  17. 4.3 Iteration review (30 minutes at the end) (p. 7)
  18. 4.4 Weekly meetings vs. iteration meetings (p. 7)
  19. 5. Operations' role in collaboration (p. 8)
  20. 5.1 Operations translates between users and engineering (p. 8)
  21. 5.2 Operations has veto power over a release (p. 8)
  22. 6. Let user feedback drive product iteration (p. 9)
  23. 6.1 Close the loop from feedback to product improvement (p. 9)
  24. 6.2 Interview beta users (reference process) (p. 10)
  25. 6.3 Combine quantitative and qualitative analysis (p. 11)
  26. 7. Core metrics (p. 11)
  27. 7.1 Every iteration needs a target metric (p. 11)
  28. 7.2 Core metrics across the commercialization funnel (p. 12)
  29. 7.3 Iteration health self-check (p. 12)
  30. 8. Manage technical debt and product refactoring (p. 13)
  31. 8.1 When is refactoring necessary? (p. 13)
  32. 8.2 Balance refactoring and feature work (p. 13)
  33. 8.3 Handle refactoring requests (p. 14)
  34. 9. Priorities by stage (p. 14)
  35. 9.1 Product cold-start stage (pre-PMF) (p. 14)
  36. 9.2 Early growth: PMF achieved, scaling begins (p. 14)
  37. 9.3 Rapid growth: growth is stable (p. 14)
  38. 10. Recommended tools (p. 15)
  39. Appendix 1: Bug report template (ready to copy) (p. 15)
  40. Appendix 2: Iteration planning meeting template (p. 17)
  41. Appendix 3: Responsibilities across product, engineering, and operations (p. 18)
  42. Appendix 3: Classic product-engineering-operations collaboration cases (p. 19)
  43. Case 1: Slack—from internal tool at a gaming company to $27.7B (p. 19)
  44. Case 2: Superhuman—six months of refinement, PMF first (p. 19)
  45. Case 3: Figma—a collaborative product and engineering culture (p. 20)
  46. Case 4: Notion—operations shape product direction (p. 21)
Team Motivation Operations Manual Original 9 pages · 30 entries
  1. Foreword (p. 1)
  2. Layer 1: Daily stand-up—information sharing and self-management (p. 1)
  3. Why hold a stand-up? (p. 1)
  4. Design philosophy (p. 2)
  5. Standard format (p. 2)
  6. A good stand-up example (p. 2)
  7. Common scenarios (p. 3)
  8. Guidelines for the COO (p. 3)
  9. Layer 2: Weekly meeting—alignment and shared understanding (p. 3)
  10. Why hold a weekly meeting? (p. 3)
  11. Design philosophy (p. 4)
  12. Monday meeting agenda: 25 minutes, strictly timed (p. 4)
  13. Company updates (p. 4)
  14. Personal updates (p. 4)
  15. Scrum master (p. 4)
  16. Guidelines for the COO (p. 5)
  17. Layer 3: One-on-one—personal wellbeing and deeper trust (p. 5)
  18. Why 1:1s are difficult—and essential (p. 5)
  19. Quantitative pulse check (5 min) (p. 5)
  20. Deep dive (15–20 min) (p. 6)
  21. About the work itself (p. 6)
  22. About decisions and ownership (p. 6)
  23. About candor (p. 7)
  24. About growth (p. 7)
  25. About people and the organization (p. 7)
  26. Two-way feedback (5–10 min) (p. 7)
  27. Action items before the next 1:1, if any (p. 7)
  28. Guidelines for the COO (p. 7)
  29. Frequently asked questions (p. 8)
  30. The one-sentence summary (p. 8)
OPC Starter Guide 1 document
OPC Starter and Service Productization Action Guide Original 16 pages · 31 entries
  1. 1. Close the smallest loop and reward incremental progress (p. 2)
  2. Methodology: invest what you can afford to get real feedback (p. 2)
  3. 1.1 Complete one small order first (p. 2)
  4. 1.2 Give yourself a reason to continue after each step (p. 2)
  5. 1.3 Confirm just four things before you begin (p. 3)
  6. 2. Validate what you can sell (p. 3)
  7. 2.1 Inventory your skills and resources (p. 3)
  8. 2.2 Turn a capability description into a service description (p. 4)
  9. Methodology note: use Jobs to Be Done to understand why people buy (p. 5)
  10. 3. Scope a service you can deliver (p. 5)
  11. 3.1 Service description template (p. 5)
  12. 3.2 Example: website diagnostic service package (p. 6)
  13. 4. Validate real demand (p. 7)
  14. 4.1 Outreach paths (p. 7)
  15. 4.2 First conversation SOP (p. 8)
  16. 4.3 Client-fit assessment table (p. 9)
  17. 5. Validate willingness to pay (p. 9)
  18. 5.1 Choose a trial-project format (p. 9)
  19. 5.2 Basis for pricing (p. 10)
  20. 5.3 Delivery standards for paid diagnostics (p. 11)
  21. 6. Validate your delivery capability (p. 11)
  22. 6.1 Standard delivery workflow (p. 11)
  23. 6.2 Capacity and quality (p. 12)
  24. 7. Review the work and start another cycle (p. 13)
  25. 7.1 Trial-project retrospective template (p. 13)
  26. 7.2 Rules for adjusting the business (p. 14)
  27. 8. Action overview and supporting resources (p. 14)
  28. 8.1 Plan one cycle (p. 14)
  29. 8.2 Maintain just one progress card (p. 15)
  30. 8.3 How to keep going when you are stuck (p. 16)
  31. 8.4 Supporting materials and methodology sources (p. 16)

Add WeChat for inquiries

Add WeChat to learn about the knowledge base, global growth community, or official account.

staywildgrow