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

# Creating Quotes

> How to create and edit quotes in CharleOS

Creating quotes in CharleOS involves a multi-step wizard that guides you through capturing client requirements and scope.

## Creating a new quote

### Access

Navigate to:

* Sidebar → **Quotes**
* Click **Create Quote Request**
* Multi-step wizard opens

### Who can create

* CSMs
* Project Managers
* Managers
* Not available to Delivery Team

<Note>
  Clients can submit quote requests via the client portal, which follow the same workflow but have a "client\_request" origin.
</Note>

## Quote creation wizard

### Step 1: Overview

Basic quote information:

**Required fields:**

* **Client** - Select from dropdown
* **Title** - Brief description (max 200 characters)
* **Description** - Detailed rich text overview
* **Requirement types** - Select at least one:
  * Design
  * Development
  * SEO
  * Retainer

<Tip>
  Choose requirement types carefully - you'll provide detailed scope for each selected type in the next steps.
</Tip>

### Step 2: Design (if selected)

If you selected "Design" requirement:

**Required fields:**

* **Goal** - What the design aims to achieve
* **Design types** (select at least one):
  * UI/UX Design
  * Visual Assets
  * Brand/Identity
  * Marketing Materials
  * Prototypes
* **Timeline**:
  * Flexible
  * Within 2 weeks
  * Within 1 week
  * Urgent (ASAP)

**Optional fields:**

* **Target audience** - Who the design is for
* **Reference links** - Examples or inspiration
* **Brand guidelines** - Yes/No (provides context)

### Step 3: Development (if selected)

If you selected "Development" requirement:

**Required fields:**

* **Goal** - What the development aims to achieve
* **Work type**:
  * New Feature
  * Enhancement
  * Bug Fix
  * Integration
  * Performance Optimization
  * Other
* **Expected outcome** - What should happen after implementation
* **Timeline** - Same options as Design

**Optional fields:**

* **Current behavior** - For enhancements/bug fixes
* **Relevant links** - Related pages or resources
* **Technical constraints** - Limitations or requirements

<Info>
  For bug fixes or enhancements, describing current behavior helps provide accurate estimates.
</Info>

### Step 4: Review

Final step before submission:

* Review all entered information
* Check requirement types selected
* Verify client and title
* Go back to edit if needed
* Click **Submit** to create quote

## After creation

### Quote status

New quotes start as "awaiting\_quote":

* Ready for team to work on estimates
* Can assign team members
* Can edit requirements

### AI T-Shirt Size Suggestions

When a quote is created, Alan automatically generates t-shirt size suggestions for each requirement. These suggestions appear in the requirement details:

<Info>
  **Alan suggests: Medium**

  "Based on similar development work for this client and their deliverability score (tasks typically take 10% longer than quoted), a Medium size is recommended for this feature implementation."
</Info>

The AI considers:

* **Brief details** - Goal, expected outcome, technical constraints
* **Client history** - Similar tasks and how they performed
* **Deliverability score** - Whether this client's work typically runs over or under

#### Confidence Levels

Suggestions include a confidence level:

* **High**: Clear scope with good historical data
* **Medium**: Reasonable information to make an estimate
* **Low**: Limited information - treat as a starting point

#### Using Suggestions

Team members can:

1. **Accept** the suggestion by selecting that t-shirt size
2. **Override** by choosing a different size based on their expertise
3. Review the reasoning to understand Alan's logic

<Tip>
  AI suggestions are most accurate for clients with good historical data. For new clients, use the suggestions as a starting point but apply extra judgment.
</Tip>

### Next steps

1. Assign team members to provide estimates
2. Team members complete requirements (with AI suggestions available)
3. When all requirements complete → "quoted"
4. PM/CSM reviews and approves
5. Send to client for approval

## Editing quotes

### When you can edit

Quotes can be edited until approved:

* ✅ **Awaiting Quote** - Full editing
* ✅ **In Progress** - Full editing
* ✅ **Awaiting CSM Review** - Full editing
* ✅ **Awaiting Client Approval** - Full editing
* ❌ **Approved** - Cannot edit (task created)
* ✅ **Rejected** - Can edit and resubmit
* ✅ **Cancelled** - Can edit after reopening

### What you can edit

**Basic details:**

* Title
* Description
* Client (before approval)

