Client and Customer-Facing Communication Questions

Happy overall can still hide risk. Flat usage plus rising support tickets usually means value is not growing and friction is increasing. I would treat that as a yellow flag, not an emergency, but not something to ignore.

My first step would be to break the signals into three buckets: adoption, friction, and relationship. Adoption means who is using the product and how often. Friction means the number and type of tickets. Relationship means whether the champion and sponsor still see value.

For example, if active users stayed at 20 but the account has 30 intended users, adoption is actually falling. Then I would review the last few tickets to see whether they are random issues or a pattern. After that, I would ask the champion one direct question: What is making it harder to expand usage?

That tells me quickly whether the account is healthy on the surface or drifting toward risk.

Even if implementation is simple, I would make the first 90 days feel structured.

First, I would run a kickoff with the customer sponsor, day-to-day owner, and internal team to confirm goals, milestones, risks, and who owns what. A success plan is just a shared definition of what good looks like.

Then I would set a communication cadence:

• Week 1: kickoff and timeline recap
• Weeks 2 to 4: weekly progress updates
• Day 30: check adoption and open issues
• Day 60: review outcomes and training gaps
• Day 90: success review and next-step plan

I would also keep one written tracker for actions, owners, and due dates so nothing falls through the cracks. For example, if the goal is to get 25 users live in month one, I would report progress against that number, not just say onboarding is on track. This keeps the customer guided, internal teams aligned, and surprises low.

First I would separate lagging indicators from leading indicators. Lagging indicators show results after the fact, like renewal outcome. Leading indicators are earlier signals that predict trouble.

I would investigate:

• Product adoption breadth, depth, and recency
• Executive and champion engagement
• Support ticket volume, severity, and reopen rate
• Sentiment from calls and email
• Implementation status or workflow blockers
• Commercial signals such as discount pressure or late billing questions

Example: if weekly active users fell from 80 to 50 over two months, tickets rose from 3 to 8 per month, and the sponsor missed two meetings, I would treat that as real risk even if the invoice is current.

To internal stakeholders, I would say the revenue is safe today, but the account is drifting. The risk is not only churn at renewal. It can also mean expansion stalls, escalations increase, and recovery becomes harder later. My recommendation would be to stabilize adoption, resolve the top support issue, and re-engage the sponsor before the renewal window opens.

I would run this as two parallel workstreams under one account narrative. The unhappy business unit is the retention risk, so I would address that first enough to stop escalation. The expanding unit is the growth opportunity, so I would keep it moving, but not at the expense of the broader relationship.

Step 1: Triage the unhappy unit. I would get the facts, confirm impact, and agree on a short-term remediation plan with one owner and a deadline.
Step 2: Protect the expansion. I would keep the growing unit informed on delivery and value, but I would not use its success to dismiss the other unit's concerns.
Step 3: Align leadership. If needed, I would brief one executive view of the account so the customer hears a coherent story, not competing internal agendas.

Example: if Unit A wants to expand seats and Unit B has a service complaint, I would not push the upsell meeting first. I would stabilize Unit B, then use that recovery to strengthen the overall relationship. The key is to avoid letting one part of the account become collateral damage.

I would make the QBR about their business goals, not our activity log. The best structure is goal, progress, value, risk, and next bets.

I would include:

• Their original business objective
• Adoption and outcome data tied to that objective
• Wins, open risks, and what we learned
• A small number of next actions with owners

I would tell the story from before to after. For example, if the goal was to reduce manual reporting, I would show the old process, the current workflow, and what that changed for their team. That is more credible than listing features.

I would avoid a product demo, a long pipeline update, or slides that make us look busy but do not prove value. If the leadership team is skeptical, I would also name the gaps honestly and explain how we plan to close them. Candor builds more trust than polish.

The meeting should end with: here is the value so far, here is what still needs work, and here is the plan to get more from the partnership.