Artifact | Responsibility | Audience | Type | Status, Link/Location |
|---|---|---|---|---|
Pre-Agreement Documentation & Initial Outreach | ||||
OEM Program Overview One-page or webpage summary covering program benefits, features, and partnership terms. | External | Written | Exists - needs updating. | |
Sales Guide: Talking points, pricing, and benefits specifically for OEM ISVs. | Internal | written | ||
Transition Guide: How to transition from legacy to new. Additional features and benefits of full CCH license | External | written | ||
Sales Enablement Training: Teach Partner sales team to sell UC in their product. | External | written | ||
Standard OEM Agreement A legal template with clear licensing terms, updated by the legal team. | Legal | External | Written | |
Initial Document Setup List of starting Authority Documents (IDs, names) for each ISV, referenced in the OEM agreement. | Customer Success & Sales | Internal | written | |
Onboarding and Account Configuration Guide | ||||
Onboarding Deck
| Customer Success & Product Management | External | Written | https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide |
Account & Subscription Setup Guide Step-by-step guide for creating and configuring OEM partner accounts within UC’s systems (CCH or other systems), detailing the process for Sales and Dev. | Sales Operations & Customer Success | Internal | Visual & Written | |
Account and Subscription Management Flowchart Visual documentation outlining the lifecycle from new account creation through renewal, including roles and system interactions. | Product Management | Internal | Visual | |
UC Federated Data License Setup Instructions for assigning Federated Data Licenses within the OEM account, defining access permissions and entitlements. What can we share from IP-restricted documents? | Legal | Internal | Written | |
OEM Federated Data License It needs to be incorporated in agreements.
| Legal Review agreement with team. | External | ||
API Key Provisioning and Documentation Step-by-step guide for generating API keys. | Development & Support | External | Written | |
Sample Customer Journey for API Access Simple outline for an ISV customer’s end-to-end experience, covering account setup, API key access, and documentation handoffs. Use OEM Demo account. | Customer Success & Product Management | External | Visual | |
Schema Guide for Data Migration Visual and text documentation of the new data structures for each API endpoint, especially for transitions from old to new IDs and structures. | Development & Product Management | External | Visual & Written | |
FAQs Commonly asked questions to guide OEM partners through their journey. | Customer Support & Product Management | External | Written | |
Billing, Invoicing, and Reporting | ||||
Financial Reporting and Invoicing Guide Template and instructions for billing, invoicing, and financial reporting, tailored for OEM ISV partners. | Finance & Sales Operations | External | Written | |
Cross-Functional Collaboration and Handoff Processes | ||||
Handoff Summary Key handoff points for each team (e.g., Sales, Dev, Finance), including communication tools, points of contact, and role responsibilities. | Customer Success & Product Management * Sales | Internal | Visual & Written | |
Content Providers
Resources
PlantUML - https://UCFNextgen.ai/public/plantuml/956
Content Provider agreement template (signed with redistribution rights and compensation requirements) | |
Content Provider subscription plan/add-on set up. | |
Content Provider account set up including CP designation in our backend for entitlement verification that UC has rights to redistribute their content and for usage reporting. Yes, an organization can be a Content Provider, ISV, and a reseller. | |
Content Provider entitlement set up in our backend for entitlement verification which ISVs and customer accounts are entitled to receive redistributed Content Provider content. | |
Content Provider renumeration based on subscription content usage. | |
Content Provider usage reporting by subscription plan with associated accounts, by AD with associated accounts and by Accounts with associated ADs. |