Why we do not sell subscription SaaS modules
A common question we get from prospective buyers: why is our cart recovery module £349 lifetime instead of £29 per month? The honest answer is that we have packaged modules from 500+ store engagements since 2019 and we have strong opinions about why subscription pricing for installed Magento extensions is wrong for most customers, with a few specific exceptions where it makes sense.
This post is the long-form version of the answer.
The economics of module subscription versus lifetime
A Magento module installs once and runs forever. Once the code is in your vendor/ directory and the database tables are created, the module's marginal serving cost to the vendor is zero. The vendor's real costs are upfront engineering, periodic compatibility updates against new Magento versions, and customer support.
Subscription pricing for that cost structure has two effects. It charges customers continuously for what is functionally a one-time install. And it shifts the vendor's incentive away from polishing the install and toward maximizing customer retention, often through artificial migration costs or feature gating that punishes customers who consider cancelling.
We did the math early. A £349 lifetime price covers our development time at typical UK engineering rates inside roughly 200 customer purchases. Past that, the module is profit margin. A £29 per month subscription with 24-month median retention generates more revenue per customer in aggregate, but at the cost of treating every customer's renewal decision as a battle to be won.
We did not want to build the renewal-battle business. So we priced lifetime.
What subscription pricing actually pays for and what it does not
The subscription pitch for installed modules is usually some combination of: continuous updates, faster bug fixes, included support. Worth interrogating each claim.
Continuous updates. Magento ships two to three significant releases per year. A well-built module needs one to two engineering days per release to verify compatibility. That is roughly £1,200 to £2,400 per year in maintenance cost across the entire user base. A £349 lifetime price assumes that maintenance is funded by ongoing new sales, not by recurring revenue from existing customers. As long as the catalog keeps growing, that math works.
Faster bug fixes. Subscription vendors love to imply that paying customers get priority. In practice, every Magento bug-fix release we have ever shipped has gone to all customers on all tiers because shipping a fix for some and not others is operationally impossible. The subscription gating is theatrical.
Included support. This is the one real value driver of subscription pricing. We chose to bundle 12 months of support into the lifetime price and offer a half-price annual support renewal afterwards, which preserves the lifetime promise while still funding ongoing support. Customers who never want to renew never have to. The module keeps working.
The three exceptions where subscription is honest
We are not against subscription pricing in general. Three patterns make it appropriate:
The module requires ongoing third-party costs. Modules that send SMS, run AI inference, sync data through a paid API, or otherwise carry per-customer marginal cost legitimately need recurring revenue. Subscription is the only sustainable model here.
The module is fundamentally a SaaS product with a Magento connector. Email service platforms like Klaviyo, customer-data platforms, hosted search like Algolia. The module is a thin connector to a real SaaS product. Subscription pricing of the SaaS is honest; the connector is usually free.
The module needs continuous data updates. Tax rate engines, currency conversion services, fraud detection scoring. The data itself is what you are paying for, and the data goes stale without ongoing refresh.
Our own AI Cart Recovery + WhatsApp module sits at the boundary. The module is lifetime priced, but customers pay WhatsApp Business API costs through their own account, which is the natural way to price ongoing third-party cost without dressing it up as a module subscription.
What our customers told us in pricing research
Before we set our pricing model, we asked 30 Magento store owners (across our existing client base plus prospects) what they preferred and why. Three findings shaped what we shipped.
Preference for lifetime pricing was 70 percent. Even when we presented matched economics where the lifetime price was higher in total than two years of subscription, store owners preferred the lifetime option. The reason was not financial. It was the certainty.
The biggest objection to subscriptions was "module dies if I cancel". Store owners had been burned by modules that stopped working at subscription end, locking them into renewal under threat of broken stores. Lifetime was a defense against that pattern.
No one mentioned wanting "always-latest" updates as a reason to prefer subscription. The use case subscription vendors emphasize most was not what customers actually wanted.
What we would do differently if we were starting over
A few honest reflections. We would set a lower support-renewal price for the years after the first 12, because the actual ongoing support cost per customer is lower than we initially estimated and the renewal price should reflect that. We are evaluating dropping it from 50 percent of original to 30 percent.
We would also publish per-module support response-time data, because subscription vendors lean on their support story heavily and lifetime modules need to compete on the same measurable ground. The data exists in our ticket queue; we should make it public.
And we would offer the option of a one-year support extension at purchase time, not just at renewal. Some customers want a known three-year support window upfront.
The honest scope of this position
We are a small marketplace. Our pricing model works because our cost structure is small. A vendor with 50 engineers and a sales team probably cannot run the lifetime model and would be honest about that.
What we will not do is hide behind subscription pricing as a feature-velocity story when the real driver is investor pressure for recurring revenue. If a Magento module is priced as a subscription, ask the vendor specifically what the recurring cost funds. The answer often illuminates whether the price model is for you or for them.
Related
- Magento extension buyer's guide covers the seven questions we ask before installing any module, including pricing-model scrutiny.
- eTechFlow vs Amasty covers one specific subscription-vs-lifetime trade-off head to head.
- Magento development cost guide covers the economics from the other side, when subscription retainers are appropriate.