Most partnerships start with enthusiasm. Two companies like each other, see an obvious fit, and want to move fast. The deal gets done on goodwill and a short agreement. Then, twelve to eighteen months later, someone feels the split is unfair, a key customer relationship is muddy, and nobody's sure how to unwind it.
Partnerships rarely fail because the other side is bad. They fail because the important terms were never made explicit while it was still easy to talk about them.
Start with the result, not the relationship
Before talking terms, write down what this partnership has to make possible. New revenue? Access to customers you can't reach? A capability you don't have? Faster entry into a market?
Then ask a sharper question: why partner instead of doing it yourself? Good answers: they control access you can't get, they materially speed you up, or they share real risk. A weak answer: "they're great people and it feels right."
Check who needs it more
Every partnership has a balance of need. If you need them much more than they need you, you'll make concessions over time, whether you plan to or not. That doesn't mean don't do it. It means price that imbalance into the terms now, and build a credible alternative so you're not trapped.
Ask yourself: if this partnership disappeared tomorrow, what would we do? If the answer is "we'd have no option," you have a dependency, not a partnership.
Model what you actually keep
Headline revenue is misleading. Take the expected annual revenue, subtract the partner's share, your delivery cost, and the internal time it takes to manage the relationship. Then discount it for how proven the demand really is. Positive conversations aren't pipeline. A paid pilot is.
Picture a channel deal projected at a large annual number. After a 30% revenue share, delivery costs and one full-time person to manage the relationship, the retained margin is small, and that's before you discount for the fact that no customer has signed yet. The deal might still be worth doing. But you should know that before you sign, not after.
Write the exit while you're friends
Agree in writing on who owns the customer relationship, who controls pricing and delivery decisions, how either side can exit, and what happens to shared customers, data and work if you do. These conversations feel awkward early. They're far worse late.
What to do this week
- Write the one result the partnership must produce.
- Answer "why not do it ourselves" in one sentence.
- Model retained margin, not headline revenue.
- Name your fallback if the partner walks away.
- List the three terms you must agree on before signing: customer ownership, control and exit.
Partnership Decision Engine
The Partnership Decision Engine walks you through outcome, economics, contribution, risk and decision, so you can see what you actually keep after revenue share and delivery cost, who controls what, and the conditions to negotiate before you commit. Nothing you enter is uploaded.
Know the deal before you make the deal.
Open Partnership Decision Engine →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →