business-model-canvas
Build, fill, stress-test, and iterate on a Business Model Canvas for a solopreneur. Use when designing or redesigning how a business creates, delivers, and captures value — covering all nine BMC blocks plus solopreneur-specific adaptations like the "Time & Energy" block and unit economics validation. Trigger on "business model canvas", "design my business model", "how will I make money", "business model", "BMC", "value proposition canvas", "how does my business work", "monetize my idea".
What this skill does
# Business Model Canvas ## Overview The Business Model Canvas (BMC) is a one-page strategic tool that maps every element of how your business works. For solopreneurs, the standard BMC needs one critical addition: a Time & Energy block, because your scarcest resource isn't money — it's you. This playbook walks you through filling every block, validating the connections between them, and finding the weaknesses before the market does. --- ## The Nine (+1) Blocks Fill these in the order listed. Each block informs the next. Do not skip around. ### Block 1: Customer Segments **Question:** Who exactly are you serving? - Be specific. Not "small businesses." Define 1-3 tight segments. - For each segment: size estimate, pain level, budget, and how they currently solve the problem. - Rank segments by: pain intensity × willingness to pay × reachability. - Your primary segment (the one you build for first) should score highest across all three. ### Block 2: Value Propositions **Question:** What specific value do you deliver to each segment? - Write one value proposition per segment. Make it concrete and measurable. - Format: "[Customer type] can [achieve specific outcome] in [timeframe/way], instead of [current painful alternative]." - Quantify the value wherever possible: "Save 5 hours/week", "Cut churn by 30%", "Close deals 2x faster." - Identify whether your value is primarily: cost savings, time savings, quality improvement, risk reduction, or new capability. ### Block 3: Channels **Question:** How do customers discover and buy from you? - Map the full customer journey: Awareness → Consideration → Purchase → Delivery → Post-purchase. - For each stage, identify the specific channel or touchpoint. Example: Awareness = LinkedIn content + SEO blog. Consideration = free trial. Purchase = website checkout. Delivery = onboarding email sequence. Post-purchase = in-app onboarding. - Identify which channels are owned (blog, email list, social following), earned (word-of-mouth, reviews, press), or paid (ads). Aim for a mix, but as a solopreneur, owned and earned channels are your lifeline. ### Block 4: Customer Relationships **Question:** What kind of relationship does each customer segment expect? Choose the dominant model(s) for your business: - **Self-service:** Product does the work. Minimal human touch. (SaaS tools, digital products) - **Automated personal service:** Personalized at scale via automation. (Email sequences, chatbots, personalized dashboards) - **Community:** Customers help each other. (Forum, Slack group, peer network) - **One-to-one:** Direct personal interaction. (Consulting, coaching, white-glove service) As a solopreneur, self-service and automated are your scaling levers. One-to-one doesn't scale but can be your revenue bridge while building. ### Block 5: Revenue Streams **Question:** How does money flow in, and from whom? For each customer segment, define: - **Revenue model:** One-time purchase / Subscription (monthly or annual) / Usage-based / Freemium / Marketplace commission / Service retainer - **Price point:** Specific dollar amount per unit or per month - **Payment trigger:** What action causes the customer to pay? - **Expected ARPU (Average Revenue Per User):** Monthly and annual List ALL revenue streams. Most successful solopreneur businesses have 2-3 streams (e.g., a SaaS product + a consulting arm + a digital course). ### Block 6: Key Resources **Question:** What do you need to deliver your value proposition? As a solopreneur, resources are: your time, your skills, tools/software, and any intellectual property or data you have. - List every resource required. - Flag which are one-time investments vs. ongoing costs. - Identify the resource that is your biggest bottleneck. This often reveals a scaling problem early. ### Block 7: Key Activities **Question:** What must you actually DO every day/week to keep this business running? Split into: - **Product/Service delivery** — the core thing you do to serve customers - **Customer acquisition** — marketing, sales, outreach - **Operations & maintenance** — support, invoicing, infrastructure, updates **Solopreneur time-check:** Estimate hours per week for each activity. If the total exceeds your available hours (realistically 30-40 for a full-time solo operation), something must be cut, automated, or outsourced. ### Block 8: Key Partnerships **Question:** What external relationships reduce risk or fill capability gaps? Partnerships for solopreneurs often include: - Tool/platform partnerships (integration partners, affiliate relationships) - Freelancer or contractor relationships for skills you lack - Distribution partners (someone who sends customers your way in exchange for value) - Technology dependencies (API providers, hosting, payment processors) **Risk flag:** If your business depends on a single platform or partner that could change terms or shut down, that's a critical risk. Identify these and have contingency plans. ### Block 9: Cost Structure **Question:** What does it cost to run this business? Categorize costs: - **Fixed costs** (don't change with volume): hosting, tools/subscriptions, insurance, legal - **Variable costs** (scale with revenue or customers): payment processing fees, ad spend, contractor hours, per-unit delivery costs - **One-time costs:** Initial setup, branding, first version of product Calculate your **monthly burn rate** (fixed + baseline variable) and your **break-even point** (how many customers or revenue needed to cover all costs). ### Block 10 (Solopreneur Addition): Time & Energy Budget **Question:** Can YOU actually do all of this without burning out? This block doesn't exist in the standard BMC but is the #1 killer of solopreneur businesses. - List every key activity from Block 7. - Assign realistic weekly hours to each. - Identify what can be automated (Block 7 cross-reference). - Identify what can be outsourced and at what cost (feeds back into Block 9). - Calculate your remaining personal hours for rest, learning, and life. **Rule:** If your time budget doesn't balance, the business model is broken. Fix it before launching — not after burning out six months in. --- ## Validation Step: Cross-Block Consistency Check After filling all blocks, run these checks. Each one catches a common mistake: | Check | What to Verify | |---|---| | Value ↔ Segments | Does each value proposition directly address a pain that each segment actually has? | | Revenue ↔ Value | Are customers willing to pay the price you set for the value you deliver? (Cross-reference customer discovery data) | | Channels ↔ Segments | Can you actually reach your target segments through the channels you listed? | | Activities ↔ Time | Do your key activities fit within realistic available hours? (Block 10) | | Costs ↔ Revenue | Does your revenue exceed your costs at a realistic customer volume? (Unit economics) | | Resources ↔ Activities | Do you have every resource needed to execute every activity? | | Partnerships ↔ Risks | Are critical dependencies identified and mitigated? | **For every "no" answer:** Either fix the block or fundamentally rethink the model. A business model with unresolved inconsistencies will fail predictably. --- ## Unit Economics Sanity Check Before finalizing, calculate these three numbers: - **CAC (Customer Acquisition Cost):** Total marketing/sales spend ÷ number of new customers acquired. Target: CAC < 3 months of customer revenue. - **LTV (Customer Lifetime Value):** ARPU × average customer lifespan in months. Target: LTV > 3× CAC. - **Payback Period:** CAC ÷ monthly ARPU. Target: < 12 months. If unit economics don't work, adjust: raise price, reduce CAC via better channels, or increase retention to extend LTV. --- ## When to Revisit - Before every major decision (new feature, new market, new pricing). - Monthly during the first 6 months of operation. - Quarterly thereafter. - Whenever a key assumption is proven wrong by re
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.