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

# How Sapt works

> Connect your ad accounts, Sapt builds one shared memory and fixes the signal, and your team and AI run ads from it — the whole model in one picture.

Sapt sits behind your ads. You connect your accounts, Sapt pulls what's scattered across them into one shared memory and improves the signal going back to the platforms, and from then on your team and your AI work from that memory. This page is the whole model in one picture.

## Connect your accounts

Everything starts by connecting the tools you already run on:

| Source                       | What it holds                                                             |
| ---------------------------- | ------------------------------------------------------------------------- |
| **CRM**                      | People, companies, lists, and where each one sits in your pipeline.       |
| **CMS**                      | Your content — pages, bottom-funnel assets, and the metadata around them. |
| **Third-party integrations** | Meta, Google Ads, Google Business Profile, email, SMS, and more.          |

Connecting your ad platforms is the important part — it's what lets Sapt see the full picture instead of one dashboard at a time. See [Integrations](/docs/mintlify/platform/integrations).

## One shared memory

Once connected, the details, campaigns, and results stop living in separate places. They become one [memory](/docs/mintlify/platform/memory) for the account that every teammate and every AI assistant reads from — so nobody starts from scratch and nothing gets re-explained.

## Workflows turn it into action

When something changes — a new lead, a new review, a campaign result — a workflow can act on it. Common ones:

* **Send an email** — reply to a new inquiry.
* **Update a record** — move a lead along the pipeline.
* **Post or reply** — respond on a connected channel.
* **Wait and follow up** — pause, then continue when someone replies.

Whatever comes back flows into the same Project, so work stays in one place across every tool.

## Why it's built this way

* **Run ads from memory.** People and content and channels share one context, not four disconnected apps.
* **Steps you can trust.** Anything customer-facing can require review before it runs. See [Workflows](/docs/mintlify/platform/workflows).
* **The same model for everyone.** A gym, a clinic, and an online store all use the same building blocks; only the content differs.

## Keep going

<CardGroup cols={2}>
  <Card title="Ads" href="/docs/mintlify/platform/ads" description="Run your Meta and Google ads on better signal." />

  <Card title="Memory" href="/docs/mintlify/platform/memory" description="The shared context every campaign and assistant runs from." />

  <Card title="Workflows" href="/docs/mintlify/platform/workflows" description="How repeatable work moves through review and execution." />

  <Card title="Quickstart" href="/docs/mintlify/guides/quickstart" description="Connect Sapt to Claude, ChatGPT, or your own app." />
</CardGroup>
