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

# Planning Your Sale

> Key decisions for configuring your Sonar token sale

## Overview

When configuring a Sonar sale, you make two independent decisions:

1. **Pricing Strategy**: How is the token price determined?
2. **Settlement**: How are tokens allocated if demand exceeds supply?

## Pricing Strategies

Sonar supports two pricing strategies:

| Use Case | Pricing strategy | Result |
| - | - | - |
| Community sale, predictable experience | Fixed Price | Everyone pays the same price |
| Price discovery | English Auction | Market determines price via competitive bidding |

## What Sonar Does vs What You Do

| Responsibility | Sonar | Your Team |
| - | - | - |
| KYC/KYB verification | ✓ | |
| Wallet risk screening | ✓ | |
| Purchase permit issuance | ✓ | |
| Smart contract deployment | ✓ (standard configs) | Custom only |
| Settlement computation | | ✓ |
| Frontend/website | | ✓ |
| Token distribution | | ✓ |
| Vesting/lockup enforcement | | ✓ |

<Info>
  Sonar handles the sale infrastructure: collecting funds, enforcing compliance, and processing refunds. You decide how to allocate commitments, and Sonar syncs those decisions to the contract. Token distribution to buyers is a separate process managed by your team after the sale.
</Info>

## Next Steps

<CardGroup cols={2}>
  <Card title="Pricing Strategies" href="/sonar/planning/pricing-strategies" icon="tag">
    Fixed price vs English auction
  </Card>

  <Card title="Settlement" href="/sonar/planning/settlement-strategies" icon="layer-group">
    How settlement works after the commitment phase
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.