> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/business-and-setup-context/brand-onboarding-workflow.md).

# Brand onboarding workflow

High-level onboarding flow, ownership, and launch checklist for a new MVNO brand.

### Overview

Use this workflow to take a new **MVNO brand** from **kickoff to launch**.

Use the companion onboarding pages in this section for exact fields, asset specs, and broader platform scope.

### At a glance

* **Brand provides** inputs and assets.
* **Reach configures** the tenant and journeys.
* **Brand reviews** staging and signs off.
* **Reach launches** production.
* **Brand + Reach** run post-launch changes through a controlled request process.

### Workflow

{% stepper %}
{% step %}

#### Kickoff and scope

Confirm what you’re launching. Lock **owners**, **dates**, and **sign-off criteria**.

Decisions to confirm:

* **Brand name** and **legal entity**
* **Service availability model**
* **Plans and pricing model**
* **Support model**
* Any required add-ons

**Output:** scoped launch plan and owners.
{% endstep %}

{% step %}

#### Provide onboarding inputs

Share the required **business details** and **brand assets**.

Brand provides:

* Completed onboarding inputs (fields + assets)
* Credentials and IDs for any brand-owned integrations (if applicable)

**Output:** onboarding packet marked complete.
{% endstep %}

{% step %}

#### Reach configuration and build

Reach sets up your **tenant**, **journeys**, **content**, and **policies**.

Common parallel workstreams:

* **Domain readiness**
* **Marketing and analytics tags**
* **Support tooling and contact points**
* Optional device store enablement

**Output:** staging environment ready for review.
{% endstep %}

{% step %}

#### Staging review and acceptance

Validate the **end-to-end customer experience**.

Minimum checks:

* **Homepage content** renders correctly across devices
* **Plan selection**, **checkout**, and **payment descriptor**
* **Eligibility gates** behave as intended
* **Support contact details** are correct
* **SEO** and **social cards** preview correctly when shared

Payment rules, fraud controls, and purchase screening should be confirmed before sign-off.

**Output:** sign-off to launch.
{% endstep %}

{% step %}

#### Launch and post-launch rhythm

Reach takes production live after sign-off. Then the program moves into BAU operations.

Align on:

* **Escalation path** and **operational contacts**
* **Reporting cadence** and **distribution lists**
* Who approves future **catalog**, **content**, and **policy changes**

Most BAU changes later route through the catalog, communications, or bolt-on change process.

**Output:** brand live, with an operating rhythm.
{% endstep %}
{% endstepper %}

### Suggested owners (minimum)

* **Brand onboarding owner:** accountable for inputs and sign-off.
* **Reach onboarding lead:** accountable for configuration and launch.
* **Brand marketing owner:** content and SEO approvals.
* **Brand care/ops owner:** support model, contacts, and escalation readiness.

### Also read

* [Brand onboarding configuration](/business-and-setup-context/brand-onboarding-configuration.md) for the exact fields and assets required before launch
* [Reach Platform offering](/foundation-platform-overview/reach-platform-offering.md) for the standard scope and operating model
* [Payments, fees, and compliance](/core-product-structure/product-catalog-offering/payments-fees-and-compliance.md) for checkout, payment, and dunning rules
* [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md) for add-ons that can affect scope and timeline

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reachplatform.com/business-and-setup-context/brand-onboarding-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.