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

# Stop revenue leaks

> The setup path for finding and fixing the silent problems costing you sales: connect your store, run an audit, review ranked findings, and apply a fix with an undo point.

This is the path to follow when something in your store is quietly costing you money and you want it found, explained and fixed. If your priority is winning demand you are not capturing yet, start with [Accelerate growth](/start-here/accelerate-growth) instead. Both paths run on the same platform and you can switch at any time.

## What this path gives you

A ranked list of what is wrong, each finding written with the reason it matters, the revenue at stake and the exact change that fixes it, and then a route to apply that change safely with a way back.

<CardGroup cols={3}>
  <Card title="Find" icon="magnifying-glass">
    Your store is scanned and every issue becomes a finding, ranked by the revenue at stake.
  </Card>

  <Card title="Explain" icon="lightbulb">
    Each finding carries the cause, the before and after, and the exact fix. Not a checklist.
  </Card>

  <Card title="Fix" icon="wrench">
    Approved findings become applied changes, a pull request, or guided steps. Always with an undo point.
  </Card>
</CardGroup>

## Follow these steps

<Steps>
  <Step title="Connect your store">
    Add your commerce platform first, then the sources that explain behaviour: analytics, search, payments and advertising. Each connector widens what can be detected. See [Connectors](/nerve-centre/connectors) and the [connector catalogue](/integrations/connector-catalogue).
  </Step>

  <Step title="Run a store audit">
    The audit reads every connected source and returns findings ranked by revenue impact rather than by severity label. It is read-only and never changes your store. See [Store Audit](/actions/store-audit).
  </Step>

  <Step title="Review what came back">
    Work the findings on the [Kanban Board](/actions/kanban). Each card carries the evidence behind it, so you are approving a change you can see the reason for.
  </Step>

  <Step title="Apply a fix, with a way back">
    Approve a card and the change is applied within the permissions you granted. Where the platform and workflow support it, a restore point is kept first. See [Vortex Apps](/vortex-apps/overview), [StagingPro](/vortex-apps/staging-pro) and [RollbackPro](/vortex-apps/rollback-pro).
  </Step>

  <Step title="Keep watching">
    Set up the monitoring that catches the next one earlier: KPI cards for the measures that matter to you, and alerts when they move. See [KPI cards](/nerve-centre/kpi-cards) and [Alerts](/nerve-centre/alerts).
  </Step>
</Steps>

## Every finding ends in one of three outcomes

A finding never disappears quietly. When a fix can be applied through the API, it is applied and a restore point is kept. When it needs code, a pull request is opened for your developers to review. When it cannot be automated at all, you get guided steps rather than a button that pretends. There is no fourth outcome and no silent failure.

<Note>
  Which outcome applies depends on the finding, the connector, your permissions and the workflow. The audit itself never changes anything.
</Note>

## Who does this work

Two teams carry this path. **Pulse** runs store health: it scans, enriches every finding with the reason and the fix, and verifies findings before you see them. It never applies changes itself. **CodeCraft** is the development team that takes an approved finding and makes the change, then hands the result back. **Bridge** provides the staging copies and change tracking that make the undo possible.

See [Your AI teams](/start-here/your-ai-teams) for what each team does and which are running today.

## Where to go next

<CardGroup cols={2}>
  <Card title="Store Audit" icon="clipboard-check" href="/actions/store-audit">
    The scan itself: what it reads, how findings are ranked, and how to run one.
  </Card>

  <Card title="Kanban Board" icon="list-check" href="/actions/kanban">
    Where findings become work you approve.
  </Card>

  <Card title="Vortex Apps" icon="shield-halved" href="/vortex-apps/overview">
    Staging, backup and rollback for supported workflows.
  </Card>

  <Card title="Ask Viq" icon="comments" href="/ask-viq/overview">
    Ask plain questions about your store and the findings behind an answer.
  </Card>
</CardGroup>