The Stateless Founder
SOP

The 14‑Day Partner Sprint Kit (/t/partner‑sprint)

A time‑boxed SOP to land two feed‑drops and ship one co‑created mini‑template in 14 days — with 5 outreach scripts, a negotiation checklist, a Notion calendar + asset tracker, UTMs/SmartPromos/GA4 wiring, a post‑attribution survey snippet, and a 15‑minute reply SLA (Slack + email).

From EpisodeThe 14-Day Partner Sprint: Feed-Drops, Mini-Templates, and the 15-Minute SLA

Use this SOP to run a 14‑day acquisition sprint that lands two partner feed‑drops and ships one co‑created mini‑template — with measurement wired and a 15‑minute human reply SLA for any referred demos. It’s built for remote founders who need predictable lead flow without live appearances or travel.

  1. 1

    Day 0 — Define the target and math

    • Outcome: 2 feed‑drops + 1 co‑created mini‑template shipped in 14 days.
    • Capacity: Block 90 minutes/day for 10 workdays.
    • Target list size: 20 qualified partners (expect ~20–30% positive replies, 2–4 fast yeses).
    • Baseline expectation: Podcast‑to‑podcast swaps often convert sub‑1% of exposed devices; tight adjacency and a host‑voiced intro are multipliers. Plan volume accordingly.
    • Success metrics: 2 feed‑drops live, 1 mini‑template published, ≥1 qualified demo from partner traffic, ≥80% of “referred” replies answered inside 15 minutes during coverage hours.
  2. 2

    Day 1 — Build the partner list and apply the adjacency test

    Create a 20‑row shortlist across 5 types (4 each): creators (podcasts), communities, tools, agencies, educators. Adjacency test (must pass 4/5):

    • ICP overlap: [Your ICP] ≈ [Their ICP] (job title, company size, problem).
    • Topic overlap: recent posts/episodes within your top 3 themes.
    • Format fit: accepts swaps/feed‑drops or curated mentions; editor contact visible.
    • Channel quality: recent engagement (e.g., podcast ≥150 7‑day downloads; newsletter CTR ≥2%).
    • Friction: can ship async (no live webinar or back‑and‑forth design cycles). Where to source: Apple/Spotify related shows, partner pages of adjacent tools, community digests, LinkedIn creators, agency case study blogs.
  3. 3

    Day 1 — Create the shared calendar + asset tracker (Notion)

    Create a Notion database named “Partner Sprint — Calendar + Assets.” Use these fields:

    • [Partner Name] (title)
    • [Type] (creator/community/tool/agency/educator)
    • [Status] (Prospect → Pitched → Discussing → Agreed → In Production → Scheduled → Live → Reported)
    • [Owner] (assignee)
    • [Deliverable] (Feed‑drop, 5‑min swap, Newsletter blurb, Mini‑template)
    • [Intro Style] (host‑voiced/dry)
    • [Launch Window] (date)
    • [Links] (Docs/drive/asset LP)
    • [UTM Code] (paste once; reuse everywhere)
    • [Measurement] (SmartPromos ID, GA4 event)
    • [Notes] (negotiation details) Board view by Status; Calendar view by Launch Window. Store assets in a single folder with versioning: PS-[YYYYMM]-[Partner]-[Asset]-v1.ext.
  4. 4

    Day 1 — Wire measurement: UTMs, GA4, SmartPromos, self‑reported

    1. UTM standard (use lowercase, no spaces):
    utm_source=[partner]
