What I Ask Every Brand Partner After the Cameras Stop Rolling
Photo: Alexa Curtis, Public domain, via Wikimedia Commons
Last spring, after a three-week campaign with a small home fragrance brand, I did something that felt a little awkward: I sent an exit interview. Not to my audience. To the brand.
I called it a project debrief in the email, because exit interview sounds like I am quitting a job I never had. But in my head, that is exactly what it was. The project was over. The posts were live. The invoice was paid. Before I moved on to the next thing, I wanted to know what the partnership looked like from the other side of the table.
I expected a polite corporate reply. Instead, the founder sent me a 14-minute voice note. She told me the shoot day was the easiest part of the whole campaign, the approval process was the hardest, and my original concept had almost missed the product story she cared about most. That voice note changed my pitch template more than any analytics dashboard ever has.
Why I Started Interviewing the Other Side
I used to treat the end of a collab like a finish line. Deliverables sent. Thank-you note. Wait for the next opportunity. I was collecting content and call logs, but I was not collecting context.
Now I send a short debrief within 48 hours of the final deliverable going live. It is usually a five-minute Google Form, and I always offer a 15-minute call as an alternative. Low pressure. No scorecards. No long survey. Just enough space for the partner to tell me what I could not see from my own side of the project.
I do not call it an exit interview in the form itself. That phrasing can make people defensive. But that is the energy I bring to it: the project is done, and I want an honest read before I decide what to repeat.
The Three Questions I Always Ask
1. When did this project feel easiest for you, and when did it feel like work?
This question surfaces friction without asking anyone to complain. A beauty brand once told me the easiest moment was shoot day, and the hardest was the approval thread. I had assumed slow approvals were just how that team operated. In my next pitch, I included two built-in review windows and a final lock date. We closed the next campaign in nine days.
The answer does not always lead to a big fix. Sometimes it just tells me where to put more communication. That is still useful.
2. What did you expect me to do that I did not do, or that I did differently than you pictured?
This is the question that catches unspoken expectations. A home organization brand once expected the product to appear in a pantry scene. My concept was a desk drawer. They had approved the mood board, but they had not caught the mismatch until the first cut. Now I ask about expectations at kickoff, and I ask again in the debrief. The second ask is where people usually tell the truth.
3. If you could change one thing about how we worked together, what would it be, and would you work with me again?
This one combines critique and verdict. The would-you-work-with-me part is not about ego. It tells me whether this is a repeat relationship or a one-off. The change-one-thing part gives me something specific to fix. A fitness app told me they loved the final content but wished I had shared raw footage for their ads. I now offer a raw-asset add-on in my pitches. That one answer turned into a paid upsell I would never have thought to propose.
What the Answers Actually Changed
This is not just a feelings exercise. My pitch deck now has a slide called how we will work. It lists communication cadence, approval windows, asset handoff, usage rights, and a mid-project pulse check. I also mention that I send a short debrief at the end. Partners relax when they see it, because it signals that I care about their experience, not just my deliverables.
The answers also help me decide who to pitch again. If a partner gives generic praise and skips the questions, that is data too. It does not mean the collab was bad. It might mean they are busy. But if the same friction shows up twice, I do not sign a third time. That protects my calendar and my brand.
The Template I Send
I keep the email short. Subject line: Quick debrief on [project name]. Then a few lines: thanks again for the collaboration, I am doing a short debrief to improve how I work with partners, and there are three questions below. I add that there are no wrong answers and that a voice note is welcome if typing feels like too much.
After the three questions, I include one optional metrics question: anything I should know about how the final assets performed? I keep that separate because it is about results, not relationship. I do not send a 20-question survey. Three is enough to get a real answer.
The Mistake I Made First
I once sent a debrief right after a tense collab, while I was still annoyed. I asked leading questions. It was not a debrief. It was a cross-examination with a smiley face.
Now I wait until 48 hours after the final post. I write from a neutral place. I do not use the debrief to relitigate a problem. If there is a real issue, I handle it separately. The debrief is for learning, not scoring. And I never make it mandatory. It is an invitation.
How It Shows Up in My Next Pitch
My next pitch to a skincare brand included this line: you will get a shared project doc with decision deadlines, a 24-hour response window for urgent notes, and a post-campaign debrief so we both know what to repeat. The brand replied that no creator had offered that before. We booked a call the same week.
That is the whole point. The exit interview is not about closing the door. It is about learning where the hinges are so the next door opens easier. If you try one thing after your next collab, send three questions. Keep it short, keep it kind, and actually use the answers.