Why I Don't Run Discounts on RAXXO Tools

#ai #productivity #claudecode #automation

I have never run a sitewide discount on a RAXXO tool, and every product has kept its launch price with no countdown timers or "was/now" banners
The one time I got close to a markdown, a customer email talked me out of it before I ever touched the price field
A flat price is a promise to whoever already paid, and a discount a week later breaks that promise even if nobody complains
Bundling and free tools do the same job a discount would, without punishing the people who bought on day one

The Discount I Never Ran

Every product on raxxo.shop has carried the price I set at launch. Git Dojo costs what it cost the day it shipped. Statusline Builder is free, and it was free from the first version. Nothing has a strikethrough price next to it, nothing counts down to midnight, and nothing says "limited time" anywhere on the store. That is not an accident and it is not because discounting never crossed my mind. It crossed my mind once, seriously, and I talked myself out of it in about a day.

The moment came a few months after I shipped my second tool. Traffic was flat for a stretch, the kind of quiet week every solo store owner recognizes, where the graph just sits there and you start looking for a lever to pull. A markdown felt like the obvious lever. Cut the price for a week, watch the graph move, put the price back. I got as far as opening the product page in the admin and staring at the price field before I closed the tab without touching it.

What stopped me was not a rule I had already written down. It was picturing the person who bought the tool full price the week before. They would open their inbox, see a discount code for the exact thing they just paid for, and learn something about the store they could not unlearn: that the price on the page is a starting offer, not a real number. Once someone learns that, they stop trusting the price on the page ever again. They wait. They assume a better deal is coming if they just hold off, and the next launch gets harder, not easier, because now every price looks negotiable.

I did not write a policy that day. I just never opened that tab again. Every tool since has shipped the same way: one number, set once, changed only when the product itself changes enough to justify it, and even then announced as a new price going forward, never as a "sale." I would rather have a quiet week than a customer who feels punished for buying early.

What a Discount Tells a Buyer About the Price

A price is a claim. It says: I did the work of figuring out what this is worth, and this is the number. The first time you cut that number for a countdown clock, you are telling every future visitor that the claim was soft. That the number was padded on purpose so there would be room to knock some off later. Even if that is not true, a discount makes it look true, and a shopper who has been online for more than five minutes has learned to read that signal correctly most of the time.

I see this constantly as a shopper myself. A tool I am considering shows a "40% off, ends Sunday" banner, and my first instinct is not excitement, it is suspicion. What was the real price supposed to be. Why does a piece of software need a countdown clock at all, when the marginal cost of another download is close to nothing. The urgency is manufactured, and once I notice that, I trust the rest of the page less too, including the parts that were honest.

RAXXO tools do not carry that problem because they have never had a discount to notice. The price on the product page is the price. New visitors and returning customers see the same number, and I never have to think about timing a launch around a sale calendar or worry that a customer will feel cheated by checking back a month later. It also means I never have to write "price subject to change without notice" anywhere, because in practice it almost never does.

There is a second, quieter cost to discounting that took me longer to notice: it trains people to time their purchase around your marketing instead of their actual need. A visitor who wants Git Dojo today but has seen a "wait for the sale" pattern somewhere else will bookmark the page and leave. A flat price removes that calculation entirely. If the tool solves the problem today, today is as good a day to buy it as any other, because tomorrow's price is the same number.

Bundling and Free Tools Do the Discount's Job Better

None of this means I think value only flows one direction, toward the buyer paying full price forever. I just do not think a markdown is the right way to hand more value back. A discount changes the number on one product for a window of time. A bundle or a free tool changes what the whole storefront offers, permanently, without ever touching a price tag that someone already paid.

Statusline Builder is the clearest example. It is free, has been free since the first version, and I have written before about why I keep it that way. Giving a whole tool away costs me nothing in trust, because nobody who paid for it feels burned when the price changes, since it never had a price to begin with. It also does something a 20% discount on Git Dojo could never do: it puts a complete, working RAXXO tool in front of someone who has never bought anything from the store, with zero friction and zero fine print.

Bundling works the same way without the trust problem. When I pair two tools together on a landing page, or point a Blueprint buyer toward Git Dojo as a natural next step, the person who already owns one of them is not penalized for having bought early. They just see a new reason to come back, on their own schedule, not because a timer told them to. Nobody who bought last month opens their inbox to find out this month's buyers got a better deal.

I think about it as two different questions that look similar but are not. "How do I move more units this week" is the discount question, and it treats price as the only lever. "How do I make the whole storefront worth more to the person already standing in it" is the bundling question, and it treats trust as the asset you are actually protecting. The second question has never once led me back to that price field I closed a few months into running the store.

The One Exception That Proves the Rule

I do change prices. I just do it in one direction, forward, and I say so plainly instead of dressing it up as an event. When a tool grows enough that the old price stops reflecting what it does, I raise it for new buyers and I do not touch what existing buyers already paid. That is the opposite of a discount, and it is the only kind of price movement the store has ever done.

The reasoning is the same trust logic, just pointed the other way. A price increase on a tool that has visibly grown makes sense to anyone looking at it: the thing got bigger, the number got bigger. A price cut with no explanation, or worse, a price cut with a countdown clock bolted on, asks a shopper to believe the original number was never quite honest. One of those moves is consistent with the tool actually getting better. The other one only makes sense as a way to create pressure that was not there naturally.

I also never call a price increase a "launch special ending" the way plenty of stores frame it, because that framing is just a discount wearing a different name, urgency manufactured from the other side. If a price changes, the product page says so, and it says why, in plain language, the same way I would explain it to someone asking in person. No banner, no clock, no "act now."

This is also why the product pages lean so hard on a clear, honest description up front. A shopper who knows exactly what they are getting before they pay is far less likely to feel let down after. Getting the price and the description right the first time, and leaving both alone, has turned out to be a much smaller job than the alternative: managing a calendar of sales, writing copy for each one, and hoping the next markdown does not make last month's buyer feel like they overpaid.

Bottom Line

A discount solves a short-term problem by creating a longer one. It moves the graph for a week and quietly teaches every future visitor that the number on the page is negotiable, which makes the next honest price harder to sell. I would rather keep one number, set it carefully, and only ever move it forward when the product genuinely earns a new price.

Free tools and bundles have done everything I once thought a sale would do, without asking anyone who bought early to feel foolish for it. Statusline Builder being free from day one has brought in more first-time visitors than any markdown ever could have, and it never put a single existing customer in the position of seeing a better deal than the one they took.

Running a one-person studio means every trust signal matters more, not less, because there is no brand history to fall back on if one goes wrong. A flat price is the cheapest trust signal I know how to send. I have not needed a countdown clock yet, and I do not expect to start now.