Contents
Make understanding the client part of the job
Asking a client how satisfied they are can feel uncomfortable. In our research interviews, professional services leaders who said client retention was well under control described account owners who kept asking these questions, which matter for the continuity of the collaboration.
Make the conversation specific and easy to respond to. Ask about delivery, communication, expertise or the value the client expects. Give the client room to say what is working and what needs attention, so that raising a concern feels natural.
Some of the experienced account owners we have spoken with handle these topics very naturally. They ask follow-up questions and check that they have understood the answer correctly.
A routine makes this easier. It creates regular opportunities to hear from the relevant people, record their assessments and notice what has changed.
An annual survey gives a useful overview. During the collaboration, however, you need feedback that helps you decide what to continue, clarify or improve in that specific account.
Decide in advance when feedback will be collected
Set the feedback schedule as part of the account or project plan, and assign someone to own it.
If feedback is collected whenever someone has time or the moment feels right, it easily gets left undone. Agree in advance when you will check how the collaboration is going, and stick to it, even during busy periods.
In our research interviews, it typically took 3–9 months from a client’s first doubt until the collaboration was scaled back or ended, so a once-a-year check-in may come too late. For an ongoing relationship, three check-ins a year can be a good starting point. A key account may need a more frequent rhythm, while twice a year may be enough for a smaller, stable account.
In project work, agree on feedback points at the planning stage. A good moment is when the client has enough experience of the collaboration, but the team still has time to act before the project ends.
Keep listening between scheduled check-ins as well. A new concern is worth addressing as soon as it comes up.
Gather the relevant perspectives at the same time
A B2B client is often several people. A typical account involves decision makers, operational contacts and your own team.
Decision makers assess whether the partnership creates value. Operational contacts experience the day-to-day collaboration. Your team sees how the work is progressing, where expectations are unclear, and what may affect whether the relationship continues.
Gather these perspectives within the same period, so that they describe the same stage of the collaboration. That makes differences easier to interpret.
Choose respondents based on how the account works, and ask each person about the expectations and experiences relevant to their role.
If an answer is unclear, ask a follow-up question. “Have I understood this correctly?” helps you confirm what the person means before you decide how to act.
Track the numbers and keep the context
A consistent metric, such as NPS or client satisfaction, shows changes over time. But keep the score linked to the account, the respondent and the work they are assessing.
A result is hard to interpret unless you know whose view it reflects, which part of the collaboration it concerns and what explains the answer. A decision maker assessing overall value may answer from a different perspective than an operational contact assessing a recent delivery.
Keep the comments and the relevant account or project background alongside the score. Check who responded, whose view is missing, and whether the feedback relates to the same period.
Then compare the client’s assessment with your own team’s view. Changes and differences show where a conversation is needed.
Review the feedback together
Make sure everyone responsible for the client work has read the feedback and understands it. Bring in your own team’s view, and resolve any differences in how the situation is understood.
Agree on what needs attention and who will resolve it. Record what will change, who is responsible and when the change will happen, and make sure everyone involved knows.
Go through the response with the client. Explain how the feedback has been handled, and check later whether the change helped. Continue collecting feedback at the agreed rhythm.
Reminders, feedback requests and feedback routing can be automated if your tools support it. Responsibility for interpreting and acting on the information must still be clear.
Plan the rhythm
Decide when feedback is collected and who is responsible.
Gather perspectives
Collect feedback from the relevant contacts and your own team within the same period.
Understand the situation
Compare perspectives, clarify differences and identify what needs attention.
Review the feedback together
Make sure everyone responsible for the client work has read and understood the feedback. Record how concerns will be addressed, by whom and when.
Discuss and continue
Go through the response with the client, check whether it helped, and continue collecting feedback at the agreed rhythm.
The cycle repeats at the agreed rhythm.
Keep the process light enough to repeat
Start with a few relevant questions, an agreed rhythm and a clear owner. Keep the information in one place and use it in account discussions.
The routine is there to help the account owner understand the client and support the team’s work. Its value comes from using feedback throughout the collaboration, not only at the end.
This article draws on the hypotheses and tests we have run with B2B companies while developing Foxie. Through this work, we have explored when information gathered from clients and internal teams is reliable, and when it is most useful for improving client collaboration and spotting signals of risk and growth opportunities.