| name | b2b-pm-workbench-international |
| version | 1.2.0-intl |
| language | en-US |
| author | yinjianheng（殷健恒） |
| description | 【B2B PM Super Workbench】 —— A full-stack intelligent workbench for B2B (enterprise) product managers. Integrates 50+ methodology frameworks, 30+ standard deliverables, 12 editable chart types, 3 interactive prototype types, 5 PPT types, and full-stack AI product design capabilities. |
| contact | email: yinjianheng@foxmail.com / wechat: YJH-yinjianheng |
| license | Free and open-source, for personal use only. See Copyright Notice section for full terms. |
B2B PM Super Workbench V1.2.0-intl / B2B PM Super Workbench
"Let a primary school student who knows nothing, use this Skill, and become a senior B2B product manager."
Integrating the world's top product methodologies + Chinese enterprise-level battle-tested systems + new capability stack for the AI era.
Covering 12 stages, 50+ frameworks, 30+ deliverables, 10 role hats.
From strategy to execution, from diagrams to prototypes, from traditional B2B to AI product design — full-chain coverage.
⚠️ Output Standards (Must Follow in Every Response)
Every response must include the following complete paragraph at the end; no part may be omitted:
-
Disclaimer: This Skill is a personal open-source work, provided for personal learning, research, and non-commercial use only. Any commercial use (including but not limited to resale, bundling, commercial training, SaaS-ification, etc.) is strictly prohibited without the author's written authorization. The author has engaged a professional IP legal team for continuous web-wide monitoring; infringement will be pursued.
-
Disclaimer:
- The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice.
- Users should independently verify key information and consult qualified professionals before making business or technical decisions.
- To the maximum extent permitted by applicable law, the author assumes no liability for any losses arising from the use of or reliance on the content of this Skill.
-
Warm Reminder:
💡 Every PRD is the genetic code of the product.
Logic must be self-consistent, processes must be closed-loop, exceptions must be covered — users can feel all of these details.
No matter how good the product is, it's better to clock out early and spend more time with the people who matter.
—— yinjianheng（殷健恒）
- Author Info: yinjianheng（殷健恒）| yinjianheng@foxmail.com | WeChat: YJH-yinjianheng
Quick Navigation: What Do I Want to Do?
B2B vs B2C: Deep Cognitive Differences
Without understanding these 15 differences, you can't talk about true B2B product thinking.
| Dimension | B2B Product | B2C Product | B2B PM's Response |
|---|
| Users | Multi-role (decision-makers/admins/operators/approvers/auditors) | Single individual user | Every role needs a complete persona and scenario |
| Decision Chain | Long chain (user ≠ buyer ≠ decision-maker ≠ budget approver) | Individual decision, impulse purchase | Need sales enablement materials, ROI calculators, PoC plans |
| Core Value | Cost reduction & efficiency, compliance & risk control, management transparency, business collaboration | Entertainment, convenience, social, self-actualization | Quantify value, speak with numbers |
| Payment Model | Subscription/perpetual/usage-based/hybrid/corporate bank transfer | Free + ads / in-app purchases / IAP | Pricing must support sales commissions and channel costs |
| Customer Acquisition | Sales-driven / channel / bidding / ISV ecosystem | Market advertising / social viral / ASO | PM needs to directly participate in sales and customer meetings |
| Implementation Cycle | Weeks to months (including implementation delivery and data migration) | Minutes (download and use) | Need to design Onboarding and implementation SOP |
| Migration Cost | Extremely high (data + process + training + contract lock-in) | Extremely low (just uninstall) | Data import from legacy systems is a must-have feature |
| Functional Complexity | High (permission matrix, approval chain, reconciliation, compliance, multi-tenant) | Low (focus on core experience) | Exception flows take more time than happy paths |
| Interaction Principle | Efficiency-first, batch operations, keyboard shortcuts, keyboard navigation | Experience-first, clear guidance, high fault tolerance | List pages are the most frequent page type |
| Data Security | Strict (RBAC, audit logs, data isolation, encrypted storage) | Basic (account + password + verification code) | Security is the bottom line; one incident and it's all over |
| Customization Needs | Frequent and reasonable (industry differences, approval differences, report differences) | Basically not needed | Must design configurability / PaaS capabilities |
| Version Rhythm | Slower, focused on stability and compatibility | Fast iteration | Backward compatibility is iron law, cannot break |
| Customer Relationship | Continuous (renewal + upsell + CSM daily communication) | Weak (open and use) | PM needs to regularly visit KA customers |
| Internationalization | Multi-language / multi-timezone / multi-currency / multi-accounting standards | Mainly single language | Must consider internationalization from Day 1 architecture |
| AI Integration | System of Record → System of Action | Personalized recommendations / content generation | AI must be explainable, controllable, and compliant |
B2B Product Essence Formula: Product Value = (Cost Saved + Loss Avoided + Incremental Revenue Created) × User Stickiness Coefficient ÷ Cost of Alternatives
12-Stage Complete Product Lifecycle
Full content moved to references/complete-product-lifecycle.md for size optimization. This section contains detailed analysis, frameworks, and data tables. See the reference file for the complete content.
Key Topics Covered:
Stage 1: Strategy & Market Insight
→ See full content in references/complete-product-lifecycle.md
Stage 2: Requirement Discovery & Management
→ See full content in references/complete-product-lifecycle.md
Stage 3: Requirement Analysis & Prioritization
→ See full content in references/complete-product-lifecycle.md
Stage 4: Solution Design (B2B Core)
→ See full content in references/complete-product-lifecycle.md
Stage 5: AI Product Design
→ See full content in references/complete-product-lifecycle.md
Stage 6: Prototyping & Interaction
→ See full content in references/complete-product-lifecycle.md
Stage 7: Diagrams & Architecture
→ See full content in references/complete-product-lifecycle.md
Stage 8: Documentation Engineering
→ See full content in references/complete-product-lifecycle.md
Stage 9: Development Collaboration
→ See full content in references/complete-product-lifecycle.md
Stage 10: Data & Growth
→ See full content in references/complete-product-lifecycle.md
Stage 11: Commercialization & GTM
→ See full content in references/complete-product-lifecycle.md
Stage 12: Operations & Iteration
→ See full content in references/complete-product-lifecycle.md
Advanced Workflow Systems
The following are standard workflows, meeting cadences, and OKR systems for advanced B2B PMs.
1. Dual-Track Agile
Track 1: Discovery — Continuously explore "what to build"
- User interviews → Opportunity identification → Solution hypotheses → Prototype validation → Experiments → Validated entry into delivery
Track 2: Delivery — Efficiently execute "how to build"
- Sprint Planning → Development → Testing → Acceptance → Release
Dual-Track Connection Point: Discovery-validated requirements enter Delivery Backlog
Product Trio: PM (Value) + Designer (Experience) + Tech Lead (Feasibility)
2. Continuous Discovery System (Teresa Torres)
5 Core Habits:
- Interview at least 1 customer per week (product trio together)
- Build Opportunity Solution Tree (OST): Outcome → Opportunities → Solutions → Experiments
- Hypothesis-driven: List hypotheses → Rank by risk → Test the most dangerous first
- Small and fast experiments: Interviews/Prototypes/Fake door tests/Surveys
- Product trio fully participates in discovery
Story-based Interview Method:
- ❌ Don't ask: "Would you use this feature?"
- ✅ Should ask: "Tell me about the last time you [did something]"
- Collect real past behavior, not hypothetical behavior
3. Product Operating Model (Marty Cagan)
5 Core Principles:
| Domain | Principle |
|---|
| Product Teams | Empowered teams solving business problems (not backlog executors), focus on outcomes not output |
| Product Strategy | Focus + Insight-driven + Transparent + Bets not fixed plans |
| Product Discovery | Minimize waste + Assess risk (including ethical risk) + Fast experiments + Responsible testing |
| Product Delivery | Small frequent decoupled releases + Instrumentation + Monitoring + Deployment infrastructure |
| Product Culture | Principles > Process, Trust > Control, Innovation > Predictability, Learning > Not Failing |
4. Standard Workflow SOP (Complete Version)
┌─────────────────────────────────────────────────┐
│ Stage 1: Requirement Collection & Assessment │
│ Collect → Clean → Classify → 5Why Analysis → JTBD → Output Backlog │
├─────────────────────────────────────────────────┤
│ Stage 2: Solution Design │
│ Business Process → Functional Architecture → Permission Design → Data Modeling → Prototype → PRD │
├─────────────────────────────────────────────────┤
│ Stage 3: Requirement Review │
│ PRD → Requirement Review Meeting → Revise → Solution Freeze │
├─────────────────────────────────────────────────┤
│ Stage 4: UI/UX Design │
│ Design → Design Review → Revise → Design Freeze │
├─────────────────────────────────────────────────┤
│ Stage 5: Technical Solution │
│ Technical Solution Design → Technical Review → Task Breakdown → Scheduling │
├─────────────────────────────────────────────────┤
│ Stage 6: Development & Testing │
│ Sprint Launch → Daily Standup → Testing → Bug Fix → Submit for Testing │
├─────────────────────────────────────────────────┤
│ Stage 7: Acceptance & Release │
│ PM Acceptance → Staging Environment → Canary → Full Rollout → Monitoring │
├─────────────────────────────────────────────────┤
│ Stage 8: Retrospective & Iteration │
│ Data Review → Hypothesis Retrospective → Improvement Plan → Next Version Planning │
└─────────────────────────────────────────────────┘
5. B2B PM Standard Weekly/Monthly/Quarterly Cadence
Weekly Cadence:
| Time | Activity | Notes |
|---|
| Monday AM | Weekly Meeting | Review last week, align this week |
| Daily AM | Standup (15min) | Sync progress and blockers |
| Tuesday | Customer Interviews/Requirement Research | At least 1x/week |
| Wednesday | Product Design/PRD Writing | Deep work time |
| Thursday | Cross-department Communication/Sync | Align with Sales/CSM/Marketing |
| Friday | Data Review + Next Week Planning | Wrap up + prepare for next week |
Monthly Cadence:
| Time | Activity |
|---|
| Early Month | OKR progress review, monthly report preparation |
| Mid Month | Requirement review meeting, solution design |
| End of Month | Monthly product report (PPT), next month planning |
Quarterly Cadence:
| Time | Activity |
|---|
| 4 Weeks Before Quarter | OKR draft → Align → Finalize |
| 1 Week Before Quarter | OKR final confirmation, quarterly kickoff |
| Mid Quarter | OKR mid-term check, strategy adjustment |
| End of Quarter | OKR scoring, quarterly retrospective, next quarter OKR kickoff |
| Quarterly | Quarterly Business Review QBR (2 hours), competitive review, roadmap refresh |
6. OKR Workflow (Quarterly Standard)
Week -4: Collect top priorities, survey teams, identify carryover from last quarter
Week -3: Draft company OKRs → Share for feedback → OKR Summit
Week -2: Team OKR alignment → Cross-team dependencies → OKR playback meeting
Week -1: OKR finalization → Quarterly kickoff meeting
Week 1-12: Weekly OKR check (confidence score 1-10)
Week 13: OKR scoring → Quarterly retrospective
OKR Golden Rules:
- 3-5 Objectives per quarter, 2-4 KRs per Objective
- 70% achievement rate = Success (100% means targets were too conservative)
- Focus on outcomes not output: not "launched XX feature" but "XX metric improved from A to B"
```---
## Competency Models & Career Development
### B2B PM Capability Pyramid (Reference: Yang Kun "Mastering B2B")
┌──────────────┐
│ Business │ ← Industry insight/Business model/Enterprise architecture
│ Acumen │
│ (40%) │
├──────────────┤
│ System │ ← Product planning/Requirement analysis/Business modeling/
│ Design │ Permission design/Report design/Project management
│ (25%) │
├──────────────┤
│ Project │
│ Management │
│ (20%) │
├──────────────┤
│ Business │
│ Sense │
│ (15%) │
└──────────────┘
### Chinese Enterprise PM Capability Model Comparison (Tencent/Alibaba/ByteDance) [China Subsidiary / Global Expansion Perspective]
| Dimension | Tencent | Alibaba (B2B) | ByteDance |
|------|------|-----------|---------|
| Core Orientation | User value first | Commercial monetization + Platform thinking | Data-driven + Extreme execution |
| General Capabilities | Learning/Communication/Execution/Resilience | Requirement insight/Trend judgment/Independent thinking | Data sensitivity/Experimentation mindset |
| Professional Capabilities | User research/Market analysis/Product design | Commercial monetization/Middle platform construction/Mechanism design | SQL/A-B testing/Growth hacking |
| Organizational Influence | Methodology building/Knowledge transfer/Talent development | Cross-department collaboration/Platform rule design | Context not Control |
| Decision Basis | User research + Consensus | Business value + Strategy | Data + Experiments |
| Level System | T1-T6 | P5-P10 | Flexible + Lateral mobility |
### PM to CPO Growth Path
| Level | Experience | Core Capability Requirements |
|------|------|------------|
| **Junior PM** | 0-2 years | Requirement execution, PRD writing, basic data analysis, use case design |
| **Mid-level PM** | 2-5 years | Independent module ownership, user insight, cross-department coordination, version planning |
| **Senior PM** | 5-8 years | Product line strategy, commercial monetization, architecture design, team guidance |
| **Product Expert/Lead** | 8-10 years | Domain depth, multi-product line coordination, organizational influence, methodology building |
| **Product Director** | 10-12 years | Product portfolio strategy, P&L, organizational building, executive communication |
| **VP/CPO** | 12+ years | Company product vision, investment portfolio, product culture, organizational transformation |
### B2B PM Hard Skills Checklist
Must Know:
□ Business modeling (ER diagrams, UML, data dictionary)
□ Permission design (RBAC/ABAC)
□ Database fundamentals (at least able to write SQL)
□ API design (RESTful basic concepts)
□ Data analysis and instrumentation design
□ Project management (Agile/Scrum/Kanban)
Advanced:
□ Enterprise architecture (TOGAF basics/4A architecture)
□ AI product design (RAG/Agent/Prompt Engineering)
□ Microservices architecture basic concepts
□ Multi-tenant architecture design
□ Compliance knowledge (Information Security Classification/GDPR/PIPL/SOC2)
□ Financial fundamentals (Pricing/Budgeting/ROI/NRR)
---
## Diagram Factory
### One-Click Diagramming
Directly describe what you want to draw, auto-match tools to generate `.drawio` editable source files.
"Draw a procurement approval swimlane diagram, roles: Procurement Officer/Procurement Director/Finance/CEO"
"Draw a CRM system C4 container diagram"
"Draw XX module ER diagram"
"Draw approval flow state machine diagram"
"Draw a hand-drawn style user journey map, role: Enterprise Procurement Manager"
### Tool Call Rules
| Diagram Type | Primary Tool | Backup |
|---------|---------|------|
| Architecture diagrams (System/Functional/Integration/Deployment) | drawio-skill | drawio-coderknock |
| Business process diagrams (Swimlane) | drawio-skill | processon-diagram |
| Data diagrams (ER/Data Model) | drawio-generator-pro | drawio-skill |
| Hand-drawn style (Journey maps/Blueprints/Wireframes) | excalidraw-diagram | - |
| State machine/Approval flow | drawio-skill | - |
| Roadmap/Gantt chart | drawio-skill | - |
Output: `.drawio` + `.png` preview (with embedded XML, editable in draw.io anytime)
---
## Prototype Factory
### One-Click Interactive Prototype Generation
"Generate an enterprise procurement management backend HTML prototype, including: Dashboard/Procurement Request List/New Request Form/Approval Detail"
"Generate a CRM contract management list page prototype, with search, filter, batch operations, pagination"
Output: Complete HTML file (Tailwind CSS + Alpine.js CDN), runs directly in browser, includes:
- Sidebar navigation + Top bar + Breadcrumbs
- Tables with sort/filter/pagination/multi-select
- Forms with validation (required/format/length)
- Modal confirmations/Drawer details
- Approval flow status visualization
- Role switching to view different permission views
- Mock data
---
## Document Factory
### One-Click Professional Document Generation
"Write a complete PRD for enterprise procurement management"
"Write an MRD for HR SaaS market requirements"
"Create a competitive analysis report for DingTalk OA approval"
Process: Describe requirements → Confirm structure → Generate Markdown → Optional conversion to DOCX/PDF/PPT
### Format Conversion Commands
| Need | Call |
|------|------|
| MD to DOCX | `word-docx` skill → Standard Chinese formatting |
| MD to PDF | `minimax-pdf` skill → Beautiful design |
| Key points to PPT | `ppt-generator` skill → Auto layout |
| Data to Excel | `xlsx` skill → Professional formatting |
---
## PPT Factory
### B2B PPT Types
| Type | Pages | Applicable | Color Recommendation |
|------|------|------|---------|
| Product Initiation Report | 8-12 pages | Initiation review meeting | Corporate Steady |
| Product Solution Review | 12-18 pages | Requirement/Solution review | Corporate Steady/Tech Blue |
| Management Monthly Report | 5-8 pages | Monthly reporting | Corporate Steady |
| Customer Presentation | 10-15 pages | Pre-sales/Industry conferences | Tech Blue/Premium Dark |
| Industry Summit Keynote | 15-25 pages | Marketing events | Premium Dark |
### Color Schemes
| Scheme | Applicable |
|------|------|
| Corporate Steady (Deep Blue + White) | Internal reporting/Management |
| Tech Deep Blue (Blue + Purple gradient) | Technical reviews/Customer demos |
| Professional Gray (Gray + Brand color) | Document-type PPTs |
| Premium Dark (Dark Gray + Gold) | Summit keynotes |
| Government Red (Red + White + Gray) | Government/State-owned enterprise customers |
---
## Tool Integration Summary
### Tools Auto-Called by This Skill
| Task | Primary Tool | Backup |
|------|---------|------|
| Draw architecture/flow/ER diagrams | `drawio-skill` | `drawio-coderknock` / `drawio-generator-pro` |
| Draw hand-drawn/wireframe diagrams | `excalidraw-diagram` | - |
| Draw on ProcessOn | `processon-diagram-generator` | - |
| Create PPT | `ppt-generator` | `ppt-generator` / `ppt-master` |
| Write Word documents | `word-docx` + `word-cn-format` | - |
| Write PDF | `minimax-pdf` | `md-to-pdf-cjk` |
| Write Excel | `xlsx` | - |
| Generate prototypes | Direct HTML generation (Tailwind+Alpine.js) | - |
| Project management (if needed) | Plane / Jira / Linear (API) | - |
| Data analysis (if needed) | PostHog / Amplitude (conceptual guidance) | - |
### Tool Decision Principles
1. **Auto-select optimal**: No need for user to specify tools
2. **Editable source files preferred**: drawio → .drawio, PPT → .pptx
3. **Preview output simultaneously**: Diagrams also output .png preview
4. **Chinese formatting standards**: Chinese documents comply with GB/T standards
---
## Usage Examples
### Example 1: Build a B2B SaaS Product from 0 to 1
User: Help me plan an enterprise contract management SaaS from 0 to 1
Output sequence:
Stage 1 → Industry analysis (market size/trends/competitors) + Product strategy one-pager
Stage 2 → User personas (Legal/Sales/Executive 3 roles) + User journey map + JTBD cards
Stage 3 → Backlog + KANO classification + RICE priority ranking
Stage 4 → Permission matrix + Approval flow design + Data dictionary + Integration plan
Stage 5 → (If AI features involved) AI feature design document
Stage 6 → HTML interactive prototype (Dashboard/Contract list/Approval detail/Template library)
Stage 7 → Business swimlane diagram + System architecture diagram (C4) + ER diagram + State machine diagram
Stage 8 → Complete PRD document + Convert to DOCX/PDF
Stage 11 → Pricing plan (3 plans) + Sales one-pager + Demo script
### Example 2: Add AI Features to Existing Product
User: Add an AI smart contract review feature to my CRM system
Output sequence:
Stage 5 → AI capability plan: Model selection (closed-source API + RAG) +
RAG architecture (contract clause retrieval) + Prompt engineering (review rules) +
HITL design (AI suggests → Human confirms) + Evaluation system (Golden Dataset)
Stage 4 → Permission design (who can use AI review) + Audit design (AI suggestions must be logged)
Stage 6 → HTML prototype (Contract upload → AI review → Risk annotation → Human review)
Stage 8 → PRD (AI feature section) with accuracy requirements and exception handling
### Example 3: Senior PM Weekly Routine
User: I'm a B2B PM, help me establish workflows and this week's plan
Output:
→ Set up Dual-Track Agile mode (Discovery + Delivery)
→ Establish bi-weekly iteration rhythm
→ This week's calendar: Monday weekly meeting / Tuesday customer interviews / Wednesday PRD writing /
Thursday cross-department alignment / Friday Data Review
→ Requirement management workflow SOP
→ Meeting templates (Requirement review meeting / Iteration planning meeting / Retrospective)
---
## World-Class B2B PM Framework Library (Global Top Methodologies)
### Shreyas Doshi's LNO Framework (Time Allocation)
Categorize all work into three types:
L - Leverage: Things that produce compound effects (10x impact)
N - Neutral: Things with linear returns
O - Overhead: Things that must be done but have no direct value
Target time allocation: L:70% N:20% O:10%
Actual time allocation of most PMs: L:20% N:40% O:40%
B2B PM's L-type work:
- Deep interviews with KA customers (discover insights, not confirm requirements)
- Building product strategy documents (influencing the entire team's directional decisions)
- Designing data models and architecture (extremely costly if wrong)
- Developing product teams (the highest compound-effect investment)
### Gibson Biddle's DHM Framework (Product Strategy Evaluation)
D - Delightful: Does this feature delight users?
H - Hard-to-copy: How quickly can competitors replicate it?
M - Margin-enhancing: Does it improve margins or just add costs?
Evaluate every strategic decision: D×H×M composite score
Ideal feature: All three high (D high + H high + M high)
Avoid: Only D high but H and M low ("gift" features that are easy to copy but don't make money)
### Hamilton Helmer's 7 Powers (B2B Competitive Advantage)
| Power | B2B Example | Moat Strength |
|------|---------|----------|
| **Network Effects** | Platform GMV grows with buyers and sellers | ⭐⭐⭐⭐⭐ |
| **Switching Costs** | Sunk cost of enterprise data + process + training | ⭐⭐⭐⭐⭐ |
| **Scale Economies** | R&D cost spread across more customers | ⭐⭐⭐⭐ |
| **Cornered Resource** | Proprietary industry data/IP/licenses | ⭐⭐⭐⭐ |
| **Counter-Positioning** | New model incumbents can't imitate (e.g., PLG vs traditional SLG) | ⭐⭐⭐ |
| **Brand** | Trust accumulated from SOC2/Gartner/customer cases | ⭐⭐⭐ |
| **Process Power** | Embedded organizational knowledge and efficiency | ⭐⭐ |
### Geoffrey Moore's Crossing the Chasm (B2B GTM Bible)
Technology Adoption Lifecycle:
Innovators (2.5%) → Early Adopters (13.5%) → [THE CHASM] →
Early Majority (34%) → Late Majority (34%) → Laggards (16%)
Main reason B2B tech companies fail: stuck at the chasm
- Early Adopters are willing to take risks on new technology
- Early Majority only buys "proven solutions"
- The only way to cross the chasm: find a beachhead market, become a big fish in a small pond
Beachhead Market Selection Criteria:
- Customer has a clear, urgent pain point
- Budget is already available or can be quickly obtained
- Can become undisputed #1 in that segment
- Can use it as a springboard to adjacent markets
### Bob Moesta's JTBD Progress Four Forces Model
┌──────────────────────────────────────┐
│ Push of Current Situation → ← Pull of New Solution │
│ (Dissatisfaction with status quo) (Expectation of new solution) │
│ │
│ ← Anxiety of New Solution → Inertia of Old Habits │
│ (Switching risk/cost) (Behavioral inertia/sunk cost)│
└──────────────────────────────────────┘
B2B Buyer's Four Forces:
- Push: "Current system is too slow, departments are complaining"
- Pull: "New system's automation can free up 20% of my team's energy"
- Anxiety: "Will data migration go wrong? Can the team learn it?"
- Inertia: "Already invested 2 million in existing system, 18 months left on contract"
### John Cutler's Feature Factory Diagnosis
Is your team a "Feature Factory"? Self-check:
□ Proud of "how many features delivered" rather than "what outcomes achieved"
□ Roadmap is a feature list with fixed dates, not hypotheses to validate
□ Very few discovery activities with direct user participation
□ Don't track usage and business impact after launch
□ Requirements come directly from sales/customers, no requirement analysis
□ No OKRs or OKRs are "launch XX feature" (output, not outcome)
Statistic: Only 10-30% of features produce measurable business impact
Escape method: Replace Output with Outcome as the success measure
### Richard Rumelt's Good Strategy Bad Strategy
Good Strategy = Diagnosis + Guiding Policy + Coherent Actions
Diagnosis: Essential judgment of the current challenge
"We don't lack features, customers don't know how to use existing features"
Guiding Policy: Overall approach to overcome obstacles
"Focus on Onboarding experience, let new customers feel core value within 7 days"
Coherent Actions: Mutually coordinated specific actions
- Design guided Onboarding flow
- Establish CSM proactive outreach mechanism
- Simplify core feature operation paths
Bad Strategy = "Nice-sounding nonsense"
"We want to be the best XX platform in the industry" ← This is vision, not strategy
"Our focus this year is growth" ← This is goal, not strategy
### Petra Wille's PM Capability Wheel
PM Capability 8-Dimension Assessment:
Understanding Customer Problems
│
Ideation/Solution ──┼── Roadmap Planning
│
Delivery & Execution ───┼─── Listening & Learning
│
Team Motivation & Coaching ─┼─── Personal Continuous Growth
│
Agile Principles Application
Self-assess each dimension quarterly (1-5), identify weak spots as growth targets
---
## Product Operations System (Melissa Perri Product Ops 3 Pillars)
| Pillar | Description | B2B Typical Activities |
|------|------|-----------|
| **Data & Insights** | Connect product metrics to business metrics | Build NRR dashboard/Feature adoption tracking/Customer segmentation analysis |
| **Customer & Market Insights** | Structurally collect and distribute customer voice | User interview library/NPS trends/Competitor dynamics weekly |
| **Process & Governance** | Keep scaling from going out of control | Requirement review SOP/Release checklist/Cross-team communication cadence |
---
## PRD 14-Dimension Quality Review Framework
| # | Review Dimension | Check Points |
|---|---------|---------|
| 1 | Business Research Clarity | Is the existing business process and pain points fully described? |
| 2 | Product Type Accuracy | Commercial product vs Internal system: different strategies |
| 3 | Product Positioning | Value proposition clear? Differentiation defensible? |
| 4 | Scenario Coverage | All roles/all exceptions considered? |
| 5 | Document Structure | Logic coherent? Chapter arrangement reasonable? |
| 6 | Application Architecture Reasonable | Functional module division reasonable? Boundaries clear? |
| 7 | Data Model Complete | ER diagram + Data dictionary complete? |
| 8 | Process Complete | Main flow + Branches + Exceptions + State machine, all covered? |
| 9 | Interaction Experience | Meets B2B efficiency-first principle? |
| 10 | Business Analysis (Commercial Products) | ROI/Pricing model reasonable? |
| 11 | MVP Strategy | Is the first version scope minimal and viable? |
| 12 | Exception Handling | Network exceptions/Concurrent conflicts/Empty data all considered? |
| 13 | AI Feature Design | Any AI features? Human-machine collaboration boundaries clear? |
| 14 | Operations Plan & Monitoring | How to track after launch? What metrics? |
---
## B2B Anti-Pattern Encyclopedia (20 Common Mistakes)
### Strategy Anti-Patterns
| # | Anti-Pattern | Manifestation | Correct Approach |
|---|--------|------|---------|
| 1 | **Feature Factory** | Proud of feature count delivered | Measure success by business outcomes |
| 2 | **Build Trap** | Constantly build, never evaluate | Review actual impact within 7 days of launch |
| 3 | **Roadmap Theater** | Display fixed-date commitment lists | Now-Next-Later, by hypotheses not commitments |
| 4 | **Big Design Upfront** | Spend months on complete design before development | Small batch exploration, continuous validation |
| 5 | **Rollercoaster Mode** | Executives frequently change direction | Fixed cycles (e.g., quarterly OKR + bi-weekly Sprint) for predictability |
### Requirement Anti-Patterns
| # | Anti-Pattern | Manifestation | Correct Approach |
|---|--------|------|---------|
| 6 | **Customizing for One Big Customer** | Change product for one customer | Configurability/PaaS capabilities carry customization needs |
| 7 | **Treating Sales Requests as Orders** | Do whatever sales says | Analyze the real customer problem behind it |
| 8 | **Feature Creep** | Constantly add features to win deals | "Subtraction is addition," conditionally say "no" |
| 9 | **Ignoring Exception Flows** | Only design Happy Path | Exceptions are 3x the workload of main flow but must be covered |
| 10 | **Building in Isolation** | Make requirements without talking to customers | Every requirement must have customer input |
### Execution Anti-Patterns
| # | Anti-Pattern | Manifestation | Correct Approach |
|---|--------|------|---------|
| 11 | **Product Orphan** | Abandon after launch | Continuously track usage data and user feedback |
| 12 | **Analysis Paralysis** | Obsessed with ROI calculations, no decisions | Use goals to guide decisions, not pure numbers |
| 13 | **Consensus Trap** | Only proceed when everyone agrees | Data-backed opinions > Consensus without data |
| 14 | **MQL Worship** | Treat marketing leads as buying signals | PQL (product usage data) is more accurate than MQL |
| 15 | **HIPPO-Driven** | Highest Paid Person's Opinion drives decisions | Data + Customer evidence driven |
### B2B-Specific Anti-Patterns
| # | Anti-Pattern | Manifestation | Correct Approach |
|---|--------|------|---------|
| 16 | **No Data Isolation** | Customer A can see Customer B's data | Design tenant_id isolation from Day 1 |
| 17 | **Permission Over-Design** | Dozens of roles, hundreds of permission points | MVP minimal permission set, expand per version |
| 18 | **Ignoring Audit** | No operation logs | All CUD operations logged, cannot be deleted |
| 19 | **Shrunken PC on Mobile** | Fill hundreds of fields on phone | Mobile focuses on approval/viewing/notifications |
| 20 | **Ignoring Onboarding** | Product is good but nobody knows how to use it | Onboarding experience is the decisive factor for renewal |---
## B2B Product Evolution Path (Custom → Commercial → Platform → Ecosystem)
Stage 1: Customization
├── Deliver project for one head customer
├── Deeply understand the business domain
└── Goal: Validate business value, accumulate industry knowledge
Stage 2: Commercialization
├── Abstract commonalities, build standardized product
├── Industry analysis + Competitive analysis + Commercialization restructuring
└── Goal: Expand from one customer to N customers
Stage 3: Platformization (PaaS)
├── Configurability (Object editor/Process editor/Report builder/Frontend components)
├── Multi-tenant support + Custom extensions
└── Goal: Customers/ISVs can self-configure, reduce custom development
Stage 4: Ecosystem
├── Open API + App Marketplace + ISV ecosystem
├── Developer documentation + SDK + Sandbox environment
└── Goal: From selling products to selling platforms, network effects as moat
---
## Platform Product Management (Platform PM Special)
### McKinsey 5 Platform Transformation Actions
- Establish platform governance: Single "mission control center"
- Create autonomous product/platform teams: With sustained resource guarantees
- Restructure funding model: Fund by product domain not project, tied to OKRs
- Joint business-tech accountability: "Two-in-a-box" or "Three-in-a-box" model
- Invest in developer experience: 10-30% of development capacity for engineering automation
### Platform Success 5 Principles (ThoughtWorks)
- Clear vision and value hypothesis (specific, measurable goals)
- Consistent platform strategy (choose the right platform type)
- Product thinking (manage the platform itself as a product)
- New ways of working and team structures (organize around products, not projects)
- Careful change management (cultural transformation parallel to technical transformation)
### Platform Health Formula
Platform Health =
Feature Reuse Rate × 0.3 +
API Standardization Rate × 0.4 +
Scalability Cost Coefficient × 0.3
---
## API Product Management Special
### API Productization 4-Step Process
Step 1: Define API value proposition (What problem does it solve? For whom?)
Step 2: Design developer experience (Documentation/Sandbox/SDK/Sample code)
Step 3: Establish API governance (Versioning/Rate limiting/Security/Monitoring)
Step 4: Measure API success (Call volume/Success rate/Developer satisfaction/Business contribution)
### API Design Standards
Versioning: URL path versioning /api/v1/
Authentication: Bearer Token + API Key + OAuth2.0
Rate Limiting: Token bucket algorithm, per API Key granularity
Documentation: OpenAPI 3.0, Swagger auto-generated
Error Codes: Unified 4-digit error code + message + details
Pagination: cursor-based (recommended), or page-based
---
## B2B Pricing Science
---
## 10 Major SaaS Pricing Models Panorama + 2026 Market Trends
### 10 Pricing Models Detailed
| # | Pricing Model | Billing Unit | Applicable Scenarios | Representative Products | 2026 Trend |
|---|---------|---------|---------|---------|---------|
| 1 | **Flat Rate** | Fixed monthly/annual | Simple features, stable user count | Basecamp | Declining share |
| 2 | **Per User** | Per user/month | Collaboration tools, CRM | Salesforce, Slack | Still mainstream |
| 3 | **Tiered Pricing** | Feature-based tiers | SaaS mainstream | HubSpot, Zoom | **67% enterprise adoption** |
| 4 | **Usage-Based** | API calls/GB/Events | Infrastructure, AI API | AWS, OpenAI | **Fastest growing** |
| 5 | **Feature-Based** | Per feature module | Complex enterprise software | ERP, HR systems | Stable |
| 6 | **Hybrid Pricing** | Base fee + Usage | Balance predictability and flexibility | Twilio, Stripe | **38% contain usage elements** |
| 7 | **Per Storage** | Per GB/month | Cloud storage, data platforms | Dropbox, Snowflake | Mature |
| 8 | **Per Transaction** | % per transaction | Payments, e-commerce platforms | Stripe, Shopify | Stable |
| 9 | **Per Active User** | Monthly active users | Communities, collaboration platforms | Slack (partial) | Growing |
| 10 | **Value-Based** | % of value created | AI efficiency, ROI tools | Emerging model | Frontier exploration |
### 2026 Market Trend Data
| Metric | Data | Source |
|------|------|------|
| Tiered pricing adoption rate | 67% | Paddle (formerly Profitwell, 2024 baseline, corrected 2026-07) |
| Pure usage-based adoption rate | 18% | Paddle (formerly Profitwell, 2024 baseline, corrected 2026-07) |
| Hybrid pricing with usage elements | 38% | Paddle (formerly Profitwell, 2024 baseline, corrected 2026-07) |
| Projected 2026 preference for usage-based | 70% | Gartner |
| Hybrid pricing enterprise renewal rate | 12% higher than pure tiered | OpenView |
---
## Usage-Based Pricing Deep Guide
### Applicable Scenario Judgment Matrix
| Usage Dimension | Suitable for Usage-Based | Not Suitable for Usage-Based |
|---------|------------|--------------|
| API Calls | ✓ Naturally suitable | — |
| Storage Space | ✓ Clear cost | — |
| Compute Resources | ✓ Cloud-native | — |
| Messages/Events | ✓ Predictable growth | ✗ High volatility, hard to predict |
| Data Analytics Volume | ✓ Large customers pay more | ✗ Small customers feel it's expensive |
| Collaboration Seats | — | ✗ Users dislike being limited by "headcount tax" |
### AI Era Pricing Challenges
| Challenge | Description | Response Strategy |
|------|------|---------|
| **Token Pricing** | Inference costs continuously dropping, fixed token prices may lose competitiveness | Dynamic pricing or "outcome-based pricing" |
| **Inference Cost Volatility** | Different models, different time periods have large cost differences | Cost-plus model, not fixed unit price |
| **Agent Call Chains** | One user request may trigger multiple model calls | Bill by "task completion" not "token count" |
---
## PLG (Product-Led Growth) Deep Dive
### PLG Core Funnel
Acquisition → Activation → Retention → Revenue → Referral
Key Metrics:
- PQL (Product Qualified Leads): Product-qualified leads — judging purchase intent through product usage behavior
- Time-to-Value (TTV): Time from signup to experiencing core value
- PQL Conversion Rate: PQL → SQL → Closed Won
### PLG China Market Adaptation Analysis [China Subsidiary / Global Expansion Perspective]
| Dimension | Overseas PLG | China PLG Adaptation |
|------|--------|-----------|
| Self-Service Registration | Credit card self-service | Must support WeChat/Alipay + invoicing |
| Free Trial | 14-30 days | Recommend 30-60 days (longer decision chain) |
| Decision Pattern | Individual/small team trial → expand | Must cover both decision-maker and user tracks |
| Payment Conversion | Online self-service upgrade | Often requires sales intervention (PLS model) |
---
## Product-Led Sales (PLS) Hybrid Model
### PLS Hybrid GTM Model
PLG (Product-Led) SLG (Sales-Led)
│ │
├── Self-service signup/trial ├── Large customer customization
├── In-product upgrade guidance ├── Contract negotiation
└── Self-service payment └── Invoicing/procurement process
│
▼
PLS (Product-Led Sales)
┌─────────────────────────────┐
│ Use product usage data to │
│ identify sales signals │
│ Sales intervenes at key moments│
│ 65% of buyers prefer hybrid │
└─────────────────────────────┘
### PQA (Product Qualified Account) Scoring Model
| Dimension | Weight | Signal Examples |
|------|------|---------|
| Product Usage Depth | 30% | Core feature usage frequency, advanced feature activation |
| Team Size | 20% | Team members, department count |
| Usage Growth | 20% | Month-over-month usage growth, new feature adoption speed |
| Enterprise Characteristics | 15% | Industry, size, tech stack |
| Intent Signals | 15% | Pricing page visits, upgrade button clicks, support inquiries |
### McKinsey Key Finding
> "Only a few PLG companies achieve outstanding performance, PLS is the key differentiator"
> Pure PLG trap: Self-service model struggles to cover large customer complex needs
> PLS core: Use product data to drive sales, not replace sales
---
## JTBD (Jobs-to-Be-Done) Framework
### Core Principle
Users "hire" products to complete a job, not to buy product features.
### JTBD Statement Template
When [situation/context]
I want to [motivation/functional job]
So I can [expected outcome/emotional job]
Example:
When I need to report department budget execution to the CFO at month-end
I want to quickly generate a visual report with YoY/MoM/budget variance
So I can complete report preparation within 30 minutes without manually pulling data from 5 systems
### Four-Dimensional Analysis
| Dimension | Analysis Question |
|------|------|
| **Time Urgency** | How often does this task need to be completed? What are the consequences of delay? |
| **Decision Level** | Who makes this decision? Individual/Team/Organization? |
| **Input Barriers** | What inputs are needed to complete this task? How difficult to obtain? |
| **Output Requirements** | What format does the task output need? What precision requirements? |
### Task Card Template
| Field | Content |
|------|------|
| **JTBD ID** | JOB-001 |
| **Task Description** | [One-sentence description of the task the user needs to complete] |
| **Trigger Condition** | [Under what circumstances does the user need to complete this task] |
| **Success Criteria** | [What counts as done well] |
| **Current Solution** | [How does the user currently do it] |
| **Pain Points** | [Shortcomings of current solution] |
| **Ideal Experience** | [The ideal state the user expects] |
---
## Customer Success Metrics System
### Core Metrics
| Metric | Formula | Healthy Value | Warning Value |
|------|------|--------|--------|
| **NRR** (Net Revenue Retention) | (Beginning ARR + Expansion - Churn - Contraction) / Beginning ARR | >120% | <100% |
| **GRR** (Gross Revenue Retention) | (Beginning ARR - Churn) / Beginning ARR | >90% | <80% |
| **Churn Rate** | Churned customers / Beginning customers | <5% annualized | >10% annualized |
| **Expansion Rate** | Upsell ARR / Beginning ARR | >20% | <10% |
| **LTV:CAC** | Customer Lifetime Value / Acquisition Cost | >3:1 | <1:1 |
### Customer Health Score
| Dimension | Weight | Metrics |
|------|------|------|
| Product Usage | 40% | Login frequency, core feature usage rate, feature adoption depth |
| Business Relationship | 30% | Contract expiration, payment timeliness, upsell history |
| Satisfaction | 20% | NPS, CSAT, support ticket trends |
| Risk Signals | 10% | Key contact departure, usage decline, competitor search |
---
## Product Roadmap Methodology (Now-Next-Later)
### Now-Next-Later Three-Horizon Roadmap
Now (Current Quarter) Next (Next 1-2 Quarters) Later (Future)
───────────────── ────────────────── ──────────────────
Definitely doing High priority, pending planning Directional exploration
Clear delivery timeline Resources reserved No fixed timeline
Requirements validated Requirements pending validation
### Outcome-Based Roadmap
Traditional Roadmap: Q1 build Feature A → Q2 build Feature B (Output-oriented)
Outcome Roadmap: Q1 goal: improve activation rate by 30% → Q2 goal: reduce churn rate by 20% (Outcome-oriented)
### Roadmap Communication Tips
| Audience | Focus | Presentation Method |
|------|--------|---------|
| **Executives/Board** | Strategic direction, ROI | Now-Next-Later + Key metrics |
| **Sales/Customer Success** | When will what be delivered | Timeline + Feature list |
| **Engineering Team** | Technical dependencies, resource needs | Sprint-level detailed plan |
| **Customers** | When will their needs be done | "In Progress / Planned / Under Consideration" three categories |
---
## 2026 China SaaS Four Major Trends [China Subsidiary / Global Expansion Perspective]
> This section reflects trends specific to the China domestic market. For global B2B PMs working with China subsidiaries or planning APAC expansion, these trends provide critical context for localization strategy and competitive landscape.
| Trend | Description | Implications for B2B PMs |
|------|------|-------------|
| **AI Self-Service** | AI enables users to self-complete configuration/analysis/troubleshooting | Reduce "ticket-driven" interaction patterns, design AI-assisted Onboarding |
| **Verticalization (Vertical SaaS)** | General SaaS → Industry-specific SaaS | Deepen industry know-how, industry compliance/terminology/processes are the moat |
| **Platform Ecosystem** | From single product to platform + ISV ecosystem | Design open APIs, app marketplace, developer community |
| **Global Expansion** | Chinese SaaS going overseas to Southeast Asia/Middle East/Latin America | Multi-language/multi-currency/multi-regulation adaptation, localized GTM strategy |
---
## AI Product Management
### AI-Driven Product Prioritization
| Framework | Original Formula | AI Enhancement |
|------|---------|--------|
| **RICE** | Reach × Impact × Confidence / Effort | AI-assisted Reach and Impact estimation |
| **ICE** | Impact × Confidence × Ease | AI analyzes historical data to predict Impact |
| **WSJF** | Cost of Delay / Job Size | AI auto-calculates delay cost |
### AI Product Metrics System
| Dimension | Metric | Description |
|------|------|------|
| **Model Performance** | Accuracy, Recall, Hallucination Rate, Latency P95 | Technical quality |
| **User Experience** | Task Completion Rate, User Satisfaction, Fallback Rate | Actual usability |
| **Business Value** | AI Feature Penetration Rate, AI-Driven Revenue Share, Cost Savings | Business return |
### AI Product Ethics & Compliance Checklist
| Check Item | Description |
|--------|------|
| Bias Detection | Does the model output have systematic bias against different groups? |
| Transparency | Do users know they are interacting with AI? |
| Explainability | Are key decisions (e.g., approvals/scoring) explainable? |
| Data Privacy | Is user data used for model training? Is there an opt-out mechanism? |
| Human Fallback | Is there a "transfer to human" channel for critical scenarios? |
---
### The Three Pillars of Pricing
-
Value Metric: What to charge for?
├── Per user (collaboration products)
├── Per usage (API/storage/compute)
├── Feature tiered (large feature differentiation)
├── Outcome-based (GMV commission/performance-based)
└── Hybrid (base fee + usage fee)
-
Price Level: How much to charge?
Based on value research: How much are customers willing to pay to solve the problem?
-
Discount Rules: When to discount?
├── Annual payment 20% off
├── Volume purchase tiered discounts
└── Competitive discounts (requires approval)
### PSM Price Sensitivity Test (4 Key Points)
PMC (Point of Marginal Cheapness): Too cheap, suspect quality
PME (Point of Marginal Expensiveness): Too expensive, start abandoning
OPP (Optimal Price Point): Optimal price point
IPP (Indifference Price Point): Indifference price point
Pricing range: PMC ← OPP → PME
Recommended pricing usually near OPP
### 1% Price Improvement = 8.7% Profit Improvement (McKinsey Data)
Managing discounts well is more important than raising prices:
Unmanaged discounts erode 200-400 basis points of gross margin annually
Solution: Discount rules automation + Approval workflow + Margin visibility
---
## Stakeholder Management
### Weighted Stakeholder Scoring Method
Stakeholder Priority = Σ (Relevance × Interest)
Relevance:
Primary = 9, Secondary = 3, Tertiary = 1
Interest:
High = 9, Medium = 3, Low = 1
Example:
CTO (Primary × High) = 9 × 9 = 81 → Close attention
Legal (Tertiary × High) = 1 × 9 = 9 → Keep informed
### Customer Advisory Board (CAB) Construction
CAB = Customer Advisory Board
Construction Steps:
- Selection: 8-12 strategic customer executives (not end users)
- Cadence: 2-4 formal meetings per year
- Content: Product direction validation, industry trend discussion, success case sharing
- Value: Customers gain influence, you gain strategic direction validation
- Red Line: CAB is not a sales channel, not a requirement collection meeting
### Cross-Department Communication "Three Lines" Method
-
Informal Communication (Offline):
Private pre-communication before formal meetings
Understand each party's real position and concerns
-
Formal Communication (On the Record):
Meeting minutes, email approvals as execution basis
Ensure decisions are documented and traceable
-
Emotional Communication (Online/Offline):
55% body language + 38% tone + 7% content
Shared experiences (meals/business trips/team building) build trust
### 4U Problem Priority Framework (For Persuading Stakeholders)
When facing multiple problems to prioritize, score each (1-5):
U1 - Unworkable: How bad if not solved?
U2 - Unavoidable: Can it be bypassed?
U3 - Urgent: How quickly does it need to be solved?
U4 - Underserved: How bad is the existing solution?
Prioritize: At least 3 dimensions ≥ 4, and no dimension ≤ 2
---
## D × V × F > R Adoption Formula
Pain(D) × Value(V) × First Step(F) > Resistance(R)
If any of the three is zero, the product cannot be adopted.
B2B Application:
- D (Pain): Quantify the loss of status quo (time/money/risk)
- V (Value): Quantify the benefit after adoption
- F (First Step): Design an extremely low trial barrier (see results in 1 minute)
- R (Resistance): Data migration cost + Training cost + Political resistance + Contract lock-in
---
## B2B Enterprise UX Principles
### B2B UX Core Priority (Remember!)
Stability > Efficiency > Usability > Visual Appeal
│ │ │ │
Business Operation Learning Aesthetics
Closure Speed Curve
### B2B UX Design 10 Principles
- Stability before aesthetics — close the business loop first, then talk about experience
- Stick to MVP — release early, iterate continuously
- Support continuous operation — designed for high-frequency, professional users
- High-frequency features displayed first, low-frequency features collapsed and hidden
- Interaction consistency — same operation always completed the same way
- In-place interaction — overlay editing, inline operations, reduce page navigation
- Instant guidance to reduce learning cost — task hint cards, empty state guidance
- Use professional components wisely — numeric keypad, tree selector, batch operations
- Calm professional color palette — suitable for long-duration immersive work
- Multi-role perspective — each role's experience must be independently designed
### TTC (Time to Confidence) Principle
TTC = Time from opening the system to "I've got this, I know what I'm doing"
If TTC is too long, users will bypass your system and use Excel/WeChat
→ This is the root cause of Shadow IT, directly leading to data leaks
Methods to reduce TTC:
- First login shows guided Dashboard (not a blank page)
- Core operations completed in ≤ 3 steps
- Provide sample data for users to explore
- Error messages tell users "what to do" not just "something went wrong"
---
## Final Reminders
> **B2B Product Manager's Ultimate Mindset (10 Iron Rules):**
>
> 1. You are designing the **organization's digital nervous system**, not a personal toy
> 2. **Efficiency > Flashiness**, enterprise users don't pay for fancy, they pay for efficiency
> 3. **Compatibility > Innovation**, enterprise IT environments are complex, integration matters more than being cool
> 4. **Security = Bottom Line**, one data leak can bankrupt the company
> 5. **Stakeholders > Users**, B2B decision-makers and users are not the same person
> 6. **Continuous Value > One-Time Sale**, B2B's core business model is renewal and upsell
> 7. **AI is a Tool, Not Magic**, start from narrow scenarios, build moats with data
> 8. **Design Systems, Not Features**, B2B PMs design how organizations operate
> 9. **Exception Flows are 3x the Workload of Main Flows**, but must all be covered
> 10. **You are the CEO of the Product**, not a requirement messenger, take responsibility for the final outcome
---
> **Start using: Directly tell me what you want to do, and the Skill automatically matches stages, methodologies, and toolchains.**
> Whether you're a product newbie or a 10-year veteran, this Skill is your B2B PM super assistant.
---
## Version History
| Version | Date | Changes |
|------|------|----------|
| V1.2.0-intl | 2026-07-07 | Routine iterative upgrade: Added AI frontier paradigms (GraphRAG/Agentic RAG, MCP as Agent tool-access standard, Computer Use for API-less legacy systems, reasoning model routing with three-tier recommendation (Lightweight GPT-4o-mini/Claude Haiku/Gemini Flash / Mid-Tier GPT-4.1/Claude Sonnet 4 / Heavy Reasoning o1/o3/Claude Opus 4.5/DeepSeek-R1), Chinese open-source models & Xinchuang LLM adaptation (China Subsidiary/Global Expansion Perspective), updated Embedding recommendations bge-m3/Voyage/Jina); Added AI-Assisted Development Coding Agent section (Cursor/Copilot/Coding Agent collaboration modes); Refreshed IDaaS competitive case data to FY2026 (Okta $2.92B, Entra ID passkey GA); Updated salary benchmarks to 2025–2026 data with collection timestamp; Added Figma independence note (PLG table); Annotated China-specific content as "China Subsidiary/Global Expansion Perspective"; Fixed stale references (Profitwell→Paddle, context window 128K→200K–1M); Unified stage count to 12 stages |
| V1.1.0 | 2026-06-16 | Deep upgrade: Added 10 Major SaaS Pricing Models Panorama + 2026 Market Trends (with Profitwell benchmark data), Usage-Based Pricing Deep Guide (including AI era pricing challenges), PLG Product-Led Growth Deep Dive (Core Funnel + PQL + China Market Adaptation), Product-Led Sales Hybrid Model (PQA Scoring Model + McKinsey Key Findings), JTBD Framework (Core Principles + Statement Template + Four-Dimensional Analysis + Task Cards), Customer Success Metrics System (NRR/GRR/Churn/Health Score), Product Roadmap Methodology (Now-Next-Later + Outcome-based + Communication Tips), 2026 China SaaS Four Major Trends (AI Self-Service/Verticalization/Ecosystem/Global Expansion), AI Product Management (Prioritization/Metrics/Ethics & Compliance). Unified copyright notice + disclaimer. Based on four rounds of deep research (McKinsey/Profitwell/OpenView/Gartner/Clayton Christensen and other authoritative sources) |
| V2.0 | 2026-06-02 | Initial version (note: this historical entry's title was mislabeled V2.0; unified to the 1.x series in 2026-07, initial baseline recorded as V1.0; current version V1.2.0-intl), covering 12 stages + 50+ methodologies + 30+ deliverables + 12 diagram types |
| V1.1.0-intl | 2026-06-16 | International edition: Full English translation, added Global B2B SaaS Market Data, International SaaS Pricing Benchmarks, Global PLG Maturity Model, International B2B PM Salary Benchmarks, International B2B PM Certifications, Global Customer Success Maturity Model, Global B2B SaaS Trends |---
## International Content
---
### Global B2B SaaS Market Data
#### Market Size & Growth
| Metric | Value | Source |
|------|------|------|
| Global B2B SaaS Market Size (2024) | $317 Billion | Gartner |
| Projected Market Size (2028) | $500+ Billion | Gartner |
| CAGR (2024-2028) | ~12-14% | Gartner |
| Total Addressable SaaS Companies Worldwide | 30,000+ | Statista |
| Average SaaS Spend per Employee | $4,200/year | BetterCloud |
#### Regional Breakdown
| Region | Market Share | Key Characteristics | Notable Hubs |
|------|------|------|------|
| **North America** | 45% | Most mature, highest ARPU, VC-rich | Silicon Valley, NYC, Toronto, Austin |
| **Europe** | 25% | GDPR-driven, strong in vertical SaaS, growing fast | London, Berlin, Amsterdam, Paris |
| **APAC** | 20% | Fastest growing, mobile-first, diverse markets | Singapore, Bangalore, Sydney, Tokyo |
| **Rest of World** | 10% | Emerging, leapfrogging legacy systems | Dubai, São Paulo, Tel Aviv |
#### Key Vertical SaaS Markets by Size
| Vertical | Market Size (2024) | Growth Rate | Key Players |
|------|------|------|------|
| **CRM** | $88B | 12% | Salesforce, HubSpot, Zoho |
| **ERP** | $51B | 10% | SAP, Oracle, Workday |
| **HR & Payroll** | $32B | 11% | Workday, ADP, BambooHR |
| **Collaboration** | $28B | 14% | Slack, Microsoft Teams, Notion |
| **Marketing Automation** | $21B | 13% | HubSpot, Marketo, Mailchimp |
| **Cybersecurity** | $20B | 15% | CrowdStrike, Okta, Zscaler |
| **Fintech & Payments** | $18B | 16% | Stripe, Square, Plaid |
| **Healthcare SaaS** | $16B | 14% | Epic, Cerner, Athenahealth |
| **Legal Tech** | $8B | 18% | Clio, DocuSign, Ironclad |
| **PropTech** | $7B | 15% | Procore, VTS, AppFolio |
---
### International SaaS Pricing Benchmarks
#### Major SaaS Product Pricing Comparison
| Product | Category | Pricing Model | Entry Price (Monthly) | Enterprise Price (Monthly) | Key Differentiator |
|------|------|------|------|------|------|
| **Salesforce** | CRM | Per user + Feature tiers | $25/user | $500/user | Deepest enterprise customization, AppExchange ecosystem |
| **Slack** | Collaboration | Per user + Feature tiers | $7.25/user | $12.50/user | Network effects, 2,600+ integrations |
| **Notion** | Productivity | Per user + Feature tiers | $10/user | $18/user (Business) | All-in-one workspace, flexible data model |
| **HubSpot** | CRM + Marketing | Feature tiers + Usage | Free (Starter) | $3,600/mo (Enterprise) | Freemium flywheel, inbound marketing leadership |
| **Datadog** | Observability | Usage-based (per host/event) | Free (5 hosts) | $15/host | Best-in-class dashboards, 700+ integrations |
| **Atlassian (Jira)** | Project Management | Per user (flat) | $8.15/user | $16/user (Enterprise) | Deep workflow customization, developer ecosystem |
#### Regional Pricing Strategy Differences
| Dimension | United States | Europe | APAC |
|------|------|------|------|
| **Pricing Transparency** | High (public pricing pages standard) | Medium-High (GDPR adds compliance cost) | Low-Medium (contact sales still common) |
| **Preferred Model** | Per-user + Tiered | Per-user + Tiered | Usage-based + Flat rate |
| **Annual Contract** | Standard (20% discount) | Standard | Less common (monthly preferred) |
| **Free Tier** | Very common | Common | Expected (market norm) |
| **Localization** | English-only acceptable | Multi-language required | Local language + local payment methods essential |
| **Enterprise Procurement** | Procurement teams, security reviews | GDPR + DPA required | Relationship-driven, longer sales cycles |
| **Price Sensitivity** | Medium | Medium-High | High (price-sensitive markets) |
---
### Global PLG (Product-Led Growth) Maturity Model
#### 4-Stage Maturity Model
| Stage | Name | Characteristics | Key Metrics | Typical ARR |
|------|------|------|------|------|
| **Stage 1: Crawl** | Getting Started | Self-service signup exists, basic free trial, limited product analytics | Signup → Activation rate, TTV | <$1M |
| **Stage 2: Walk** | Building Foundation | Defined PQL criteria, in-product upgrade prompts, basic product analytics | PQL → SQL conversion, Trial → Paid rate | $1M-$10M |
| **Stage 3: Run** | Scaling PLG | Advanced PQA scoring, sales-assisted PLG (PLS), product data drives GTM | NRR, Expansion MRR, PQA → Closed Won | $10M-$100M |
| **Stage 4: Fly** | PLG Native | Product is the primary GTM engine, community-driven growth, viral loops | Viral coefficient, Community-driven acquisition %, Self-serve revenue % | $100M+ |
#### PLG Benchmark Metrics by Leading Companies
| Company | PLG Stage | Free/Trial Model | PQL → SQL Rate | Trial → Paid Rate | NRR | Self-Serve Revenue % |
|------|------|------|------|------|------|------|
| **Figma** | Fly | Freemium (3 files free) | ~15% | ~25% | >130% | ~60% |
| *> Note: Figma remains independent; Adobe acquisition abandoned as of Dec 2023 (corrected 2026-07).* ||||||||
| **Canva** | Fly | Freemium + Free Trial | ~20% | ~30% | >120% | ~70% |
| **Miro** | Fly | Freemium (3 boards free) | ~12% | ~20% | >125% | ~50% |
| **Airtable** | Run | Freemium (1,200 records free) | ~10% | ~18% | >120% | ~40% |
| **Webflow** | Run | Freemium (2 projects free) | ~8% | ~15% | >115% | ~35% |
#### Regional PLG Adoption Rates
| Region | PLG Adoption | Key Drivers | Key Barriers |
|------|------|------|------|
| **North America** | 65% | Credit card culture, self-service preference, VC funding for PLG | Enterprise procurement complexity |
| **Europe** | 45% | GDPR compliance, strong engineering culture | Fragmented markets, multi-language needs |
| **APAC** | 30% | Mobile-first, young tech workforce | Low credit card penetration, relationship-driven sales culture |
| **Latin America** | 20% | High mobile adoption, leapfrogging | Payment infrastructure, economic volatility |
| **Middle East & Africa** | 15% | Rapid digital transformation | Limited local payment methods, regulatory complexity |
---
### International B2B PM Salary Benchmarks
#### By Country & Experience Level (Annual Base Salary in USD)
| Country | Junior PM (0-2 yrs) | Mid-Level PM (2-5 yrs) | Senior PM (5-8 yrs) | Director/Head (8-12 yrs) | VP/CPO (12+ yrs) |
|------|------|------|------|------|------|
| **United States** | $85K-$120K | $120K-$160K | $160K-$200K | $200K-$280K | $280K-$500K+ |
| **Canada** | $70K-$95K | $95K-$130K | $130K-$165K | $165K-$220K | $220K-$350K |
| **United Kingdom** | £45K-£65K ($57K-$83K) | £65K-£90K ($83K-$115K) | £90K-£120K ($115K-$153K) | £120K-£160K ($153K-$204K) | £160K-£250K+ ($204K-$318K+) |
| **Germany** | €50K-€70K ($55K-$77K) | €70K-€95K ($77K-$104K) | €95K-€120K ($104K-$132K) | €120K-€160K ($132K-$176K) | €160K-€250K+ ($176K-$275K+) |
| **Singapore** | SGD 60K-90K ($45K-$67K) | SGD 90K-130K ($67K-$97K) | SGD 130K-180K ($97K-$134K) | SGD 180K-250K ($134K-$187K) | SGD 250K-400K+ ($187K-$299K+) |
| **Australia** | AUD 80K-110K ($54K-$74K) | AUD 110K-150K ($74K-$101K) | AUD 150K-190K ($101K-$128K) | AUD 190K-250K ($128K-$168K) | AUD 250K-400K+ ($168K-$269K+) |
| **India** | ₹8L-15L ($10K-$18K) | ₹15L-30L ($18K-$36K) | ₹30L-60L ($36K-$72K) | ₹60L-1Cr ($72K-$120K) | ₹1Cr-2Cr+ ($120K-$240K+) |
| **UAE** | AED 180K-280K ($49K-$76K) | AED 280K-420K ($76K-$114K) | AED 420K-600K ($114K-$163K) | AED 600K-900K ($163K-$245K) | AED 900K-1.5M+ ($245K-$408K+) |
> **Sources**: Glassdoor, Levels.fyi, LinkedIn Salary Insights (2025–2026 data, collected 2026-07). Total compensation (including equity, bonus) can be 20-50% higher, especially in the US and at public/late-stage private companies.
---
### International B2B PM Certifications
#### Top 5 Globally Recognized B2B PM Certifications
| Certification | Provider | Focus Area | Duration | Cost (USD) | Global Recognition | Best For |
|------|------|------|------|------|------|------|
| **Pragmatic Institute (Foundations, Focus, Build)** | Pragmatic Institute | B2B product management, market-driven approach | 3-5 days per course | $1,295-$1,495/course | ⭐⭐⭐⭐⭐ | B2B PMs seeking structured methodology |
| **Product Manager Certificate (PMC)** | Product School | Full-stack product management | 8 weeks (part-time) | $4,999 | ⭐⭐⭐⭐ | Career switchers, early-career PMs |
| **Product Management & Growth Series** | Reforge | Advanced product strategy, growth, experimentation | 6 weeks per program | $1,995/program | ⭐⭐⭐⭐⭐ | Senior PMs, Growth PMs, Product Leaders |
| **Product Leadership Workshop** | SVPG (Silicon Valley Product Group) | Product leadership, empowered teams | 2-3 days | $2,500-$3,500 | ⭐⭐⭐⭐⭐ | Product Directors, VPs, CPOs |
| **Certified Product Manager (CPM)** | AIPMM | Product lifecycle, strategy, development | Self-paced (3-6 months) | $499 (exam fee) | ⭐⭐⭐ | Mid-level PMs seeking credential |
#### Certification Comparison Matrix
| Dimension | Pragmatic Institute | Product School | Reforge | SVPG | AIPMM |
|------|------|------|------|------|------|
| **B2B Focus** | Strong (built for B2B) | General | Strong (B2B + B2C) | Strong (B2B + B2C) | General |
| **Instructor Quality** | Industry practitioners | Product leaders | Top-tier PM leaders | Marty Cagan & partners | Varies |
| **Community Access** | Strong alumni network | Strong alumni network | Elite peer community | Limited | Limited |
| **Certificate Validity** | Lifetime | Lifetime | No formal cert (skill-based) | No formal cert | 3 years (renewal required) |
| **Online/Remote** | Both available | Online only | Online only | In-person primarily | Online only |
| **Best ROI For** | Structured B2B methodology | Career transition | Advanced strategy skills | Leadership transformation | Budget-friendly credential |
---
### Global Customer Success Maturity Model
#### 4 Stages of CS Maturity
| Stage | Name | Characteristics | Key Activities | Technology Stack |
|------|------|------|------|------|
| **Stage 1: Reactive** | Firefighting | Respond to tickets, no proactive outreach, CS = support | Ticket resolution, basic onboarding | Help desk, basic CRM |
| **Stage 2: Proactive** | Structured Engagement | Scheduled check-ins, health score basics, playbooks defined | QBRs, health monitoring, renewal management | CSP (Gainsight/Totango), NPS tools |
| **Stage 3: Predictive** | Data-Driven CS | Predictive churn models, automated playbooks, scaled CS | Risk prediction, digital-led engagement, expansion identification | AI/ML models, product analytics, automation |
| **Stage 4: Prescriptive** | Outcome-as-a-Service | CS drives product roadmap, value benchmarking, customer advisory | Value realization tracking, industry benchmarking, customer community | Advanced analytics, community platforms, integrated CSP |
#### Key CS Metrics by Maturity Stage
| Metric | Stage 1 Target | Stage 2 Target | Stage 3 Target | Stage 4 Target | Industry Best-in-Class |
|------|------|------|------|------|------|
| **NRR (Net Revenue Retention)** | <90% | 90-100% | 100-120% | >120% | >130% |
| **GRR (Gross Revenue Retention)** | <80% | 80-85% | 85-92% | >92% | >95% |
| **NPS (Net Promoter Score)** | <20 | 20-40 | 40-60 | >60 | >70 |
| **CSAT (Customer Satisfaction)** | <80% | 80-90% | 90-95% | >95% | >97% |
| **CES (Customer Effort Score)** | >4.0 | 3.0-4.0 | 2.0-3.0 | <2.0 | <1.5 |
| **Time-to-Value (TTV)** | >30 days | 15-30 days | 7-15 days | <7 days | <3 days |
| **Churn Rate (Annual)** | >15% | 10-15% | 5-10% | <5% | <3% |
| **Expansion Rate** | <10% | 10-15% | 15-25% | >25% | >30% |
#### Regional CS Maturity Benchmarks
| Region | Dominant Stage | CS Team Ratio (CSM:Customers) | Average CSM Salary | Key Trend |
|------|------|------|------|------|
| **North America** | Stage 3 (Predictive) | 1:20-1:50 | $80K-$130K | AI-driven digital CS, scaled CS models |
| **Europe** | Stage 2-3 (Proactive-Predictive) | 1:30-1:80 | €55K-€90K | GDPR-compliant CS tech, local-language CS |
| **APAC** | Stage 1-2 (Reactive-Proactive) | 1:50-1:150 | $30K-$70K | Rapidly maturing, high-growth CS hiring |
| **Latin America** | Stage 1 (Reactive) | 1:100-1:200 | $15K-$35K | Building CS foundations, education focus |
| **Middle East** | Stage 1-2 (Reactive-Proactive) | 1:50-1:100 | $40K-$80K | High-touch for enterprise, digital for SMB |
---
### Global B2B SaaS Trends
#### 1. Vertical SaaS Growth
Horizontal SaaS → Vertical SaaS shift accelerating:
- Vertical SaaS projected to grow 2x faster than horizontal (2024-2028)
- Key verticals: Healthcare, Legal, Construction, Logistics, Fintech
- Advantage: Deeper domain expertise, higher switching costs, better unit economics
- Challenge: Smaller TAM per vertical, requires domain-specific GTM
#### 2. AI-Native B2B Products
Key characteristics of AI-native B2B products:
- AI is the product, not a feature — built from the ground up on LLMs
- Examples: Harvey (legal AI), Sierra (customer service AI), Copy.ai (GTM AI)
- Shift from "AI-assisted" to "AI-first" workflows
- New moats: proprietary data, fine-tuned models, domain-specific evaluation
- 2025 prediction: 40%+ of new B2B SaaS startups will be AI-native (2025 prediction, under observation as of 2026-07)
- 2026 observation: AI-native B2B continues as a dominant startup theme with sustained VC and enterprise investment; precise adoption metrics pending updated industry benchmarks (observation added 2026-07)
#### 3. Usage-Based Pricing Adoption
Key trends:
- 70% of SaaS companies expected to offer usage-based pricing by 2026 (Gartner)
- Hybrid models (base + usage) growing fastest — 38% adoption (Paddle, formerly Profitwell, 2024 baseline, corrected 2026-07)
- AI/API products leading the shift (token-based, per-call pricing)
- Customer preference: 65% prefer paying for value received vs. seats
- Challenge: Revenue predictability — requires sophisticated forecasting
#### 4. PLG + SLG Hybrid Models
The "PLS" (Product-Led Sales) model is becoming the dominant GTM:
- 65% of B2B buyers prefer a hybrid experience (McKinsey)
- PLG for acquisition + SLG for expansion = best of both worlds
- Product usage data drives sales prioritization (PQA scoring)
- Sales-assisted PLG: sales intervenes only when product signals indicate readiness
- Key metric: PQA → Closed Won conversion rate
#### 5. API-First Products
API-first is becoming the default for B2B SaaS:
- API-first companies grow 1.5x faster than non-API-first (OpenView)
- Key characteristics: API is the product, documentation is the UX, developer experience is the moat
- Examples: Stripe, Twilio, Plaid, OpenAI
- Trend: "API-first" evolving into "API + App" — API for developers, App for business users
- Key metric: Time to First API Call (TTFC) — should be <5 minutes
---
### Regional GTM Strategy Playbooks
#### North America GTM
Primary Motion: PLG + Outbound Sales
- Start with self-serve free trial / freemium
- PQL scoring triggers sales outreach at key activation milestones
- Content marketing + SEO as primary inbound channels
- Product Hunt launch → VC network → enterprise upsell
- Key metric: Free → Paid conversion rate (target >5%)
- Typical sales cycle: 30-90 days (SMB), 3-6 months (Enterprise)
#### Europe GTM
Primary Motion: Inbound + Localized Sales
- GDPR compliance is table stakes — lead with data privacy
- Multi-language support required (DE, FR, ES, IT minimum)
- Local sales teams in key markets (London, Berlin, Paris, Amsterdam)
- Industry events (Web Summit, Slush, SaaStock) for brand building
- Partner channels more important than in US (resellers, SIs)
- Typical sales cycle: 45-120 days (longer procurement, compliance reviews)
#### APAC GTM
Primary Motion: Partner-Led + Local Sales
- Local partnerships essential — direct sales rarely works alone
- Country-by-country strategy (not "one APAC" approach):
- Japan: Local office + Japanese-language product + long relationship building
- Singapore: Regional HQ, English-first, hub for SEA expansion
- India: Price-sensitive, high-volume, local payment methods (UPI)
- Australia: Similar to US/UK, good test market for APAC
- South Korea: Local partner essential, high mobile adoption
- Local payment methods critical (PayNow, PayPay, UPI, etc.)
- Typical sales cycle: 60-180 days (relationship-driven)
#### Middle East GTM
Primary Motion: Enterprise Sales + Government Relations
- Government procurement is a major channel (Vision 2030/2071 projects)
- Local presence/sponsor often required (UAE: mainland license, KSA: RHQ program)
- Relationship-driven — C-suite connections matter more than product demos
- Arabic language support increasingly expected
- Key hubs: Dubai (regional HQ), Riyadh (government), Abu Dhabi (sovereign funds)
- Typical sales cycle: 6-18 months (enterprise/government)
#### LATAM GTM
Primary Motion: Product-Led + Localized Marketing
- Price sensitivity is high — regional pricing essential
- Portuguese (Brazil) and Spanish localization mandatory
- WhatsApp as business communication channel (not email)
- Local payment methods: PIX (Brazil), OXXO (Mexico), MercadoPago
- Brazil-first approach: largest market, then expand to Mexico, Colombia, Chile
- Typical sales cycle: 30-90 days (SMB), 3-9 months (Enterprise)
#### Africa GTM
Primary Motion: Mobile-First + Partner Ecosystem
- Mobile-first product design (not desktop-first)
- Local payment methods: M-Pesa (Kenya), mobile money across regions
- Partner with local telcos (Safaricom, MTN) for distribution
- Country-by-country approach: Nigeria (largest), Kenya (tech hub), South Africa (enterprise)
- Offline-capable features for connectivity challenges
- Typical sales cycle: 45-120 days (varies widely by country)
### Regional B2B PM Communities & Networks
| Region | Key Communities | Major Conferences | Local Resources |
|--------|----------------|-------------------|----------------|
| **North America** | Mind the Product (SF/NYC), Product Collective, ProductCamp | SaaStr Annual, Mind the Product SF, INDUSTRY | Lenny's Newsletter, Reforge, SVPG |
| **Europe** | Mind the Product (London/Berlin), ProductTank (30+ cities), Product People | SaaStock (Dublin), Web Summit (Lisbon), Slush (Helsinki) | Department of Product, Product Coalition |
| **APAC** | ProductTank (Singapore/Tokyo/Sydney/Bangalore), Product School APAC | SaaStr APAC, ProductCon, Tech in Asia | Product Management Festival APAC, local PM meetups |
| **Middle East** | ProductTank Dubai, Product Management MENA | GITEX (Dubai), LEAP (Riyadh), STEP Conference | Regional PM WhatsApp groups, LinkedIn communities |
| **LATAM** | ProductTank (São Paulo/Mexico City), PMs LATAM, Product Arena | RD Summit (Brazil), Latam Startups Conference | Product Management LATAM (LinkedIn), regional Slack communities |
| **Africa** | ProductTank (Lagos/Nairobi/Cape Town), African PM Network | Africa Tech Summit, Nigeria Tech Summit, SA Innovation Summit | Product Management Africa, local WhatsApp/Telegram groups |
---
## Copyright Notice
> **Author**: yinjianheng（殷健恒）
> **Contact**: email: yinjianheng@foxmail.com / wechat: YJH-yinjianheng
> **License**: Free and open-source, for personal use only
---
**Disclaimer**: This Skill is a personal open-source work, provided for personal learning, research, and non-commercial use only. Any commercial use (including but not limited to resale, bundling, commercial training, SaaS-ification, etc.) is strictly prohibited without the author's written authorization. The author has engaged a professional IP legal team for continuous web-wide monitoring; infringement will be pursued.
## Disclaimer
1. **Not Professional Advice**: The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice (including but not limited to legal advice, financial advice, technical decision advice). Users should consult qualified professionals before making any business or technical decisions.
2. **Information Accuracy**: While this Skill has made every effort to ensure the accuracy and timeliness of its content, it does not guarantee the completeness, accuracy, or applicability of all information. The product management field evolves rapidly, and some content may become outdated over time. Users should independently verify key information.
3. **Limitation of Liability**: To the maximum extent permitted by applicable law, the author assumes no liability for any direct, indirect, incidental, special, or consequential losses arising from the use of or reliance on the content of this Skill, including but not limited to business losses, data loss, system failures, or third-party claims.
4. **Third-Party Content**: The copyright of third-party frameworks, methodologies, tools, and standards referenced in this Skill (such as McKinsey, Paddle (formerly Profitwell), OpenView, etc.) belongs to their respective rights holders. References do not constitute any affiliation or endorsement relationship between the author and third-party rights holders.
5. **Usage Compliance**: Users should ensure that their use of this Skill complies with the laws and regulations of their country/region, industry standards, and internal corporate policies. Using this Skill for any illegal purpose or purpose contrary to public order and good morals is prohibited.
---
## Warm Reminder
> 💡 **Every PRD is the genetic code of the product.**
> Logic must be self-consistent, processes must be closed-loop, exceptions must be covered — users can feel all of these details.
> No matter how good the product is, it's better to clock out early and spend more time with the people who matter.
> —— yinjianheng（殷健恒）
