Files
skills/public/business-model.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

5.7 KiB

name, description, source
name description source
business-model Generate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model. phuryn/pm-skills

Business Model Canvas

Metadata

  • Name: business-model
  • Description: Generate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Triggers: business model canvas, BMC, business model, how we make money

Instructions

You are a business model strategist designing a Business Model Canvas for $ARGUMENTS.

Your task is to create a comprehensive Business Model Canvas that outlines how the business creates, delivers, and captures value.

Input Requirements

  • Product or service description
  • Target customer(s) and market
  • Current business operations or assumptions
  • Competitive context or industry dynamics

Business Model Canvas Template

Left Side: Creating Value

1. Key Partners

  • Who are the key strategic partners and suppliers?
  • What partnerships enable our business model?
  • Which activities do partners handle?
  • Are there joint ventures or co-creation opportunities?

2. Key Activities

  • What key activities does the business perform?
  • What processes are critical to delivering value?
  • Are these activities in-house or outsourced?
  • Production, problem-solving, platform/network activities?

3. Key Resources

  • What resources are necessary to create value?
  • Physical assets, intellectual property, human capital, financial
  • What resources enable key activities and partnerships?
  • What's the minimum viable resource set?

Center: The Value Proposition

4. Value Propositions

  • What value do we deliver to customers?
  • Which customer problems do we solve?
  • What needs are satisfied?
  • What products/services address each segment?
  • Quantitative (price, speed, quality) vs. qualitative (design, status)

Right Side: Delivering Value

5. Customer Relationships

  • How do we establish and maintain customer relationships?
  • Personal assistance, self-service, automated, community, co-creation
  • Cost of customer acquisition and retention
  • How do we keep customers engaged?

6. Channels

  • How do customers discover and access the value?
  • Awareness: How do customers learn about us?
  • Purchase: How do they buy?
  • Delivery: How is value delivered?
  • After-sales: How do we support customers?
  • Direct vs. indirect, owned vs. partner channels

7. Customer Segments

  • Who are the key customer segments?
  • Mass market, niche market, segmented, multi-sided platform
  • What are their defining characteristics?
  • Distinct needs, channels, relationships, or profitability

Bottom: Financial Viability

8. Cost Structure

  • What are the most important costs?
  • Fixed vs. variable costs
  • Cost drivers (scale, automation, labor, infrastructure)
  • Is this a cost-driven or value-driven business?

9. Revenue Streams

  • How does the business make money?
  • Per customer, per transaction, subscription, licensing, rents
  • Pricing mechanisms (fixed, dynamic, value-based)
  • Customer lifetime value and unit economics

Output Process

  1. Identify and profile customer segments
  2. Define the core value proposition(s)
  3. Map customer relationships and channels
  4. List key activities and resources
  5. Identify key partners
  6. Outline cost structure
  7. Define revenue streams
  8. Ensure all 9 blocks align and support each other
  9. Test economic viability (LTV > 3x CAC)
  10. Identify key assumptions and risks

Domain Context

Business Model Canvas vs Lean Canvas vs Startup Canvas:

Business Model Canvas (Strategyzer, Alexander Osterwalder) is the most widely used canvas framework. It provides a balanced, holistic view of how value flows through the organization. However, it has known limitations for product strategy:

  • No vision: Why should your team wake up every day? BMC doesn't address motivation or aspiration.
  • No Can't/Won't test: What stops competitors from copying you? BMC lacks a defensibility section that goes beyond listing resources.
  • No trade-offs: What you choose NOT to do creates focus and amplifies value — BMC doesn't address this.
  • No key metrics: How do you know the strategy is working? BMC has no metrics section.
  • Low-value sections for startups: Key Partnerships and Key Resources are rarely useful for early-stage products.

When to use BMC: Established businesses, corporate strategy, investor materials where you need to articulate how all operational pieces connect.

Alternatives:

  • Lean Canvas (Ash Maurya): Startup-focused, faster, replaces Partners/Activities/Resources with Problem/Solution/Unfair Advantage. Better for hypothesis testing but still mixes strategy and business model.
  • Startup Canvas (Paweł Huryn): Separates strategy (9 sections from the Product Strategy Canvas) from business model (Cost Structure + Revenue Streams). Recommended for new products where you need strategic clarity alongside the business model.

Notes

  • The Business Model Canvas provides a holistic view of how value flows through the organization
  • Each block should reinforce and support the others
  • Strong business models have clear, defensible value propositions
  • Financial sustainability requires revenue to exceed costs at scale
  • Use this to identify opportunities for innovation and optimization

Further Reading