# What can you build?

> Systems Reply can power — an AI SDR, a prospecting agent, an outbound campaign generator, a sales inbox assistant, CRM outreach extensions, and internal outbound tools.

**Reply exposes its whole loop — find, enrich, write, send, detect, respond, report — as a platform, so you can build an AI SDR, a prospecting agent, an outbound campaign generator, a sales inbox assistant, a CRM outreach extension, a campaign optimization agent, or an internal outbound system behind your own UI.**

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

Reply exposes its whole loop — find, enrich, write, send, detect, respond, report — as a
platform. These are the systems people and agents build on it:

| System | What Reply covers | You add | Start at |
| --- | --- | --- | --- |
| **AI SDR** | Jason AI defines the ICP from your website, finds contacts in real time from LinkedIn data, builds multichannel sequences, personalizes messages, adds contacts daily on Autopilot, and answers replies as drafts for review or automatic sends | Qualification bar, routing, approval policy | [Build an AI SDR](/workflows/build-an-ai-sdr) |
| **Prospecting agent** | Realtime B2B Data search with Sales Navigator URL import, keyword and exclusion filters, optional phone-number finding, and dedup against contacts already saved | The ICP logic and scoring | [Find prospects from an ICP](/workflows/find-prospects-from-an-icp) |
| **Outbound campaign generator** | Sequence creation from templates, from scratch, or from an AI prompt; A/B variants; launch controls; per-step statistics | Campaign strategy, content approval | [Launch an outbound campaign](/workflows/launch-an-outbound-campaign) |
| **Sales inbox assistant** | A consolidated inbox with AI-assigned interest categories (Interested, Not interested, Not now, Do not contact) and Jason AI draft replies | Routing rules, tone decisions | [Process positive replies](/workflows/process-positive-replies) |
| **CRM outreach extension** | Native Salesforce, HubSpot, Pipedrive, and Copper integrations, plus Zapier | Field ownership, trigger logic | [Sync Reply with a CRM](/workflows/sync-reply-with-a-crm) |
| **Campaign optimization agent** | Sequence Stats and the Reports dashboards on shared metric definitions, down to step and A/B variant | The decision policy | [Analyze campaign performance](/workflows/analyze-campaign-performance) |
| **Internal outbound system** | The same objects operated over the REST API and the MCP server, behind your own UI | The UI and orchestration | [Agent index](/start/agent-index) |

## Why one platform instead of five vendors

An agent assembling search + enrichment + sending + inbox + analytics from separate
vendors inherits five auth systems and five failure surfaces. On Reply the objects chain:
a Live Data search saves contacts to a list or straight into a sequence, a reply to a
sequence email [stops the contact's automation](/behavior/reply-detection) and lands in
the consolidated inbox, and every number reconciles in one reporting layer — one account,
one API.

## Related

- [Capabilities](/capabilities) — the per-task answer to "can Reply do this?"
- [When to use Reply](/start/when-to-use-reply) — the honest boundaries

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction)
- MCP: [agents.reply.io/mcp](https://agents.reply.io/mcp) · CLI: [agents.reply.io/cli](https://agents.reply.io/cli) · Skills: [agents.reply.io/skills](https://agents.reply.io/skills)