How to actually vet us-based subcontractors before your first joint campaign—what questions do you ask?

Hey everyone. I’m Alex, running a boutique agency here, and we’ve been trying to expand into cross-border work more seriously. The thing is, every time we’ve outsourced to someone new—whether it’s a US-based partner or anyone else—there’s always this moment of doubt: “Are they actually going to deliver what we agreed on, or are we going to get something that needs a complete rework?”

I’ve learned the hard way that portfolio alone tells you almost nothing about how someone actually works. I’ve seen gorgeous case studies that turned into absolute nightmares when we actually had to collaborate. The communication gaps, the different interpretations of briefs, pace mismatches—it kills momentum fast.

Recently, I started asking different questions before we even shake hands. Not just “show me your work,” but stuff like: How do you handle feedback loops? What’s your process when a brief feels ambiguous? How do you work across time zones without everything taking three times longer? Have you worked with bilingual briefs before, and what tripped you up?

I’ve also noticed that the vibe of a potential partner matters way more than I thought. If someone gets defensive about clarifying scope or acts like we’re being difficult for asking questions, that’s usually a red flag for later.

I’m curious—what’s your actual vetting process? Do you test them on a small project first, or do you have a set of questions you ask upfront that actually predict how the partnership will go? And more importantly, what’s the one thing you wish you’d asked before signing on with someone and realizing mid-project that it wasn’t going to work?

Great question, Alex. From my perspective managing DTC campaigns, I’ve developed a pretty structured approach. I treat the vetting process like a mini-case study. I describe a realistic scenario—something like: “Our client’s UGC brief got flagged by legal halfway through, and now we need three alternative concepts in 48 hours without blowing the budget.” Then I see how they respond. Do they panic? Do they ask clarifying questions? Can they think through the constraints?

I also ask specifically about their last failed project—not their successes. How did they recover? What did they learn? Someone who can articulate failure clearly is usually more dependable than someone with a spotless portfolio.

One more thing: I always check references, but I ask the references a different question than you’d expect. Instead of “Do you recommend them?” I ask, “When was the last time they pushed back on you, and was it justified?” You want partners who aren’t yes-men.

Also, regarding time zones and communication—I’ve started documenting everything in a shared Notion or Asana during the vetting phase, even for conversations. It shows immediately whether someone is willing to work within a structured system or if they’re going to insist on doing things their way. That’s been surprisingly predictive of long-term compatibility.

Mark’s advice on the failure question is gold. I did something similar recently—asked a potential subcontractor about a project that didn’t go as planned. The way they explained it told me everything. One person owned it, explained what they’d do differently, and moved on. Another made excuses and blamed the client. Obvious choice.

I also started doing a paid trial project now. Usually something small—maybe 3-5 days of work, clear deliverables, real money changing hands. Not a “test” per se, but actual work with actual stakes. You learn more in those three days than you would from any interview.

I love this thread because it’s so practical. From the partnerships side, I’d add one thing: talk to them about their ideal client, not their portfolio clients. Ask them, “What kind of project makes you excited to wake up in the morning?” If their answer is “anything that pays,” you’re probably not aligned. If they light up about something specific, that usually means they actually care about doing good work in that space.

I’ve also found that asking about their communication style upfront saves so much friction. Some people are Slack warriors; some need everything in writing in formal documents. Some love weekly syncs; others find them draining. Talking about this openly feels a bit awkward, but it beats discovering incompatibility three weeks in.

And if you’re working cross-border, definitely ask about their experience with cultural differences in briefs. Have they navigated that before? Do they get that a brief written for a Russian audience might need different nuances than one for a US audience? That’s not obvious to everyone, and it matters.

From a data perspective, I track one metric that’s been surprisingly predictive: revision rounds. I ask potential partners whether they can estimate, on average, how many revision rounds a typical project goes through before final delivery. Their answer tells you a lot about their clarity in execution and communication.

If someone says zero revisions—red flag. If they say five or six on average, also a bit of a concern. The sweet spot I’ve found is 1-2 rounds max, which suggests they either really understand briefs or have a disciplined communication process.

I also ask about their project success rate—what percentage of projects come in on time and on budget? And more importantly, by whose definition of success? Theirs or the client’s? That distinction matters.

One thing I learned the hard way during expansion: always ask about their expansion experience. If you’re planning to scale work with them, do they have a history of growing teams or capacity without losing quality? I partnered with someone amazing who could handle it locally, but when we tried to scale to three simultaneous projects, everything fell apart because they had no system.

Now I specifically ask: “If we grow this from one project to five projects a month, how would your team structure that? What would scale? What wouldn’t?” If they haven’t thought about this, they’re not ready for growth partnerships.