sales-agency-outbound

Name: sales-agency-outbound
Author: sales-skills

80installs9forks

How to install sales-agency-outbound?

sales-skills/sales/sales-agency-outbound

$npx -y skills add sales-skills/sales --skill sales-agency-outbound

Installs into the current project.

Summary

Multi-client outbound for lead gen agencies — infrastructure architecture, client isolation, domain strategy, warmup at scale, white-labeling, unified reporting, client onboarding playbooks, and cross-client operations. Use when one client's domain reputation is dragging down oth

Files · 1

View on GitHub

SKILL.md

1	# Multi-Client Outbound for Agencies
2
3	Help the user architect, scale, and operate outbound infrastructure for a lead generation agency — from client isolation and domain strategy through warmup at scale, onboarding playbooks, and cross-client reporting. This skill is tool-agnostic and covers Smartlead, Instantly, Mailshake, and multi-tool setups.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. How many clients do you serve (or plan to)?
13	- A) Starting out — 1-3 clients
14	- B) Growing — 4-10 clients
15	- C) Scaled — 10-25 clients
16	- D) Enterprise agency — 25+ clients
17
18	2. What's the typical sending volume per client?
19	- A) Light — under 100 emails/day
20	- B) Standard — 100-500 emails/day
21	- C) High volume — 500-2,000 emails/day
22	- D) Varies widely across clients
23
24	3. What tooling are you using?
25	- A) Smartlead (unlimited mailboxes, master inbox)
26	- B) Instantly (bulk warmup, simple UI)
27	- C) Mailshake (Lead Catcher, CRM integration)
28	- D) Apollo (prospecting + sequences)
29	- E) Mix of tools — describe
30	- F) Haven't decided yet
31
32	4. What's your client onboarding process today?
33	- A) Ad hoc — no standard process
34	- B) Have a rough checklist but it's inconsistent
35	- C) Documented and repeatable
36	- D) Starting from scratch — need to build it
37
38	5. What's your biggest challenge right now?
39	- A) Setting up infrastructure for the first time
40	- B) One client's issues affecting others (cross-contamination)
41	- C) Scaling — adding clients without proportional ops work
42	- D) Reporting — clients want better visibility
43	- E) Deliverability across multiple domains/clients
44	- F) Something else — describe it
45
46	6. Do you need white-labeling? (client-facing branding)
47
48	7. What's your team structure? (solo founder, small team, dedicated account managers per client)
49
50	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
51
52	## Step 2 — Architecture decisions
53
54	Read `references/platform-guide.md` for detailed module documentation, pricing, integrations, and data model.
55
56	You no longer need the platform guide details — focus on the user's specific situation.
57
58	## Step 3 — Actionable guidance
59
60	Based on the user's challenge, provide specific recommendations for infrastructure isolation, domain strategy, warmup scheduling, client onboarding, reporting setup, or platform-specific implementation. Use the platform guide for reference data, then focus on actionable next steps tailored to their agency setup.
61
62	## Gotchas
63
64	- Don't share sending domains across clients. One client's reputation meltdown (high bounces, spam complaints, blacklisting) poisons all clients sharing that domain. The cost of a $12/year domain is nothing compared to rebuilding reputation for 5 clients.
65	- Don't skip per-client warmup. New domains need their own warmup regardless of mailbox age. Even if you're reusing an established mailbox on a new domain, the domain itself has zero reputation. Follow the full warmup schedule.
66	- Don't report vanity metrics. Report meetings booked and pipeline generated, not opens and clicks. Clients who focus on opens will micromanage subject lines instead of trusting the process. Set expectations during onboarding about which metrics matter.
67	- Don't use a single Zapier account for all clients. Billing, rate limits, and error handling cascade across all zaps in one account. If one client's integration breaks and triggers retries, it can exhaust your Zapier task quota and break every other client's integration. Use separate Zapier accounts or a dedicated integration layer.
68
69	- Self-improving: If you discover something not covered here, append it to `references/learnings.md` with today's date.
70
71	## Before recommending a specific platform skill
72
73	This s

