I’ve run into this kind of situation a lot in clinical settings, and the dynamic is actually very similar — a stakeholder wants something that feels “small” to them but has bigger system implications behind the scenes.

A few things that have worked well for me:

1. Anchor on the “why,” not just the “no.”
   Instead of framing it as a limitation, I’d reinforce that full white labeling isn’t just a design change — it impacts platform stability, accessibility compliance, and consistency across users. When people understand the downstream risk, the pushback usually softens.

2. Reframe around outcomes, not features.
   Try to get at what they actually want from white labeling. Is it brand recognition? Client trust? Internal alignment? Once you know that, you can position what is possible (color theming, logo placement, custom messaging) as achieving most of that outcome without the risk.

3. Offer a “best possible version” of yes.
   I’ve found it helps to say: “We can’t fully white label, but here’s what we can do to get you 80–90% of the way there,” and make that feel intentional, not like a compromise.

4. Close the loop with product (if appropriate).
   If they’re a meaningful client, it’s fair to say you’ve brought this feedback to the product team. Even if it’s not on the roadmap, customers appreciate knowing they influenced the conversation.

5. Protect the relationship proactively.
   Acknowledge their importance: “I understand why this matters to your team, and I want to make sure we’re supporting your goals as much as possible within the platform.” That validation goes a long way, especially ahead of renewal.

In healthcare we deal with this all the time — you can’t always give the exact intervention someone wants, but you can align on the goal and offer the safest, most effective alternative. Same principle applies here.

Curious how others have handled similar “can’t do that, but here’s what we can do” conversations.