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

# Meeting to Deal Workflow

> Pre-call prep through closed deal: the complete meeting-driven sales cycle.

Every important sales meeting deserves a prepared entry and a structured exit. This workflow covers both.

## The workflow

<Steps>
  <Step title="Cortex: pre-call brief">
    ```text theme={null}
    Prep me for my call with the CTO at Linear tomorrow at 2pm.
    ```

    Cortex generates a meeting prep brief in under 3 minutes: company snapshot, who you're meeting, why now, talking points, anticipated objections, questions to ask.

    Saved to memory tagged with company name.
  </Step>

  <Step title="Meeting happens">
    You run the call with the brief in hand. Take notes — even rough ones.
  </Step>

  <Step title="Striker: post-call blueprint">
    ```text theme={null}
    Create a post-call blueprint. Linear CTO call.
    Notes: They mentioned budget concerns, liked the AI positioning,
    want to see a proposal by Friday. Two competitors in the deal: HubSpot and a homegrown tool.
    ```

    Striker generates the post-call blueprint canvas: recap, audience profile, content that resonated, outreach plan, competitor mentions, sales playbook update, follow-up email draft.
  </Step>

  <Step title="Follow-up email sent">
    Follow-up email drafted from the blueprint. Personalized to what was discussed. Sent the same day via Gmail.
  </Step>

  <Step title="Proposal generated">
    ```text theme={null}
    Create a proposal doc for Linear: 3-month implementation, $4,500/month.
    ```

    Structured Doc canvas generated. Exported as PDF. Sent.
  </Step>

  <Step title="Deal stage updated">
    HubSpot deal stage updated to `Proposal` automatically via Striker tool call. Timeline tracked from here.
  </Step>

  <Step title="Silence after 5 days: Striker follow-up">
    Striker sends a follow-up referencing the specific proposal and timeline discussed. Not generic — references the Friday deadline mentioned in the call.
  </Step>

  <Step title="Objection: Striker handles it">
    Budget concern raised. Striker applies the Acknowledge-Answer-Bridge-Ask framework. ROI Calculator canvas generated to address the CFO question.
  </Step>
</Steps>