PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

BL-03

From branded pilot to partner-operated offer.

Branding is only one part of launch; the operating path also needs tenant provisioning, offer configuration, acceptance, support, upgrades, and commercial governance.

governed lifecycle

Launch lifecycle
  1. 1
    Select licensing model
  2. 2
    Configure brand and theme
  3. 3
    Configure offer and catalog
  4. 4
    Provision tenant
  5. 5
    Acceptance test
  6. 6
    Partner launch
  7. 7
    Operate and support
  8. 8
    Versioned upgrade
Decision gate
  • Ready to launch
  • Conditional launch
  • Revise and retest
  • Hold launch

About this figure

This diagram describes the governed lifecycle for turning a branded pilot into a partner-operated offer. It shows that launch is not complete when the brand and theme are configured: the full operating path also includes offer and catalog setup, tenant provisioning, acceptance testing, partner launch, ongoing support, versioned upgrades, and commercial governance. The lifecycle makes exception states explicit, including brand or domain gaps, acceptance failures, and unresolved support boundaries, so launch readiness can be assessed before handoff. Once live, the partner offer remains monitored for usage and entitlement, while support responsibilities, version provenance, and upgrade history are retained to preserve control across the offer’s operational life.

Embed in a route

<FigureFromSource sourcePath="content/publications/figures/partners/brand-licensing.dsl.md" figureId="BL-03" />

Citation

From branded pilot to partner-operated offer. (BL-03). AI Security LLC Figure Library. https://aisecurity.llc/publication-dsl/figures/BL-03