Questions to Ask Clients After a Project
For freelancers, agency leads, consultants and contractors closing out a finished job with a client, on a wrap-up call or in a short follow-up form. The questions follow the order a good debrief takes: the result, the process, communication, what to change, loose ends and what comes next. Each has a note on what a good or a worrying answer sounds like and what to do with it, and an agency can read 'we' wherever a question says 'I'.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The result
Did the project achieve what you hoped for when you first got in touch?
Why ask it
Read the goal back from the brief or proposal before you ask, so you are both judging the same thing. A good answer names the goal and points at something that shows it was met. 'I think so' usually means nobody has checked yet, so ask what would settle it and when.
On a scale of 1 to 10, how happy are you with the finished work?
Why ask it
The score is only the way in. Ask what would have made it one point higher, because an 8 with a reason is more use to you than a 10 with none. On a follow-up form, put this first, since it is the quickest to answer, and follow it with a box asking why.
What is different for you now that the work is in place?
Why ask it
This asks for the effect, not for an opinion of you, so clients find it easy to answer honestly. Hope for something concrete, such as a task that no longer lands on them or a complaint that has stopped. If nothing has changed yet, ask whether the work is in use, since a result still sitting in a folder is the more urgent problem.
Which part of what I delivered has turned out to be the most useful?
Why ask it
It is often not the part you spent longest on. Whatever they name is what to lead with when you describe this kind of job to the next client, and what to protect if a future budget is tight.
Is there any part you are not using, or using less than you expected?
Why ask it
An unused deliverable is feedback on the brief as much as on the work. Ask what got in the way: no time, no one trained to run it, or a poor fit with how they work. A short session may fix the first two, and the third is a note for how you scope the next job.
How does the finished work compare with what you pictured at the start?
Why ask it
The picture in a client's head rarely makes it into a brief in full. 'Better than I imagined' and 'different, but it works' are both fine. 'Not quite what I had in mind' needs a follow-up about when they first noticed the gap, because that is where a check-in was missing.
What have the people who work with it every day said?
Why ask it
The person who hired you is often not the person who lives with the result. Staff, customers or a manager above them may have a view your contact has only half passed on. If nobody has been asked yet, suggest they ask before your next conversation, and offer to sit in.
Is there a figure you are watching to judge this, and where does it stand today?
Why ask it
Sales, inquiries, hours saved, error counts: whatever the job was meant to move. Write down the figure and the date so you can compare it later. If there is no figure, do not push one on them, and ask what they would look at instead, even if it is only how the week feels.
Is it too soon to judge the result, and if so, when should we look again?
Why ask it
Some work shows its value weeks or months after handover. Let the client pick the date, since a check-in they chose is welcome where one you invented can feel like chasing. Put it in your calendar before the conversation ends, and say what you will both check.
Looking at what you paid and the time you put in, did this feel worth it?
Why ask it
It is uncomfortable to ask, so it often gets skipped, yet the client is weighing the same thing. A quick yes is a strong sign that they would come back. A hesitation is rarely about the fee alone, so find out whether it was the cost, the effort on their side or the wait to see something back.
The process
Which stage went most smoothly from where you sat?
Why ask it
Open the process questions here, because people criticize more freely once they have said something kind. Ask what made it smooth. If the answer is 'I always knew what to do next', that is a thing to copy into the stages that went less well.
Did you feel I understood your business and what you needed from this?
Why ask it
Hope for a yes with an example, such as a suggestion that fit how they really work. 'Eventually' means the early weeks went on teaching you, and they were paying for those weeks. Ask what you should have read, seen or been told before you began.
Where did things feel slow, confusing or like more effort than they should have been?
Why ask it
Offering three words lets the client pick one, which is easier than volunteering a complaint from nothing. Ask for the particular week or handoff. A vague 'the middle dragged a bit' turns useful once you learn it was the ten days they waited on a draft.
What surprised you about working with me, good or bad?
Why ask it
A surprise marks the gap between what your proposal and first call led them to expect and what the project was like. A good one is something you undersold and could mention sooner. A bad one is a line to change in how you describe your process, so ask what gave them the other impression.
How did the pace feel: too fast, too slow or about right?
Why ask it
Too slow is the complaint you expect. Too fast is the one that surprises people: a client who felt rushed through decisions may be uneasy about the result without knowing why. If that comes up, ask which decision they would have liked longer on.
When a date moved, did you understand why and know the new one?
Why ask it
A late delivery is easier to forgive than a silent one. The worrying answer is 'I only found out when I chased'. Skip this if every date held, and ask in its place whether the deadlines you gave them for feedback were realistic.
How much of your own time did this take, and was that what you had planned for?
Why ask it
A client's budget covers your fee and tends to leave out their own hours: reviewing drafts, finding files, sitting in meetings. If it took more than they expected, your next proposal should say plainly what you will need from the client each week. If it took less, that is a selling point you are probably not mentioning.
Looking back, which question do you wish I had asked you at the start?
Why ask it
By the end, the client often knows which missing fact cost everyone time. Add whatever they say to your intake questions the same day. If they cannot think of anything, ask what they wish they had told you sooner.
When the scope changed, were you comfortable with how I handled the extra cost and time?
Why ask it
A change mid-project is an easy place to lose goodwill, and a client who felt overcharged may never say so unless asked. A good answer is that they knew the price of the change before agreeing to it. If a charge surprised them, look at when you raised it, not at whether you were entitled to bill for it.
Did the final bill match what you expected to pay?
Why ask it
Ask it even when you are sure the answer is yes. A client who expected one total and received another may pay without a word and then not come back. If there was a gap, find out which line caused it and how your proposal described that kind of cost.
Was there a moment when you were worried about how this would turn out?
Why ask it
Many projects have such a moment, and the client often kept it to themselves. Ask what they did about it: if they waited and hoped, you need an easier way for clients to raise a worry early. If they told you and it was dealt with, ask what made that easy to do.
Communication
Could you tell where the project stood at any point without having to ask me?
Why ask it
The test is whether they could have answered their own boss or business partner without calling you. If they often had to ask, a short weekly status note would have covered it. Ask what they would have wanted in that note, and use their list.
Would you have liked to hear from me more often, or less?
Why ask it
There is no correct amount, only what this client wanted. Someone who says 'less' still read the updates, so ask which ones they would have dropped. Keep the answer in your notes on this client, since it is the first thing to get right if they hire you again.
When you had a question, how long did it take to get an answer you could act on?
Why ask it
The words 'could act on' matter: a fast reply that says 'I will look into it' does not count for much on their side. Slow answers at one stage usually point to where you were stretched. Leave the explanation out of the debrief and just note the stage.
Was there anything I explained that never quite made sense to you?
Why ask it
Few clients admit mid-project that they did not follow, especially on technical or financial detail. Whatever they name is still unclear to them today, so explain it again now, briefly. Then rewrite that part of your handover notes in plainer words.
When I asked for your feedback on a draft, was it clear what I needed and by when?
Why ask it
Late or scattered feedback is often the fault of the request, not the client. Listen for 'I was not sure what you wanted me to look at' or 'I did not know others had to see it too'. Either one is fixed by a short note with each draft: what to check, what is already settled, and the date.
When you disagreed with something I recommended, did you feel listened to?
Why ask it
Two worrying answers sit at opposite ends: 'you did it your way anyway', and 'you just did what I said' from a client who was paying for your judgment and wanted you to argue. Ask for the instance they have in mind before you respond.
Did you ever learn about a problem later than you would have liked?
Why ask it
This is the question about bad news. When they found out can stay with a client longer than what the problem was. If there was a case, ask at what point they would have wanted the call, and treat that as the rule for them from now on.
Who else on your side needed to be kept informed, and did they get what they needed?
Why ask it
A finance lead, a co-owner or an IT contact may have been relying on forwarded emails. If someone was left out, your contact probably spent time relaying messages, which is a hidden cost of working with you. On the next job, ask for those names at kickoff.
What to change
If we ran this project again from day one, what is the first thing you would change?
Why ask it
Asking for the first thing gets a priority, where 'any feedback?' gets a shrug. Take it down in their words and do not defend the choice you made at the time. If the answer is about their own side, such as starting earlier or involving someone sooner, it still belongs in your kickoff advice to future clients.
What should I keep doing exactly as I did here?
Why ask it
You may not know which of your habits clients value, and the ones they name are often small: a summary after each call, a reply the same day. It also balances the conversation, so the debrief does not become a list of faults. Anything named here is fair to mention when you describe how you work.
What is one thing you would like me to stop doing?
Why ask it
'Stop' draws out irritations that 'improve' does not, such as long emails, too many options to choose from, or meetings that could have been a message. Expect a pause, and wait through it. If they truly have nothing, ask what they would warn a friend about before hiring you.
Was there a point where you wanted me to push back harder, or to push back less?
Why ask it
Part of what an outside hire brings is an opinion, and some clients feel shortchanged when all they get is agreement. Others felt lectured. Which way this one leans tells you how firmly to argue with them next time, and it differs from client to client, so do not build a rule on one answer.
Was there something I should have asked you for that would have made the work better or faster?
Why ask it
It turns the debrief into a shared review and lets the client admit their own part without being accused of it. Common answers are access to a person, a decision made sooner, or real examples in place of descriptions. Build the answer into what you request at the start of the next job.
Was there something you needed during the project that you did not feel able to ask for?
Why ask it
Listen for worries about cost ('I assumed it would be extra') or about bothering you. Both mean your limits were clearer than your invitations. Tell them what the answer would have been, and think about saying up front what is included and what a quick question costs.
Now that you have seen how the work went, was anything in the proposal or contract unclear or missing?
Why ask it
The client read that document once, months ago, and then lived the reality. Gaps they name, such as how many rounds of revisions there were or who supplies the content, are the ones to write into your template. Treat it as feedback on your paperwork, and have any change to contract terms looked at by someone qualified where you work.
Loose ends
Is there anything you were expecting from me that you have not received?
Why ask it
Ask it plainly, with your own list of deliverables open in front of you. A mismatch is usually a file sent to the wrong person or a small item promised on a call and never written down. Agree on a date for anything missing before you move on.
Is anything not working as it should, or is there a part you are unsure about?
Why ask it
Small faults go unreported when a client does not want to seem difficult, and then the fault becomes what they remember. Write each one down and sort them aloud into what you will fix as part of this job and what would be new work. Which is which depends on your agreement, so check it before you promise.
Do you have everything you need to run this without me: files, logins, instructions?
Why ask it
Go through it item by item, not as a yes or no: source files and logins on a digital job, manuals and warranty papers on a building one. A client who cannot find them a year from now will blame the handover, fairly or not. Send anything missing in a single message they can search for later, with a subject line that says what it is.
Who is looking after this day to day now, and do they feel ready?
Why ask it
If the answer is 'nobody yet', the work is at risk whatever its quality. Offer a short walkthrough with that person, or a one-page guide, and say whether it is included or billed. A named owner who was never in your meetings is someone to meet before you close the file.
Do I still have any access, data or equipment of yours that I should hand back or delete?
Why ask it
Raise it yourself, because most clients have forgotten which passwords and admin rights they gave out. Confirm in writing what you returned or removed, and when. How long you may or must keep client records depends on your contract and the rules where you work, so check both before deleting anything.
If something goes wrong next month, do you know how to reach me and what happens then?
Why ask it
Some clients assume fixes are free forever, and others assume you have vanished. Say what your agreement covers after handover and for how long, and what a request outside it would cost. If that was never written down, put it in an email after the call.
Was anything from the original brief set aside that you would still like done?
Why ask it
Projects shed items along the way, and the client may believe they were postponed while you believe they were cut. Read out what you think was dropped and ask about each. Whatever they still want is either a loose end to close or the outline of a next piece of work, and it helps to say which.
Is there anything left to settle on the paperwork: sign-off, the last invoice, a purchase order?
Why ask it
A debrief is an easy moment to ask, while the client still has the project in mind. Find out who approves the final payment and whether they need anything from you first, such as a completion note or a form. If a written sign-off matters under your contract, ask for it now and not three weeks from now.
Is there anything that has been on your mind about this project that we have not covered?
Why ask it
Save it for the end of the loose ends, then stay quiet. What comes out is frequently the real feedback, held back because no earlier question fit it. If the answer is a firm no, believe it and go on to what happens next.
What next
What happens next with this on your side?
Why ask it
Hear their plan before you suggest anything. A launch, a second phase, a handover to an in-house team or simply leaving it alone for a year each call for something different from you. If they have no plan, offer one or two sensible next steps, not a proposal.
Would you hire me again, and what would it depend on?
Why ask it
The second half is where the information is. 'Yes, if the budget is there' is about them, while 'yes, for this kind of work' tells you what they would not bring you, which is worth asking about. A pause before the yes may mean something earlier in the debrief was softened.
If someone asked you whether to hire me, what would you tell them?
Why ask it
It gets a fuller answer than 'would you recommend me', which is easy to say yes to out of politeness. Listen for the 'but': 'great work, but allow extra time' is the caveat they are already passing on. This is for your ears, so do not quote it anywhere without asking.
Is there anything coming up in the next few months that I could help with?
Why ask it
It is the simplest way to ask for more work, and it only lands well once the earlier groups have been heard out. Note anything they mention with a rough date, and follow up near that date. 'Not right now' is a normal answer and no comment on the job you just finished.
Would ongoing support suit you, or would you rather get in touch when something comes up?
Why ask it
Offer both as equal choices so it does not feel like a pitch. A client who wants regular help will ask what it costs, so have a figure or a range ready. One who prefers to call as needed should leave knowing your usual turnaround and your rate for small jobs.
Do you know anyone dealing with a similar problem who I should talk to?
Why ask it
Describing the problem works better than 'do you know anyone who needs a designer', because people think of friends by their troubles. If a name comes up, ask whether they would introduce you or prefer you to write and mention them. Leave this out when the debrief has turned up real unhappiness, and fix that first.
Would you be willing to write a short review, and where would be easiest for you?
Why ask it
Ask only after the debrief itself is finished, so the client never wonders whether the earlier questions were a warm-up for this one. Make it easy: send the link and suggest two or three sentences. Review sites and marketplaces set their own rules on asking and on offering anything in return, so read the rules of the one you use.
May I show this project in my portfolio, and is there anything that should stay private?
Why ask it
Get the answer in writing, even as a one-line email reply. Many clients are happy to be shown but want figures, internal names or unreleased plans left out, and some contracts restrict it altogether, so reread yours first. Offer to send the page before it goes live.
How to run a client debrief after a project
Practical guidance for the conversation itself
Before the debrief
Pick the moment
Ask within a week or two of handover, while the details are fresh and before the final invoice becomes the last thing the two of you talked about. Do not fold it into the meeting where you present the finished work: a client seeing the final version for the first time is reacting, not reflecting. If the result will take months to show, hold a short debrief now on the process and communication, and agree on a later date for the questions under The result.
Choose a call or a form
A call of 20 to 30 minutes lets you follow up and hear tone. A short form reaches busy clients and the ones who would rather not say a criticism out loud. For a large or difficult project, use both: the form first, then a call about what it turned up.
Say what it is for
In the invitation, say that you hold a debrief at the end of every project to close anything still open and to learn what to do better, and that it is not a sales call. Send three or four of the questions ahead. A day to think usually brings a more specific answer than a question sprung on the call.
Do your own review first
Reread the brief, the proposal and any change requests, and list what was delivered and when. Then write your own answers to the questions under What to change. Comparing your list with the client's afterwards shows you what you could not see from your side.
Choose about ten
Nobody sits through the whole list. Take one or two from each group, weighted toward wherever you suspect the project was weakest, and always include the first question under Loose ends. Keep the rest as spares for when an answer opens something up.
On the call
Keep the order
Start with the result, move through the process and communication, ask what to change, close the loose ends, and only then talk about what comes next. A client who is asked for a referral before they have been asked what went wrong will reasonably conclude the call was about the referral.
Do not defend
When a criticism comes, thank them, ask one question to understand it and write it down. An explanation, however fair, sounds like an argument and teaches the client to stop offering. If they have a fact wrong, correct it afterwards in your written summary, in one calm sentence.
Ask for the moment
'Communication could have been better' gives you nothing to change. 'Which week was that most true?' gives you a date, a deliverable and usually the cause. Nearly every question under The process and Communication gets better with a request for one particular instance.
Leave room after a hard question
Questions such as whether it felt worth the money, what you should stop doing, or what they would tell someone thinking of hiring you are followed by a pause. Let it run. If you fill it with a joke or a softer version of the question, the client takes the exit you offered.
If the project went badly
Hold the debrief anyway, and open by saying you know parts of it did not go well and want to hear their account before giving yours. Stay with The process, Communication and Loose ends, where there is something you can still put right. From What next, ask only what happens on their side, and leave the questions about more work, referrals and reviews for another day, if at all.
Keep the review request separate
A debrief is for hearing what happened. A testimonial is for publishing the good part. If the debrief went well, ask for the review at the very end or in a follow-up message the next day. If it surfaced a real problem, do not ask until the problem has been dealt with.
If you send a form instead
Keep it to one screen
Five to eight questions is plenty. Use the 1 to 10 score, one open question from each group, and the last question under Loose ends as a catch-all. A form that looks long is one the client puts off.
Leave space to write
Scores are quick to answer but tell you little on their own, so pair each one with a text box asking for the reason. Avoid making the open questions required: a client forced to type something will type 'n/a' and you will have learned nothing.
Say how long it takes and who reads it
Put the time in the first line and keep it honest. Tell them that you read every answer yourself and that nothing they write will be published without their permission. That second promise is what makes people willing to be frank.
Send it to more than one person
On a project with several people on the client side, the one who signed the contract and the one who handled the work day to day often saw two different projects. Ask your main contact first whether they mind you sending it to the others.
Remind once
One short reminder after about a week is reasonable. After that, let it go, and mention at your next natural contact that the offer of a quick call still stands.
After the debrief
Send a short summary
Within a day or two, write back with what you heard, what you will fix and by when, and anything the two of you agreed for later. It shows the client the conversation was not a formality, and it puts the loose ends and their dates in writing.
Close the loose ends before anything else
Missing files, small faults and unanswered questions come first, ahead of any message about new work. A client who has to chase a promised fix will remember that longer than anything good about the project.
Keep one record across clients
Put the answers from every debrief in the same document or spreadsheet, under the same six headings as this page. One client's complaint may be a preference. The same complaint from three clients is your process, and that is the one to change.
Change one thing each time
Pick a single change to your proposal, your kickoff questions or your updates after each debrief, and make it before the next project starts. A long list of resolutions tends to get filed and forgotten.
Keep the check-in date
If you agreed to look at the result again in a few months, do it on the day you said. Bring the figure you wrote down at the debrief, ask how it stands now, and ask again whether anything is coming up that you could help with.