"Should Be Free. One Star." — Replying to Price-Complaint Reviews

Reply to a price-complaint review by acknowledging the cost honestly, stating plainly what the price pays for, and pointing to the free or cheaper path if one exists. Then stop. Don't apologize for charging money, don't argue, and don't dangle a discount. You will almost never change the mind of the person who wrote "should be free, one star." The reply isn't for them. It's for the next hundred people reading it while they decide whether your price is a rip-off or fair.

This is the most common review you'll never fully win, and the most misread. Someone pays nothing, or pays once, or hits a paywall, and leaves a star because the app dared to have a business model. Below is how to answer the whole genre, from the subscription "greedy" one-star to the "used to be free" betrayal to the price-hike protest, without sounding defensive and without caving on a price that's keeping the lights on.

Strip the emotion out and most price complaints are one of three things wearing the same costume. There's the value mismatch: the person doesn't see what they'd get for the money, usually because the paywall hit before the payoff did. There's surprise: they felt ambushed by a subscription prompt or a feature that used to be free, and "expensive" is really "I didn't see this coming." And there's the small, loud minority who believe all software should be free and will one-star anything with a price tag.

You can move the first two. The third you cannot, and trying is how good developers end up in a comment-thread brawl on their own store page. So sort which one you're looking at in about five seconds, answer the movable ones with a real reason, and treat the immovable ones as a stage. You're performing calm and fairness for the audience, not negotiating with the heckler.

"Sorry you feel that way about the price" and "We're sorry it's not free" both concede the reviewer's premise: that charging is a mistake you got caught making. It isn't. You built something, it costs money to run, and asking to be paid for it is not a customer-service failure. The moment your reply sounds apologetic about the existence of a price, every reader clocks it as weakness and the complaint looks legitimate by default.

The alternative isn't to be cold. It's to be matter-of-fact and generous with information: acknowledge that money is a real consideration, then be specific about what the price covers and where the free option lives. Confidence about your own pricing reads as trustworthy. Defensiveness reads as guilt. Hold the ground, warmly.

Almost every strong reply to a cost review runs the same four beats. Acknowledge the concern in one line, reframe toward value with a concrete detail, surface the free or lower path if you have one, and close without begging. It fits comfortably inside Google Play's 350-character reply cap when you skip the padding.

Here are the real sub-genres, each with a reply built on the four beats. Notice none of them apologize for charging, and each hands the next reader a reason rather than an excuse. Steal the shapes, swap in your own specifics, and if you want the wider set for every review type, the [app review response templates](/blog/app-review-response-templates) library covers the rest.

Sometimes "too expensive" is a symptom, not the disease. If a wave of cost complaints all mention the same thing, like a paywall that appears before they've done anything or a trial that charged without warning, that isn't a pricing objection you reply your way out of. It's product feedback in an angry wrapper. Cluster those reviews, look at what they share, and fix the surprise: a paywall that lands after the first win instead of before it turns "cash grab" reviews into conversions.

This is the honest limit of a good reply. You can't template your way out of a genuinely bad deal, and shouldn't try — when the value isn't there, the reply just buys goodwill while you go fix it. Some one-stars, similarly, aren't a pricing call or even yours to fix, like a billing hiccup from the store's own payment system. We cover that category in [reviews that aren't your fault](/blog/app-reviews-that-arent-your-fault), and the structure for any negative review in [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews).

The failure modes here are specific and they all make the store page worse for the next reader, which is the only reader who matters. Avoid these:

For that one reviewer, rarely — the person committed to "all apps should be free" isn't updating their star over a well-worded paragraph. But replying to negative reviews correlates with a measurable lift overall: when Google rolled out recency-weighted ratings at I/O 2019, it reported that responding to reviews is associated with an average increase of about 0.7 stars. And in a study of 4.5 million reviews, users who got a developer reply were roughly six times likelier to raise their rating than those who didn't, 4.4% versus 0.7% (Hassan et al.). Price complainers sit at the stubborn end of that distribution, but they're not immune, and a fair reply occasionally flips a two-star "price went up" into a grudging update.

The bigger return is invisible and compounding. Every reasonable person shopping your app reads the one-stars first, because that's where they check for deal-breakers. A calm, specific answer under a "greedy" review reframes it in real time: the complaint stops being evidence and becomes a question you already answered well. That's the conversion nobody attributes to review replies but everyone feels. More on that in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

Price complaints arrive in every market you're in, and a translated-looking English wall under a German or Spanish review reads as a brush-off. The four-beat shape carries over cleanly. Here's the subscription reply rebuilt in Spanish, holding the same ground without a word of apology for charging:

Meeting a reviewer in their own language matters more on a price complaint than almost anywhere else, because the whole job is sounding fair rather than corporate, and nothing sounds more corporate than a machine-translated apology. If you're replying across markets, we walk through doing it at inbox scale in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language).

The price one-star is the review you make peace with never fully winning, and answer well anyway, because the reply was never really addressed to the person who wrote it. Acknowledge the cost, name what it pays for, show the free door, and hold your ground without a flinch. Do that under every "should be free" and your store page quietly tells the next thousand shoppers that your price is fair and you're not embarrassed by it. The hard part is keeping that tone across every review, every store, and every language on the busiest week. [Start free with ReplyArgus](/signup), no card needed, and Argus drafts your first reply in minutes, in the reviewer's own language and already sized to each store's limits, so the calm answer is waiting for you to approve instead of write from scratch.