**Requirements:**

* Scope content
* T-shirt sizing
* Brief details

**Cannot change:**

* Requirement types (cannot add/remove)
* Quote origin

<Warning>
  Editing a completed requirement marks it as incomplete again. The quote will return to "in\_progress" status.
</Warning>

## Client-created requests

### How clients create requests

Clients use the portal:

1. Navigate to **Quotes** → **New Request**
2. Similar wizard but simplified:
   * No client selector (auto-filled)
   * Only Design and Development options
   * Same required fields
3. Submit creates quote with `origin: "client_request"`

### Processing client requests

When a client submits a request:

1. Appears in CSM's quotes list
2. Marked as "client\_request" origin
3. Status: "awaiting\_quote"
4. CSM assigns team to provide estimates
5. Follow normal workflow

### Differences from internal quotes

Client requests:

* Cannot select client (auto-filled)
* No SEO or Retainer options
* Cannot be edited by client after submission
* CSM must handle all edits

<Tip>
  Client requests often need clarification. Contact the client before starting estimates if anything is unclear.
</Tip>

## Assigning team members

### Who to assign

Assign based on requirement type:

* **Design requirements** → Designers
* **Development requirements** → Developers
* Multiple assignees allowed

### How to assign

1. Open quote detail page
2. Click **Assign**
3. Select team members
4. Team members notified
5. They can work on requirements

### Assignee responsibilities

Assigned team members should:

* Review requirement scope
* Provide t-shirt size estimate
* Add detailed scope content
* Mark requirement complete when done

## Common creation scenarios

### Scenario 1: Simple bug fix quote

**Steps:**

1. Select client
2. Title: "Fix checkout button issue"
3. Select **Development** only
4. Work type: Bug Fix
5. Describe current behavior and expected outcome
6. Timeline: Within 1 week
7. Submit

**Result:** Quick quote with single development requirement

### Scenario 2: Full redesign quote

**Steps:**

1. Select client
2. Title: "Homepage redesign"
3. Select **Design** and **Development**
4. Design: UI/UX Design, target audience, references
5. Development: New Feature, expected outcome
6. Both timelines: Flexible
7. Submit

**Result:** Comprehensive quote with both requirements

### Scenario 3: Client-submitted request

**Client submits:**

* "Add product filtering to collections"
* Development requirement
* Describes desired functionality

**CSM actions:**

1. Review request
2. Clarify if needed (via comments)
3. Assign developer
4. Developer provides estimate
5. CSM reviews and sends to client

## Best practices

<CardGroup cols={2}>
  <Card title="Detailed descriptions" icon="align-left">
    More detail = more accurate estimates
  </Card>

  <Card title="Relevant attachments" icon="paperclip">
    Include mockups, examples, or references
  </Card>

  <Card title="Clear timelines" icon="calendar">
    Set realistic expectations with clients
  </Card>

  <Card title="Verify client" icon="building">
    Double-check you've selected the correct client
  </Card>

  <Card title="Single requirement" icon="cube">
    For simple work, one requirement is often enough
  </Card>

  <Card title="Review before submit" icon="eye">
    Use the review step to catch errors
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="I can't edit an approved quote">
    Approved quotes cannot be edited because they've been converted to tasks. Edit the task instead.
  </Accordion>

  <Accordion title="Client selector is missing">
    You're likely in the client portal where the client is auto-selected. Only internal users see the client selector.
  </Accordion>

  <Accordion title="I want to add another requirement type">
    Requirement types cannot be changed after creation. Cancel the quote and create a new one, or work around with the existing types.
  </Accordion>

  <Accordion title="My changes weren't saved">
    Check if the quote was approved before you edited. Approved quotes cannot be edited.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Requirement Blocks" icon="cube" href="/user-guide/quotes/requirement-blocks">
    Learn how to complete requirement blocks
  </Card>

  <Card title="Approval Workflow" icon="check-circle" href="/user-guide/quotes/approval-workflow">
    Understand the approval process
  </Card>

  <Card title="Converting to Tasks" icon="arrow-right" href="/user-guide/quotes/converting-to-tasks">
    See what happens when quotes are approved
  </Card>

  <Card title="Tasks" icon="check-square" href="/user-guide/tasks">
    Learn about tasks created from quotes
  </Card>
</CardGroup>