Open the pricing page of almost any premium WordPress plugin and you’ll find the same shape: an attractive first-year price, an automatic renewal at a higher rate, and no way off the treadmill. The SaaS subscription model has become the default for WordPress software, and mostly nobody asks why.<\/p>\n
We want to be straight about where we landed, because it isn’t the dramatic version. We still sell annual licences, and annual is still the default option on our pricing pages.<\/strong> What changed is that we stopped making it the only<\/em> option: every paid tier of Trinity Forms<\/a>, JnK Linkweave<\/a> and EntryVault<\/a> now has a lifetime licence next to it \u2014 pay four times the yearly price once, and you’re done. No renewals, ever.<\/p>\n Here’s the thinking behind that, and the part of the subscription critique we think is actually right.<\/p>\n No single subscription is unreasonable. It’s the accumulation. Hosting, theme, SEO plugin, caching, backups, form builder, security \u2014 each one modest, and suddenly a small business site costs several hundred dollars a year in renewals before anyone has done any work. The first instinct when another recurring charge appears is to cancel something, and that decision usually isn’t made on merit.<\/p>\n This is the one we feel most strongly about, because it changes what gets built. If revenue depends on annual renewals, there’s constant pressure to ship visible new features so the renewal feels justified. That’s how a contact form plugin acquires an AI assistant nobody asked for. The features get announced; the plugin gets heavier; the site gets slower. Everyone loses except the renewal rate.<\/p>\n Charging once removes that particular pressure. It doesn’t make us better developers \u2014 it just means “we made it faster and fixed twelve bugs” is a perfectly good year.<\/p>\n The practice we genuinely object to: form plugins that stop you reading your own submissions when a licence lapses. The data is in your<\/em> database, on your<\/em> server, collected from your<\/em> visitors. Putting the interface to it behind a payment wall is a choice, and it’s the wrong one.<\/p>\n It’s why Trinity Forms<\/a> has a readable Entries<\/strong> screen in the free version, and why EntryVault<\/a>’s CSV export isn’t a premium feature. We wrote about where that line sits across the market in WPForms vs Contact Form 7<\/a>.<\/p>\n Because the honest version is that annual licences suit plenty of people better, and pretending otherwise would be marketing rather than reasoning.<\/p>\n So both exist. Annual if you want the lower entry price and the option to walk away; lifetime if you’re settling in and would rather never see the invoice again. We’ve laid out the arithmetic in flat pricing vs subscriptions<\/a> \u2014 the break-even lands around year four.<\/p>\n To be fair to the model: subscriptions are the right answer when there’s an ongoing cost to serve. Hosting, email delivery, anything calling a paid API, anything with a crawler running on someone else’s infrastructure \u2014 those cost the vendor money every month, and a one-time payment doesn’t cover them.<\/p>\n A PHP plugin running entirely on your<\/em> server, using your<\/em> database, is a different thing. The vendor’s ongoing cost is updates and support \u2014 real, but not per-user-per-month real. That’s the distinction we tried to price against.<\/p>\n One last thing, since it’s the natural question. All three plugins have free versions \u2014 Trinity Forms<\/a>, JnK Linkweave<\/a>, EntryVault<\/a> \u2014 and they’re not time-limited or crippled. Form entries are readable, conditional logic works, keyword rules work, CSV export works. Plenty of sites will never need the paid tier, and that’s a perfectly good outcome.<\/p>\n What’s paid is the genuinely expensive-to-build end: payments and integrations in Trinity Forms; bulk link operations and analytics in Linkweave. If you’re curious where every line sits, the lifetime-deal roundup<\/a> covers it alongside other pay-once plugins.<\/p>\nWhat’s genuinely wrong with plugin subscriptions<\/h2>\n
1. The stack cost is invisible until it isn’t<\/h3>\n
2. Recurring revenue rewards feature bloat<\/h3>\n
3. Holding data hostage<\/h3>\n
Why we didn’t drop subscriptions entirely<\/h2>\n
\n
Where subscriptions genuinely make sense<\/h2>\n
The free tiers aren’t a trial<\/h2>\n
Related reading<\/h2>\n