Per-feature pricing models are the most common for platforms that have nailed down their base pricing and now expanding secondary, add-on functionality. The model is combined with the Per-user pricing model to control access to the additional features.
Before we begin you should decide if your product or service will be using a monthly or yearly pricing strategy. Meaning will you be charging your users a license fee once a month or once a year?
<aside class="callout">💡 This is only for a SKU’s pricing and not it’s billing. RevOps provides a Billing Frequency term to allow you to bill customers at a different interval than your pricing.</aside>
To create a Per-feature priced SKU, you need to start by going to the SKUs settings page (Hover on Settings, click the 1st item in the list, SKUs).
Once there, create a new SKU using the Create SKU button. In the Create New SKU modal, from the Select a pricing model dropdown, select:
Fill in all relevant information for your SKU. The SKU Name will be used only within RevOps while the Line Item Title will be what your customer sees. Update the Unit Name to something like “support cases” or “profiles”. Include any specifying language in the Description field, like how overages or upgrades will be handled.
Once done filling in information on the Product Info tab, continue on to the Pricing tab and confirm your List Price, Currency, and that the Unit Pricing Schedule is set to either “Month” or “Year”, depending on what you selected in the Create New SKU modal.
After you’re happy with how you’ve set up your SKU, scroll to the bottom of the page, and click the Save button in the bottom right corner.
To start quoting, head to RevOps, and click on the Create Deal button in the top right corner. On the deal, click the Add SKUs button to create a new line item with our new per-feature SKU. Click the Done button to create a pricing table, titled "Subscription" by default, with your SKU as a line item. To learn more about how to adjust the display of this table, take a look at this article.
Now we can adjust the Quantity sold and apply a Discount, if appropriate. Though this is a Per-feature SKU, you will want to set the Quantity to the number of licenses or seats the customer is looking to buy unless you have structured your features to have a Flat-rate pricing model.