The 5 Questions To Ask Before You Say Yes To Any Collaboration
The ask never arrives in a form that invites a decision
It shows up as a lovely email from a lovely person. Usually someone you like. Often someone you've been hoping would ask.
There's a deadline attached, close enough to feel urgent. The roster already has names you recognize. And the whole thing is worded warmly enough that saying anything other than yes feels vaguely rude.
So the yes happens in about ninety seconds. Not because of bad judgment. Because the ask arrived in a shape that makes fast agreement the path of least resistance, and there's no obvious moment built in where you'd stop and evaluate anything.
Then twelve weeks of your year quietly reorganize around it.
These are the five questions worth running before that ninety seconds is up. They take about ten minutes. Two of them are the ones almost nobody asks.
How do you decide which collaborations to say yes to?
Run five questions: what job it's for, whether the audience is actually yours, whether you're set up to receive them, what it truly costs, and whether the relationship is worth having regardless of results.
The five, in order:
What job am I hiring this collaboration for?
Is this actually my audience, or an adjacent one?
Do I have anywhere for these people to land?
What does this actually cost me, all in?
Would I want to work with this person again even if nothing else came of it?
The order matters. Question one makes the other four answerable, and questions three and four are the ones that get skipped.
1. What job am I hiring this collaboration for?
Pick one primary job before you say yes: volume, revenue, relationships, or message testing. Everything downstream depends on this answer.
Four jobs a collaboration can do. Pick a primary.
Volume. Names on your list, quickly. Revenue. Sales in a defined window. Relationships. Hosts, contributors, referral chains, the people you'll be working alongside for years. Message testing. Finding out what actually lands with people who have zero context for you.
Most can produce two of these. Almost none produce all four, and the ones being pitched to you as producing all four are being pitched, not described.
The reason this question comes first is that it converts every other question from a matter of opinion into a matter of fact. A bundle taken for volume is a good decision. The identical bundle taken for revenue this quarter is a bad one. Same event, same effort, opposite verdicts, and the only variable is what you decided it was for.
Naming the job is the first move in making collaborations actually convert.
Write the answer down somewhere you'll find it in ninety days. Then, when you're evaluating what it produced, you're checking against the job you actually took it for rather than whatever you happen to want that week.
2. Is this actually my audience, or an adjacent one?
Adjacent audiences are the most common expensive mistake. A large audience of people one step removed from your buyer will produce volume and almost nothing else.
The obvious mismatches are easy. Nobody joins a collaboration for an audience with no connection to their work.
The costly ones are the near misses. The host has a real audience, engaged, sizable, in something that sounds like your field. And they're one step off. Beginners when you serve people five years in. Service providers when you sell to course creators. People with the same job title and a completely different problem.
The tell is usually stage rather than topic. Two people can both be "email marketing" audiences while one is full of people trying to send their first newsletter and the other is full of people with a list of four thousand trying to make it convert. Those are different businesses and different buyers.
Worth asking the host directly: who's in the room, what stage are they at, what do they usually buy. Good hosts know and will tell you. A host who can't answer is telling you something too.
3. Do I have anywhere for these people to land?
The honest readiness check. If the nurture rhythm isn't running yet, the collaboration isn't the thing to fix first.
This is the question people skip because it's about them rather than the opportunity, and it's uncomfortable in a way the others aren't.
Three things to check:
Is there a specific place for them to arrive that connects to whatever they'll have just met me through, rather than a general front door?
Is there a rhythm running, actually running, that these people will land inside of?
Is there something small and related they could buy without having to leap straight to the biggest thing I sell?
If the answer is no across the board, the collaboration will do exactly what it's supposed to do and produce very little anyway. Not because anything went wrong. Because borrowed attention needs somewhere to go.
This isn't a reason to never say yes. Plenty of good reasons to do one anyway, and question five is one of them. But knowing the answer changes what you expect, and expecting the right thing is most of what keeps you from concluding collaborations don't work.
4. What does this actually cost me, all in?
Hours, your own list's attention, and whatever you won't do that week. Collaborations feel free because no invoice arrives.
Nobody sends you a bill, so the cost registers as zero and the decision gets made against a blank column.
The real figure:
Your hours. Prep, creation, recording, promotion, follow-up. A rough number is fine. Rough and written down beats precise and imagined.
Your list's attention. If you're promoting to your own audience, you're spending something finite on somebody else's event. That's often the right trade. It's never free.
The thing you won't do. The offer you don't promote that week. The launch that slides. This is usually the biggest number in the column and the one that never gets entered.
Two collaborations that look identical on the upside can be wildly different once this side is filled in. And a small one with a low cost frequently beats a prestigious one that eats a month.
Which you only find out by measuring both sides properly.
5. Would I want to work with this person again even if nothing else came of it?
The relationship is often the largest thing a collaboration produces. It's also the only part that compounds regardless of how the numbers land.
Strip out the subscribers. Strip out the sales. Would you still be glad you did this because of who you'd now know?
If yes, that's frequently enough on its own. Relationships are the quietly compounding asset in all of this. Hosts recommend people sideways. Contributors become collaborators. Year three of doing this looks nothing like year one, and the difference is mostly who you know and what you're like to work with.
This question also works in reverse, which is where it earns its place. A host who's disorganized, vague about details, late with everything, or a bit extractive with contributors is going to be all of those things for the next three months, and you'll be inside it. The numbers would have to be extraordinary to justify that, and the numbers are rarely extraordinary.
Ask people who've worked with them before. It's a normal question and everyone answers it honestly.
What if you get a mixed answer?
Mixed is normal. The test isn't five yeses, it's whether the honest answers still add up to a reason.
Almost nothing scores five for five.
What tends to work: a clear job, a genuinely good relationship, and a cost you've actually counted. Those three carrying a bit of weakness elsewhere is usually a fine yes, taken with clear eyes.
What tends not to work: no named job, an adjacent audience, and nothing built to receive people. That combination produces the collaboration you'll be vaguely disappointed by in November without being able to say why.
The point of the five questions isn't to generate more nos. It's to make the yeses deliberate, so that whatever happens afterward is information rather than a mystery.
How do you say no without damaging the relationship?
Quickly, warmly, specifically, and with a door left open. A fast clear no is a favor to a host, and they know it.
This deserves more attention than it gets, because the fear of the relationship cost is what produces most of the reflexive yeses.
The mechanics:
Answer fast. Hosts are filling a roster against a deadline. A no on day two is genuinely helpful. A no on day nineteen, or worse, a slow fade into silence, is the thing that actually costs you.
Be warm and specific about why. Capacity, timing, fit, whatever the true reason is. Specific reads as respect. Vague reads as a soft brush-off, even when it isn't.
Leave the door open if you mean it. Ask about the next round. Say what timing would work. Hosts remember who was gracious about a no far more than you'd expect.
Offer something small if you have it. A name they should ask instead. A share when it launches. Costs you nothing and lands as generous.
The people who say no well get asked again. The people who go quiet don't, and they never find out why.
That's the same hospitality that runs through everything else here, just pointed at peers instead of an audience. People get to decide what's right for them at their own pace, and that includes you deciding about someone else's event.
When should you say yes even though the numbers don't justify it?
When the relationship is worth it on its own, or when you need to test your message on a cold room.
Two situations where the math looking unimpressive doesn't matter.
The person. Someone you've wanted to work with, whose audience is small, whose event will produce modest numbers. Say yes. That's a relationship investment and it's usually the highest-returning kind of yes there is, on a timeline nobody's dashboard is measuring.
The test. A room with no context for you is one of the few places you can find out whether your message actually holds up. If a line lands cold, it'll land anywhere. That's worth real money and it never shows up as revenue.
Both of these are still question one. Job named, expectations set accordingly, no disappointment on the back end. The only bad version is taking one of these and then judging it on subscriber count in week three.
The part I actually care about
Nobody's short on opportunities. What's short is the ten minutes before the yes.
Five questions. A few notes in whatever you use. Then the collaboration you say yes to is one you chose on purpose, for a reason you wrote down, with a cost you counted and an expectation that matches reality.
Which is a completely different experience from the one where a lovely email arrives and twelve weeks quietly rearrange themselves around it.
What happens after the yes is its own thing entirely.
