RAXXO sells across three shapes of value, merch, one-time digital downloads, and hosted tools, and the pricing model follows the shape instead of a single house rule
The test I run on every new tool is one question, does the value get handed over complete at the moment of download, or does it keep accruing only as long as something keeps running
Blueprint shipped as a one-time package on purpose, a finished guide does not need a server to keep paying rent after someone owns it
Free is not a third pricing tier, it is a deliberate zero for tools built to earn trust before anyone is asked to pay for anything
Two Very Different Kinds of Value
RAXXO sells three shapes of thing under one roof: merch, one-time digital downloads, and hosted tools that behave more like small SaaS products. For a while I assumed all three needed to share one pricing philosophy, because they all come from the same one-person studio and show up on the same storefront. That assumption did not survive contact with actually pricing a second and third tool. Merch is obviously a single transaction, a shirt does not need ongoing anything once it ships. But the digital side split in ways I had not planned for, and pretending it had not would have meant forcing every new tool into whichever model I happened to use last.
A one-time digital download and a hosted tool look similar from the outside, both are things a customer clicks buy on and both live somewhere on a computer afterward. The difference is what happens the day after purchase. A packaged guide is finished the moment someone owns it. Nothing about it changes, nothing about it needs to keep running on my end, and nothing about it depends on a service staying online somewhere. Claude Blueprint, the tool I built by packaging a longer stretch of learning into a single install, is exactly that kind of thing. It is complete the day it is downloaded. Charging for it as a subscription would have made no sense, there is nothing recurring to bill against.
A hosted tool is a different animal even when the price tag looks similar at first glance. If a tool needs to keep talking to a live service, refresh data, or stay running in the background to be useful at all, the value is not handed over once, it is delivered continuously for as long as the customer keeps using it. That distinction sounds obvious written out like this, but it took building more than one tool before I stopped defaulting to whatever pricing shape felt familiar and started asking what each specific thing actually was.
The Test I Run Before Pricing Anything New
Before I decide how a new tool gets priced, I ask myself one question first: is the value complete the moment someone downloads it, or does it only exist while something keeps running. Everything else follows from the answer.
If the answer is complete on download, a one-time price is the honest choice. Billing that same thing every month would mean charging for nothing new happening, which is the kind of thing customers notice and resent, and rightly so. A finished guide, a template, a packaged set of instructions, these do not improve by themselves while sitting on someone's drive. Whatever value they had on day one is the value they will have a year later. Pricing them once matches how they actually work.
If the answer is only exists while something keeps running, a subscription is the honest choice instead, because the studio is still doing something for that customer every single day they use it, whether or not they notice. A tool that watches a live status or refreshes against a service that changes on its own schedule is not a static object I hand over once. It is closer to a relationship than a purchase, and pricing it as a single payment would eventually leave me maintaining something for free, which is not sustainable for a studio built around evenings and weekends rather than a large team.
The test is deliberately simple because pricing decisions made under pressure, right before a launch, tend to default to copying whatever worked last time. A simple question is easier to actually ask in the moment than a complicated framework would be, and it has caught more than one case where I almost reused the wrong model out of habit.
I have also learned to distrust my own first instinct on this, because the instinct usually favors whichever model I priced most recently rather than whichever model actually fits the new tool. Building something new tends to put me in a mindset shaped by the last thing I shipped, so the honest fix was writing the question down somewhere I actually look at it before pricing anything, instead of trusting myself to remember to ask it under deadline pressure. A rule that only lives in memory gets skipped exactly when it matters most, which is usually the moment right before a launch when every instinct says just ship it and figure out pricing later.
Where Free Fits Into the Split
Free is not a third pricing tier hiding between one-time and subscription. It is a deliberate zero, chosen for specific reasons rather than left as a default. Statusline Builder is the clearest example, a tool I give away without charging anything, on purpose, because its job is to be the easiest possible way for someone to see what RAXXO actually builds before they are asked to trust the studio with a purchase of any kind.
That only works because the tool costs little to keep running and does not depend on the kind of ongoing infrastructure that would make giving it away unsustainable. A free tool that needed heavy upkeep would eventually have to either start charging or get shut down, and neither outcome serves anyone well. So free gets reserved for tools where the shape of the thing, low upkeep, high trust value, actually supports giving it away, rather than applying it everywhere out of generosity that the studio cannot actually sustain long term.
The same logic that separates one-time from subscription applies here too. Free is not a mood, it is a conclusion drawn from the same question. If a tool costs almost nothing to keep available and its job is to open a door rather than deliver ongoing value on its own, free is the honest price. If it would quietly drain time and attention every month forever, free stops being generous and starts being unsustainable, which helps nobody, including the customers who came to depend on it.
What Customers Actually Ask Me
The question I get most often in the support inbox, the same one I answer alone for five RAXXO tools, is some version of will this ever change on me. Someone who bought a one-time guide wants to know it will not suddenly turn into a subscription later, and someone paying monthly for a hosted tool wants to know the price is not about to move without warning. Both questions come from the same place, a reasonable fear that the rules of a purchase might shift after the fact.
My answer has stayed consistent because the pricing model is tied to what the tool actually is, not to a mood or a growth target. A one-time tool stays one-time because its nature has not changed, it is still complete the day it is downloaded. A subscription tool stays a subscription because it still needs to keep running for the value to exist at all. Customers seem to relax once they understand the reasoning is structural rather than arbitrary, that the model was chosen because of what the tool does, not because a spreadsheet somewhere said to try charging more.
That structural honesty matters more to me than optimizing for whichever model looks better on paper. A customer who understands why they are paying the way they are paying trusts the studio more than one who is simply told a number and asked to accept it.
The other question that comes up almost as often is whether a subscription tool will ever get downgraded quietly, features removed one release at a time until the price no longer matches what is actually delivered. I take that concern seriously, because it is a reasonable thing to worry about from anyone who has been burned by a tool that shrank after they committed to paying for it every month. The answer again ties back to the same structural honesty. A subscription only stays a subscription as long as the studio keeps doing the ongoing work that justifies it, and if that ongoing work stops, the tool should stop being a subscription too, not quietly get smaller while the price stays the same.
Bottom Line
Five tools under one roof do not need one pricing philosophy, they need pricing that matches what each one actually is. A finished guide and a tool that runs every day are not the same kind of thing, and charging them the same way would be dishonest about what a customer is actually getting. The test stayed simple on purpose: is the value complete on delivery, or does it only exist while something keeps running. That single question has done more to keep pricing decisions consistent across five very different tools than any house-wide rule ever could.
Free earns its place the same way, as a deliberate choice for tools built to open a door rather than a default setting applied everywhere. None of this is about squeezing more out of a purchase. It is about a customer being able to look at what they are buying and understand, without having to ask, why it costs what it costs and whether that is ever going to quietly change on them.
That is the whole point of running the same test on every new tool before deciding anything else about it. A pricing model chosen for the right structural reason tends to still make sense a year later, long after the excitement of a launch has faded and only the actual daily use of the tool remains.
Top comments (0)