We brought together Sean Hogan, CRO of CodeScience, and Melissa Burnell, Director of AppExchange Partnerships at Salesforce, to share a master`s session to accelerate your partnership agreement. For the first time in our series, we reviewed the partnership agreement process with Salesforce. Doing your partnership agreement correctly is essential because it creates the necessary conditions for your entry into the market. and unless you`ve already experienced it, there are Gotchas on the way that you can really slow down if you`re not careful. These two things will slow you down and lead you to the deadlock in the agreement on revisions and revisions. Melissa recommends talking to your Account Manager (PAM) partner to check your application name and description before submitting it. To give you a starting point, she gave an example of description. The bold text is the place where you would place your own information: when developing your partnership agreement, you must provide your application name and a description of the performance of your application. This is very different from what you will eventually make available in your Public AppExchange entry. Some partners who are navigating this process for the first time see this as an opportunity to enthuse Salesforce with marketing messaging, or, worse, they may not have a good understanding of their skills and leave the description too vague to get an idea of what it actually does. Salesforce takes security seriously when it comes to apps that are allowed on AppExchange.

The partnership agreement should therefore not be surprised that safety and compliance are also at the centre of the concerns. There are two areas where compliance can slow things down. Q: Is the new technology and marginal model applicable to consulting partners? A: No, these changes only affect partners who have ISV agreements. Q: What happens if my trailblazer score is wrong? A: If you think your trailblazer score may be wrong, please be aware of this. Another aspect of the ISVforce partnership is that ISVforce customers can develop or expand your application using custom objects. The advantage is more flexibility and scalability in evaluating your entire opportunity in the market. This is not possible with the OEM Embedded partnership. If you`re trying to understand at the highest level the difference between the OEM Embedded and ISVforce partnership types, think of the ISVforce partnership as a way to sell your app to existing Salesforce customers via AppExchange. Speed up your business with AppExchange Q`s new affiliate program: How can I access my new benefits? A: For more information on access to exclusive benefits and technologies, see the program manual.

Read the program guide > The ISVforce Partnership is the most common way to work with Salesforce. These apps typically extend Salesforce`s functionality in one way or another – they`re an add-on that fills the ecosystem void. For many who want to develop an app on the AppExchange, they recognize that many of their customers and prospects are already using Salesforce and want to use their app where their target market is. Typically, this requires an extension of the sales offer or cloud service (salesforce part) in one way or another, so it`s a win-win situation for the partner and Salesforce. Partners interested in registering the marginal PNR model should complete and submit the de minimis royalty form to understand eligibility and other requirements for the marginal NNP framework. Q: How do I get the PNR discount as soon as I get the first volume of value from the annual order? A: Once a partner is registered in the “Marginal Royalty Model” and has an annual value (AOV) of more than USD 1,000,000, the update of the partner`s product list is automatic and the new pnr adaptation will be reflected in future orders. For some business offers, a solution can be a mixture of the two types of partnership. This is perfectly acceptable to Salesforce.