Saying no to a collaboration: how to do it well

When you are starting out, turning things down feels almost impossible. It seems like saying no to work. In fact you are protecting the only thing that makes that work valuable: that people trust what you recommend.

When saying no is the right call

When you would not use the product. Recommending something you are not convinced by shows, and it works exactly once.

When the offer does not cover the work. Three pieces and several rounds of revisions in exchange for a small product is not a collaboration, it is working for free.

When they want to dictate every word. If the script arrives closed, they have not hired you, they have hired your profile as a billboard.

And when the business does not fit the people who follow you. If your people are from your neighbourhood and the proposal is from the other side of the city, it serves nobody.

How to say it

Quickly and clearly. What burns bridges is not the no, it is the two weeks of silence.

Without inventing excuses. "It is not a fit for me right now" is enough, and it is almost always true.

And leave the door open where it makes sense: "not this, but if you ever do X, write to me". Plenty of good collaborations start out as a no to something else.

What not to do

Accepting out of obligation and doing it half-heartedly. It hurts the business, it hurts you, and it leaves lukewarm content that helps nobody.

A well-delivered no today is worth more than a forced yes: whoever asked will come back when they have something that genuinely fits.