跳到正文
cccskills
免费在 GitHub 公开

startup-business-models

Evaluate startup revenue models and pricing plans against customer value and delivery costs. Build a per-customer financial picture, compare scenarios, and define pricing experiments that track revenue, margins, retention, and potential side effects.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when choosing or evaluating a startup revenue model, pricing/value metric, packaging/tier design, or calculating unit economics (LTV, CAC, payback, gross margin, NRR), including usage-based/credit/AI pricing and variable compute/COGS constraints.

查看安装方法

适用场景

  • Choosing a revenue model for a startup
  • Reviewing usage-based pricing for an AI product
  • Redesigning pricing tiers and included usage
  • Planning how to evaluate a pricing change

包含的文件(1)

  • SKILL.md7.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Startup Business Models

Systematic workflow for choosing revenue models, pricing, and unit economics.

Quick Start (Inputs)

Ask for the smallest set of inputs that makes the decision meaningful:

  • Business type: SaaS, usage-based/API, marketplace, services, hardware + service
  • ICP/segment(s): SMB / mid-market / enterprise (and ACV/ARPA bands)
  • Current pricing and packaging: value metric, tiers, limits, discount policy, billing cadence
  • Unit economics drivers: fully-loaded CAC, gross margin/COGS (include LLM/infra/third-party), churn/retention, expansion (NRR)
  • Constraints: sales motion (PLG vs sales-led), implementation constraints (billing metering, proration), gross margin floor, payback target

If numbers are missing, proceed with ranges + explicit assumptions and highlight what to measure next.

Workflow

  1. Classify the model
  • Subscription, usage-based, freemium, marketplace take-rate, transaction fee, ads, outcome-based, credit-based, hybrid.
  1. Build a segment-level unit economics snapshot
  1. Evaluate model fit and risks
  • Align price metric with value delivered and cost incurred (especially usage + AI compute).
  • Identify failure modes: margin compression, adverse selection, channel conflict, support cost explosions, metering/overage friction.
  1. Propose pricing + packaging changes
  • Use pricing-strategy for willingness-to-pay research and tier differentiation.
  • Draft a tier table with segment, value metric, price, included usage, limits, upgrade trigger, and enforcement rule. Label untested prices as hypotheses.
  1. Define measurement and roll-out
  • Define success metric + guardrails, evaluation design, and explicit lag windows (conversion now, retention later).
  1. Deliver a decision-ready output
  • Recommendation, rationale, assumptions, scenarios (base/best/worst), and next experiments.

2026 Heuristics (Context-Dependent)

  • Prioritize payback and gross margin over a single ratio; LTV:CAC is easiest to game.
  • Typical SaaS targets (directional, by segment/stage): LTV:CAC 3-5x, payback 6-12 months (PLG) or 12-18 months (sales-led early), NRR >100% (mid-market/enterprise) and gross margin >70% (software-only).
  • For usage-based / AI products: model contribution margin per unit (token/job/workflow) and set pricing guardrails (rate limits, minimums, commit tiers, credit expiries).

Related Skills (Routing)

For idea validation, record the customer problem, evidence of willingness to pay, and the next experiment before committing to a model.

Pricing Change Measurement & Experiment Design

Use this when you are changing pricing, packaging, value metric, limits, discounts, or billing cadence.

1) Define success and guardrails (before launch)

TypeExamples
Primary success metricNet revenue retention (NRR), ARPA/ARPU, gross margin %, payback period, upgrade rate, expansion MRR
GuardrailsNew logo conversion, activation rate, refund rate, support load, churn (logo + revenue), sales cycle length

2) Pick an evaluation design

DesignBest whenHow to read results
A/B (randomized)Self-serve / PLG flowsCompare conversion, ARPA, refunds, and downstream retention by assignment
Holdout/control cohortPricing is hard to randomizeCompare treated vs. holdout cohorts matched on segment, channel, and start month
Step rollout (time-based)Enterprise contracts, invoicing cyclesCompare pre/post with a parallel cohort (not exposed yet) to reduce seasonality bias
Geo/account rolloutRegions/segments are separableCompare regions/segments; watch for channel mix shifts

3) Use explicit lag windows (avoid premature conclusions)

  • Short lag (days to 2 weeks): checkout conversion, activation, sales cycle friction, refund/support spikes.
  • Medium lag (4 to 8 weeks): upgrades, expansion MRR, usage growth, discounting behavior, proration effects.
  • Long lag (90 to 180+ days, B2B): churn, net revenue retention, renewal outcomes, contraction risk.

