The Psychology of Undercharging: Why Indie Makers Price Too Low (And How to Stop)

Someone uses your product for the first time and sends you a message: "This is exactly what I needed, how much does it cost?" Your brain does something strange. Before you type the number, something pulls it down. You start qualifying. You almost apologize. You name a price that's lower than the one you were thinking before they asked.

This has nothing to do with confidence in the normal sense. You're proud of what you built. You know it works. The problem is more specific than that: you're running several cognitive biases simultaneously, each one reasonable-sounding on its own, each one nudging your price in the same direction. None of them involve a clear-eyed assessment of the value your product delivers.

The good news is that these biases are documented, predictable, and breakable. But you have to name them first.

The IKEA Effect, Running in Reverse

The IKEA effect is the well-established finding that people overvalue things they helped create. Assemble a bookshelf yourself and you'll rate it as better than the identical, pre-assembled version. The effort makes it feel more valuable.

Indie makers experience a strange inversion of this. You know exactly how the product was built. You remember the shortcuts. You know which parts are duct-taped together. You know it took you a long weekend. And instead of overvaluing it because you built it, you discount it, because the intimacy with the process makes it feel less impressive than it looks from the outside.

The customer sees a working product that solves their problem. You see the rough commits, the workarounds, and the features you didn't get around to building. They're buying the bookshelf. You're pricing it based on the fact that you know how wobbly one of the shelves is.

This is worth sitting with. Your customer has zero access to your internal view of the product. They experience the output. And if the output solves a real problem, their experience of it is genuinely different from yours. You're not being objective when you discount the price based on how the build felt from inside. You're letting behind-the-scenes knowledge corrupt your external pricing judgment.

Loss Aversion and the Math You're Ignoring

Loss aversion is one of the most replicated findings in behavioral economics: losing something hurts roughly twice as much as gaining the equivalent thing feels good. We are asymmetrically wired to fear loss.

For pricing, this plays out in a specific and costly way. When you're deciding whether to charge $49 instead of $29, the mental simulation you run goes like this: if I charge $49, that person might leave. That potential loss, one customer, one rejection, feels vivid and immediate. The cost of charging $29, the cumulative revenue you're forfeiting across every customer for the next two years, is abstract and invisible.

The math, when you actually run it, tells a different story. Say your product converts 10% of trial users. If you raise the price from $29 to $49 and that conversion rate drops from 10% to 8%, you're still ahead. $49 times 8 is $392. $29 times 10 is $290. The loss you feared cost you nothing. It made you money.

The one customer you imagined losing wasn't your most valuable customer anyway. The buyer who chooses you at $49 is making a more deliberate decision than the one who signs up at $29 because it barely registers as a financial choice. Correct pricing doesn't just improve margin. It improves the quality of your customer base. But loss aversion doesn't let you see that. It only lets you feel the imagined loss.

For a more detailed look at how this plays out in the numbers, the piece on SaaS metrics for bootstrapped founders covers the relationship between price, churn, and LTV in practical terms.

Imposter Syndrome as a Pricing Anchor

Imposter syndrome gets discussed a lot in the context of showing up publicly, talking about your work, or pitching investors. Its most direct and measurable damage is actually in pricing.

When you price based on how expert you feel rather than on the value you deliver, you've made a category error. Your customer is not paying for your expertise. They're paying for the result. They're paying for the gap between their life before your product and their life after it. That gap doesn't get smaller because you feel uncertain about your technical choices.

The insidious part is that imposter syndrome presents as professional humility. "I don't want to claim to be something I'm not." "I'm still learning." "Once I've done this longer, I'll feel justified charging more." These feel like measured, responsible positions. What they actually are is a moving threshold that permanently delays pricing confidence.

There's always something you don't know yet. There's always a more experienced version of yourself that feels like the real expert. If you're waiting to feel like that person before you raise your price, you're waiting for a feeling that won't come, and in the meantime you're charging rates that have more to do with your internal self-assessment than with what your product actually does for people.

