When Someone Asks to Partner With You
Someone emails you. They think there’s a great opportunity to work together. They’d love to explore synergies. Their audience would be perfect for your product, and vice versa. Could you find 30 minutes this week?
The instinct, especially if business is going well and you’re feeling generous, is to say yes. But most inbound partnership requests, even the genuinely well-meaning ones, aren’t worth a meeting, and the faster you can work that out the better for everyone involved.
The problem with treating all inbound as flattery
An inbound request feels different from a cold sales pitch. Someone is coming to you, which carries a small psychological charge. It implies you’ve done something right, that you’re visible, that people want to attach themselves to what you’re building. That feeling is worth being suspicious of, because it’s exactly the feeling that leads teams to spend two months in exploratory conversations with a company that was never a real fit.
The opposite trap is just as real: declining too quickly, too bluntly, and leaving the other party feeling snubbed. A bad exit from a partnership conversation can damage a relationship that would otherwise have been useful, just not in the form they proposed.
What you need is a lightweight filter you can run in five minutes, before you commit time to either outcome.
Four questions worth asking before you book a call
What, specifically, are they proposing? Vague requests, “I think we could do something together” or “there seems to be a natural fit here,” are a signal that the other party hasn’t thought it through yet. That doesn’t make them bad partners, but it does mean the first meeting will be spent doing the work they should have done before reaching out. It’s entirely fair to reply asking them to sketch the specific arrangement they have in mind: a referral exchange, a co-marketing campaign, a reseller agreement, an integration. If they can’t answer that in writing, a call isn’t going to produce clarity.
Who exactly would benefit, and how? The most common failure mode in partnership conversations is that the proposer has a clear picture of what they get and a vague optimism about what you get. Before you meet, try writing down, in one sentence each, what your company gains and what theirs gains. If you can’t write your sentence, that’s worth knowing before you spend an hour on a call finding out.
Does this fit the company you are right now? It’s very easy to evaluate a partnership against the company you imagine being in 18 months rather than the one you’re actually running today. A referral arrangement with a large enterprise software firm sounds compelling in the abstract, but if your sales team is two people and your onboarding process can’t handle a sudden surge of leads, the timing is wrong regardless of the fit. Evaluate against your actual capacity, not your aspirational one.
What does it pull you away from? Every partnership, even a light one, costs real time: kick-off meetings, co-ordination overhead, the internal alignment required to make anything happen. Before saying yes to a call, name concretely what that time would otherwise be spent on. If the honest answer is “something more important,” you have your decision.
What to do when the answer is no
Declining is less awkward than most people fear, provided you’re direct and reasonably quick about it. A reply that arrives three weeks later, after several chaser emails, is far more damaging to the relationship than a prompt, honest no. Something like “it doesn’t fit our priorities right now, but we’d be glad to revisit in Q3” is specific enough to be respectful and leaves an actual door open rather than a polite fiction.
The “not now” framing is genuinely useful, not just as a face-saving device but because circumstances do change. Keeping a short record of declined conversations, with a note on what would need to be different, costs almost nothing and occasionally pays off when the timing finally lines up.
When the answer is yes
If the request passes the filter, the most useful next step before any formal commitment is a bounded, measurable pilot. Agree on what a successful first 60 or 90 days would look like, put a specific number on it, qualified referrals accepted by both teams, content published, integrations tested by real users, and review the result before expanding scope. Most partnerships that eventually fail do so because they scaled before anyone had evidence that the underlying mechanics actually worked.
It’s also worth sharing your evaluation criteria openly from the start. A partner who knows you’re measuring audience overlap and referral quality upfront, rather than discovering it during a tense quarterly review, will work more productively within those parameters throughout.