{ "schemaVersion": "1.0", "item": { "slug": "revenue-model-design", "name": "Revenue Model Design", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/JK-0001/revenue-model-design", "canonicalUrl": "https://clawhub.ai/JK-0001/revenue-model-design", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/revenue-model-design", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=revenue-model-design", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/revenue-model-design" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/revenue-model-design", "agentPageUrl": "https://openagent3.xyz/skills/revenue-model-design/agent", "manifestUrl": "https://openagent3.xyz/skills/revenue-model-design/agent.json", "briefUrl": "https://openagent3.xyz/skills/revenue-model-design/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "A revenue model is not just \"how much do I charge\" — it is the complete system of how value translates into money. The wrong model can make a great product fail (people love it but won't pay the way you structured it). The right model turns a good product into a sustainable business. This playbook helps you choose, design, and validate the right model for your specific situation." }, { "title": "Step 1: Understand the Revenue Model Landscape", "body": "Know your options before choosing. Each model has different implications for cash flow, customer behavior, product design, and growth." }, { "title": "Recurring Revenue Models", "body": "Money comes in on a predictable schedule. The backbone of sustainable solopreneur businesses.\n\nSubscription (monthly/annual): Customer pays a fixed amount per period for ongoing access.\n\nPros: Predictable cash flow. Compounds over time. Customers amortize the cost mentally (feels cheaper than one-time).\nCons: Churn is constant. Must continuously deliver value or people cancel.\nBest for: SaaS products, tools, services with ongoing value delivery.\n\nRetainer: Customer pays a fixed monthly fee for a defined scope of ongoing work or access.\n\nPros: Guaranteed income. Simplifies scoping conversations.\nCons: Can become a trap if the customer expects unlimited work within the retainer.\nBest for: Consulting, managed services, ongoing advisory relationships.\n\nMembership: Customer pays to be part of a group that provides ongoing value (community, content, access).\n\nPros: Low churn if community is strong. Scales well.\nCons: Requires consistent content or community value delivery.\nBest for: Courses + community, mastermind groups, niche professional networks." }, { "title": "One-Time Revenue Models", "body": "Single payments. Great for cash flow spikes, less predictable long-term.\n\nProduct sale: Customer buys a product once and owns it.\n\nPros: No churn. Simple. High margin if digital.\nCons: Must constantly acquire new customers. No revenue compounds.\nBest for: Digital products (templates, ebooks, courses without updates), software with perpetual licenses.\n\nService/project: Customer pays for a defined deliverable.\n\nPros: High revenue per transaction. Flexible scope.\nCons: Time-capped. Must sell the next project constantly. No recurring base.\nBest for: Consulting projects, freelance work, custom builds." }, { "title": "Usage-Based Models", "body": "Revenue scales with how much the customer actually uses the product.\n\nPer-transaction: Customer pays each time they complete an action (e.g., per invoice sent, per email sent).\n\nPros: Aligns cost with value received. Low barrier to entry.\nCons: Unpredictable revenue. Customers may cap usage to control costs.\nBest for: Payment processing, marketplace platforms, API products.\n\nTiered usage: Customer pays based on usage bands (e.g., up to 100 transactions = $X, up to 500 = $Y).\n\nPros: More predictable than pure per-transaction. Still usage-aligned.\nCons: Slightly more complex to communicate.\nBest for: SaaS products where usage varies significantly between customers." }, { "title": "Marketplace / Commission Models", "body": "Revenue comes from facilitating a transaction between two parties.\n\nCommission: You take a percentage of each transaction on your platform.\n\nPros: Scales with the marketplace's GMV. Low upfront cost for users.\nCons: Requires two-sided network effects. Chicken-and-egg problem at launch.\nBest for: Platforms connecting buyers and sellers.\n\nLead generation: You send qualified leads to businesses and charge per lead or per conversion.\n\nPros: Scales well with content/SEO.\nCons: Dependent on advertiser budgets. Can be commoditized.\nBest for: Content-heavy businesses in high-value verticals (finance, real estate, B2B services)." }, { "title": "Step 2: Match Model to Your Situation", "body": "Answer these questions to narrow your options:\n\nQuestionIf Yes → Lean TowardDoes my product deliver value continuously (not just once)?Subscription or membershipIs my product digital with near-zero marginal cost per user?Subscription or one-time saleDo customers' usage levels vary wildly?Usage-based or tiered usageAm I selling my time or expertise directly?Retainer or project/serviceDo I need predictable monthly income?Subscription or retainerAm I early and need to reduce purchase friction to get first customers?Freemium (free tier) or usage-basedCan I connect two groups who want to transact?Marketplace or commission" }, { "title": "Step 3: Design Your Revenue Stream Stack", "body": "Most sustainable solopreneur businesses have 2-3 revenue streams, not one. A single stream is fragile — if it dips, everything dips.\n\nRevenue stream stacking rules:\n\nOne primary stream (60-70% of revenue): Your main product or service. This is where you focus growth efforts.\nOne secondary stream (20-30%): A complementary revenue source that serves the same customers or ecosystem. Often lower-effort or more passive.\nOne opportunistic stream (5-10%): Something that generates revenue when opportunity arises. Can be inconsistent.\n\nCommon solopreneur stack patterns:\n\nPrimarySecondaryOpportunisticSaaS subscriptionDigital course or template packConsulting/speakingConsulting retainersProductized service (fixed scope, fixed price)Affiliate revenue from tool recommendationsDigital product (one-time)Subscription upgrade (premium features or updates)Freelance projectsContent/newsletterSponsored posts or affiliate linksWorkshops or cohorts\n\nStack design rule: Every stream should serve the same core customer or ecosystem. Revenue streams that pull you in different directions dilute your focus and brand." }, { "title": "Step 4: Design the Payment Flow", "body": "For each revenue stream, map the exact payment experience:\n\nREVENUE STREAM: [name]\nMODEL: [subscription / one-time / usage / etc.]\nPRICE: [amount and cadence]\nPAYMENT TRIGGER: [what action causes the charge — signup, usage threshold, renewal]\nPAYMENT METHOD: [credit card, invoice, etc.]\nBILLING TOOL: [Stripe, Paddle, Lemon Squeezy, etc.]\nFREE TRIAL: [yes/no, length, requires card?]\nCANCELLATION FLOW: [how easy is it to cancel? — make this frictionless or you'll get chargebacks]\nUPGRADE PATH: [how does a customer move to a higher tier or add a stream?]\n\nSolopreneur billing tool recommendations:\n\nStripe — most powerful, best developer experience, industry standard\nPaddle — handles tax/VAT globally, good for digital products sold internationally\nLemon Squeezy — simpler than Stripe, good for digital products, handles EU VAT\nGumroad — simplest for one-time digital product sales" }, { "title": "Step 5: Model Your Revenue Projections", "body": "For each stream, build a simple projection:\n\nSTREAM: [name]\nCUSTOMERS MONTH 1: [number]\nMONTHLY GROWTH RATE: [%]\nAVERAGE REVENUE PER CUSTOMER: [$/month]\nCHURN RATE: [%/month] (for recurring streams)\n\nMONTH 1 REVENUE: customers × ARPC\nMONTH 3 REVENUE: [calculate with growth and churn]\nMONTH 6 REVENUE: [calculate]\nMONTH 12 REVENUE: [calculate]\n\nChurn math for recurring models: If you have 100 customers and 5% churn, you lose 5/month. To grow, your new customer acquisition must exceed your churn. This is why retention matters as much as acquisition.\n\nSanity check: Sum all streams. Does total projected revenue cover your costs and provide a livable income within 12 months? If not, either the projections are wrong (re-examine growth assumptions) or the model needs rethinking." }, { "title": "Step 6: Validate Before Building", "body": "Before investing heavily in building out a revenue model, validate the core assumption:\n\n\"Will customers actually pay this way?\"\n\nTest methods:\n\nPre-sales: Offer the product at a discounted \"founding member\" price before it's built. If people pay, the model works.\nFake checkout: Build a landing page with a real checkout button. When someone clicks, show a \"coming soon\" page and capture their email. Measure how many click the buy button.\nManual first version: Deliver the product manually (by hand) at the planned price to 5-10 customers. If they pay and come back, the model is validated." }, { "title": "Revenue Model Mistakes to Avoid", "body": "Choosing a model because it sounds impressive, not because it fits your product and customers.\nIgnoring churn when projecting subscription revenue. Churn compounds painfully.\nBuilding a marketplace model as a solopreneur. Two-sided markets require significant scale to work. Start with a one-sided model first.\nNever testing alternative models. If subscription isn't working, try one-time + upgrade. Revenue models are experiments.\nStacking too many streams too early. Master one stream first, then layer in a second once the first is stable." } ], "body": "Revenue Model Design\nOverview\n\nA revenue model is not just \"how much do I charge\" — it is the complete system of how value translates into money. The wrong model can make a great product fail (people love it but won't pay the way you structured it). The right model turns a good product into a sustainable business. This playbook helps you choose, design, and validate the right model for your specific situation.\n\nStep 1: Understand the Revenue Model Landscape\n\nKnow your options before choosing. Each model has different implications for cash flow, customer behavior, product design, and growth.\n\nRecurring Revenue Models\n\nMoney comes in on a predictable schedule. The backbone of sustainable solopreneur businesses.\n\nSubscription (monthly/annual): Customer pays a fixed amount per period for ongoing access.\n\nPros: Predictable cash flow. Compounds over time. Customers amortize the cost mentally (feels cheaper than one-time).\nCons: Churn is constant. Must continuously deliver value or people cancel.\nBest for: SaaS products, tools, services with ongoing value delivery.\n\nRetainer: Customer pays a fixed monthly fee for a defined scope of ongoing work or access.\n\nPros: Guaranteed income. Simplifies scoping conversations.\nCons: Can become a trap if the customer expects unlimited work within the retainer.\nBest for: Consulting, managed services, ongoing advisory relationships.\n\nMembership: Customer pays to be part of a group that provides ongoing value (community, content, access).\n\nPros: Low churn if community is strong. Scales well.\nCons: Requires consistent content or community value delivery.\nBest for: Courses + community, mastermind groups, niche professional networks.\nOne-Time Revenue Models\n\nSingle payments. Great for cash flow spikes, less predictable long-term.\n\nProduct sale: Customer buys a product once and owns it.\n\nPros: No churn. Simple. High margin if digital.\nCons: Must constantly acquire new customers. No revenue compounds.\nBest for: Digital products (templates, ebooks, courses without updates), software with perpetual licenses.\n\nService/project: Customer pays for a defined deliverable.\n\nPros: High revenue per transaction. Flexible scope.\nCons: Time-capped. Must sell the next project constantly. No recurring base.\nBest for: Consulting projects, freelance work, custom builds.\nUsage-Based Models\n\nRevenue scales with how much the customer actually uses the product.\n\nPer-transaction: Customer pays each time they complete an action (e.g., per invoice sent, per email sent).\n\nPros: Aligns cost with value received. Low barrier to entry.\nCons: Unpredictable revenue. Customers may cap usage to control costs.\nBest for: Payment processing, marketplace platforms, API products.\n\nTiered usage: Customer pays based on usage bands (e.g., up to 100 transactions = $X, up to 500 = $Y).\n\nPros: More predictable than pure per-transaction. Still usage-aligned.\nCons: Slightly more complex to communicate.\nBest for: SaaS products where usage varies significantly between customers.\nMarketplace / Commission Models\n\nRevenue comes from facilitating a transaction between two parties.\n\nCommission: You take a percentage of each transaction on your platform.\n\nPros: Scales with the marketplace's GMV. Low upfront cost for users.\nCons: Requires two-sided network effects. Chicken-and-egg problem at launch.\nBest for: Platforms connecting buyers and sellers.\n\nLead generation: You send qualified leads to businesses and charge per lead or per conversion.\n\nPros: Scales well with content/SEO.\nCons: Dependent on advertiser budgets. Can be commoditized.\nBest for: Content-heavy businesses in high-value verticals (finance, real estate, B2B services).\nStep 2: Match Model to Your Situation\n\nAnswer these questions to narrow your options:\n\nQuestion\tIf Yes → Lean Toward\nDoes my product deliver value continuously (not just once)?\tSubscription or membership\nIs my product digital with near-zero marginal cost per user?\tSubscription or one-time sale\nDo customers' usage levels vary wildly?\tUsage-based or tiered usage\nAm I selling my time or expertise directly?\tRetainer or project/service\nDo I need predictable monthly income?\tSubscription or retainer\nAm I early and need to reduce purchase friction to get first customers?\tFreemium (free tier) or usage-based\nCan I connect two groups who want to transact?\tMarketplace or commission\nStep 3: Design Your Revenue Stream Stack\n\nMost sustainable solopreneur businesses have 2-3 revenue streams, not one. A single stream is fragile — if it dips, everything dips.\n\nRevenue stream stacking rules:\n\nOne primary stream (60-70% of revenue): Your main product or service. This is where you focus growth efforts.\nOne secondary stream (20-30%): A complementary revenue source that serves the same customers or ecosystem. Often lower-effort or more passive.\nOne opportunistic stream (5-10%): Something that generates revenue when opportunity arises. Can be inconsistent.\n\nCommon solopreneur stack patterns:\n\nPrimary\tSecondary\tOpportunistic\nSaaS subscription\tDigital course or template pack\tConsulting/speaking\nConsulting retainers\tProductized service (fixed scope, fixed price)\tAffiliate revenue from tool recommendations\nDigital product (one-time)\tSubscription upgrade (premium features or updates)\tFreelance projects\nContent/newsletter\tSponsored posts or affiliate links\tWorkshops or cohorts\n\nStack design rule: Every stream should serve the same core customer or ecosystem. Revenue streams that pull you in different directions dilute your focus and brand.\n\nStep 4: Design the Payment Flow\n\nFor each revenue stream, map the exact payment experience:\n\nREVENUE STREAM: [name]\nMODEL: [subscription / one-time / usage / etc.]\nPRICE: [amount and cadence]\nPAYMENT TRIGGER: [what action causes the charge — signup, usage threshold, renewal]\nPAYMENT METHOD: [credit card, invoice, etc.]\nBILLING TOOL: [Stripe, Paddle, Lemon Squeezy, etc.]\nFREE TRIAL: [yes/no, length, requires card?]\nCANCELLATION FLOW: [how easy is it to cancel? — make this frictionless or you'll get chargebacks]\nUPGRADE PATH: [how does a customer move to a higher tier or add a stream?]\n\n\nSolopreneur billing tool recommendations:\n\nStripe — most powerful, best developer experience, industry standard\nPaddle — handles tax/VAT globally, good for digital products sold internationally\nLemon Squeezy — simpler than Stripe, good for digital products, handles EU VAT\nGumroad — simplest for one-time digital product sales\nStep 5: Model Your Revenue Projections\n\nFor each stream, build a simple projection:\n\nSTREAM: [name]\nCUSTOMERS MONTH 1: [number]\nMONTHLY GROWTH RATE: [%]\nAVERAGE REVENUE PER CUSTOMER: [$/month]\nCHURN RATE: [%/month] (for recurring streams)\n\nMONTH 1 REVENUE: customers × ARPC\nMONTH 3 REVENUE: [calculate with growth and churn]\nMONTH 6 REVENUE: [calculate]\nMONTH 12 REVENUE: [calculate]\n\n\nChurn math for recurring models: If you have 100 customers and 5% churn, you lose 5/month. To grow, your new customer acquisition must exceed your churn. This is why retention matters as much as acquisition.\n\nSanity check: Sum all streams. Does total projected revenue cover your costs and provide a livable income within 12 months? If not, either the projections are wrong (re-examine growth assumptions) or the model needs rethinking.\n\nStep 6: Validate Before Building\n\nBefore investing heavily in building out a revenue model, validate the core assumption:\n\n\"Will customers actually pay this way?\"\n\nTest methods:\n\nPre-sales: Offer the product at a discounted \"founding member\" price before it's built. If people pay, the model works.\nFake checkout: Build a landing page with a real checkout button. When someone clicks, show a \"coming soon\" page and capture their email. Measure how many click the buy button.\nManual first version: Deliver the product manually (by hand) at the planned price to 5-10 customers. If they pay and come back, the model is validated.\nRevenue Model Mistakes to Avoid\nChoosing a model because it sounds impressive, not because it fits your product and customers.\nIgnoring churn when projecting subscription revenue. Churn compounds painfully.\nBuilding a marketplace model as a solopreneur. Two-sided markets require significant scale to work. Start with a one-sided model first.\nNever testing alternative models. If subscription isn't working, try one-time + upgrade. Revenue models are experiments.\nStacking too many streams too early. Master one stream first, then layer in a second once the first is stable." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/JK-0001/revenue-model-design", "publisherUrl": "https://clawhub.ai/JK-0001/revenue-model-design", "owner": "JK-0001", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/revenue-model-design", "downloadUrl": "https://openagent3.xyz/downloads/revenue-model-design", "agentUrl": "https://openagent3.xyz/skills/revenue-model-design/agent", "manifestUrl": "https://openagent3.xyz/skills/revenue-model-design/agent.json", "briefUrl": "https://openagent3.xyz/skills/revenue-model-design/agent.md" } }