Partner guide
Write a white-label brief that covers more than the logo
Clarify the customer experience, commercial rights and service ownership.
Define the customer and workflow
Name the buyer you intend to serve, the problem you understand and the initial workflow you want to offer. Start with a specific proposition before expanding to a portfolio.
Specify the visible experience
Document the name, colours, domain, sender identity, client-facing language and portal scope. Decide which parts of the system the end customer will see and who controls those settings.
Describe customer boundaries
Identify access roles and the required separation between customer records and environments. Ask how those boundaries will be demonstrated during acceptance. Avoid assuming shared tenancy or automated provisioning already exists.
Own the support relationship
Agree first-line support, escalation, maintenance, provider billing and changes. Customers need a clear route for help; the partnership needs a sustainable service model.
Separate hosting from rights
Resale rights, source licensing and ownership are contractual decisions. A branded deployment does not automatically transfer intellectual property or create unlimited deployment rights.