ogt-docs-define-business
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseOGT Docs - Define Business
OGT 文档 - 业务定义
Complete guide for creating business definition documents.
创建业务定义文档的完整指南。
Overview
概述
Business definitions establish the commercial and operational foundation of your product. They answer questions about money, users, markets, and constraints.
mermaid
mindmap
root((Business<br/>Definitions))
Pricing
Tiers
Features per tier
Limits
Billing cycles
Users
User types
Personas
Journeys
Permissions
Revenue
Revenue streams
Unit economics
Growth model
Market
Target market
Competitors
Positioning
Differentiation业务定义为你的产品奠定商业与运营基础,解答关于资金、用户、市场及约束条件的相关问题。
mermaid
mindmap
root((Business<br/>Definitions))
Pricing
Tiers
Features per tier
Limits
Billing cycles
Users
User types
Personas
Journeys
Permissions
Revenue
Revenue streams
Unit economics
Growth model
Market
Target market
Competitors
Positioning
DifferentiationWhen to Use This Skill
何时使用该技能
Use when defining:
ogt-docs-define-business- Pricing models and tiers
- User types and permissions
- Revenue models and streams
- Market positioning
- Customer personas
- Operational limits and quotas
- Business rules and constraints
在定义以下内容时使用 :
ogt-docs-define-business- 定价模型与层级
- 用户类型与权限
- 收入模型与收入流
- 市场定位
- 客户角色
- 运营限制与配额
- 业务规则与约束条件
Folder Structure
文件夹结构
docs/definitions/business/
├── pricing_model/
│ ├── definition.md # Core pricing philosophy
│ ├── tiers.md # Tier breakdown
│ ├── limits.md # Usage limits per tier
│ ├── billing.md # Billing cycles and rules
│ ├── enterprise.md # Enterprise/custom pricing
│ ├── .version
│ └── .approved_by_founder
│
├── user_types/
│ ├── definition.md # User type taxonomy
│ ├── free_user.md # Free tier user
│ ├── pro_user.md # Pro tier user
│ ├── team_admin.md # Team administrator
│ ├── enterprise_admin.md # Enterprise administrator
│ ├── permissions.md # Permission matrix
│ └── .version
│
├── customer_personas/
│ ├── definition.md # Persona framework
│ ├── indie_developer.md # Persona: Indie dev
│ ├── startup_founder.md # Persona: Founder
│ ├── enterprise_buyer.md # Persona: Enterprise
│ ├── hobbyist.md # Persona: Hobbyist
│ └── .version
│
├── revenue_model/
│ ├── definition.md # Revenue philosophy
│ ├── streams.md # Revenue streams breakdown
│ ├── unit_economics.md # CAC, LTV, margins
│ ├── growth_model.md # Growth projections
│ └── .version
│
├── market_position/
│ ├── definition.md # Market positioning
│ ├── target_market.md # Target market definition
│ ├── competitors.md # Competitive analysis
│ ├── differentiation.md # Unique value proposition
│ └── .version
│
└── operational_limits/
├── definition.md # Limits philosophy
├── api_limits.md # API rate limits
├── storage_limits.md # Storage quotas
├── feature_limits.md # Feature usage limits
└── .versiondocs/definitions/business/
├── pricing_model/
│ ├── definition.md # 核心定价理念
│ ├── tiers.md # 层级细分
│ ├── limits.md # 各层级使用限制
│ ├── billing.md # 计费周期与规则
│ ├── enterprise.md # 企业/定制定价
│ ├── .version
│ └── .approved_by_founder
│
├── user_types/
│ ├── definition.md # 用户类型分类
│ ├── free_user.md # 免费层级用户
│ ├── pro_user.md # Pro层级用户
│ ├── team_admin.md # 团队管理员
│ ├── enterprise_admin.md # 企业管理员
│ ├── permissions.md # 权限矩阵
│ └── .version
│
├── customer_personas/
│ ├── definition.md # 用户角色框架
│ ├── indie_developer.md # 角色:独立开发者
│ ├── startup_founder.md # 角色:创业者
│ ├── enterprise_buyer.md # 角色:企业采购者
│ ├── hobbyist.md # 角色:爱好者
│ └── .version
│
├── revenue_model/
│ ├── definition.md # 收入理念
│ ├── streams.md # 收入流细分
│ ├── unit_economics.md # CAC、LTV、利润率
│ ├── growth_model.md # 增长预测
│ └── .version
│
├── market_position/
│ ├── definition.md # 市场定位
│ ├── target_market.md # 目标市场定义
│ ├── competitors.md # 竞品分析
│ ├── differentiation.md # 独特价值主张
│ └── .version
│
└── operational_limits/
├── definition.md # 限制理念
├── api_limits.md # API调用频率限制
├── storage_limits.md # 存储配额
├── feature_limits.md # 功能使用限制
└── .versionBusiness Definition Types
业务定义类型
1. Pricing Model
1. 定价模型
Defines how you charge for your product.
定义产品的收费方式。
Example: pricing_model/
示例:pricing_model/
pricing_model/
├── definition.md
├── tiers.md
├── limits.md
├── billing.md
├── enterprise.md
├── .version
└── .approved_by_founderpricing_model/
├── definition.md
├── tiers.md
├── limits.md
├── billing.md
├── enterprise.md
├── .version
└── .approved_by_founderdefinition.md
definition.md
markdown
undefinedmarkdown
undefinedDefinition: Pricing Model
定义:定价模型
Overview
概述
{Product} uses a freemium pricing model with usage-based scaling.
Free tier provides core functionality with limits. Paid tiers unlock
higher limits and premium features. Enterprise tier offers custom limits
and dedicated support.
{Product} 采用Freemium定价模型,并基于使用量进行扩展。免费层级提供带有限制的核心功能,付费层级解锁更高限制与高级功能,企业层级提供定制限制与专属支持。
Philosophy
理念
- Value-first: Free tier must be genuinely useful, not crippled
- Clear upgrade path: Users know exactly what they get by upgrading
- No surprise charges: Limits are soft (warnings) before hard (blocks)
- Fair for all sizes: Pricing scales with value received
- 价值优先:免费层级必须真正实用,而非功能残缺
- 清晰升级路径:用户明确知晓升级后可获得的权益
- 无隐形收费:在触发硬性限制(阻断)前会先发出软性限制(警告)
- 适配各类规模:定价随用户获得的价值同步增长
Pricing Strategy
定价策略
| Strategy Element | Approach |
|---|---|
| Model | Freemium + Usage-based |
| Anchor | Pro tier ($X/mo) is the anchor |
| Free tier goal | Conversion to Pro within 30 days |
| Enterprise goal | Predictable revenue, long contracts |
| 策略要素 | 实施方式 |
|---|---|
| 模型 | Freemium + 基于使用量计费 |
| 锚点 | Pro层级(每月$X美元)为核心锚点 |
| 免费层级目标 | 30天内转化为Pro层级用户 |
| 企业层级目标 | 可预测收入、长期合作合同 |
Key Decisions
关键决策
- Why freemium? Lower barrier to entry, viral growth potential
- Why usage-based? Aligns cost with value, fair scaling
- Why not per-seat? Product value is per-project, not per-person
- 为何选择Freemium? 降低准入门槛,具备病毒式增长潜力
- 为何基于使用量计费? 成本与价值对齐,实现公平扩容
- 为何不按席位计费? 产品价值基于项目而非个人
Success Metrics
成功指标
- Free → Pro conversion rate: Target X%
- Pro → Enterprise conversion rate: Target Y%
- Monthly churn rate: Target < Z%
- 免费→Pro转化率:目标X%
- Pro→企业层级转化率:目标Y%
- 月度流失率:目标<Z%
Related Definitions
相关定义
- User Types
- Operational Limits
- Revenue Model
undefined- 用户类型
- 运营限制
- 收入模型
undefinedtiers.md
tiers.md
markdown
undefinedmarkdown
undefinedPricing Tiers
定价层级
Tier Overview
层级概述
| Tier | Price | Target User | Core Value |
|---|---|---|---|
| Free | $0 | Hobbyists, evaluators | Try before buy |
| Pro | $X/mo | Indie devs, freelancers | Full feature access |
| Team | $Y/mo | Small teams | Collaboration features |
| Enterprise | Custom | Large orgs | Scale + support |
| 层级 | 价格 | 目标用户 | 核心价值 |
|---|---|---|---|
| Free | $0 | 爱好者、产品评估者 | 先试后买 |
| Pro | $X/月 | 独立开发者、自由职业者 | 完整功能访问权限 |
| Team | $Y/月 | 小型团队 | 协作功能 |
| Enterprise | 定制化 | 大型企业 | 扩容+专属支持 |
Free Tier
免费层级
Target User
目标用户
Hobbyists exploring the product, developers evaluating for future purchase.
探索产品的爱好者、评估未来采购可能性的开发者。
Included Features
包含功能
- Feature A (limited)
- Feature B (limited)
- Feature C (full)
- Community support only
- 功能A(受限)
- 功能B(受限)
- 功能C(完整)
- 仅社区支持
Limits
限制
| Resource | Limit |
|---|---|
| Projects | 3 |
| API calls/day | 100 |
| Storage | 100MB |
| Team members | 1 (solo only) |
| 资源 | 限制 |
|---|---|
| 项目数量 | 3 |
| 每日API调用量 | 100 |
| 存储空间 | 100MB |
| 团队成员数 | 1(仅单人使用) |
Upgrade Triggers
升级触发点
User should consider upgrading when:
- Hitting project limit
- Needing collaboration
- Requiring priority support
当用户出现以下情况时,应考虑升级:
- 达到项目数量限制
- 需要协作功能
- 需要优先支持
Pro Tier
Pro层级
Price
价格
$X/month (billed monthly)
$X×10/year (billed annually, 2 months free)
每月$X美元(按月计费)
每年$X×10美元(按年计费,立享2个月免费)
Target User
目标用户
Independent developers, freelancers, small projects.
独立开发者、自由职业者、小型项目团队。
Included Features
包含功能
- All Free features (unlimited)
- Feature D
- Feature E
- Feature F
- Email support (48h response)
- 所有免费层级功能(无限制)
- 功能D
- 功能E
- 功能F
- 邮件支持(48小时响应)
Limits
限制
| Resource | Limit |
|---|---|
| Projects | 20 |
| API calls/day | 10,000 |
| Storage | 10GB |
| Team members | 1 (solo only) |
| 资源 | 限制 |
|---|---|
| 项目数量 | 20 |
| 每日API调用量 | 10,000 |
| 存储空间 | 10GB |
| 团队成员数 | 1(仅单人使用) |
Upgrade Triggers
升级触发点
User should consider upgrading when:
- Needing team collaboration
- Hitting API limits
- Requiring faster support
当用户出现以下情况时,应考虑升级:
- 需要团队协作
- 达到API调用限制
- 需要更快的支持响应
Team Tier
Team层级
Price
价格
$Y/month base + $Z/member/month
Billed monthly or annually (2 months free)
基础费用每月$Y美元 + 每位成员每月$Z美元
支持按月或按年计费(按年立享2个月免费)
Target User
目标用户
Small teams (2-20 people) needing collaboration.
需要协作功能的小型团队(2-20人)。
Included Features
包含功能
- All Pro features
- Team collaboration
- Shared projects
- Role-based permissions
- Priority support (24h response)
- 所有Pro层级功能
- 团队协作
- 项目共享
- 基于角色的权限
- 优先支持(24小时响应)
Limits
限制
| Resource | Limit |
|---|---|
| Projects | 100 |
| API calls/day | 100,000 |
| Storage | 100GB |
| Team members | 20 |
| 资源 | 限制 |
|---|---|
| 项目数量 | 100 |
| 每日API调用量 | 100,000 |
| 存储空间 | 100GB |
| 团队成员数 | 20 |
Upgrade Triggers
升级触发点
Team should consider upgrading when:
- Exceeding 20 members
- Needing SSO/SAML
- Requiring dedicated support
- Compliance requirements
当团队出现以下情况时,应考虑升级:
- 成员数量超过20人
- 需要SSO/SAML单点登录
- 需要专属支持
- 合规要求
Enterprise Tier
企业层级
Price
价格
Custom pricing based on:
- Number of users
- Usage volume
- Support requirements
- Compliance needs
基于以下因素定制定价:
- 用户数量
- 使用量
- 支持需求
- 合规需求
Target User
目标用户
Large organizations, regulated industries, high-volume users.
大型企业、受监管行业、高使用量用户。
Included Features
包含功能
- All Team features
- SSO/SAML integration
- Custom integrations
- Dedicated account manager
- SLA guarantees
- Compliance certifications
- Custom contracts
- 所有Team层级功能
- SSO/SAML集成
- 定制集成
- 专属客户经理
- SLA服务水平保障
- 合规认证
- 定制合同
Limits
限制
| Resource | Limit |
|---|---|
| Projects | Unlimited |
| API calls/day | Custom |
| Storage | Custom |
| Team members | Unlimited |
| 资源 | 限制 |
|---|---|
| 项目数量 | 无限制 |
| 每日API调用量 | 定制化 |
| 存储空间 | 定制化 |
| 团队成员数 | 无限制 |
Sales Process
销售流程
- Contact sales
- Discovery call
- Custom proposal
- Security review
- Contract negotiation
- Onboarding
undefined- 联系销售团队
- 需求调研沟通
- 定制方案提案
- 安全审核
- 合同协商
- 上线部署
undefinedlimits.md
limits.md
markdown
undefinedmarkdown
undefinedUsage Limits
使用限制
Limit Philosophy
限制理念
- Limits exist to ensure fair usage and system stability
- Soft limits warn users before blocking
- Hard limits block with clear upgrade path
- Limits should feel generous for the tier's target user
- 设置限制是为了确保公平使用与系统稳定性
- 软性限制会先向用户发出警告,而非直接阻断
- 硬性限制会阻断操作,并提供清晰的升级路径
- 对于各层级的目标用户而言,限制应足够宽松
Limit Types
限制类型
Soft Limits
软性限制
User is warned but not blocked. Exceeding triggers:
- In-app notification
- Email warning
- Usage dashboard highlight
用户会收到警告但不会被阻断。触发时会:
- 应用内通知
- 邮件警告
- 使用仪表盘高亮提示
Hard Limits
硬性限制
User is blocked from the action. Exceeding shows:
- Clear error message
- Current usage vs limit
- Upgrade CTA
用户的操作会被阻断。触发时会显示:
- 清晰的错误提示
- 当前使用量与限制对比
- 升级引导
Limits by Resource
各资源限制
Projects
项目数量
| Tier | Soft Limit | Hard Limit |
|---|---|---|
| Free | 2 | 3 |
| Pro | 15 | 20 |
| Team | 80 | 100 |
| Enterprise | N/A | Unlimited |
When exceeded:
- Cannot create new projects
- Can still access existing projects
- Must delete or archive to create new
| 层级 | 软性限制 | 硬性限制 |
|---|---|---|
| Free | 2 | 3 |
| Pro | 15 | 20 |
| Team | 80 | 100 |
| Enterprise | 不适用 | 无限制 |
触发后影响:
- 无法创建新项目
- 仍可访问现有项目
- 需删除或归档旧项目才能创建新项目
API Calls (per day)
每日API调用量
| Tier | Soft Limit | Hard Limit | Burst Limit |
|---|---|---|---|
| Free | 80 | 100 | 10/min |
| Pro | 8,000 | 10,000 | 100/min |
| Team | 80,000 | 100,000 | 500/min |
| Enterprise | Custom | Custom | Custom |
When exceeded:
- Returns 429 Too Many Requests
- Retry-After header indicates reset time
- Daily limit resets at midnight UTC
| 层级 | 软性限制 | 硬性限制 | 突发限制 |
|---|---|---|---|
| Free | 80 | 100 | 10次/分钟 |
| Pro | 8,000 | 10,000 | 100次/分钟 |
| Team | 80,000 | 100,000 | 500次/分钟 |
| Enterprise | 定制化 | 定制化 | 定制化 |
触发后影响:
- 返回429请求过多错误
- Retry-After响应头会提示重置时间
- 每日限制在UTC时区午夜重置
Storage
存储空间
| Tier | Soft Limit | Hard Limit |
|---|---|---|
| Free | 80MB | 100MB |
| Pro | 8GB | 10GB |
| Team | 80GB | 100GB |
| Enterprise | Custom | Custom |
When exceeded:
- Cannot upload new files
- Can still access existing files
- Must delete files or upgrade
| 层级 | 软性限制 | 硬性限制 |
|---|---|---|
| Free | 80MB | 100MB |
| Pro | 8GB | 10GB |
| Team | 80GB | 100GB |
| Enterprise | 定制化 | 定制化 |
触发后影响:
- 无法上传新文件
- 仍可访问现有文件
- 需删除文件或升级层级
Team Members
团队成员数
| Tier | Limit |
|---|---|
| Free | 1 (no teams) |
| Pro | 1 (no teams) |
| Team | 20 |
| Enterprise | Unlimited |
When exceeded:
- Cannot invite new members
- Existing members unaffected
- Must remove members or upgrade
| 层级 | 限制 |
|---|---|
| Free | 1(不支持团队) |
| Pro | 1(不支持团队) |
| Team | 20 |
| Enterprise | 无限制 |
触发后影响:
- 无法邀请新成员
- 现有成员不受影响
- 需移除成员或升级层级
Overage Handling
超额使用处理
Free Tier
免费层级
No overages. Hard block at limit.
不支持超额使用,达到硬性限制后直接阻断。
Pro Tier
Pro层级
No overages. Hard block at limit with upgrade prompt.
不支持超额使用,达到硬性限制后触发升级提示并阻断。
Team Tier
Team层级
Optional overage billing:
- API calls: $X per 10,000 over limit
- Storage: $Y per GB over limit
- Must opt-in to overage billing
可选超额计费:
- API调用:每超额10,000次收费$X美元
- 存储空间:每超额1GB收费$Y美元
- 需主动开启超额计费功能
Enterprise Tier
企业层级
Custom overage terms in contract.
undefined根据合同定制超额使用条款。
undefinedbilling.md
billing.md
markdown
undefinedmarkdown
undefinedBilling Rules
计费规则
Billing Cycles
计费周期
Monthly Billing
按月计费
- Charged on signup date each month
- Example: Sign up Jan 15 → charged Feb 15, Mar 15, etc.
- Pro-rated for mid-cycle changes
- 每月在注册日期扣费
- 示例:1月15日注册 → 2月15日、3月15日等日期扣费
- 周期内变更套餐会按比例折算费用
Annual Billing
按年计费
- Charged on signup date each year
- 2 months free (pay for 10, get 12)
- No pro-rating for downgrades
- Pro-rated upgrades
- 每年在注册日期扣费
- 立享2个月免费(支付10个月费用,使用12个月)
- 降级不按比例退费
- 升级按比例折算费用
Payment Methods
支付方式
Accepted
支持的方式
- Credit/debit cards (Visa, Mastercard, Amex)
- PayPal (Pro and above)
- Wire transfer (Enterprise only)
- Purchase orders (Enterprise only)
- 信用卡/借记卡(Visa、Mastercard、Amex)
- PayPal(仅Pro及以上层级)
- 电汇(仅企业层级)
- 采购订单(仅企业层级)
Failed Payments
支付失败处理
- First failure: Retry in 24 hours, email notification
- Second failure: Retry in 48 hours, in-app warning
- Third failure: Account downgraded to Free after 7 days grace
- Grace period: Full access for 7 days to update payment
- 首次失败:24小时后重试,发送邮件通知
- 二次失败:48小时后重试,应用内发出警告
- 三次失败:7天宽限期后账户降级为免费层级
- 宽限期:7天内可正常访问全部功能,用于更新支付信息
Upgrades
套餐升级
Free → Pro
免费→Pro
- Immediate access to Pro features
- First charge: Full month
- Billing date: Day of upgrade
- 立即获得Pro层级全部功能
- 首次扣费:全额月费
- 计费日期:升级当日
Pro → Team
Pro→Team
- Immediate access to Team features
- Pro-rated credit for remaining Pro period
- New billing date: Day of upgrade
- 立即获得Team层级全部功能
- 剩余Pro周期按比例折算为信用额度
- 新计费日期:升级当日
Any → Enterprise
任意套餐→企业
- Custom contract required
- Migration assistance provided
- Billing per contract terms
- 需要定制合同
- 提供迁移协助
- 按合同条款计费
Downgrades
套餐降级
Pro → Free
Pro→免费
- Effective at end of current billing period
- Data retained for 30 days after downgrade
- Over-limit resources become read-only
- 生效时间:当前计费周期结束时
- 降级后数据保留30天
- 超出免费层级限制的资源变为只读
Team → Pro
Team→Pro
- Effective at end of current billing period
- Must remove team members first
- Team features disabled at period end
- 生效时间:当前计费周期结束时
- 需先移除多余团队成员
- 周期结束后团队功能禁用
Enterprise → Lower
企业→低层级
- Per contract terms
- Typically 30-day notice required
- Migration assistance provided
- 按合同条款执行
- 通常需要提前30天通知
- 提供迁移协助
Refunds
退款政策
Policy
规则
- 14-day money-back guarantee for first payment
- No refunds for renewals
- No partial refunds for downgrades
- Enterprise: Per contract terms
- 首次支付享受14天无理由退款保障
- 续费不支持退款
- 降级不支持部分退款
- 企业层级:按合同条款执行
Process
流程
- Request via support
- Review within 48 hours
- Refund processed within 5-7 business days
---- 通过支持渠道提交申请
- 48小时内完成审核
- 5-7个工作日内完成退款处理
---2. User Types
2. 用户类型
Defines the different types of users in your system.
定义系统中的不同用户类型。
Example: user_types/
示例:user_types/
user_types/
├── definition.md
├── free_user.md
├── pro_user.md
├── team_admin.md
├── team_member.md
├── enterprise_admin.md
├── permissions.md
└── .versionuser_types/
├── definition.md
├── free_user.md
├── pro_user.md
├── team_admin.md
├── team_member.md
├── enterprise_admin.md
├── permissions.md
└── .versiondefinition.md
definition.md
markdown
undefinedmarkdown
undefinedDefinition: User Types
定义:用户类型
Overview
概述
{Product} has distinct user types based on subscription tier and role
within teams. User type determines feature access, limits, and permissions.
{Product} 根据订阅层级与团队内角色划分不同的用户类型,用户类型决定了功能访问权限、限制与操作权限。
User Type Hierarchy
用户类型层级
mermaid
flowchart TD
subgraph Individual ["Individual Users"]
F[Free User]
P[Pro User]
end
subgraph Team ["Team Users"]
TA[Team Admin]
TM[Team Member]
TV[Team Viewer]
end
subgraph Enterprise ["Enterprise Users"]
EA[Enterprise Admin]
EM[Enterprise Member]
EV[Enterprise Viewer]
end
F -->|Upgrade| P
P -->|Create Team| TA
TA -->|Invite| TM
TA -->|Invite| TV
TA -->|Upgrade| EA
EA -->|Invite| EM
EA -->|Invite| EVundefinedmermaid
flowchart TD
subgraph Individual ["个人用户"]
F[Free User]
P[Pro User]
end
subgraph Team ["团队用户"]
TA[Team Admin]
TM[Team Member]
TV[Team Viewer]
end
subgraph Enterprise ["企业用户"]
EA[Enterprise Admin]
EM[Enterprise Member]
EV[Enterprise Viewer]
end
F -->|Upgrade| P
P -->|Create Team| TA
TA -->|Invite| TM
TA -->|Invite| TV
TA -->|Upgrade| EA
EA -->|Invite| EM
EA -->|Invite| EVundefinedUser Type Matrix
用户类型矩阵
| Type | Tier | Role | Can Create | Can Invite |
|---|---|---|---|---|
| Free User | Free | Owner | Projects (limited) | No |
| Pro User | Pro | Owner | Projects | No |
| Team Admin | Team | Admin | Projects, Members | Yes |
| Team Member | Team | Editor | Projects | No |
| Team Viewer | Team | Viewer | Nothing | No |
| Enterprise Admin | Enterprise | Admin | Everything | Yes |
| Enterprise Member | Enterprise | Editor | Projects | No |
| Enterprise Viewer | Enterprise | Viewer | Nothing | No |
| 类型 | 层级 | 角色 | 可创建内容 | 可邀请成员 |
|---|---|---|---|---|
| Free User | Free | 所有者 | 项目(受限) | 否 |
| Pro User | Pro | 所有者 | 项目 | 否 |
| Team Admin | Team | 管理员 | 项目、团队成员 | 是 |
| Team Member | Team | 编辑者 | 项目 | 否 |
| Team Viewer | Team | 查看者 | 无 | 否 |
| Enterprise Admin | Enterprise | 管理员 | 全部内容 | 是 |
| Enterprise Member | Enterprise | 编辑者 | 项目 | 否 |
| Enterprise Viewer | Enterprise | 查看者 | 无 | 否 |
Key Concepts
核心概念
Owner vs Admin vs Member
所有者 vs 管理员 vs 成员
- Owner: Created/purchased the account, billing contact
- Admin: Can manage users and settings, may not be owner
- Member: Can use features, cannot manage
- 所有者:创建/购买账户的用户,负责账单联系
- 管理员:可管理用户与设置,不一定是所有者
- 成员:可使用功能,无法进行管理操作
Viewer Role
查看者角色
Read-only access for stakeholders who need visibility but not edit access.
为需要查看权限但无需编辑权限的利益相关者提供只读访问。
Related Definitions
相关定义
- Pricing Model
- Permissions
undefined- 定价模型
- 权限
undefinedfree_user.md
free_user.md
markdown
undefinedmarkdown
undefinedUser Type: Free User
用户类型:Free User
Definition
定义
Individual user on the Free tier with limited access to core features.
免费层级的个人用户,对核心功能的访问受限。
Characteristics
特征
- Individual account (no team)
- Limited project count
- Limited API calls
- Community support only
- No collaboration features
- 个人账户(不支持团队)
- 项目数量受限
- API调用受限
- 仅社区支持
- 无协作功能
Permissions
权限
| Permission | Allowed |
|---|---|
| Create projects | Yes (up to limit) |
| Edit own projects | Yes |
| Delete own projects | Yes |
| Invite others | No |
| Access API | Yes (limited) |
| Export data | Yes |
| Priority support | No |
| 权限 | 是否允许 |
|---|---|
| 创建项目 | 是(最多限制数量) |
| 编辑自有项目 | 是 |
| 删除自有项目 | 是 |
| 邀请他人 | 否 |
| 访问API | 是(受限) |
| 导出数据 | 是 |
| 优先支持 | 否 |
Limits
限制
See Pricing Limits - Free Tier
查看定价限制 - 免费层级
Upgrade Path
升级路径
Free User → Pro User (upgrade subscription)
Free User → Pro User(升级订阅套餐)
Identification
类型标识
typescript
interface FreeUser {
type: 'free';
tier: 'free';
role: 'owner';
teamId: null;
}typescript
interface FreeUser {
type: 'free';
tier: 'free';
role: 'owner';
teamId: null;
}User Journey
用户旅程
- Sign up (email or OAuth)
- Onboarding flow
- Create first project
- Hit limits → Upgrade prompt
- Convert to Pro or continue with limits
undefined- 注册(邮箱或OAuth授权)
- 引导流程
- 创建首个项目
- 达到限制 → 升级提示
- 转化为Pro用户或继续使用受限功能
undefinedpermissions.md
permissions.md
markdown
undefinedmarkdown
undefinedUser Permissions Matrix
用户权限矩阵
Permission Categories
权限分类
Project Permissions
项目权限
| Permission | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| Create project | ✅ | ✅ | ✅ | ✅ | ❌ |
| View project | ✅ | ✅ | ✅ | ✅ | ✅ |
| Edit project | ✅ | ✅ | ✅ | ✅ | ❌ |
| Delete project | ✅ | ✅ | ✅ | ❌ | ❌ |
| Share project | ❌ | ❌ | ✅ | ❌ | ❌ |
| Transfer project | ❌ | ❌ | ✅ | ❌ | ❌ |
| 权限 | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| 创建项目 | ✅ | ✅ | ✅ | ✅ | ❌ |
| 查看项目 | ✅ | ✅ | ✅ | ✅ | ✅ |
| 编辑项目 | ✅ | ✅ | ✅ | ✅ | ❌ |
| 删除项目 | ✅ | ✅ | ✅ | ❌ | ❌ |
| 分享项目 | ❌ | ❌ | ✅ | ❌ | ❌ |
| 转移项目 | ❌ | ❌ | ✅ | ❌ | ❌ |
Team Permissions
团队权限
| Permission | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| Create team | ❌ | ❌ | ✅ | ❌ | ❌ |
| Invite member | ❌ | ❌ | ✅ | ❌ | ❌ |
| Remove member | ❌ | ❌ | ✅ | ❌ | ❌ |
| Change roles | ❌ | ❌ | ✅ | ❌ | ❌ |
| View team | ❌ | ❌ | ✅ | ✅ | ✅ |
| 权限 | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| 创建团队 | ❌ | ❌ | ✅ | ❌ | ❌ |
| 邀请成员 | ❌ | ❌ | ✅ | ❌ | ❌ |
| 移除成员 | ❌ | ❌ | ✅ | ❌ | ❌ |
| 变更角色 | ❌ | ❌ | ✅ | ❌ | ❌ |
| 查看团队 | ❌ | ❌ | ✅ | ✅ | ✅ |
Billing Permissions
计费权限
| Permission | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| View billing | ✅ | ✅ | ✅ | ❌ | ❌ |
| Update payment | ✅ | ✅ | ✅ | ❌ | ❌ |
| Change plan | ✅ | ✅ | ✅ | ❌ | ❌ |
| View invoices | ✅ | ✅ | ✅ | ❌ | ❌ |
| 权限 | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| 查看账单 | ✅ | ✅ | ✅ | ❌ | ❌ |
| 更新支付方式 | ✅ | ✅ | ✅ | ❌ | ❌ |
| 变更套餐 | ✅ | ✅ | ✅ | ❌ | ❌ |
| 查看发票 | ✅ | ✅ | ✅ | ❌ | ❌ |
API Permissions
API权限
| Permission | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| Generate API key | ✅ | ✅ | ✅ | ✅ | ❌ |
| Revoke API key | ✅ | ✅ | ✅ | Own only | ❌ |
| View API usage | ✅ | ✅ | ✅ | Own only | ❌ |
| 权限 | Free | Pro | Team Admin | Team Member | Team Viewer |
|---|---|---|---|---|---|
| 生成API密钥 | ✅ | ✅ | ✅ | ✅ | ❌ |
| 撤销API密钥 | ✅ | ✅ | ✅ | 仅自有密钥 | ❌ |
| 查看API使用情况 | ✅ | ✅ | ✅ | 仅自有数据 | ❌ |
Permission Inheritance
权限继承
- Team Members inherit all Viewer permissions
- Team Admins inherit all Member permissions
- Enterprise users follow same hierarchy with additional enterprise permissions
---- Team Member继承所有Team Viewer的权限
- Team Admin继承所有Team Member的权限
- 企业用户遵循相同层级结构,并拥有额外企业权限
---3. Revenue Model
3. 收入模型
Defines how your business makes money.
定义业务的盈利方式。
Example: revenue_model/
示例:revenue_model/
revenue_model/
├── definition.md
├── streams.md
├── unit_economics.md
├── growth_model.md
└── .versionrevenue_model/
├── definition.md
├── streams.md
├── unit_economics.md
├── growth_model.md
└── .versiondefinition.md
definition.md
markdown
undefinedmarkdown
undefinedDefinition: Revenue Model
定义:收入模型
Overview
概述
{Product} generates revenue through a combination of subscription fees
and usage-based charges. Primary revenue comes from Pro and Team
subscriptions with high-value Enterprise contracts providing stability.
{Product} 通过订阅费用与基于使用量的收费组合实现盈利,主要收入来自Pro与Team层级订阅,高价值的企业合同提供收入稳定性。
Revenue Philosophy
收入理念
- Sustainable: Revenue must cover costs with margin for growth
- Aligned: Revenue grows when customers get more value
- Predictable: Subscription base provides predictable MRR
- Scalable: Usage-based components scale with customer success
- 可持续性:收入必须覆盖成本并留有增长空间
- 一致性:收入随客户获得的价值同步增长
- 可预测性:订阅用户群提供可预测的月度经常性收入(MRR)
- 可扩展性:基于使用量的计费组件随客户成功同步增长
Revenue Mix Target
收入结构目标
| Stream | % of Revenue | Rationale |
|---|---|---|
| Pro subscriptions | 40% | Volume, predictable |
| Team subscriptions | 35% | Higher ARPU, lower churn |
| Enterprise contracts | 20% | High value, annual |
| Usage overage | 5% | Aligned with value |
| 收入流 | 收入占比 | 依据 |
|---|---|---|
| Pro层级订阅 | 40% | 用户基数大、收入可预测 |
| Team层级订阅 | 35% | 每用户平均收入(ARPU)更高、流失率更低 |
| 企业合同 | 20% | 高价值、年度合同 |
| 超额使用收费 | 5% | 与客户获得的价值对齐 |
Key Metrics
核心指标
- MRR (Monthly Recurring Revenue)
- ARR (Annual Recurring Revenue)
- ARPU (Average Revenue Per User)
- Net Revenue Retention
- Gross Margin
- MRR(月度经常性收入)
- ARR(年度经常性收入)
- ARPU(每用户平均收入)
- 净收入留存率
- 毛利率
Related Definitions
相关定义
- Pricing Model
- Unit Economics
undefined- 定价模型
- 单位经济效益
undefinedunit_economics.md
unit_economics.md
markdown
undefinedmarkdown
undefinedUnit Economics
单位经济效益
Customer Acquisition Cost (CAC)
客户获取成本(CAC)
Definition
定义
Total cost to acquire a new paying customer.
获取一位新付费客户的总成本。
Calculation
计算公式
CAC = (Marketing Spend + Sales Spend) / New Customers Acquired
CAC = (营销支出 + 销售支出) / 新增付费客户数
Targets by Tier
各层级目标
| Tier | Target CAC | Acceptable Range |
|---|---|---|
| Pro | $X | $X-Y |
| Team | $Y | $Y-Z |
| Enterprise | $Z | $Z-W |
| 层级 | 目标CAC | 可接受范围 |
|---|---|---|
| Pro | $X | $X-Y |
| Team | $Y | $Y-Z |
| Enterprise | $Z | $Z-W |
CAC Components
CAC构成
| Component | % of CAC |
|---|---|
| Paid ads | 40% |
| Content marketing | 25% |
| Sales team | 20% |
| Events/conferences | 10% |
| Other | 5% |
| 构成部分 | 占CAC比例 |
|---|---|
| 付费广告 | 40% |
| 内容营销 | 25% |
| 销售团队 | 20% |
| 活动/会议 | 10% |
| 其他 | 5% |
Lifetime Value (LTV)
客户生命周期价值(LTV)
Definition
定义
Total revenue expected from a customer over their lifetime.
客户在整个合作周期内为企业带来的总收入预期。
Calculation
计算公式
LTV = ARPU × Gross Margin × (1 / Churn Rate)
LTV = ARPU × 毛利率 × (1 / 流失率)
Targets by Tier
各层级目标
| Tier | Target LTV | Calculation |
|---|---|---|
| Pro | $X | $A × B% × (1/C%) |
| Team | $Y | $D × E% × (1/F%) |
| Enterprise | $Z | $G × H% × (1/I%) |
| 层级 | 目标LTV | 计算方式 |
|---|---|---|
| Pro | $X | $A × B% × (1/C%) |
| Team | $Y | $D × E% × (1/F%) |
| Enterprise | $Z | $G × H% × (1/I%) |
LTV:CAC Ratio
LTV:CAC比率
Target
目标
LTV:CAC > 3:1 (healthy SaaS benchmark)
LTV:CAC > 3:1(健康SaaS行业基准)
Current by Tier
各层级当前数据
| Tier | LTV | CAC | Ratio | Status |
|---|---|---|---|---|
| Pro | $X | $Y | X:1 | ✅/⚠️/❌ |
| Team | $X | $Y | X:1 | ✅/⚠️/❌ |
| Enterprise | $X | $Y | X:1 | ✅/⚠️/❌ |
| 层级 | LTV | CAC | 比率 | 状态 |
|---|---|---|---|---|
| Pro | $X | $Y | X:1 | ✅/⚠️/❌ |
| Team | $X | $Y | X:1 | ✅/⚠️/❌ |
| Enterprise | $X | $Y | X:1 | ✅/⚠️/❌ |
Payback Period
投资回报周期
Definition
定义
Months to recover CAC from a customer.
从客户身上收回CAC所需的月数。
Calculation
计算公式
Payback Period = CAC / (ARPU × Gross Margin)
投资回报周期 = CAC / (ARPU × 毛利率)
Target
目标
< 12 months for Pro
< 18 months for Team
< 24 months for Enterprise
Pro层级<12个月
Team层级<18个月
Enterprise层级<24个月
Gross Margin
毛利率
Definition
定义
Revenue minus cost of goods sold (COGS).
收入减去销货成本(COGS)后的比率。
Calculation
计算公式
Gross Margin = (Revenue - COGS) / Revenue × 100
毛利率 = (收入 - COGS) / 收入 × 100
Target
目标
80% (typical for SaaS)
80%(SaaS行业典型水平)
COGS Components
COGS构成
| Component | % of Revenue |
|---|---|
| Infrastructure | X% |
| Support | Y% |
| Payment processing | Z% |
| Total COGS | X+Y+Z% |
---| 构成部分 | 占收入比例 |
|---|---|
| 基础设施 | X% |
| 支持服务 | Y% |
| 支付处理 | Z% |
| 总COGS | X+Y+Z% |
---4. Market Position
4. 市场定位
Defines your place in the market.
定义产品在市场中的位置。
Example: market_position/
示例:market_position/
market_position/
├── definition.md
├── target_market.md
├── competitors.md
├── differentiation.md
└── .versionmarket_position/
├── definition.md
├── target_market.md
├── competitors.md
├── differentiation.md
└── .versioncompetitors.md
competitors.md
markdown
undefinedmarkdown
undefinedCompetitive Analysis
竞品分析
Competitor Landscape
竞品格局
mermaid
quadrantChart
title Market Position
x-axis Low Price --> High Price
y-axis Simple --> Complex
quadrant-1 Enterprise
quadrant-2 Premium
quadrant-3 Budget
quadrant-4 Value
Competitor A: [0.7, 0.8]
Competitor B: [0.3, 0.4]
Competitor C: [0.8, 0.5]
Our Product: [0.5, 0.6]undefinedmermaid
quadrantChart
title 市场定位
x-axis 低价 --> 高价
y-axis 简单 --> 复杂
quadrant-1 企业级
quadrant-2 高端
quadrant-3 经济型
quadrant-4 高性价比
Competitor A: [0.7, 0.8]
Competitor B: [0.3, 0.4]
Competitor C: [0.8, 0.5]
Our Product: [0.5, 0.6]undefinedDirect Competitors
直接竞品
Competitor A
Competitor A
| Aspect | Details |
|---|---|
| Website | example.com |
| Founded | 20XX |
| Funding | $XM Series B |
| Pricing | $X-Y/mo |
| Target | Enterprise |
Strengths:
- Strong brand recognition
- Enterprise features
- Large customer base
Weaknesses:
- Expensive
- Complex setup
- Slow innovation
How we differentiate:
- Simpler UX
- Lower price point
- Faster time-to-value
| 维度 | 详情 |
|---|---|
| 官网 | example.com |
| 成立时间 | 20XX |
| 融资 | $XM B轮 |
| 定价 | $X-Y/月 |
| 目标用户 | 企业级 |
优势:
- 品牌知名度高
- 企业级功能完善
- 客户基数大
劣势:
- 价格昂贵
- 部署复杂
- 创新速度慢
我们的差异化优势:
- 更简洁的用户体验
- 更低的价格
- 更快的价值交付
Competitor B
Competitor B
| Aspect | Details |
|---|---|
| Website | example2.com |
| Founded | 20XX |
| Funding | $XM Seed |
| Pricing | Free / $X/mo |
| Target | SMB |
Strengths:
- Free tier
- Easy to use
- Growing fast
Weaknesses:
- Limited features
- Reliability issues
- Poor support
How we differentiate:
- More features
- Better reliability
- Professional support
| 维度 | 详情 |
|---|---|
| 官网 | example2.com |
| 成立时间 | 20XX |
| 融资 | $XM 种子轮 |
| 定价 | 免费 / $X/月 |
| 目标用户 | 中小企业 |
优势:
- 免费层级
- 易于使用
- 增长迅速
劣势:
- 功能有限
- 可靠性问题
- 支持服务差
我们的差异化优势:
- 功能更丰富
- 可靠性更高
- 专业支持服务
Indirect Competitors
间接竞品
Spreadsheets (Excel, Google Sheets)
电子表格(Excel、Google Sheets)
Many potential customers use spreadsheets instead of dedicated tools.
Why they choose spreadsheets:
- Already have it
- Familiar interface
- Free
Why they should switch to us:
- Purpose-built features
- Collaboration
- Automation
许多潜在客户使用电子表格而非专用工具。
客户选择电子表格的原因:
- 已拥有该工具
- 界面熟悉
- 免费
客户应转向我们的原因:
- 为特定场景打造的功能
- 协作能力
- 自动化
Competitive Positioning Statement
竞争性定位声明
For [target customer] who [need], {Product} is a [category] that
[key benefit]. Unlike [competitor], we [key differentiator].
---针对[目标客户]的[需求],{Product} 是一款[产品类别],可提供[核心价值]。与[竞品]不同,我们[核心差异化优势]。
---Signal Files for Business Definitions
业务定义的标识文件
Status Signals
状态标识
| Signal | Meaning |
|---|---|
| Still being written |
| Ready for stakeholder review |
| Approved for implementation |
| Founder approved |
| Finance approved (pricing) |
| Legal approved (terms) |
| 标识 | 含义 |
|---|---|
| 仍在编写中 |
| 已准备好供利益相关者审核 |
| 已批准可实施 |
| 创始人已批准 |
| 财务已批准(定价相关) |
| 法务已批准(条款相关) |
Content Signals
内容标识
| Signal | Content |
|---|---|
| Schema version JSON |
| When this takes effect |
| When to review again |
| Previous version this replaces |
| 标识 | 内容 |
|---|---|
| 架构版本JSON |
| 生效日期 |
| 下次审核日期 |
| 替代的旧版本 |
Quality Checklist for Business Definitions
业务定义质量检查表
Before requesting review:
- All monetary values use consistent currency
- Percentages are clearly labeled
- Tiers are exhaustively defined
- Limits have soft and hard values
- Edge cases documented (overages, refunds)
- Competitive analysis is current
- User types map to pricing tiers
- Permissions matrix is complete
- Unit economics calculated
- Related definitions linked
undefined提交审核前请确认:
- 所有货币单位保持一致
- 百分比标注清晰
- 层级定义完整
- 限制包含软性与硬性数值
- 边缘情况已记录(超额使用、退款)
- 竞品分析内容最新
- 用户类型与定价层级匹配
- 权限矩阵完整
- 单位经济效益已计算
- 相关定义已关联
undefined