Partner Sourcing Plan

free skill · agency-operations

Find the partners whose customers are your buyers, and structure the first conversation so it produces something.

Install it
bash
/plugin marketplace add mambalabsdev/mamba-labs-skills

What it does

Partner brainstorms produce a list of well known companies who will not reply. The partners worth approaching are the ones already serving your buyers with something adjacent, and that overlap is detectable rather than guessable. This skill finds them by overlap and structures the first exchange around a small reciprocal test rather than a partnership agreement.

When to use it

  • find referral partners
  • co marketing
  • channel partnerships
  • who should we partner with
  • warm route into a market

What it needs from you

  • customers: your customers and what else they buy
  • offer: what you would give a partner
  • capacity: how many partner relationships you can actually service

Live data it reads

Overlap is detected from the tools your customers already run and the vendors present on their sites, so the partner list comes from evidence rather than from a brainstorm. - gtm-tech-stack-signal-scraper: the adjacent tools your customers already run Store page: https://apify.com/mambalabs/gtm-tech-stack-signal-scraper - company-social-presence-mapper: the partner's reach and audience Store page: https://apify.com/mambalabs/company-social-presence-mapper Runnable example input:

How it works

  1. Detect the overlap. Look at what your existing customers already use and who already serves them adjacent to your offer. That set is the partner list and it is evidence rather than a guess.
  2. Rank by overlap size and by whether the partner has an incentive. A partner with a large overlap and no reason to care will not act.
  3. Decide what you give before what you ask. A first approach that leads with an ask is a cold email with extra steps.
  4. Structure the first exchange as a small reciprocal test: one introduction each way, or one piece of content each, with a date. Partnership agreements before a test are how these die.
  5. Set the measurement: what a successful test looks like in referrals or meetings, and by when.
  6. Cap the number of relationships at what can be serviced. An unserviced partner relationship is worse than none because it consumed the introduction.
  7. Write down what happens if the test produces nothing, so the relationship ends cleanly rather than lingering.

What you get back

The detected partner list ranked by overlap and incentive, what you give per partner, the reciprocal test with a date, the measurement, the capacity cap, and the clean ending condition.

The quality bar

  • Partners are found by detected overlap, not by brainstorm
  • Partner incentive is assessed, not assumed
  • The first exchange is a small reciprocal test with a date
  • The relationship count is capped at serviceable capacity
  • An ending condition is written

Where it runs

  • Claude Code
  • Codex CLI
  • Cursor
  • MCP-compatible agents

Get the skill

We will email you the install command and a link to the skill. No account, no purchase.