# White-label platform acceptance worksheet

Source: https://lindo.ai/guides/how-to-start-a-white-label-web-design-business
Updated: 2026-09-03
Published by: Lindo Team

Includes role tests, brand-surface checks, a responsibility map, cost assumptions, and an exit rehearsal.
Illustrative planning aid, not market data or a guarantee. Do not store credentials or private client data here.

## Working brief

### Service model / provider / plan / test date

- Notes:
- Owner / decision:
- Evidence / next action:

### Workflow / expected behavior / observed behavior / evidence

- Notes:
- Owner / decision:
- Evidence / next action:

### Invitation, sign-in, editor, support and notification branding

- Notes:
- Owner / decision:
- Evidence / next action:

### Client role permissions and workspace isolation

- Notes:
- Owner / decision:
- Evidence / next action:

### Fixed costs / variable costs / support allowance

- Notes:
- Owner / decision:
- Evidence / next action:

### Incident owner / escalation route / client communication

- Notes:
- Owner / decision:
- Evidence / next action:

### Domain owner / content archive / transfer limits

- Notes:
- Owner / decision:
- Evidence / next action:

### Pilot exceptions / decision / next review

- Notes:
- Owner / decision:
- Evidence / next action:

## Acceptance checklist

- [ ] The offer distinguishes managed service, self-service, and fulfillment.
  Owner / evidence / date:

- [ ] Client-role access and brand surfaces have been tested.
  Owner / evidence / date:

- [ ] Critical website functions work on the intended plan.
  Owner / evidence / date:

- [ ] Costs include support time and low-client-count scenarios.
  Owner / evidence / date:

- [ ] Support, incident communication, and provider escalation have owners.
  Owner / evidence / date:

- [ ] Domain, content, billing, and exit responsibilities are documented.
  Owner / evidence / date:

- [ ] A complete pilot is reviewed before expansion.
  Owner / evidence / date:

## Examples and templates from the guide

### Platform acceptance test

Workflow: invite a client editor to the pilot site.
Role and plan tested: [record].
Expected: only the intended site and editing controls are visible.
Test: sign in separately; inspect navigation, billing, publishing and support.
Observed result: [record with evidence].
Brand surfaces: invitation, sign-in, recovery, editor, notifications.
Unresolved limitation: [record].
Decision: accept / change the offer / reject.

## Working tables

### Responsibility questions to resolve

| Task | Possible owner | Evidence to request |
| --- | --- | --- |
| Website editing | Agency or client | Test using the intended role |
| Infrastructure incident | Provider, coordinated by agency | Escalation path and service terms |
| Content accuracy | Client with agency review | Named approver and record |
| Billing and cancellation | Depends on service model | Example invoice and exit workflow |

## Sources and next steps

- Understand cost, markup, and margin: https://lindo.ai/guides/how-to-price-website-design
- Check current Lindo pricing: https://lindo.ai/pricing
- Define the service boundary before selling: https://lindo.ai/guides/how-to-package-website-services
- Define incident handling and monthly evidence: https://lindo.ai/guides/how-to-create-website-maintenance-plans