> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thesozocrm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Launch Sozo CRM for your sales team with a clean, customer-first setup checklist.

# Quickstart

Get your team live fast and avoid rework later.

## 1) Set up your workspace

<Steps>
  <Step title="Create your core team">
    Add one admin, at least one manager, and one rep before importing deals.
  </Step>

  <Step title="Confirm role boundaries">
    * **Admins**: full system access
    * **Managers**: team-wide visibility
    * **Reps**: own pipeline and earnings visibility
  </Step>

  <Step title="Turn on notification channels">
    Decide which alerts should go to email, in-app notifications, and team chat.
  </Step>
</Steps>

## 2) Configure your operating flow

<CardGroup cols={2}>
  <Card title="Pipeline Stages" icon="kanban">
    Define the exact stages your team runs every day.
  </Card>

  <Card title="Commission Rules" icon="dollar-sign">
    Lock in split rules, payout milestones, and exception handling.
  </Card>

  <Card title="Installer Handoffs" icon="link">
    Define required fields so installs never get blocked by missing data.
  </Card>

  <Card title="Rep Visibility" icon="eye">
    Make sure reps can track earnings and stage movement in real time.
  </Card>
</CardGroup>

## 3) Connect integrations

Start with the high-impact connectors first:

* Proposal/design tool
* Messaging/notification channel
* Accounting or payout source

<Tip>
  Keep phase 1 simple: connect only what your team uses every day, then expand.
</Tip>

## 3.1) Technical launch checklist

Use this if your ops lead or developer is handling implementation details:

<Check>
  Confirm role-based access paths using one real user per role.
</Check>

<Check>
  Verify integration payloads use stable IDs (not names) for matching.
</Check>

<Check>
  Confirm retry-safe behavior for inbound webhook or automation events.
</Check>

<Check>
  Add alerting for failed syncs before opening rollout to the full team.
</Check>

## 4) Train and launch

<Steps>
  <Step title="Run a dry-run week">
    Use real deal scenarios with a small test cohort before full rollout.
  </Step>

  <Step title="Publish operating rules">
    Document required fields, stage ownership, and handoff SLA expectations.
  </Step>

  <Step title="Go live with scorecards">
    Track adoption by stage movement, handoff quality, and payout confidence.
  </Step>
</Steps>

## Next steps

* **[Account & Access](/account-and-access)** - Role setup and security baseline.
* **[Integrations](/integrations)** - Connect Sozo to your daily stack.
* **[MCP Setup](/mcp)** - Use your hosted docs MCP endpoint with AI tools.
* **[API Reference](/api-reference/introduction)** - Auth and integration implementation patterns.