Five Questions After the Invoice: The Client Exit Interview We Never Skip

There's a specific silence that follows a finished project. The deliverable is approved, the invoice is paid, the thank-you email has been sent and replied to with a thumbs-up. Everyone is behaving beautifully.

That silence is exactly why we wait.

Why ask after the money clears

Ask a client how the project went during the final review and you get a verdict, not information. "Love it." "Great working with you." "We'll definitely be in touch." Nobody wants to critique a studio while there's still an approval sitting on the table.

A week after the invoice clears, that pressure is gone. There's nothing left to hold hostage. People get specific, and specific is the only thing that's useful.

So we send a short exit interview — five questions, one page, no scoring, no NPS widget, no "rate us 1 to 10." Just a reply-all email from a real person. Our response rate hovers around seventy percent, which is absurdly high for a survey and probably tells you something about how little most clients get asked.

The five questions

1. Walk me through the moment you felt least sure about the project.

Not "what didn't you like." That question produces polite nothing. Asking about the moment of least certainty produces a story, complete with a date and a reason. Roughly a third of the answers point at a specific review round where the client wasn't sure we'd understood something — and said nothing at the time.

2. Where did our feedback loop get confusing?

We ask this almost every time and we still get surprised. The most common answer isn't "too many rounds." It's "we weren't sure which of your questions were real questions and which were rhetorical." Which is fair. Designers ask a lot of questions that sound like decisions.

3. Was there a point where you didn't know who was approving what?

Approval ambiguity is the most expensive form of confusion in this business. It doesn't produce a bad deliverable — it produces three weeks of drift, a re-open, and a scope conversation nobody wants to have. We ask explicitly because clients rarely volunteer it.

4. What did we do that you'd want us to do again on the next one?

We stole this framing from a client who used it on us. Asking about the positive half of the experience isn't flattery — it's the only way to know which of your habits are load-bearing. Ours, apparently: the weekly two-paragraph status note. Clients cite it constantly. Internally, we had no idea anyone noticed.

5. What's one thing we should change before you hire us again?

Singular on purpose. "What could we improve" invites a list of nothing. "One thing" invites an actual thing.

What the answers actually changed

Three concrete internal shifts, all traceable to exit interviews.

We killed the ambiguous email round. Feedback used to arrive as a long email with numbered comments that sometimes contradicted each other. We replaced it with a single annotated file and a rule: every comment gets a status — must fix, open to ideas, or already handled. Rounds got shorter. Revision counts dropped.

We started naming a single approver at kickoff. Question three was the driver here. Too many projects had a client-side committee where the person with authority never appeared in a meeting until week six. Now we ask for one name in writing before the first file moves, and we say why.

We moved the budget conversation earlier. A cluster of exit interviews mentioned money arriving as a surprise near the end. Not because anything was hidden — because it was mentioned once, in a kickoff doc, alongside forty other things. It's now a dedicated five minutes at the start of the second week, in plain language.

Not one of those changes came out of a final review. Every single one came from a conversation that happened after the work was done.

The question that stings

Occasionally we get an answer that's not about process at all. "Honestly, I could never tell whether you liked the project."

That one lands. It's about tone, and it's not something you can fix with a status label. What it taught us is that quiet confidence reads differently than we think it does — inside the studio, restraint feels professional. From the other side of the table, it can look like indifference. We now make a deliberate point of saying when we're excited about something, in words, out loud, in writing.

It feels a little obvious in retrospect. Most of the useful stuff does.

How to run one without it feeling like a survey

A few practical notes, if you want to try this.

• Send it from a person, not a form. One page, plain text, first name in the signature.
• Wait at least five business days after payment. Long enough that the pressure is off, short enough that the details are still fresh.
• Fifth question optional, always. Some clients won't answer it and that's fine. Never follow up asking why.
• Close the loop. When an answer changes something, tell the client. "You mentioned the feedback rounds got muddy — we changed how we do it. Here's the new version." Almost nobody does this, and it converts a one-time client into someone who refers you.
• Read them in batches, not one at a time. A single exit interview is an anecdote. Six of them in a row is a pattern, and patterns are what you can actually act on.

The project ends when the files land. The relationship gets its best chance at continuing about two weeks later, in an email with five questions and no agenda.