## Role map

Beacon operations usually involve five core personas:

- `Owner`: sets business goals, approves go-live, owns risk.
- `Admin`: configures organization, access, and governance.
- Reconciliation owners: monitor reconciliation, month-end close, and reporting.
- `Developer`: builds APIs, webhooks, and automation.
- Operations owners: handle incidents and status communication.

## Recommended path by persona

| Persona | First week | Expected outcome |
| --- | --- | --- |
| Owner | Quickstart + go-live checklist | Launch approval with clear acceptance criteria |
| Admin | Configure workspaces + manage members | Stable team structure and permissions |
| Reconciliation owners | Configure compliance + month-end close | Repeatable fiscal process |
| Developer | Connect Stripe + configure webhooks + API essentials | Robust, auditable integration |
| Operations owners | Support operations playbook + incident runbooks | Consistent incident response |

## Cross-functional sequence (Stripe-style)

<Steps>
  <Step title="1) Define organization ownership">Set technical and operational owners for billing, webhooks, fiscal, and support.</Step>
  <Step title="2) Prepare test mode">Complete onboarding and validate every flow with test data.</Step>
  <Step title="3) Formalize go-live criteria">Move to live only after observability, alerts, and runbooks are validated.</Step>
  <Step title="4) Operate with cadence">Keep weekly rituals for incidents, backlog review, and change control.</Step>
</Steps>

<Note title="Best practice">In early stages, one person can hold multiple roles. What matters is explicit accountability per process.</Note>