Pre-Launch
Onboarding Framework
Cumulus · MetaPix

Why This Exists Before the Products Launch

The onboarding infrastructure built for myDW and Spectrum Enterprise — the SOP, the email sequence, the dealer enablement kit, the Salesforce pipeline, the webinar framework — applies directly to DW Cumulus and DW MetaPix. The process is the same. The products are different.

Building this framework now, before launch, means DW Cumulus and DW MetaPix enter the market with a tested, structured dealer onboarding system on day one. Every new product that launches without an onboarding framework inherits the same activation gap that currently affects myDW. This document prevents that from happening twice.

Placeholder fields are marked throughout. As product details are confirmed — pricing, platform URLs, SLA terms, channel counts, key structure — they drop into this document and it becomes a complete, live SOP.

What We Know — and What We Still Need

The following profiles capture confirmed product information alongside open placeholders. Update as details are received from the product team.

What Transfers Directly From myDW / Spectrum Enterprise

Every asset built for the existing MSP products applies to Cumulus and MetaPix. The table below identifies what can be used as-is, what requires product-specific adaptation, and what needs to be built new once product details are confirmed.

How the Onboarding SOP Changes for New Products

The 7-step onboarding SOP applies identically to Cumulus and MetaPix. The steps below are color-coded by what stays the same, what requires minor adaptation, and what is a genuine unknown pending product confirmation.

What Needs to Be Confirmed Before Launch

The following questions must be answered by the product team for each new platform. Assign to the appropriate internal contact and track to resolution. This list is the pre-launch discovery agenda.

DW Cumulus

• QWhat is the core product function — cloud storage, VMS, VSaaS, or something else?
• QWhat is the pricing model and MSRP? Per-camera, per-site, or something different from myDW?
• QAre subscription keys the mechanism — 12 and 36-month terms as with myDW — or a different commercial structure?
• QDoes Cumulus have its own CP portal, or does it share the existing myDW or Spectrum Enterprise portal?
• QIs there a free trial component? If so, what is the duration and how is it initiated?
• QWhat is the SLA? Is a draft document available for the MSP contact form?
• QWhat is the target customer vertical — same as myDW, or different use cases?

DW MetaPix

• QWhat is the core product function — AI analytics, metadata processing, or a hybrid service?
• QWhat is the pricing model and MSRP? Does it follow the per-camera model or a different structure?
• QDoes MetaPix require specific DW hardware to function, or is it platform-agnostic?
• QIs there an existing CP portal, or will this be new infrastructure?
• QIs MetaPix sold alongside myDW (bundled) or as a standalone subscription?
• QWhat is the SLA? Is a draft document available for the MSP contact form?
• QWhat customer profile benefits most — AI-forward enterprise, specific regulated verticals?

Everything That Must Be Done Before Day One

Work through these in order. Items tagged Both apply to all new MSP products. Items tagged with a specific product name are platform-specific.

• BothAnswer all open questions in Section 4. Assign each to a product team contact with a deadline.
• BothAdd product options to the MSP contact form — platform selection and SLA acceptance per product.
• BothAdd CP Org Number fields to Salesforce (CP_Org_Cumulus__c · CP_Org_MetaPix__c) — send updated admin brief.
• BothUpdate the MSP_Platforms__c picklist in Salesforce to include DW Cumulus and DW MetaPix.
• BothUpdate the Monthly Leadership Dashboard — move platform rows from "pre-launch" to active status on launch date.
• CumulusComplete product profile fields in Section 2 of this document — pricing, URL, SLA, key structure, CP portal.
• MetaPixComplete product profile fields in Section 2 of this document — pricing, URL, SLA, key structure, CP portal.
• CumulusDocument provisioning steps in the SOP (Step 5) by walking through the platform UI pre-launch.
• MetaPixDocument provisioning steps in the SOP (Step 5) by walking through the platform UI pre-launch.
• CumulusWrite Dealer Enablement Kit — value proposition, conversation opener, pricing math, objection handlers, best-fit customers.
• MetaPixWrite Dealer Enablement Kit — same structure as Cumulus version above.
• CumulusWrite End-User Awareness One-Pager — non-technical, benefit-led, CTA points to dealer.
• MetaPixWrite End-User Awareness One-Pager — same structure as Cumulus version above.
• BothUpdate Touch 1 email template — add platform-specific blocks for each new product.
• BothUpdate Touch 2–3 email templates with product-specific value proposition language and pricing math.
• BothUpdate CPP awareness sequence (Touches 1–3) to reference new products.
• BothAdd new product segments to the Dealer Webinar — run of show updated with platform-specific content.
• BothRun the Free Trial Conversion Analysis discovery process if a free trial exists for either product.
• BothRecord a webinar session for each new product and add the link to the Touch 2 email template.
• BothConfirm that the Automated Onboarding Workflow (Proposal 1) has been updated to include new platform provisioning triggers.
• BothBrief your Senior Director on launch readiness at the weekly meeting the week before launch — use the dashboard to frame the conversation.

Amendment Log

Record every update to this document as product details are confirmed. This log is the audit trail that shows the document was actively maintained from pre-launch through to go-live.