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

# Citation Wins Tied to Pipeline

> Match newly-won AI citations and prompt visibility against your CRM's open deals to show which AI visibility gains are touching active revenue.

"Our AI visibility improved" is a metric. "Our AI visibility improved on the exact topic three open deals are researching" is a business case. This workflow cross-references Scrunch's newest wins against your CRM's pipeline so you can show, not just say, that the work is connected to revenue.

<Info>
  **Tools used in this workflow**

  | Tool                          | Required?             | Used for                                                    |
  | ----------------------------- | --------------------- | ----------------------------------------------------------- |
  | Scrunch MCP                   | Required              | Identifying newly-won prompts and citations                 |
  | HubSpot MCP or Salesforce MCP | Required (choose one) | Matching wins against open deals and logging the connection |
</Info>

***

<Tabs>
  <Tab title="HubSpot">
    Replace the bracketed values, then paste the whole thing into Claude.

    ```text theme={null}
    For [brand name] in Scrunch, find recent AI visibility wins and check whether they touch any open HubSpot deals.

    Step 1 — Find the wins:
    Pull prompt variants filtered to brand_present = true for the last [14/30] days. Cross-reference against citation metrics to find prompts where [brand name]'s own domain is now being cited on a topic it wasn't before. List the specific prompts, their tags/topics, and the platforms involved.

    Step 2 — Match against pipeline:
    For each topic area from Step 1, search open HubSpot deals for company names or deal notes that mention that topic or a closely related keyword.

    Step 3 — Log the connection:
    For any deal that matches, add a note to the deal: "AI visibility update: [brand name] is now appearing in [platform] responses for '[topic]' as of [date]. Citation: [cited URL]. Relevant if this topic comes up in the sales conversation."

    Step 4 — Summarize:
    List every deal that got a note, its stage and amount, and the specific visibility win tied to it. This is the evidence for "AI visibility work is touching open pipeline."
    ```

    **What you get:** A short list of open deals with a dated, sourced note showing exactly which AI visibility win is relevant to that conversation — real evidence to bring into a pipeline review or a case for continued investment.
  </Tab>

  <Tab title="Salesforce">
    Replace the bracketed values, then paste the whole thing into Claude.

    ```text theme={null}
    For [brand name] in Scrunch, find recent AI visibility wins and check whether they touch any open Salesforce opportunities.

    Step 1 — Find the wins:
    Pull prompt variants filtered to brand_present = true for the last [14/30] days. Cross-reference against citation metrics to find prompts where [brand name]'s own domain is now being cited on a topic it wasn't before. List the specific prompts, their tags/topics, and the platforms involved.

    Step 2 — Match against pipeline:
    For each topic area from Step 1, search open Salesforce opportunities for account names or opportunity notes that mention that topic or a closely related keyword.

    Step 3 — Log the connection:
    For any opportunity that matches, add an activity note: "AI visibility update: [brand name] is now appearing in [platform] responses for '[topic]' as of [date]. Citation: [cited URL]. Relevant if this topic comes up in the sales conversation."

    Step 4 — Summarize:
    List every opportunity that got a note, its stage and amount, and the specific visibility win tied to it. This is the evidence for "AI visibility work is touching open pipeline."
    ```

    **What you get:** A short list of open opportunities with a dated, sourced note showing exactly which AI visibility win is relevant to that conversation — real evidence to bring into a pipeline review or a case for continued investment.
  </Tab>
</Tabs>

***

## Tips

<AccordionGroup>
  <Accordion title="Matching is fuzzy — treat it as a starting list">
    Topic-to-deal matching by keyword will surface some false positives, especially for common terms. Have Claude flag its confidence for each match ("strong: deal notes explicitly mention this topic" vs. "weak: same industry, no direct mention") and skim the weak ones before logging.
  </Accordion>

  <Accordion title="Running this before a pipeline review">
    Time this workflow a day or two before a sales or leadership pipeline review — the notes it adds are most useful when they're fresh enough to reference directly in the meeting.
  </Accordion>

  <Accordion title="No topic-level fields in your CRM?">
    If deals don't have structured topic tags, this relies on free-text matching against deal names and notes, which is noisier. Consider adding a simple "primary topic" custom field to deals going forward — it makes every future run of this workflow meaningfully more precise.
  </Accordion>

  <Accordion title="Building this into the monthly report">
    Include a "Pipeline Impact" section in the Monthly Client Report workflow that pulls directly from the deals this workflow flagged — it's one of the more concrete ROI arguments you can make to a client or to leadership.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Measure AI Visibility's Impact on Traffic" icon="chart-line" href="/mcp/workflows/ai-visibility-traffic-impact">
    Build the traffic side of the ROI case alongside the pipeline side.
  </Card>

  <Card title="Monthly Client Report, Built Automatically" icon="file-lines" href="/mcp/workflows/monthly-client-report">
    Roll pipeline-tied wins into the recurring report you already send.
  </Card>
</CardGroup>