Essential Artifacts for OEM Program Rollout

Pre-Agreement Documentation & Initial Outreach

OEM Program Overview

One-page or webpage summary covering program benefits, features, and partnership terms.

Amanda Dorothy Hunt

External

Written

It exists - needs updating.

Sales Guide

Talking points, pricing, and benefits specifically for OEM ISVs.

Dorothy Hunt

Internal

written

TBD

Transition Guide:

How to transition from legacy to new. Additional features and benefits of full CCH license

Dorothy Hunt

External

written

TBD

Sales Enablement Training:

Teach Partner sales team to sell UC in their product.

Dorothy Hunt

External

written

TBD

Standard OEM Agreement

A legal template with clear licensing terms, updated by the legal team.

Legal

External

Written

TBD

Initial Document Setup

List of starting Authority Documents (IDs, names) for each ISV, referenced in the OEM agreement.

Customer Success & Sales

Internal

written

TBD

Onboarding and Account Configuration Guide

Onboarding Deck

• OEM Entitlement overview
  Define data types each ISV can access, like Authority Documents, Citations, Tagged Mandates, and Common Controls.

• CCH Entitlement Overview

• Comparison between OEM and CCH

Customer Success &

Product Management

External

Written

OEM-Onboarding-Deck.pptx

https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide

Account & Subscription Setup & Management Guide

Step-by-step guide for creating, configuring, and maintaining OEM partner accounts within UC’s systems (CCH or other systems), detailing the process for Sales and Dev.

CS, Sales, Dev/Product

Internal

Visual & Written

CCH OEM Vendor - Set up Steps

Lucid Chart

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?

Dorian Cougias Michael Maggio

Legal

Internal

Written

TBD

OEM Federated Data License

It needs to be incorporated in agreements.

• Partner needs to Agree to UC Federated Data license.

  • does partner need end-user acceptance of FDL in partner app?

• Agreement to UC federated data license in APPlicaiton

  • confirm how it is in the nextgen app.

• Future: may need to support and force users to accept content provider license

Dorian Cougias Michael Maggio

Legal

Review agreement with team.

External

TBD

CCH OEM Partners API Guide

Step-by-step guide for generating API keys and accessing data via API endpoints.

Development & Support

External

Written

CCH OEM Vendor - API Quick Start Guide

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.

Mark Redding Adam Vercimak Vicki McEwen

External

Visual & Written

TBD

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

TBD

FAQs

Commonly asked questions to guide OEM partners through their journey.

Customer Support & Product Management

External

Written

TBD

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

TBD

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

Lucid Chart

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.