People who liked this also viewed

6 picks

Type

sales-agency-outbound

80installs9forks

View on GitHub

How to install sales-agency-outbound?

sales-skills/sales/sales-agency-outbound

$npx -y skills add sales-skills/sales --skill sales-agency-outbound

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Multi-Client Outbound for Agencies
2
3	Help the user architect, scale, and operate outbound infrastructure for a lead generation agency — from client isolation and domain strategy through warmup at scale, onboarding playbooks, and cross-client reporting. This skill is tool-agnostic and covers Smartlead, Instantly, Mailshake, and multi-tool setups.
4
5	## Step 1 — Gather context
6
7
8	If `references/learnings.md` exists, read it first for accumulated knowledge.
9
10	Ask the user:
11
12	1. How many clients do you serve (or plan to)?
13	- A) Starting out — 1-3 clients
14	- B) Growing — 4-10 clients
15	- C) Scaled — 10-25 clients
16	- D) Enterprise agency — 25+ clients
17
18	2. What's the typical sending volume per client?
19	- A) Light — under 100 emails/day
20	- B) Standard — 100-500 emails/day
21	- C) High volume — 500-2,000 emails/day
22	- D) Varies widely across clients
23
24	3. What tooling are you using?
25	- A) Smartlead (unlimited mailboxes, master inbox)
26	- B) Instantly (bulk warmup, simple UI)
27	- C) Mailshake (Lead Catcher, CRM integration)
28	- D) Apollo (prospecting + sequences)
29	- E) Mix of tools — describe
30	- F) Haven't decided yet
31
32	4. What's your client onboarding process today?
33	- A) Ad hoc — no standard process
34	- B) Have a rough checklist but it's inconsistent
35	- C) Documented and repeatable
36	- D) Starting from scratch — need to build it
37
38	5. What's your biggest challenge right now?
39	- A) Setting up infrastructure for the first time
40	- B) One client's issues affecting others (cross-contamination)
41	- C) Scaling — adding clients without proportional ops work
42	- D) Reporting — clients want better visibility
43	- E) Deliverability across multiple domains/clients
44	- F) Something else — describe it
45
46	6. Do you need white-labeling? (client-facing branding)
47
48	7. What's your team structure? (solo founder, small team, dedicated account managers per client)
49
50	If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
51
52	## Step 2 — Architecture decisions
53
54	Read `references/platform-guide.md` for detailed module documentation, pricing, integrations, and data model.
55
56	You no longer need the platform guide details — focus on the user's specific situation.
57
58	## Step 3 — Actionable guidance
59
60	Based on the user's challenge, provide specific recommendations for infrastructure isolation, domain strategy, warmup scheduling, client onboarding, reporting setup, or platform-specific implementation. Use the platform guide for reference data, then focus on actionable next steps tailored to their agency setup.
61
62	## Gotchas
63
64	- Don't share sending domains across clients. One client's reputation meltdown (high bounces, spam complaints, blacklisting) poisons all clients sharing that domain. The cost of a $12/year domain is nothing compared to rebuilding reputation for 5 clients.
65	- Don't skip per-client warmup. New domains need their own warmup regardless of mailbox age. Even if you're reusing an established mailbox on a new domain, the domain itself has zero reputation. Follow the full warmup schedule.
66	- Don't report vanity metrics. Report meetings booked and pipeline generated, not opens and clicks. Clients who focus on opens will micromanage subject lines instead of trusting the process. Set expectations during onboarding about which metrics matter.
67	- Don't use a single Zapier account for all clients. Billing, rate limits, and error handling cascade across all zaps in one account. If one client's integration breaks and triggers retries, it can exhaust your Zapier task quota and break every other client's integration. Use separate Zapier accounts or a dedicated integration layer.
68
69	- Self-improving: If you discover something not covered here, append it to `references/learnings.md` with today's date.
70
71	## Before recommending a specific platform skill
72
73	This s

People who liked this also viewed

6 picks

Type