💲

Open core pricing

Open core companies produce both open source software and source-available proprietary software and follow the buyer-based open core business model for determining what’s open source and what’s source-available. The open source project is always free and downloadable without restrictions.
Most companies have a SaaS hosting option and will provide a free, hosted version of their software. This is not the same thing as the open source project. A free tier comes with limitations, usually in the form of consumption, number of users, storage, or some combination of those things. From a business perspective, the goal of the free version is to drive people to upgrade to paid versions.
Pricing has a negative correlation with demand. When the price goes up, the number of customers willing to pay that price will go down. Optimizing pricing strategy is often a consistently evolving consideration for companies. In general, pricing alone should be the primary reason 20% of people are not willing to buy the product.

Open source versus free version

The open source project and the free version of your software are not necessarily the same thing. The open source project should always be available to download, use, and modify via the repo it’s stored in. It’s not usually available as a hosted SaaS product. The free version of the software is usually a hosted, SaaS product and it may be a forked version of the open source software.
The open source software may be hosted in a “sandbox” environment where users do not need to sign up with accounts. The hosted open source “sandbox” operates as the free tier. When this is the case, the limitations on what a non-”sandbox” free tier may look like should focus on driving users to the paid tiers more quickly to reduce friction.  A limited trial of premium features in place of an additional free tier is recommended to help reduce that friction.
Features that are available in the free version of the software should also be added to the open source version. It’s important to maintain a good, usable version of the open source project in order to contribute back to the open source community and encourage bottoms-up adoption of the product.

Good, better, best pricing tiers

In its simplest form, the open core pricing model has three tiers: good, better, and best. It’s recommended to use a price-based costing strategy for determining the market for pricing levels.
Tier
Free (Good)
Premium (Better)
Enterprise (Best)
Price
$0
$9
$25
Billing
per user/mo billed annually
per user/mo, billed annually

Good = free

The “good” tier is free and drives upgrades to a paid version. Even though the “good” tier is free and open source, it is usually a separate offering from the open source self-hosted version of the product. For products that are solely self-hosted, the open source version may be your free tier and upgrades to paid plans will be driven primarily by features. Only offer one free tier.
Avoid free forever plans. The intention of providing a free tier is to let people try out the product. Free tiers should have limitations that drive people to upgrade. Examples of limitations include usage, compute consumption, storage, and/or a number of something (for example: searches, projects, users, etc.)
Considerations for creating a “good” tier:
  1. Should require creating an account
  1. Automatically starts as a 30-day free trial of the premium offering, then reverts to basic features
  1. User and/or consumption limitations:
    1. Collaborators (5 people)
    2. Storage (1 GB)
    3. Compute (10 models)
    4. Transfer (100 syncs)

Better = premium

The” better” tier includes everything in “good” and introduces source-available paid features targeted toward managers.
Considerations for creating a “better” tier:
  1. Can include base-level support

Best = enterprise

The “best” tier is the highest-paid tier that includes everything from “good” and “better” and includes enterprise-specific paid features and support targeted toward executives.
Considerations for creating a “best” tier:
  1. Includes support SLAs
  1. Usually includes SSO features
  1. No user limitations

Discount programs

As your company grows to over 100 people and you can handle more complexity, you can consider discounted programs.
  1. Education: Free version without user limitations or paid offerings at a discounted price
  1. Non-profit: Discounted per-user price for paid offerings
  1. Startup: 50-75% discount for startups that meet specific criteria. For example, a seed-stage startup with less than $X in funding and less than $X in revenue.
Discounting may also happen outside of a specific program on a case by case basis. Companies don’t lose their ability to discount by having a list price.

Subscription terms

Simplify pricing plans by only offering an annual subscription.
It makes it easier to instrument and finance your company when all customers are on the same plan versus segmenting by monthly and annual subscriptions. (Pilot programs where needed can convert into annual contracts).
The recurring revenue metric of annual recurring revenue (ARR) versus monthly recurring revenue (MRR) differs based on the yearly or monthly billing subscription renewal period. Upfront billing ensures 12x recurring revenue when customers are billed yearly.
Reporting metrics when a company has both annual and monthly customers is duplicated if both options are available to customers.
There is a risk of losing some business upfront in only billing yearly, but those customers are more likely to churn regardless. Often companies start with monthly billing and switch later to annual billing as they mature, but it is better to start with annual billing early on.
Annual contracts help:
  1. Reduce customer churn.
  1. Provide cash upfront, which is an effective non-dilutive way to fund the company (cash impact between monthly and annual contracts is substantial).
  1. Companies can offer flexible payment terms and a money-back guarantee if customers have reservations about annual commitments.

Pricing strategies

It is harder to change the dimension for pricing than to change the price itself. Prioritize getting the pricing dimension right early on.

Price-based costing

Price-based costing looks at what competitors or substitutes would charge to provide a similar product/service to get a sense of willingness to pay. Additional Reference: https://www.priceintelligently.com/blog/price-based-costing
Both approaches are useful in determining what might be acceptable pricing for a business.

Calculating margin and markup

Companies should target an 80-90% margin.
Calculating margin and markup
Margin = (Revenue - Costs)/Revenue = 1 - Costs/Revenue
Markup = (Revenue - Costs)/Costs = Revenue/Costs -1
Markup = Margin*Revenue/Costs = (1/(1 - Margin)) - 1
Markup = (1/(1 - 80%)) - 1 = (1/20%) - 1 = 500% - 1 = 400%

Consumption or usage-based pricing

An alternative dimension for pricing based on the number of users can be through consumption or usage.
The consumption-based pricing model is a service provision and payment scheme where the customer pays according to the resources used. The provider needs to track customer usage and bill accordingly. Consumption-based billing is best for businesses that can easily break down their offerings into small, variable units.
Advantages
Drawbacks
Fair to the customer (paying for actual usage)
Difficult to predict revenue (can’t price annually)
Align operating costs with customer usage rates (e.g. cloud storage)
Receive payment in arrears as opposed to in advance

Creating a pricing web page

 
The pricing page is often the most visited web page because it quickly tells visitors what the company offers. Considerations when building a pricing page:
  1. Make the most desired choice the primary call to action.
  1. Use font size to show information hierarchy.
  1. Clearly articulate the different tiers (for example, free, team, enterprise)
  1. Use “Cloud” to describe managed services.
  1. Use three tiers “good, better, best”

Waitlists

OCV doesn’t recommend wait lists. It adds an extra conversion point where you have drop-off and creates extra complexity. Withholding the download isn't very open as in open source / open core codebase.

Communicating self-managed versus managed offerings

There are typically two ways to consume software:
  1. Self-managed: Customers host the software themselves on their own technology and infrastructure (this is sometimes called on-premises but since most customers host at a hyper cloud self-managed is a better term).
  1. SaaS: The company provides access to its own technology and infrastructure

Examples:

  1. Use Cloud to explain its “You pay the bill”
    1. Posthog: https://posthog.com/pricing
    2. Consul: https://www.hashicorp.com/products/consul/pricing
    3. Jira: https://www.atlassian.com/software/jira/pricing
  1. Unless they sell an API, not an interface:
    1. MongoDB: https://www.mongodb.com/pricing
    2. Elastic: https://www.elastic.co/cloud/
    3. Redis: https://redis.com/redis-enterprise-cloud/pricing/