Customer A wants a simpler, more streamlined workflow. Customer B wants more options and granular control. Both are paying, both are vocal, and both think their version is obviously right. If you build an app that real people use, this moment isn’t a glitch in the process — it’s the process.
Table of Contents
This guide walks through a practical way to evaluate conflicting requests, decide what actually goes into the next release, and tell both customers something that keeps them on your side either way.

Quick Answer
Don’t decide based on who asked loudest or last. Score each request against your product goals using a simple framework (how many users it affects, how much it moves the needle, how confident you are it’ll work, and how much effort it takes), pick the option that serves the broader user base or your core use case, and explain the reasoning to both customers rather than just picking a side silently.
Step 1: Figure Out If They’re Actually in Conflict
Before treating two requests as a true conflict, check whether they’re solvable independently. A lot of ‘conflicting’ requests are really just two different surface preferences on top of the same underlying need — one customer wants fewer clicks, another wants more visibility into what’s happening. Sometimes a settings toggle, a progressive-disclosure pattern (show the simple view by default, let power users expand it), or a different default for different account tiers resolves both without picking a winner.
True conflicts are rarer: one request would break or contradict the other at the architecture or workflow level (e.g., ‘remove the approval step’ vs. ‘add a mandatory second approval step’). Those are the ones that need a real decision, not a UI compromise.
Step 2: Score the Requests, Don’t Just React
When a genuine conflict exists, score it instead of guessing. A widely used method is RICE: Reach (how many users does this affect), Impact (how much does it move a goal that matters — retention, conversion, support load), Confidence (how sure are you this actually solves the problem, not just the symptom), and Effort (how much engineering time it costs). Divide the first three by effort and you get a rough priority score you can compare across competing requests.
If you need something faster and less numeric, MoSCoW (Must have, Should have, Could have, Won’t have) works well for sorting a messy backlog quickly — it won’t rank two ‘must haves’ against each other, but it’s good at telling you when one request doesn’t deserve to be in the conversation at all.
Either way, weigh requests against your actual user base and roadmap, not against whichever customer has the squeakier wheel or the bigger contract. A request from your highest-paying account still has to earn its place if it would hurt the experience for everyone else.

Step 3: Look for the Underlying Job, Not the Literal Ask
Customers describe solutions, not problems. ‘Add a dark mode toggle in settings’ and ‘make the app easier on my eyes at night’ might come from the same underlying need even if they sound like different feature requests. Ask each customer what problem they’re actually trying to solve, not just what UI change they pictured. Often the literal requests conflict but the underlying jobs don’t — and the real fix is a third option neither customer proposed.
If the jobs genuinely conflict (one workflow fundamentally needs speed, the other fundamentally needs oversight), that’s a sign you may be serving two different customer segments with one product — worth flagging to whoever owns the roadmap, because the long-term answer might be a plan tier or permission setting, not a single universal default.
Tips / Common Mistakes
Don’t let the loudest customer win by default — a vocal complaint isn’t the same as a representative one. Check usage data or ask your support/success team how common each need actually is before deciding.
Don’t silently implement one side’s request and hope the other customer doesn’t notice. They will, and it reads as being ignored rather than as a reasoned product decision.
Don’t promise both customers ‘yes’ just to keep the conversation pleasant in the moment — a vague yes that later becomes a no costs more trust than an honest ‘not right now’ up front.
Do write the decision down somewhere (a changelog note, a roadmap comment, an internal doc) so the next similar conflict isn’t argued from scratch.
Do close the loop with the customer whose request didn’t make it in. A short explanation of the tradeoff, plus an invitation to flag if the workaround doesn’t hold up, keeps the relationship intact.
Explore more: more app development guides.
Frequently Asked Questions
What if both customers are paying for the same high-value plan?
Revenue size matters, but it shouldn’t be the only input. Score the request on reach and impact across your whole customer base first — a feature that only helps one account while actively hurting others usually isn’t worth it even if that account pays well. If the account is big enough to justify custom behavior, consider a setting or permission rather than changing the default for everyone.
Should I just ask the customers to agree on a compromise themselves?
Generally no — that puts them in a negotiation they didn’t sign up for and can make both feel unheard. It’s fine to share that you’re aware of the tension and ask clarifying questions about their underlying goal, but the prioritization call should come from your team, not be outsourced to the customers.
How do I tell a customer their request didn’t make the cut?
Be specific and honest: acknowledge the request, explain briefly what you decided and why (usually in terms of broader impact or an existing workaround), and avoid vague language like ‘it’s on our roadmap’ unless it genuinely is with a rough timeframe. A clear ‘not now, here’s why’ is almost always better received than a soft non-answer.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Photo by Dylan Gillis on Unsplash.