When you're pitching a cross-border UGC deal but the brand brief changes mid-project—who actually absorbs the extra work?

This happened to me last month and it’s been bugging me. I was working on a UGC project for a US brand through a partnership on the platform. The original brief was pretty clear: 5 videos, specific messaging around product features, target audience was US-based. I quoted, they approved, I started production.

About 40% through, the brand decides they also want the content adapted for Russian TikTok audiences. Not just translated—adapted. Different hooks, different pacing, different cultural references. Suddenly I’m looking at 50% more work. I flag it immediately, but then there’s this weird back-and-forth about whether this “counts as a change” or if I should have anticipated it from the start.

Here’s where it gets messy: I’m in Russia, the brand is in the US, they’re working through an agency that’s in a third timezone. By the time clarifications come back, I’ve already lost momentum. The scope creep isn’t huge in absolute terms—maybe 8-10 additional hours—but it’s enough to eat my margin. And I feel like there’s an expectation that cross-border people should just absorb this complexity because “you’re working across markets.”

I didn’t push back hard enough, quoted a slightly higher rate for the extra work they eventually agreed to, but it felt awkward. The relationship didn’t break, but it left a weird taste.

How are you guys handling this? Are you building buffer time into cross-border quotes? Fighting harder on scope? Or is this just the cost of doing international work?

YES. This is so real. I’ve learned to be really explicit in my contracts now about what counts as a revision and what counts as a new project. I literally have a line item that says “Scope includes X. Anything beyond X is billed at $X per hour.” It feels overly formal at first, but it actually protects both sides. The brand knows exactly what they’re getting, and I know what extra work means. For cross-border stuff specifically, I now include a line about localization—“localization to one additional market = $X additional” or whatever. It sounds sterile, but honestly it makes conversations way easier because it’s not about me enforcing boundaries, it’s about what we both agreed to.

Also, I started asking questions upfront that expose scope creep before it happens. Like, “are you planning to use this content in any markets other than the US?” If they say “maybe” or “we’ll see,” I either build that into the quote or I explicitly say it’s not included. Most brands are reasonable if you ask early.

From a data perspective, cross-border project creep happens in about 70% of deals where the brief doesn’t explicitly lock down deliverables by market. The pattern I see: US brands don’t think geographically at project start, then realize partway through they need adapted content. Russian teams absorb it because we’re trained to be flexible. It becomes a hidden subsidy. What actually works: build a “market scope matrix” into your contract. List which markets the content will be used in, and any localization beyond that is Change Order #1. Document it, price it, get approval. It sounds rigid, but it actually creates consistency across your portfolio because you’re treating every project the same way.

I see this happen a lot when I’m brokering deals. Honestly, I try to prevent it at the contract stage by asking the brand hard questions: “Where will this content live? What markets? What languages? Any TikTok adaptation needed?” Most brands haven’t thought that far ahead, so when I force them to think about it upfront, scope clarifies. Then when the creator sees the brief, there are no surprises. It’s easier to prevent scope creep than to fight about it mid-project.

We handle this by separating “core deliverables” from “optional enhancements.” Core deliverables are fixed price. Enhancements (like market-specific adaptation, additional rounds of revisions, new platform formats) are scope additions. In the contract, we’re explicit: “This quote includes X. If the brand wants Y, we execute a change order.” Sounds bureaucratic, but it’s actually protective of the creative relationship. The brand can’t surprise you, and you’re not grinding yourself down for margin. I also build a 10-15% time buffer into ambitious cross-border projects because timezone delays and async communication are real. That buffer usually absorbs the small stuff without friction.

We got burned on this early and now we handle it differently. When we’re building creative campaigns with distributed teams, we literally have a “what counts as scope” conversation in the kickoff. We list the deliverables, the revisions included, the timeline, and we’re explicit about what changes that. If a brand wants to add a market, we treat it like a product roadmap—scope change, timeline impact, resource impact, price impact. Showing the impact makes it real to them instead of abstract. Most reasonable brands will adjust the timeline or the price to match, or they’ll adjust the scope.

Here’s my take: the issue isn’t specific to cross-border work—it’s scope clarity. Yes, timezone friction and language barriers make it worse, but the root problem is the brief. Before any project starts, I require explicit alignment on: deliverables (what are you actually making?), markets (where will it live?), audiences (who’s seeing it?), and revisions (how many rounds, what qualifies as a revision vs. new work?). When a brand says “we want to adapt for Russian TikTok,” I ask: Is that in scope, or is that a new project? If they waver, I offer a scenario: “We can either include that in the quote upfront for X%, or we do the US version first and treat Russian adaptation as Phase 2 with separate pricing.” This makes it a strategic choice, not an afterthought. Most brands choose Phase 2 when pricing is transparent.