utm_medium=[feeddrop|newsletter|community|agency|tool]
utm_campaign=[yyyy-mm]_partner-sprint
utm_content=[asset|hook|cta]
    1. Tracking sheet (CSV headers):
    partner,type,deliverable,utm,go-live,clicks,template_views,signups,demo_intents,qualified_demos,won_deals,notes
    1. GA4: Create event template_view (LP view), template_claim (email gate success), demo_intent (calendly/book trigger). Build an exploration by session_utm_source/medium/campaign.
    2. SmartPromos (for podcast swaps): connect your hosting, create a promo “Partner Sprint [Month]”, attach partners, and monitor device conversion/new devices.
    3. Self‑reported attribution: add a required “How did you first hear about us?” question to the template gate and demo form (see Step 14 snippet).
  5. 5

    Day 2 — Route referred replies with a 15‑minute SLA (Slack + email)

    Goal: A human answers demo‑intent replies within 15 minutes during coverage hours.

    • Create Slack channel: #sla-15-referrals.
    • Coverage: Mon–Fri, 08:00–18:00 in [Primary TZ]; assign two on‑call blocks/day (08:00–13:00, 13:00–18:00). Backups listed in channel topic.
    • Gmail/Helpdesk filter → Slack: If subject/body contains referred, from [Partner], or hits utm_campaign contains partner-sprint, push to Slack with sender, snippet, and CTA buttons (Reply | Book | Claim Owner). Use Make/Zapier.
    • Triage macros:
      • First touch (≤15m): "Thanks for coming via [Partner], [Name]! Fastest next step is a 15‑min fit check. Pick a time: [Calendly-UTM]. If you prefer async, reply with your context and we’ll send a short loom."
      • No‑show rescue: send a 60‑second Loom with next two steps.
    • SLA monitoring: Add a daily reminder to post “time‑to‑first‑reply (TFR)” median to the channel. Target: ≤10 minutes median.
  6. 6

    Day 2 — Prepare creative: hooks, CTA, and the mini‑template frame

    • Sprint hero asset: a 1‑page mini‑template that solves a partner‑relevant task. Gate it with a 7‑day free window for that partner.
    • Default hook: “Ship [Result] in 30 minutes: grab the [Mini‑Template] free for 7 days.”
    • CTA URL: /t/[slug]?utm_source=[partner]&utm_medium=[channel]&utm_campaign=[yyyy-mm]_partner-sprint&utm_content=asset.
    • Produce: LP hero copy (60–80 words), 3 bullets (what it does), and a single form. Save preview image at 1200×628.
  7. 7

    Day 3 — Send outreach (5 scripts, copy‑paste)

    Send 20 messages (4 per partner type). Personalize bracketed fields. Keep it short; one ask; booking link optional.

    1. Creators (podcasts) Subject: Quick 5‑min swap idea for [Show] Body: "Loved your ep on [Topic]. We can trade a 5‑minute host‑voiced segment next week — no scheduling. We’ll run your mini‑segment + link; you run ours with a partner‑only [Mini‑Template] free for 7 days. If useful, we can also do a one‑time feed‑drop. Draft + audio ready in 48 hours. Worth a test? [Yes/No] — details: [Brief-Doc-URL]." CTA: “Reply ‘yes’ and we’ll send assets + dates.”

    2. Communities (forums/Slack/Discord) Subject: Free teardown + template for [Community] Body: "We’ll do a 30‑min async teardown of a member workflow (‘make it nomad‑proof’) and publish the resulting 1‑pager free for 7 days to [Community]. You get the spotlight; members get a copy‑paste win. Low lift: you paste a blurb in your digest. Interested?" CTA: “If yes, we’ll send the blurb + image + unique link.”

    3. Tools (SaaS partners) Subject: Co‑branded 1‑pager your users can ship this week Body: "We built a [Your Tool] + [Outcome] mini‑template that gets users from blank to result in 30 minutes. We’ll co‑brand it and give your audience a 7‑day free window via your newsletter. You get attribution + usage stats. Want the preview + copy deck?" CTA: “Reply ‘preview’ and we’ll share the deck + UTM.”

    4. Agencies Subject: A no‑meeting lead magnet you can send to 3 clients Body: "Your clients ask for [Outcome]. We’ll give you a co‑branded 1‑pager you can send today; if it lands, we’ll hop on with your strategist. Zero meetings to start. Want the sample and your unique link?" CTA: “Reply ‘sample’ and we’ll tailor it to your niche.”

    5. Educators (newsletters/courses) Subject: A copy‑and‑paste win for your [Topic] readers next week Body: "We’ll give your readers a partner‑only [Mini‑Template] that pairs with your recent lesson on [Topic]. You paste 80 words + link; we back‑link your piece and share results. Interested in a single‑issue test next week?" CTA: “Reply ‘go’ and we’ll send the blurb + tracking link.”

  8. 8

    Day 3–4 — Negotiate fast with a standard checklist

    Use this to agree in ≤3 emails.

    • Deliverable: 5‑min host‑voiced swap OR single feed‑drop (episode title, length, clean language).
    • Placement: pre‑roll, mid, or feed‑drop publish date/time; newsletter issue date.
    • Intro style: host‑voiced preferred; 20–30s script provided.
    • Creative: 1 line hook + unique CTA URL; image 1200×628.
    • Measurement: your UTM + our UTM; SmartPromos campaign name; we both screenshot results.
    • Attribution: we include “via [Partner]” on LP; you include “free for 7 days” in blurb.
    • Timeline: asset delivery T+48h; go‑live window within 10 days.
    • Rights: 30‑day usage on audio/text; no paid redistribution.
    • Fallback: if scheduling slips, run the 5‑min swap instead of full feed‑drop.
  9. 9

    Day 4–6 — Produce assets (audio + text)

    1. 5‑minute swap segment (yours):
    • Script (host‑voiced read, 22–28s intro): "If you build from anywhere, you’ll like The Stateless Founder. This week we’re giving [Partner] listeners a mini‑template to [Result] — free for 7 days. Search ‘The Stateless Founder’ or tap the link."
    • Body: 4 minutes with 3 bullets (problem → path → payoff), 1 CTA repeat.
    • Export: WAV 16‑bit, -16 LUFS; MP3 128kbps fallback.
    1. Feed‑drop package:
    • Episode MP3, 30–60s custom intro addressing their audience, show notes (120 words) with your UTM link.

    1. Newsletter blurb (80–100 words) + image 1200×628.

    2. Mini‑template LP copy: headline, 3 bullets, 1 CTA, FAQs (2 objections).

  10. 10

    Day 6 — QA and schedule

    • Links: Click every UTM once; verify GA4 real‑time and landing state.
    • SmartPromos: Confirm campaign shows “scheduled”.
    • Audio: Loudness check (≈‑16 LUFS), no clipping; 1× listen at 1.2× speed.
    • Files: Name correctly; store in shared folder; paste final links in Notion row.
    • Calendar: Lock dates: Feed‑drop #1 (Day 8–9), Mini‑template reveal (Day 9–10), Feed‑drop #2 or 5‑min swap (Day 11–12).
  11. 11

    Day 8–9 — Go live: Feed‑drop #1

    • Partner posts with host‑voiced intro + your notes copy.
    • You: publish a matching LinkedIn post (operator angle, 120–180 words) linking to the mini‑template LP.
    • Monitor GA4 and SmartPromos hourly for first 6 hours; confirm traffic sources and device conversions are recording.
    • SLA: watch #sla-15-referrals — respond to any demo‑intent in ≤15 minutes.
  12. 12

    Day 9–10 — Co‑created mini‑template drop

    • Flip the LP gate to open the 7‑day free window for that partner (auto‑tag signups with utm_source).
    • Partner runs newsletter/community blurb with your image + UTM.
    • You publish a 6–10 minute micro‑demo video walking from blank → result; pin the template link.
  13. 13

    Day 11–12 — Go live: Feed‑drop #2 or 5‑min swap

    • Second partner placement; keep the same CTA and UTM structure.
    • Post a 3‑bullet comment with an alternative example to lift CTR on LinkedIn.
    • Keep SLA discipline; log time‑to‑first‑reply median at day’s end.
  14. 14

    Day 13 — Pull results and close the loop with partners

    Update the tracking sheet:

    • Clicks, template_views, signups, demo_intents, qualified_demos, won_deals.
    • SmartPromos: device conversion and new devices.
    • Email partner: 5‑line recap with their stats, your stats, screenshot, and a suggested next test (longer swap, second issue, or joint teardown).
  15. 15

    Day 14 — Debrief, systemize, and queue the next sprint

    • Debrief doc (one page): What worked, what missed, best hook, best intro style, TFR median, partner fit notes.
    • Turn the best‑performing intro into your default script.
    • Duplicate the Notion board, clear dates, and pre‑load 5 new prospects.
    • If ≥1 qualified demo: keep a bi‑weekly partner slot on your calendar.
  16. 16

    Reference — Post‑attribution survey snippet (paste into your form)

    Ask on the template gate and demo booking forms. Question: "How did you first hear about us? (Pick one)" Options (shuffle):

    • A podcast: [Partner Name]
    • A newsletter: [Partner Name]
    • A community/forum: [Partner Name]
    • A friend/colleague
    • Search (Google/YouTube)
    • Social (LinkedIn/X)
    • Other: [free text] Hidden field: utm_source (prefill from URL). If user selects a partner, override utm_source with the selected value for reporting. Example (HTML):
    <label>How did you first hear about us?</label>
<select name="heard_about">
  <option>Podcast: [Partner Name]</option>
  <option>Newsletter: [Partner Name]</option>
  <option>Community/forum: [Partner Name]</option>
  <option>Friend/colleague</option>
  <option>Search (Google/YouTube)</option>
  <option>Social (LinkedIn/X)</option>
  <option>Other</option>
</select>
<input type="hidden" name="utm_source" value="[partner]" />