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

# Proposal editor (wizard)

> Step-by-step flow in Quikly: proposal type, brief and client context, then Analyze and continue into scope, pricing, terms, and share.

The **proposal editor** guides you through creating a document your client can open, discuss, and sign. The main path is a **wizard** with distinct steps; the most important AI moment is moving from the **brief step** into **scope and estimates**.

## Wizard steps (typical flow)

1. **Proposal type** — Choose one of the [six proposal types](/guides/proposal-types). This controls pricing logic, fields, and how Quimy analyzes the brief.

2. **Project and brief** — Add **client** (pick from CRM or enter manually), **brief** text (email, notes, transcript, RFP excerpt), optional **attachments**, and type-specific context (dates, budget, team, contract hints for Staff Augmentation, etc.). **Project name** is often refined on the next step after analysis.

3. **Scope and configuration** — Requirements, story points or hour estimates (depending on type), phases, pricing adjustments, and Quimy outputs such as risk and governance previews. If the brief changed since the last analysis, the UI can prompt you to **re-analyze**.

4. **Further steps** — Depending on type and settings: milestones, retainer terms, **Terms & documents** (clauses, SOW fields), **Customize** (branding, visibility), then **Review** and **Share**.

<Note>
  Exact step labels and count vary by proposal type (for example Staff Augmentation adds team phases). The **type → brief → scope** pattern is always the core.
</Note>

## Analyze and continue (step 2 → 3)

When your brief is ready, you proceed with **Next**. If Quimy needs to run (or re-run) the full analysis chain, the button reads **Analyze and continue** (or your UI language equivalent). That action:

* Runs the **full analysis pipeline** (brief quality, requirements / type-specific analyzers, and related calls such as staffing estimates where applicable).
* Shows a **loading state** while processing; on failure you can retry or go back and edit the brief.
* Lands you on **scope** with structured output you can edit.

If you already have a **fresh** analysis for the current brief and context, **Next** may advance without re-running everything; if you edit the brief afterward, expect a **stale** hint and use **re-analyze** from the scope step when offered.

### Analyze with Quimy on the brief step

You can still use **Analyze with Quimy** on the brief step for **discovery-style quality feedback** (score, clarifying questions) without leaving the step. That is complementary to **Analyze and continue**, which runs when you advance to scope and triggers the pipeline that fills requirements and related sections.

## Related workflows

* [AI features](/guides/ai-features) — Everything Quimy does in the editor and limits by plan.
* [Discovery Gen](/guides/discovery-gen) — Structured discovery and reports inside the app before you build the commercial proposal.
* [Discovery Copilot](/guides/discovery-copilot-extension) — Live transcript and coaching in Meet, Zoom Web, or Teams Web, using the same Quikly account and API keys where applicable.
* [Sharing proposals](/guides/sharing-proposals) — Links, client view, and follow-up.
