Product Prioritization

Company’s 2022 Goal:Demonstrate venture scale growth by tripling the annual recurring revenue (ARR) by:

Doubling total sites to 44000.

Increasing paying sites to 8500.

Maximizing the average revenue per site to X.

Main Target Customers:Teams of professional developers who are building performant content-backed websites.

Internal teams at large organizations that are using Gatsby to build large sites or large batches of sites.

Teams of digital agencies building many websites for many clients each year.

Theme:Double down on Cloud Platform Growth.

Ensure we are addressing the most critical objections from our Agency and Enterprise teams that want to use Cloud.

The RICE scoring system is a quantitative approach to prioritize product features based on four key metrics on a scale from 1 to 10 that are used as inputs to calculate the RICE score. The higher the RICE score, the higher the efficiency of investing in a given feature.

*No dependencies, cannibalization, or external constraints are taken into consideration for this exercise.

*No “moonshot ideas”: If Gatsby Cloud is looking to prioritize high investment/high rewards initiatives I would add different weights into the scoring metrics to give merit to these “moonshot ideas”.

This feature would only reach users that belong to organizations (most likely not using a personal Git repo) that are using the free tier of Gatsby (Reach = 5) and would have a high impact on Gatsby’s ARR (Impact = 7). There is split confidence in the effectiveness of this strategy as it can drive revenue as well as churn users away (Confidence = 5) and would require a relatively low level of effort to build (Effort = 2).

This feature would only affect the subset of our users that are agencies (Reach = 3) but could drive a lot of new businesses for them and subsequently for us as well by demonstrating Gatsby’s value proposition to users (Impact= 7). There is high confidence that agencies would desire such a feature (Confidence= 8) that requires a low amount of team effort (Effort = 2).

This feature was requested (Confidence = 10) and would primarily cater to only one or a few customers (Reach = 1). This potential large deal would have a significant impact on Gatsby’s ARR (Impact = 5).*This feature would be quite labor-intensive (*Estimated Effort = 5), however in practice (based on the focus theme for Gatsby Cloud),the investment cost on this feature would be covered by the addition of a new large customer, hence the Effective Effort would rather be low (Effort = 1). *

This feature would only affect the subset of our users that are linked to agencies (Reach = 3).Agencies would most likely desire such a feature (Confidence = 8) because it would make it easier for their clients to join Gatsby Cloud without friction (Impact= 6). It would require a low amount of team effort (Effort = 3)

This feature would reach most of our existing Gatsby users (Reach= 8), there is high confidence that users would appreciate it (Confidence = 7)and it would require a low level of effort to build (Effort = 3) but it would not necessarilybe a key driver for our ARR (Impact = 2).

This feature would mostly affect new and non-technical users (Reach = 5) but it could also make it a lot easier for anyone to use Gatsby, which could potentiallyhave a positive impact on Gatsby’s ARR (Impact= 4). Even when our core user base is made of developers, this feature can be quite desirable to our users for quick prototyping (Confidence = 6). However, this feature would be quite labor-intensive to develop (Effort = 5).

This feature would reach up to 2 million new WordPress users per year (Reach = 10) that can become paid users in the future based on Gatsby’s current 20% conversion rate(Impact = 2).There is high confidence because it is a feature that has been proven with “Shopify starter” (Confidence = 7), however, this feature would be very labor-intensive (Effort = 7).

This feature would only be relevant to large scale advanced users which most likely represent less than 20% of our total user base (Reach = 2),but building an important tool for our advanced users would potentially have a positive impact on their ability to create more paid Gatsby powered websites (Impact = 7). There is high confidence that this tool would be desirable to Gatsby Cloud users (Confidence = 8), however, this feature would be quite labor-intensive (Effort = 7).