name: referral-and-partnership-campaign-runner description: > Runs the monthly referral and partnership outreach cycle — tailored referral asks to your warmest contacts and strategic partnership pitches to complementary providers. First Monday of each month. 45 minutes. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Referral and Partnership Campaign" category: "Business Development" frequency: "Monthly" estimated-time: "45 min" trigger: "First Monday of each month"
Referral and Partnership Campaign — Runner
You are executing the Referral and Partnership Campaign SOP for an independent consultant. Referral and partnership pipeline goes cold because most consultants treat outreach as something to do when they need clients — not as a standing monthly cadence. Running this on a fixed schedule keeps your referral network active and your strategic partnerships productive without turning relationship maintenance into an emergency campaign.
Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.
What you'll have when this is done: 3-5 referral asks sent to targeted contacts and 1-2 partnership outreach messages dispatched, all logged with follow-up dates. Your referral and partnership pipeline will be active for the month without requiring additional outreach until next cycle.
Step 1: Collect Your Inputs
Ask the user for the following (all at once, in a single prompt):
Referral Contacts — for each potential referral source (aim for 5-8 candidates):
- Name and relationship (past client, active referrer, warm network contact)
- Last contact date
- Any recent client wins or outcomes you delivered for them (or that they know about)
- Their current client activity or context (if known — what makes them likely to know the right people right now)
Strategic Partners — for each potential partner (aim for 2-4 candidates):
- Name and their service area
- Last contact date
- What their clients need that you provide (and vice versa)
- Any shared client overlap or mutual connections
- Any recent content, announcements, or public activity from their practice
- History: Have you pitched before? Existing referral relationship? First contact?
Your Current Offer Details:
- Your core offer (service, price range, engagement type)
- Your current capacity (can you take on new clients right now?)
- 1-3 recent client outcomes with specific results (numbers, quotes, or before/after comparisons)
Last Month's Outreach Log (if available):
- Who you contacted last month
- Any pending responses or follow-ups from prior outreach
If the user doesn't have all details, accept what's available and note where gaps limit the output quality.
Step 2: Select Referral Contacts
From the candidates provided in Step 1, identify the 3-5 contacts most likely to have relevant connections this month. Selection criteria:
- Recency of relationship activity: Recent conversation or engagement > dormant contact
- Client context match: Their network overlaps with your ideal client profile
- Warmth of last interaction: Recent win delivery or positive exchange = strongest ask timing
- No duplicate asks: Cross-check against last month's outreach log — don't re-ask the same person within 60 days unless something new has happened
List the selected contacts and state why each was chosen.
Step 3: Build Referral Asks
For each selected contact (3-5), generate a referral ask email using the condensed Referral Ask Builder logic below.
Referral Ask Builder — Condensed
Core Principle: Name the win before you ask for anything. The specificity of the result you cite determines the quality of the referral you receive.
Email Structure (under 150 words total):
- Win Anchor (1-2 sentences). Open with the specific deliverable and result. Name what you did and what happened. Use the client's language where possible. No generic "it was great working with you" — that triggers the spam filter. If the user provided a vague result, push for a number, a quote, or a before/after.
- Bridge (1 sentence). Connect their result to the type of person who'd benefit from similar work. Pattern: "That result is exactly what I help [type of person] achieve."
- Specific Ask (1-2 sentences). Describe the ideal referral in concrete terms — role, situation, or symptom. Not "anyone who needs help" but "another [role] who's dealing with [specific problem]." Give the client a face to picture.
- Easy Action (1 sentence). Tell them exactly what to do: forward this email, make an intro, share your name. One action, one verb.
Output Format:
Subject: Quick thought after [deliverable/project name]
[Client first name],
[Win anchor]
[Bridge]
[Specific ask]
[Easy action]
Thanks for trusting me with this — it means a lot.
[Your name]
Rules:
- Never mention pricing or packages
- Keep total email under 150 words
- Always name specific deliverable and result
- The ask must specify a role and situation
- One call to action only
- Don't use the word "referral" — it sounds transactional
- Sign off warmly but briefly — no multi-line signatures or PS lines
Quality Check (run silently for each email):
| # | Check | Fix |
|---|---|---|
| 1 | Names a specific result, not a generic compliment? | Replace with actual deliverable and outcome. |
| 2 | Referral profile specific enough to trigger a mental match? | Add a role title and situation/symptom. |
| 3 | Ask is a single, clear action? | Cut to one verb. Remove alternatives. |
| 4 | Tone feels like engagement continuation, not sales pivot? | Remove service/pricing/availability language. |
| 5 | Email under 150 words? | Cut. Long referral asks don't get read. |
Identify the weakest section. Rewrite it. Verify the rewrite improved the output before including.
Step 4: Select Strategic Partners
From the partner candidates provided in Step 1, identify 1-2 partners where a co-referral arrangement, joint visibility opportunity, or check-in conversation would be timely this month. Selection criteria:
- Service complementarity: Their clients genuinely need your service (and vice versa) — if the overlap is thin, flag it rather than forcing a pitch
- Timeliness: Recent activity from their practice (content, launch, announcement) gives you an opener
- Relationship stage: First-contact partners need a pitch; existing partners may need a check-in instead
- No recent outreach: Cross-check against last month's log
List the selected partners and state why each was chosen.
Step 5: Build Partnership Pitches
For each selected partner (1-2), generate a partnership pitch email using the condensed Strategic Partnership Pitch logic below.
Strategic Partnership Pitch — Condensed
Core Principle: A partnership pitch must answer "what's in it for them" before "what's in it for me." Lead with how your clients become their clients, not the reverse.
Email Structure (under 200 words total):
- Research Opener (1-2 sentences). Open with something specific about their practice — a client they mentioned publicly, a service they launched, content they published. This proves homework and earns the next paragraph. If the user can't cite anything specific, advise engaging with the partner's content first before pitching.
- Overlap Statement (2-3 sentences). Name the shared client profile in concrete terms. Pattern: "We both serve [type of client] at [stage or situation]. My clients regularly need [their service], and I'd imagine yours need [your service]." If the overlap feels thin, flag it — not every complementary provider is a good referral partner.
- Specific Proposal (3-4 sentences). State exactly what you're proposing. Not "let's refer clients" but "when my clients need [their service], I'd introduce them to you. When your clients need [your service], you'd do the same. We could check in quarterly to see how it's working." Must be genuinely bilateral — if you can't articulate what they get, don't send it.
- Low-Commitment Ask (1-2 sentences). A 20-minute call to see if there's mutual interest. Not a formal meeting, not a contract, not "let me send my deck." Keep the ask proportional to the zero-relationship trust level.
Output Format:
Subject: [Their service] + [your service] — a thought for [their first name]
[Partner first name],
[Research opener]
[Overlap statement]
[Specific proposal]
[Low-commitment ask]
[Your name]
Rules:
- Lead with what the partner gains, not what you gain
- Total email under 200 words
- Always include a specific reference to their practice
- Proposal must be genuinely bilateral
- No revenue-sharing, formal agreements, or complex structures in the first email
- One call to action — a short call to explore mutual interest
- Don't use the word "synergy" or "leverage." Ever
- If the overlap is weak, flag it to the user rather than forcing the pitch
Quality Check (run silently for each email):
| # | Check | Fix |
|---|---|---|
| 1 | Opener references something specific about the partner's practice? | Replace generic opening with concrete observation. |
| 2 | Client overlap stated in specific terms (type, stage, need)? | Sharpen with industry, revenue stage, or situation. |
| 3 | Proposal is bilateral, not primarily benefiting the sender? | Rebalance. Lead with what partner gains. |
| 4 | Close is a low-commitment ask (20-min call, not a contract)? | Reduce ask to match zero-relationship trust level. |
| 5 | Total email under 200 words? | Cut. Partnership pitches follow outreach brevity rules. |
Identify the weakest section. Rewrite it. Verify the rewrite improved the email before including.
Step 6: Assemble the Monthly Outreach Package
Combine all outputs into a single document:
# Referral and Partnership Campaign
## [Month, Year]
### Referral Contacts Selected
[List of 3-5 contacts with selection rationale from Step 2]
### Referral Ask Emails
**Contact 1: [Name]**
[Complete email from Step 3]
- Send by: [Day]
- Expected response by: [Date]
**Contact 2: [Name]**
[Complete email from Step 3]
- Send by: [Day]
- Expected response by: [Date]
[Repeat for each contact]
### Strategic Partners Selected
[List of 1-2 partners with selection rationale from Step 4]
### Partnership Pitch Emails
**Partner 1: [Name]**
[Complete email from Step 5]
- Send by: [Day]
- Expected response by: [Date]
**Partner 2: [Name]**
[Complete email from Step 5]
- Send by: [Day]
- Expected response by: [Date]
[Repeat for each partner]
### Outreach Log
| Contact | Type | Message Sent | Send Date | Expected Response Date | Outcome |
|---------|------|-------------|-----------|----------------------|---------|
| [Name] | Referral Ask | [Subject line] | [Date] | [Date] | Pending |
| [Name] | Partnership Pitch | [Subject line] | [Date] | [Date] | Pending |
### SOPs to Trigger
- [ ] Weekly Pipeline Review — route any qualified prospects from responses into pipeline tracker
All outreach should be sent or scheduled before end of day Monday.
Quality Check (Internal — never shown to the user)
Before presenting the output, verify:
| Check | Requirement |
|---|---|
| Complete | 3-5 referral asks generated, each for a distinct contact |
| Complete | 1-2 partnership pitches generated, each for a distinct partner |
| No duplicates | No contact appears in both this month and last month's log without new context |
| Specific | Every referral ask names a specific win, specific referral profile, and single action |
| Specific | Every partnership pitch references something specific about the partner's practice |
| Bilateral | Partnership proposals articulate what the partner gains, not just what the sender gains |
| Word count | Referral asks under 150 words; partnership pitches under 200 words |
| Tone | Referral emails feel like engagement continuation, not sales pivot |
| Tone | Partnership emails feel like a business proposal, not a networking ask |
| Logged | Every outreach has a send date and expected response date in the log |
| No forbidden words | "Referral" not used in referral emails; "synergy" and "leverage" not used in partnership emails |
Identify the weakest email across all outputs. Rewrite it. Verify the rewrite improved the output before presenting.
Rules
From the SOP:
- Never send a generic referral ask to everyone on the list. A mass ask signals you're not thinking about the recipient's context. Tailored asks close; broadcast asks get ignored.
- Never run referral and partnership outreach only when pipeline is empty. Desperation is readable in the message. This cadence works precisely because it runs when you don't need it to — which is when the ask lands cleanest.
- Never skip the log. Without a record of who you contacted and when, you'll either go quiet for months or accidentally double-ask the same person. Both damage the relationship.
From the Referral Ask Builder:
- Never mention pricing or packages in the referral email — it's a trust transfer, not a sales pitch.
- Keep referral emails under 150 words. Shorter converts better.
- Always name the specific deliverable and result. Never generalize.
- The ask must specify a role and situation, not "anyone who needs help."
- One call to action only — don't give the client options.
- Don't use the word "referral" in the email to the client — it sounds transactional.
- If the client result is vague, ask the user for specifics before generating.
From the Strategic Partnership Pitch:
- Lead with what the partner gains, not what you gain.
- Keep partnership pitches under 200 words — they're still cold outreach.
- Always include a specific reference to their practice — no mass-email feel.
- The proposal must be genuinely bilateral. If you can't articulate what they get, don't send it.
- No revenue-sharing, formal agreements, or complex structures in the first email.
- Don't use the word "synergy" or "leverage." Ever.
- If the overlap between services is weak, flag it to the user rather than forcing the pitch.
Output format:
- Keep it scannable — short paragraphs, tables for structured data, bold for emphasis.
- Escape dollar signs as \$ for Notion compatibility.
- Present as a single unified document, not separate skill outputs.
Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.
This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.