So I’ve been thinking about this a lot lately. I’ve worked with a handful of partners over the past couple of years—some conversations started casual, some started with a formal SOW. The ones that stayed casual often fell apart when the first real problem came up. The ones with agreements… well, some worked, some didn’t, but at least there was clarity about expectations.
But here’s my dilemma: I don’t want to come across as overly formal or rigid when I’m first connecting with someone. A lot of the best partnerships I’ve seen started with just a handshake and a shared vision. Yet I’ve also watched partnerships implode because nobody wrote down who was responsible for what.
I’m running an agency where we’re now actively trying to work with partners across borders—US brands, Russian agencies, creators. And every single one of those collaborations has some level of complexity. Different currencies, different business models, different legal expectations.
So the question isn’t really “should we have contracts?” It’s more like: at what point does it make sense to formalize things? And what should actually be in writing versus what can stay flexible?
I’m curious whether anyone here has figured out a sweet spot—a way to move fast and stay flexible while also protecting both sides. What’s your actual experience been?
Here’s my framework: formalize before money moves, but keep it simple at first.
What I mean is—you don’t need a 20-page legal document to start working together. But you do need something that covers:
- What each side is responsible for
- Timeline and deliverables
- Payment terms and amounts
- What happens if something breaks
I’ve used simple one-page SOWs that work great. Just enough structure to prevent arguments later, not so much that it feels bureaucratic.
The reason I recommend this: once money is involved, assumptions become expensive. Someone thinks they’re owed X, the other person thinks X was conditional. Suddenly you’re in a conversation about money, which is way harder to untangle than it should be.
So I’d say: have the conversation casually, feel out compatibility, then put the basic terms in a simple document before you start. Not as a negotiation tactic—just as clarity.
One more thing: include an exit clause. What happens if one side wants out? What happens if a campaign flops? Having that in the document upfront means you’re not making those decisions in a crisis. You already agreed on it when things were good between you.
I’m going to push back slightly on the “formalize before money moves” advice, though I respect where it comes from.
My experience: the first project with a partner should be small enough that you don’t need heavy paperwork. Maybe it’s a $3-5K test, or a brief collaboration on a single campaign. You figure out how you actually work together.
Once you know it’s working? Then yeah, put together something more formal. But trying to nail down every detail before you’ve ever actually worked together is just guessing.
My approach: first project is literally just email confirmation of scope and fee. Nothing legal, just clear. If it goes well, we talk about formalizing for bigger stuff.
I’ve seen partnerships die because we spent three weeks negotiating a contract about a situation that never actually came up. Meanwhile, the momentum died and everyone moved on to other things.
So my take: start minimal, prove trust, then formalize.
But yeah, once you’re doing real work together—multi-month campaigns, bigger budgets—definitely get something in writing. You want to know what “success” looks like and what happens if you don’t hit it. That’s just being professional and protecting both sides.
I think the emotional side of this matters too. Some people feel like contracts mean you don’t trust them. But actually, a good contract is about showing respect—it means you care enough to get aligned.
The partners who bristle at putting basic terms in writing? Those are usually the ones who become problems later. The good ones actually appreciate clarity.
I always frame it positively: “Hey, I want to make sure we’re both set up to succeed. Let me send over a quick one-pager so we’re on the same page.” Nobody’s ever pushed back on that framing.
For cross-border stuff specifically, I think it’s even more important because you’ve got different legal contexts. You want to at least acknowledge what happens if something goes wrong or if expectations diverge.
From a data perspective, I’d say: put the measurable stuff in writing. Revenue splits, deliverables, timelines, metrics for success. The fuzzy stuff—culture, communication style, vision alignment—that’s harder to pin down, but the concrete stuff absolutely goes in the document.
I’ve reviewed dozens of partnership agreements, and the ones that actually prevent problems are the ones that are specific about what “done” looks like. Not vague. Not “we’ll increase engagement”—actual numbers.
Also, include a clause about reporting and transparency. How often will you check in? How will you measure results? That’s where cross-border partnerships often break down—you don’t have visibility into what’s actually happening on the other side.
Real talk from someone early-stage: I’ve kept most of my partnerships flexible because I don’t actually have money for legal reviews. But every time I’ve regretted that choice.
So now what I do is: I use templates. Simple Google Doc templates that cover the basics. I’m not a lawyer, but I’m also not leaving everything to chance anymore.
I think for anyone working cross-border, this is especially true. Different countries have different expectations about what’s binding versus what’s just a conversation. So actually putting something in writing—even something simple—protects you.
My rule: if it’s under $1K and it’s a one-off, keep it simple. If it’s anything bigger or ongoing, template agreement. Takes 20 minutes and saves so much grief.