Learn About Licenses
Learning Objectives
After completing this unit, you’ll be able to:
- Explain the difference between Salesforce licensing and licensing for managed packages.
- Identify the different licensing options.
- List the stages in the customer lifecycle.
You’ve Built Your Solution—Now License It!
It’s been quite a ride, and you and your team have a lot to be proud of—your solution is ready for business! Now it’s time to sell it.
How do you sell your solution on the Salesforce platform? That’s a hefty topic, involving everything from marketing strategy to sales. For the business stuff, look at our AppExchange App Selling module.
Here, we focus on how you create a profitable business by selling licenses to your prospects, converting them to paying customers. Salesforce provides you with tools for managing licenses and for tracking prospects who install your package.
Later in the module, we discuss how you can provide support to your paying customers, keeping them happy and building your reputation as a great AppExchange partner. We give you some nifty tools to make it easier to troubleshoot problems and get your customers back in action in record time.
A License for Every Partner
When a prospect or customer installs your managed package, the contents of that package become available to users in that customer’s org according to the terms of your license. These terms dictate who can use your package, and how long they can continue using it.
You’ve completed our AppExchange App Strategy module, haven’t you? There we talk about the different types of AppExchange partners:
- AppExchange partners develop ISVforce solutions that run on the Salesforce platform, and they sell to Salesforce customers only.
- OEM partners embed the Salesforce platform in their own specialized solutions to sell to customers outside of Salesforce.
When you hear about licensing at Salesforce, it can mean any of these things:
- ISVforce and OEM solutions both come with user licenses that grant access to the managed package their creator distributes.
- OEM solutions also embed a Salesforce platform license with each managed package license.
- When you sign your Salesforce partner agreement, you license the use of Salesforce technology for your business. That license arrangement affects how you license your products to your customers, but it’s a separate agreement between you and Salesforce.
In this module, we discuss only the user licenses in the first bullet: the licenses you grant to your customers to allow them to use your package.
If you’re interested in more general licensing details, log in to the Salesforce Partner Community and get the lowdown on ISVforce and OEM licensing.
Explore Licensing Options
Your licensing scheme determines your revenue stream. Everyone’s business model is different, so Salesforce provides you with a couple of licensing options you can offer to your customers.
In deciding on a licensing approach, think about how you prefer to make your package available, and who your customers are. Do seat licenses make sense, or does everyone in an org want to use your package?
Per-User Licenses
You grant access to your package to a given number of users (seats) in a customer org. That org’s admin assigns seats to specific users in the org. If more users need access, you can give them more seats.
Site Licenses
Your package is available for use by all users in a customer’s org.
When customers install your package, they get the license that comes with the package by default. Whatever type of license you choose for the default, you can always adjust it later for specific customers. Suppose a customer decides to give your package a spin and buys five user licenses. After they realize how awesome your package is, they decide to roll it out to all 50 of their employees. Because they only have five licenses, the additional 45 users can’t use your package until you grant them more licenses.
We give you tools to work with your customers to meet their needs, adjusting license terms if and when it makes sense. We show you how in the next unit.
Free Trials and Time Limits
We offer you a variety of options for managing your customers’ licenses. Aside from controlling who gets to use your package, you can set a license to expire after a given duration. This lets you give your customers a free trial of your package, so they can decide whether they want a paid license.
Like license types, you can adjust these time limits to suit the needs of individual customers. You can also temporarily suspend a license if you want to limit access to your package within a customer org.
Free Solutions
If you’re releasing a free solution (and we mean “free” as in “costs no money”), your solution still comes with a license. Most free solutions are distributed with a site license to keep things simple.
If your free solution is part of a solution that you sell, however, it’s not really free. For example, if you already sell an off-platform solution, and you build an app to synchronize data between Salesforce and your paid solution, your data synchronizer isn’t free because its license is tied to your solution.
For more details on what we mean by free solution, look in the Salesforce Partner Program Policies document, available on the Salesforce Partner Community.
Manage New Features
As an AppExchange partner, you get special access to features on the Salesforce platform before they’re generally available (GA). What if you could offer the same sneak preview of new features to your own customers?
Good news, you can give your power users exclusive access to bleeding-edge features in your package using Feature Parameters. We give you three different options for doing this.
- Pilot features—Sometimes a feature isn’t GA, but it’s still useful to one or more of your intrepid customers. A pilot feature is a feature you can push out to certain users to see how they use it.
- Dark launches—If you’re shipping a new version of your package, but a feature isn’t quite ready for prime time, don’t rip it out of your code just yet. With a dark launch, you can ship your package with the feature disabled and enable it when you’re ready. This approach makes for more continuity and less drama.
- Two-step enablement—If the new version of your package has a feature that significantly changes how your customers use it, let them choose when to enable it. Two-step enablement gives a customer the new feature but keeps the feature disabled until the customer elects to start using it.
We elaborate on these options later in the module.
The Customer Support Lifecycle
Your relationship with a customer begins when that customer installs your package. If they like it, they pay you for a license. In return, you provide them with the package and make them feel extra special when they need a helping hand.
Your relationship with your customers follows our customer support lifecycle:
Customer Success Planning
Define a customer’s experience, starting with the installation of the package, and identify ways to help them achieve their goals.
Customer Support
Train your support staff on the Salesforce platform, and get them talking to customers.
Troubleshooting
Work with your customers to understand any issues they experience with your package in their orgs. In this module, we give you tools that make this process easier.
Release Management
Establish a plan for releasing updates to your customers. Are you using push upgrades, or do your customers upgrade manually? How do you communicate the upgrade process to customers? See our App Upgrading for AppExchange module for more details.
This cycle repeats as you plan and implement new features, take on new staff, evolve your marketing strategy, and grow your business.
Now that you’ve got the lay of the land, let’s talk tooling. In the next unit we introduce you to the License Management App, which does just what it says.