Skip to main content

DHO Pricing Model

Purpose

Hypha product development teams have been heads down refining and improving our products. Each team has created outstanding roadmaps, reliable testing procedures, and efficient source control and deployment processes. This document is looking at how we can define revenue streams (i.e. relying less on investors and investment income) by coming up with a pricing model that is aligned with the regenerative renaissance (i.e. not driven by excessive profit motives), while at the same time paying for our infrastructure costs and rewarding all participants fairly.

Assumptions

1

  1. We wantneed to generate sustainable revenue streams
    2that can cover expenses
  2. We wantdon’t need to makedecide itthe partprices ofnow, just put a circularframework economy
    3in place
  3. Circular economies require revenue
  4. The customer wants to pay for features s/he needs
    4
  5. The RR (regen renaissance) wants to support it
    5
  6. The VP (value proposition) is clearly defined

  7. Exact pricing should be part of governance (need to define who/how)
Options around longer commitment, annual vs monthly.
4- staking vs burning (?) 5- I don’t think we should offer freemium until we can reduce our costs per new DHO via automation. Orgs need skin in the game, or else we will be buried just setting them up for free and they won’t get used.
6- I think we should also have a commission program for sales reps.

Models

1 Free (genesis)
2 Freemium (default)
3 Premium (service)

Types

  1. Freemium approach;
  2. SBP - subscription-based pricing (also on top of a Freemium model, typical SaaS model);
  3. UBP - usage-based pricing (also on top of a Freemium model, typical on-demand model);
  4. VBP - value-based pricing (let the customer decide, see deck below from CAWW);
  5. PPS - paid premium services that are only sold to premium users (mostly providers);
  6. PBU - price by users; (no go, see article by David Sacks below)

(via Max):

3.1 pay per proposal;
3.2 pay per claim;
3.3 pay per feature;
3.4 pay per redemption (free for EOS);
3.5 pay-as-you-go, although may require a deposit, as well as pricing at broader levels

Also to consider are options around longer commitment, annual vs monthly.

Teams vs Individual Licenses

Team plans are where the opportunity is, and therefore where founders should focus their energy and resources. Individual plans can be useful to generate leads, but their long-term revenue potential is significantly smaller. Account-level churn rates for Individual plans are commonly around 5% per month, but only 1-2% per month for Team plans. Team plans build on a solid long-term foundation whereas Individual plans are the definition of a Leaky Bucket.

Article: https://sacks.substack.com/p/individuals-or-teams-whos-the-better (via Augusto)

Process

1 select new DHO (e.g. via impact metrics)
2 set pricing model (and other params)
3 propose and launch DHO from parent DHO (hand over protocol)

Tokenomics

1 What tokens to use
2 Value of tokens (price point)
3 Cost of services (infrastructure/capital, labor/roles)
4 Financial/knowledge/value/credit flows
5 Treasury/Store of value

Our Model (TBD)

  • How much "basic usage" can we afford and where is the threshold to UBP?
  • Are accelerators using VBP or other pricing model (T&E, Flat Rate)?
  • Is there revenue sharing between Hypha and Partners? (blue/orange and green boxes)
  • Is there a pricing policy needed and an agreement with Hypha?

image-1622070573745.png

source

References

https://stories.platformdesigntoolkit.com/pricing-platforms-marketplaces-151ab67b130a (Simone Cicero who created the Platform Design Toolkit)

https://docs.google.com/presentation/d/1NE2gxibDXvgfediqRHRKs7IJjh18P4mO_qpEIr84L4A/edit (Value-based Pricing model we developed at CAWW)

https://speckyboy.com/freelance-design-value-based-pricing/ (more on VBP)

Back to top