Social Proof Starvation: The Circular Trap

Here is a trap that catches almost every early-stage indie maker. You don't have many testimonials or public case studies yet. Without that social proof, you feel like you can't justify a premium price. So you charge less. Lower prices attract customers who are less likely to go out of their way to leave glowing reviews. The proof doesn't accumulate. You still feel like you can't justify a higher price.

The causation runs in the opposite direction from what the trap implies. You don't charge premium prices because you have social proof. You get social proof because you charge prices that select for customers who take the product seriously, experience real value from it, and are motivated to tell others.

At some level you already know this. The customer who pays $9 for something is not the one who goes out of their way to write a detailed case study about how it transformed their workflow. The customer who pays $79 and genuinely relies on the product for work they care about is.

The permission you're waiting for to charge premium prices is not in the testimonials you don't have yet. It's in your understanding of the problem you solve and the value you deliver. The testimonials follow the price, not the other way around.

The "I'd Never Pay That" Trap

This one is so common it deserves its own warning label.

At some point during your pricing decision, you will ask yourself: would I pay this much for something like this? Your answer will probably be no, or at least not without hesitation, and that will pull your price down.

The problem is that you are not your customer. This is not a platitude. It's a specific factual error with a measurable financial consequence.

Say you're a developer building a tool for Shopify store owners. You earn your income through code. You understand that software is buildable. You are, relative to your customer, unusually resistant to paying for software tools because you know you could build a version yourself if you cared enough.

Your customer owns a Shopify store doing $80,000 a month in revenue. They have zero ability to build anything. Their time is worth more per hour than they're probably admitting to themselves. And they make purchasing decisions based on a completely different set of economics, values, and alternatives than you do.

When you ask "would I pay this?", you're not testing the market. You're testing your own idiosyncratic relationship with money and software, which is probably the most atypical relationship to this purchase that exists anywhere in your customer base. You're pricing for a customer who will never show up.

Sunk Cost Mispricing

"It only took me two weeks to build" is one of the most expensive sentences in indie maker history.

The amount of time it took to build the product is a cost you've already paid. It's over. It has no bearing on what the product should cost, because the product's value to the customer is not denominated in your hours.

If you built something in two weeks that saves your customer three hours every week, you built something that delivers roughly 150 hours of value per year per customer. If their time is worth $50 an hour, you're delivering $7,500 of annual value and probably charging $29 a month because the build felt quick.

Sunk cost thinking shows up in the opposite direction too. Some founders overprice based on how long the build took, as if the years of development are a cost the customer should help recoup. That's equally disconnected from the actual value equation. The customer doesn't care what it cost you. They care what it does for them.

Build time is a cost you paid. Value delivered is the price they pay. These are separate calculations, and conflating them almost always pushes your price in the wrong direction.

What Correct Pricing Actually Signals

The instinct to price low often comes from a belief that a lower price reduces friction, attracts more customers, and signals humility and approachability. In practice, it signals something different.

A low price tells a prospective customer several things before they've read a single line of your landing page. It suggests that the product might be abandoned soon, because a product that cheap can't sustain development. It suggests that the maker isn't confident in what they built. It suggests that something is missing, because why else would it be so cheap?

Premium pricing signals the opposite. Confidence in the solution. Commitment to maintaining it. A working relationship with customers who are paying enough that you can actually afford to serve them well. When someone lands on a product that charges a serious price, they unconsciously assume it's a serious product. That assumption does marketing work before the product has a chance to.

Here's the counterintuitive data point that experienced indie makers report consistently: raising prices sometimes increases conversions. Not because the product got better, but because the price told a better story about the product. The person who bounced at $19 signed up at $49 because $49 felt like something real. The $19 product felt like something they might try and forget about.

