> ## 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.

# Quickstart

> Create your account, build your first proposal, and share it with a client in under 15 minutes.

<Steps>
  <Step title="Create your account">
    Go to [app.getquikly.com/register](https://app.getquikly.com/register) and sign up with your email or Google account. No credit card required — the Starter plan includes a 14-day trial with 3 proposals.
  </Step>

  <Step title="Complete onboarding">
    After signing up, a 6-step onboarding wizard collects the information Quimy needs to personalize your proposals:

    1. **Your name** — how you appear on proposals.
    2. **Provider type** — freelancer, dev shop / agency, or consultancy. This determines which features and proposal types are highlighted.
    3. **Work areas** — development, cloud & DevOps, data engineering, cybersecurity, consulting, automation, or others.
    4. **Role and seniority** — your lead role (developer, PM, architect, etc.) and seniority level.
    5. **Quimy configuration** — AI readiness level and technical specialty so Quimy tailors its suggestions.
    6. **Example brief** — optionally paste a real or sample brief so Quimy can show you what it does right away.

    <Tip>
      You can update all onboarding fields later in **Settings → Profile**.
    </Tip>
  </Step>

  <Step title="Create your first proposal">
    From the dashboard, click **New Proposal**. You have two paths:

    <Tabs>
      <Tab title="Editor (step-by-step)">
        1. **Step 1 — Proposal type:** Pick the model ([proposal types](/guides/proposal-types)); **Technical Proposal** is a common default.
        2. **Step 2 — Project and brief:** Choose or create the **client**, paste the **brief** (email, notes, transcript, RFP), add **attachments** if needed, and complete type-specific fields (rate, dates, budget, team context). The footer shows **Analyze and continue** when Quimy must run the **full analysis pipeline** before opening scope.
        3. **Step 3 — Scope and configuration:** Review **requirements** (or equivalent for your type), estimates, phases, and pricing. If the brief changed after analysis, use **re-analyze** when the UI offers it.
        4. **Later steps:** Terms and clauses, customization, **Review**, then **Share**. The right-hand **preview** becomes central from scope onward on large screens.
        5. On step 2 you can also click **Analyze with Quimy** for **brief-quality** feedback (score, clarifying questions) without leaving the step — that complements the full run triggered by **Analyze and continue**.

        For detail on the step 2→3 behavior, see [Proposal editor (wizard)](/guides/proposal-editor).
      </Tab>

      <Tab title="Agent Mode (chat-guided)">
        1. Click **Agent Mode** from the dashboard.
        2. Tell Quimy about the project in natural language — stack, client needs, timeline, budget.
        3. Quimy asks clarifying questions (like a Solution Architect would), identifies risks, and structures the scope.
        4. Review the generated proposal. You can edit any field before finalizing.
        5. Click **Edit in dashboard** to fine-tune in the full editor, or share directly.
      </Tab>
    </Tabs>

    <Tip>
      **Live discovery in calls:** [Discovery Copilot](/guides/discovery-copilot-extension) (browser extension for Meet, Zoom Web, Teams Web). **Structured sessions in the app:** [Discovery Gen](/guides/discovery-gen).
    </Tip>
  </Step>

  <Step title="Share with your client">
    1. Click **Share** in the editor toolbar.
    2. Optionally add the client's email to send a notification.
    3. Quikly generates a unique link. Copy it and send it via email, Slack, WhatsApp, or any channel you prefer.
    4. Your client opens the link — no account needed to view the proposal. They see a professional document with your branding, scope, pricing, timeline, and delivery conditions.
    5. To respond (accept, request changes, or reject), the client logs in with email or Google. They can also chat with you or ask Quimy to explain sections.

    <Note>
      Share links expire after 90 days. You can generate a new link at any time from the proposal's post-share view.
    </Note>
  </Step>
</Steps>

## What happens next

Once your client accepts and signs, you'll see the response in the **Follow-up** tab with the full audit trail — signature image, signer name, timestamp, IP address, and document hash.

From the Follow-up tab you can also:

* Generate **alignment questions** to align expectations before kickoff.
* Export the approved scope to **Jira, Linear, GitHub, or Asana** as ready-to-work issues.
* Continue the conversation via the built-in **chat**.