You will be offered more partnerships than you can ship. The skill is declining without making an enemy, and without leaving a zombie in the CRM.
Three honest nos
Bad fit. “We do not have overlapping customers or a workflow we would both own. I would rather say no than start something we cannot finish.”
No window. “This is real, and we do not have engineering time in the next two quarters. If you want to stay on a watchlist, I will write you when that changes. I will not pretend we are in build.”
We already have the workflow. “We already connect to Y for that job. Adding a second connector would split support. I am not going to do that.”
Do not hide behind “let’s revisit next year” unless you mean it and you have a date.
When the CEO wants the logo
Use the matrix, not a speech. Customer pull, distribution, build cost. If the logo is low on all three, say that in the room. Your job is to protect the roadmap, not to protect the CEO’s conference high.
If they override you, write it down: “Proceeding as an exception. No engineering this quarter. Partners page only.” Then do not spend your week on it.
After the no
Log it. A no with a reason is an asset. In six months the product may have moved. You can reopen with a fact, not with guilt.
Ghosting feels kinder in the moment. It is ruder. Partner managers talk. A two-sentence no is how you keep a reputation while you protect the book.