The customers who bounce specifically because your price is too high are usually not the customers you want. They're optimizing for cheapness. Cheap-optimizers are the customers most likely to churn the moment a marginally cheaper alternative exists, most likely to exhaust your support capacity relative to revenue, and least likely to become the kind of advocates who send you new customers without being asked.

Pricing correctly is not just about revenue. It's about filtering for the customer relationship you want to spend your time on.

The tactical side of setting specific price points and structuring tiers is covered in detail in the guide to pricing without fear, which pairs well with this piece.

A Practical Recalibration Exercise

Before you set or change a price, answer these three questions. Not as a framework to fill out, but as genuine constraints on the biases described above.

Question one: What does my customer do instead of using my product?

Get specific. Do they hire someone? Do it manually? Use a worse tool? Not do it at all? What does that cost them in time, money, or opportunity? Write an actual number. If your product replaces three hours of manual work per week and your customer's time is worth $60 an hour, you're delivering roughly $720 of monthly value. A $49/month price is not bold. It's a 7% capture rate.

Question two: Am I pricing for my customer or for myself?

Would the person you're building for actually care about the difference between $49 and $79? Run the numbers for their situation, not yours. What do they spend on coffee, on software subscriptions they barely use, on tools that are half as focused as yours? The price that feels significant to you often doesn't register the same way to the person you're selling to.

Question three: What would I think about a competitor charging this price?

If you saw a competitor charge what you're about to charge, would you think "that's reasonable" or "wow that's cheap, I wonder what's wrong with it"? We apply less skepticism to our own prices than we do to everyone else's. Reversing the perspective breaks the bias. The number that feels bold when it's yours usually feels normal when it's someone else's.

These three questions don't produce a price. They're designed to remove the distortions before you do the calculation.

On Raising Prices for Existing Customers

If you've been undercharging and you've figured that out, you're now facing a specific fear: telling people who already pay you that you're raising their price.

The mental model most founders have for this conversation is catastrophically wrong. They imagine customers feeling deceived, churning in protest, posting angry reviews. What actually happens, the great majority of the time, is that customers either accept the increase with a brief acknowledgment or say nothing at all.

The practical approach is simple. Announce the change clearly and in advance, at least 30 days out. Be direct about what's changing and when. Grandfathering existing customers at their current rate for a period is a goodwill gesture worth making, especially if the increase is significant. But it's not required.

Don't over-explain or apologize. The longer the explanation, the more the message reads as "we know this might be wrong, here's our justification." A calm, confident announcement says: this is what the product costs now. The customers who are genuinely getting value from your product don't leave over a reasonable price increase. The ones who do leave were usually the ones generating disproportionate support volume at your lowest margin. Their departure is often a net improvement.

If you're worried about what the actual churn risk looks like when you change pricing, the piece on reducing churn for indie SaaS has data on what actually drives customer departure. Pricing increases, done correctly, rarely make the list.

The Only Number That Matters

Here is a reframe worth carrying with you.

The price you set is not a statement about your worth. It's not a reflection of how expert you feel or how long you spent building or how polished the product is. It's a communication to your potential customer about what kind of product this is and whether it takes itself seriously.

High prices say: I believe this works and I'm willing to let that belief be tested. Low prices say: I'm not sure this is worth much, but maybe it's worth something to you.

The cognitive biases covered in this piece don't disappear once you name them. They're structural features of how humans process uncertainty, effort, and loss. But naming them means you can catch them running in real time. You can notice the moment when "I'd never pay that" sneaks in and ask whether you're actually your customer. You can notice the sunk cost reasoning and replace it with the value calculation. You can see social proof starvation for the circular trap it is.

Then you can set the number based on what the product actually does for people who actually need it.

That number is almost certainly higher than the one you had in mind before you started reading this.

Put your project on Makers Page and connect your revenue as it grows. The founders who build in public and show real numbers tend to calibrate their pricing more accurately over time, partly because they can see what others are charging, and partly because visibility creates the kind of accountability that makes self-defeating pricing harder to sustain.