PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

Deliverablesdeliverable
deliverable

Partners Hub Expansion Figures

Canonical expansion figures for the partner-program hub.

Public sample
Client deliverable
public-sample
System
Partners Hub Expansion Figures
Environment
Production pilot

# Partners Hub Expansion Figures

HUB-04

Partner Motion Selector

What does the partner want to own?

Decision selector routing a partner to embed, sell, deliver, integrate, or train motions based on what the partner wants to own.

decision point

What does the partner want to own?

gate

Embed

Choose when the partner wants to own the end-to-end product and customer experience.

1

Owns the product and UX

2

Best fit: OEM and scanner providers

3

SecEng supplies: headless engine and canonical objects

gate

Sell or resell

Choose when the partner wants to own the sales and commercial relationship.

1

Owns market access and the sale

2

Best fit: resellers and marketplaces

3

SecEng supplies: proof, packaging, and fulfillment

gate

Deliver or managed service

Choose when the partner wants to own service delivery and the client engagement.

1

Owns delivery and the client

2

Best fit: MSSP and consulting partners

3

SecEng supplies: workflows, evidence, and retest

gate

Integrate or technology partner

Choose when both products stay independent and only need to exchange data.

1

Owns a complementary product

2

Best fit: technology and interoperability partners

3

SecEng supplies: canonical contracts and round trip

gate

Train, academy, or distribution

Choose when the partner wants to own branded learning and content distribution.

1

Owns the learning channel

2

Best fit: LMS, marketplace, and academy

3

SecEng supplies: packaged courses, labs, and events

HUB-05

Commercial Path Overview

A partner engagement moves from motion selection and representative proof through commercial fit, integration, launch, and expansion.

Six-stage partner path from motion selection and application through pilot, commercial fit, integration, launch, and expansion.

Select the partnermotionSTEP 1Apply and qualifySTEP 2Run representativeproofSTEP 3Confirm commercial fitSTEP 4Integrate and validateSTEP 5Launch and expandSTEP 6Program controlsPartner ownership remains explicit • Pilot and production statesremain distinct • Expansion follows evidence, not aspiration