Quick answer: Pricing feedback is biased toward cheaper, so asking players what they would pay rarely gives a usable number. Instead, measure value perception, where players feel they got their money's worth or felt nickel and dimed, and capture purchase context and sentiment around your monetization. Combine what players say with how they behave to find signal beneath the noise.
Pricing is the one piece of feedback where players have an obvious incentive to mislead you, not out of malice but out of self interest: almost everyone would prefer to pay less. Ask a community what your game should cost and the answer trends toward free, which tells you nothing about what they would actually pay or whether they feel it is worth the money. Yet monetization feedback genuinely matters, because a price or a model that players resent will sink your reviews and your sales. This post covers how to collect pricing and monetization feedback that gets past the reflexive everyone wants it cheaper and surfaces real value perception you can act on.
Why direct pricing questions mislead
The obvious approach, asking players what they would pay, is also the least reliable. People are bad at predicting their own purchasing behavior in the abstract, and they have every reason to anchor low when an answer might influence the price they get charged. A survey that asks would you pay twenty for this almost always understates real willingness to pay, because saying no costs the respondent nothing and might win them a discount. You end up with a number that feels like data but is really a negotiating position.
Loud voices distort it further. The players most likely to comment on price are often the most price sensitive, and a forum full of that is too expensive can panic a developer into underpricing a game that most of its actual audience would happily have paid for. Treating the loudest pricing complaints as representative is a classic indie mistake. The people who quietly bought at full price and felt satisfied rarely post about it, so the visible feedback skews negative. You need methods that capture the silent majority, not just the vocal minority.
Measure value perception, not just price
The more useful question is not what would you pay but did you feel this was worth what you paid. Value perception is the real driver of reviews and word of mouth, and it can be high at a price players initially balked at, or low at a price that sounds cheap, depending on what they got. Capturing whether players finished the game feeling satisfied with the exchange tells you far more than a hypothetical price point, because it reflects the actual emotional result of the purchase rather than a guess made before playing.
Pay attention to the language of feeling cheated. Phrases like nickel and dimed, paywall, and that should have been included signal that your monetization model, not just your price, is generating resentment. That resentment is poison for reviews even when the total spend is modest, because players forgive a fair price and punish a model that feels manipulative. Tracking sentiment around how you monetize, separate from the raw number, often reveals that the problem is the structure of your offers, not the amount, which is a very different fix.
Capture purchase context with the feedback
Pricing sentiment only makes sense in context, so capture the conditions around it. Did the player buy on a sale or at full price; how many hours had they played when they formed an opinion; did they buy additional content or refund. A complaint about value from a player with two hours and one from a player with forty mean completely different things, and a too expensive from someone who bought on a deep discount is barely signal at all. Knowing the purchase context lets you weight feedback by how informed it is.
Refunds are a particularly honest signal, because a refund is a player voting with their wallet rather than just talking. When you can pair refund behavior with the feedback around it, you learn whether players are bouncing off price, off the game itself, or off a specific monetization moment. That is far more reliable than any survey, because it is a real decision with real money attached. Combining stated sentiment with this behavioral context is how you find the truth beneath the noisy chorus of make it cheaper.
Segment feedback by player type and weight it
A single average across all players hides the fact that different segments value your game in completely different ways. Non payers and payers experience your monetization from opposite sides, and lumping them together produces a muddy number that satisfies no one. The player who never spends a cent will rate any price as too high, while the player who already bought everything has signaled the opposite with their wallet. Separating feedback by whether someone has actually paid, and how much, is the first step toward reading pricing sentiment that means something rather than a blended noise.
Within payers, the spread matters even more. A first time buyer who balked at a single purchase tells you about your entry price, while a whale who has spent hundreds tells you about depth and value at the top. Both are useful, but weighting them equally distorts the picture, because the whale is a tiny fraction of accounts yet a large fraction of revenue. Tag each comment with the segment it came from and decide deliberately how much each counts. Optimizing the entry price for non payers can quietly destroy the value perception that keeps your most invested players spending.
Setting it up with Bugnet
Bugnet is not a payment system, but its feedback capture is well suited to monetization sentiment because it attaches context automatically. Use the in game report or feedback button at monetization moments, the store, an offer, a paywall, and define custom fields for hours played, purchase tier, or whether the player bought on sale. A comment like this should have been in the base game then arrives stamped with how far into the game the player was and what they had bought, so you can weight it instead of reacting to it raw. Player attributes let you slice sentiment by segment.
Because the same monetization gripe recurs, Bugnet folds duplicate reports into one issue with an occurrence count, so a paywall that many players resent surfaces as a single prioritized item with its frequency, rather than a scattered impression you might dismiss. Filter the dashboard by your purchase context fields to compare how sale buyers and full price buyers feel, or by hours played to see whether resentment comes from new or invested players. One dashboard turns anecdotal pricing chatter into a structured, weightable picture of how your monetization actually lands.
Combine what players say with what they do
The strongest pricing read comes from putting stated feedback next to behavior. Conversion rates, refund rates, attach rates on additional content, and how those move when you run a sale, are facts, and they often contradict what the loudest voices claim. When the forum says too expensive but conversion at full price is healthy and refunds are low, the price is probably right and the complaints are the price sensitive minority. When the numbers and the sentiment agree that a model feels exploitative, you have a real problem to fix.
Use this combined view to test changes rather than guess them. Adjust a price or restructure an offer, then watch both the behavior and the sentiment in the next window. Did conversion hold while resentment fell, or did you leave money on the table. Treating monetization as something you measure and iterate, with feedback and behavior in the same picture, beats both stubbornly ignoring players and reflexively caving to them. The goal is a price and a model that players feel good about and that sustain your studio, and only evidence gets you there.
Everyone wants it cheaper, so do not ask what they would pay. Measure whether players felt it was worth the money, and read that against what they actually do.