4) Report an "all-in" view (not just conversion)

  • Revenue quality: net revenue after refunds, discounts, and credits; gross margin impact (including variable compute/COGS).
  • Segments: break down by plan, seat band, channel, ACV/ARR band, and customer age (new vs. renewal).
  • Decision rule: write a go/no-go threshold (example: "NRR +2pts with no >0.5pt drop in activation and no >10% increase in support load").

Available Resources and Outputs

NeedBundled guidance
CAC, LTV, payback, and cohort analysisUnit-economics methodology and worksheet
Willingness-to-pay and tier designPricing strategy
Business model canvasProduct strategist, Business Model Canvas section
MRR/ARR, burn, runway, and scenariosStartup financial modeling

Create the pricing-tier table described in Workflow step 4 and an assumptions table with input, value/range, source URL, date, and confidence. This skill does not bundle separate canvas/pricing template files or a data-source catalog. Use current, attributable sources for business decisions.


Do / Avoid (Jan 2026)

Do

  • Define your value metric (seat/usage/outcome) and validate willingness-to-pay early.
  • Include COGS drivers in pricing decisions (especially usage-based).
  • Use discount guardrails and renewal logic (avoid ad-hoc deals).

Avoid

  • Pricing as an afterthought (“we’ll figure it out later”).
  • Margin blindness (shipping usage growth that destroys gross margin).
  • Misleading LTV calculations from immature cohorts.

What Good Looks Like

  • Packaging: a clear value metric, tier logic, and discount policy (with enforcement rules).
  • Unit economics: CAC, gross margin, churn, payback, and retention defined and tied to cohorts.
  • Assumptions: one inputs sheet, ranges/sensitivities, and scenarios (base/best/worst).
  • Experiments: pricing changes tested with decision rules (not “gut feel” rollouts).
  • Risks: margin compression, adverse selection, channel conflict, and support cost modeled.

Optional: AI / Automation

Use only when explicitly requested and policy-compliant.

  • Summarize pricing research and competitor snapshots; verify manually before acting.
  • Draft pricing page copy; humans verify claims and consistency with contracts.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Automate website tasks with agent-browser, a command-line browser tool for AI agents. Fill forms, click controls, extract page text, capture screenshots, and test web apps, with support for saving and reusing login state.

中文简介正在准备中。当前显示英语简介。

  • Automating form entry and submission
  • Extracting text from web pages
  • Capturing screenshots and checking web app behavior
MaxMiksa/Autonomous-Company31552026年10月21日 更新

Review Python, FastAPI, and React code for security weaknesses in access checks, input handling, secrets, and dependencies. Produce a report with severity levels, file locations, explanations, and recommended fixes, supported by scanning patterns.

中文简介正在准备中。当前显示英语简介。

  • Review pull requests for security weaknesses
  • Audit authentication and access checks
  • Check user input and file handling
MaxMiksa/Autonomous-Company31552026年10月21日 更新

Create a series of personalized sales emails for new prospects or older leads. Get message drafts, subject line alternatives to compare, recommended sending intervals, and ways to include customer results and clear meeting requests.

中文简介正在准备中。当前显示英语简介。

  • Drafting a seven-email sequence for SaaS prospects
  • Comparing subject lines with A/B tests
  • Reconnecting with inactive sales leads
MaxMiksa/Autonomous-Company31552026年10月21日 更新

Plan user communities that support customer acquisition, retention, and expanded use. Develop ambassador programs, user groups, and community content, then assess meaningful participation, customer advocacy, and business impact rather than relying on membership counts alone.

中文简介正在准备中。当前显示英语简介。

  • Planning a developer community
  • Designing an ambassador program
  • Creating a user group playbook
MaxMiksa/Autonomous-Company31552026年10月21日 更新

Research competitors’ features, pricing, messaging, and customer complaints to produce comparison tables and an actionable report. Identify underserved needs, clarify how an offering differs, and plan regular monitoring of competitor changes.

中文简介正在准备中。当前显示英语简介。

  • Compare competitors’ features and pricing
  • Find customer needs competitors overlook
  • Analyze why deals are won or lost
MaxMiksa/Autonomous-Company31552026年10月21日 更新

Plan content using customer questions, keyword data, and competitor coverage. Organize core themes and related articles, match topics to buying stages, and rank ideas by customer impact, product relevance, search potential, and production needs.

中文简介正在准备中。当前显示英语简介。

  • Choose core themes for a business blog
  • Turn customer conversations into content ideas
  • Group keywords into related article topics
MaxMiksa/Autonomous-Company31552026年10月21日 更新

查看 MaxMiksa 的全部技能

报告此技能的问题