# Customer kickoff prerequisite selection

Illustrative planning brief; no automatic product import.

Illustrative case: A new customer lacks a named data contact before onboarding starts.

## Decision

Start orientation while holding data preparation.

## Owned work

- Identify usable inputs
  - Owner role: Onboarding coordinator
  - Acceptance evidence: The contact gap is recorded.
- Split onboarding stages
  - Owner role: Customer enablement contributor
  - Acceptance evidence: Orientation excludes data-dependent exercises.
- Accept the first session
  - Owner role: Customer readiness reviewer
  - Acceptance evidence: The customer confirms its orientation purpose.

## Workflow

1. Record that the customer has no named data contact and identify which exercises need that input.
2. Prepare an orientation agenda limited to goals, roles and the operating overview; exclude data preparation and implementation demonstrations.
3. Ask the customer to accept that limited session purpose and name the contact needed to open the next stage.

## Judgment

An onboarding session does not prove implementation readiness.


## Filled illustrative planning example

Synthetic kickoff: orientation covers roles and the report purpose. Import preparation remains blocked until a customer data contact is confirmed. Attendance closes only the orientation stage, not implementation readiness.


## Workflow questions

### Can orientation proceed without data?

Yes, if no data-dependent result is promised

### Who selects the data contact?

The customer confirms its representative

## Product connection

Adapt the stage tasks, owner roles and acceptance evidence to your TeamBoost planning workflow. The example does not create customer records or import an onboarding plan.

Confirm account availability before adopting this manual outline.