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

# Sales Development Rep (SDR)

> Get your SDR sourcing prospects, drafting outreach and keeping your pipeline current

The **Sales Development Rep (SDR)** runs your outbound groundwork. It builds prospect lists from your ideal customer profile, researches accounts, drafts email and LinkedIn outreach, qualifies replies against your rules and keeps the pipeline current. It hands interested prospects to your team.

## Before you hire

Connect these under **Settings > Tools**:

| Tool | Why |
| - | - |
| [Google Sheets](https://docs.spinnable.ai/tools/google-sheets.md) | Prospect lists and pipeline tracking |
| [Gmail Read](https://docs.spinnable.ai/tools/gmail-read.md) and [Gmail Send](https://docs.spinnable.ai/tools/gmail-send.md), or [Outlook Read](https://docs.spinnable.ai/tools/outlook-read.md) and [Outlook Send](https://docs.spinnable.ai/tools/outlook-send.md) | Read replies and send outreach from your mailbox |
| [HubSpot](https://docs.spinnable.ai/tools/hubspot.md), [Salesforce](https://docs.spinnable.ai/tools/salesforce.md) or [Pipedrive](https://docs.spinnable.ai/tools/pipedrive.md) (optional) | Keep CRM stages current |
| [Apollo](https://docs.spinnable.ai/tools/apollo.md) and [NeverBounce](https://docs.spinnable.ai/tools/neverbounce.md) (optional) | Find and verify contacts |

## Skills it starts with

| Skill | What it does | What it asks you at setup |
| - | - | - |
| **Lead Sourcing** | Builds a shortlist of good-fit prospects from a simple request | Your ideal customer profile, how many leads per run, where to save them and buying signals to look for |
| **Customer Intelligence** | Answers "is this a good lead?" and "what should I know before this call?" | Your product and your ideal customer profile |
| **Customer Communication** | First touches, follow-ups, replies and objections | Your product and value proposition, channels, draft-or-send mode, escalation rules, signature and language |
| **Pipeline Review Reporting** | A short snapshot of what's stale, stuck and needs action | Where the pipeline lives, your stage definitions and when a lead counts as stale |

## Your first week

**1. Day 1: define who you sell to**

> "We sell \[PRODUCT] to \[ROLE] at \[COMPANY TYPE, SIZE, REGION]. Good signals are \[e.g. hiring for X, recent funding]. Our best customers are \[EXAMPLES]."

**2. Day 2: a first list**

> "Find 20 prospects that fit and add them to a Google Sheet with the reason each one fits."

Mark the good and bad fits and tell your SDR why.

**3. Day 3: outreach drafts**

> "Draft a first email for the top 5. Keep each under 100 words and make the first line specific to them. Don't send yet."

**4. Day 4: send and follow up**

Once the drafts sound right, approve them.

> "Send these. Follow up after 4 working days if there's no reply, and tell me about any positive reply right away."

**5. Day 5: put it on a schedule**

> "Every Monday at 9am, send me a pipeline review: stale leads, replies waiting, and next steps."

> [!WARNING]
>
> Outbound email affects your domain's reputation. Agree on a daily sending volume and opt-out rules with your SDR, verify addresses before sending, and watch your domain health. Emails your worker sends to outside contacts from its Spinnable address count toward your plan's [external communications](https://docs.spinnable.ai/account/usage-limits.md#what-counts-as-an-external-communication).

## Common pitfalls

* **A vague profile.** "SMBs" isn't enough. The tighter your ideal customer profile, the better the list.
* **Sending before review.** Keep outreach in draft mode until a few rounds of feedback are in.

## Next steps

> **[Using a Corporate Email](https://docs.spinnable.ai/guides/corporate-email.md)**
>
> Send outreach from your company domain

> **[Communication Restrictions](https://docs.spinnable.ai/guides/worker-communication-restrictions.md)**
>
> Control who your worker may contact


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.