Every other guide to selling a WordPress plugin is written by a company that wants to be your checkout. This one is built from live acquisition listings, revenue-verified products, Stripe payment data and what plugin developers say when nobody is selling them anything.
Selling a WordPress plugin is one of the few software businesses a single developer can still start in a weekend and run for a decade. It is also one of the most consistently misrepresented. The top-ranking guides for this topic are published by the companies that want to be your checkout, so they describe the plumbing in detail and stay silent on the economics. We pulled the economics.
Across 650+ live acquisition listings, the WordPress plugin and theme product businesses currently for sale carry a median profit multiple of 2.80x on a median profit margin of 88.9%. The wider listing pool averages 7.35x. That gap is the entire story of this business: WordPress plugins are exceptionally cheap to run and exceptionally hard to convince anyone has a future. Everything below is written to close that gap deliberately rather than discover it at exit.
Publish a genuinely functional free plugin on WordPress.org for discovery, sell the paid version from your own site with annual renewals from day one, gate updates and support rather than code, and target agencies and professional developers rather than people who build their own sites. Pick the problem from documented complaints before you write a line of PHP, which is the part every other guide skips and the part BigIdeasDB exists to solve.
We fetched and read the pages currently ranking for this topic. Every substantial one is owned by a vendor in the WordPress commerce stack, and each arrives at the conclusion that you should use that vendor’s product. To be fair to them, the technical content is often good. One of the better pages frames the problem cleanly as five pieces you need to assemble: a checkout, license keys, an update server, a customer area and a payment gateway. That framing is correct and we use it below.
What none of them tell you is whether the business is worth assembling. Not one publishes a revenue distribution, an exit multiple, a churn figure, or a list of which plugin niches still support a price. That is the gap this article fills, using the same evidence base we use for indie SaaS revenue and SaaS acquisitions.
The context worth having first: WordPress is used by 58.8% of all websites whose content management system is known, and 40.3% of all websites as of September 2026, per W3Techs. The addressable market is not the problem. The willingness to pay is.
Start at the end, because the exit price is the honest scoreboard for every pricing and distribution decision you are about to make.
We filtered our live acquisition listings for WordPress and WooCommerce businesses, then narrowed again to actual plugin and theme products with trailing revenue, excluding agencies and stores. The result is a small but unusually clean sample.
| Metric | WP plugin and theme products | All WordPress and WooCommerce | All live listings |
|---|---|---|---|
| Median profit multiple | 2.80x | — | — |
| Average profit multiple | 2.95x | 3.26x | 7.35x |
| Average revenue multiple | — | 2.23x | 2.33x |
| Median asking price | $120,000 | $106,500 | $195,800 |
| Median TTM revenue | $57,000 | $59,500 | — |
| Median profit margin | 88.9% | — | — |
| Run by a solo founder | 3 of 11 | — | — |
Notice which number does not move. The revenue multiple for WordPress businesses is 2.23x against 2.33x for everything else, effectively identical. The profit multiple collapses from 7.35x to 3.26x, and to 2.80x for pure plugin products. Buyers are not saying WordPress revenue is worth less per dollar. They are saying WordPress earnings are worth less, because the forward stream is unreliable.
If you have not priced a software business before, SaaS valuation multiples and our valuation guide explain how those two multiples diverge and why the profit multiple is the one buyers argue about.
The margin figures in this sample are almost absurd. Individual listings in our data include a WordPress content automation plugin business with $169,000 trailing revenue against $166,000 profit, a lead generation and email plugin at $165,000 revenue and $160,000 profit, and an affiliate marketing plugin at $31,000 revenue and $30,000 profit. These are businesses with essentially no cost of goods.
High margin sounds like an unambiguous good. In an acquisition it reads as a warning. A 97% margin usually means nothing is being spent on engineering, marketing or support, which means the product is coasting. Buyers price coasting at 2x. The same dynamic shows up in our broader work on what actually transfers when you sell and in the due diligence checklist buyers work through.
The practical instruction: if you want a multiple rather than a lump sum, deliberately spend some of that margin on visible forward investment. A roadmap, a recent major version, a growing renewal cohort and a documented support process are each worth more at exit than the cash they consume.
This is the single most surprising thing we found, and it reframes the whole decision.
We classified every company in our Stripe payment index that describes itself in WordPress or WooCommerce terms. These are real businesses taking real card payments. The split is not close.
| Business model | Share of WordPress companies | Flagged micro SaaS |
|---|---|---|
| Agency and services | 48.8% | 0 |
| B2B SaaS | 27.6% | 7 |
| Other | 11.0% | 1 |
| E-commerce | 6.3% | 1 |
| B2C SaaS | 4.7% | 4 |
| Marketplace and API infrastructure | 1.6% | 0 |
Nearly half of the WordPress companies taking payments are selling human time: web design, maintenance retainers, care plans, hosting with support attached, migrations, SEO work. Only 13 of 127 are flagged as micro SaaS at all. The plugin, in most successful WordPress businesses, is not the product. It is the credential that wins the retainer.
Several of the most successful WordPress businesses in our acquisition data behave exactly this way. One listing is a WordPress web design agency with 250+ clients and a stated 90% profit margin. Another is a recurring web design and local SEO agency claiming 86% margins on under eight hours of work per week. Both are priced near 1.1x profit, which tells you the market’s view of service durability too, but both are cash-generative from month one in a way a plugin is not.
A developer in one of the threads we read put the same conclusion in plainer terms after watching a nine-year plugin business decay: “the agency model with monthly retainers is something i should have explored way earlier. custom development plus maintenance for 5-10 clients paying $500-1k/month is way more stable than selling one time licenses to thousands of people who never come back.” — r/Wordpress
None of this means do not build the plugin. It means decide, before you start, whether the plugin is the business or the marketing. Our guide to deciding what business to start and the breakdown of boring industries begging for software are both useful sanity checks here.
Our revenue intelligence corpus tracks 8,600+ products where the founder has connected a real payment source. Forty of them are WordPress-related. The distribution is exactly what you would expect from any software market, which is itself the finding.
| Measure | WordPress products | All tracked products |
|---|---|---|
| Earning $0 per month | 45.0% | 56.5% |
| Clearing $1,000 per month | 10.0% | 10.3% |
| Median monthly revenue | $14 | — |
| Top five monthly figures | $8,108 / $6,504 / $2,982 / $1,576 / $997 | — |
Read that carefully, because it contradicts the doom narrative. WordPress products reach the $1,000 per month threshold at 10.0%, against 10.3% for every tracked startup in every category. They are actually less likely to be stuck at zero, 45.0% against 56.5%, which makes sense: the directory gives a new plugin a distribution channel that a new SaaS landing page does not have.
So WordPress is a perfectly normal place to reach a few thousand dollars a month, and a below-average place to build something a buyer will pay a premium for. Our analysis of startup failure statistics and solo developer revenue examples show the same long tail across every platform.
One product in our data deserves its own section. It is a WooCommerce shipping carrier integration plugin doing $2,982 per month. It has 1,172 paying customers. That works out to about $2.54 per customer per month.
Eleven hundred customers is a serious business by installed-base standards and an unserious one by revenue standards. Every one of those customers can open a support ticket. Every one of them is affected when WordPress or WooCommerce ships a breaking change. The support load scales with the customer count and the revenue does not.
This is the defining failure mode of WordPress plugin pricing, and it is structural rather than accidental. The ecosystem trained buyers on $25 to $49 one-time licenses, so plugins accumulate seats instead of revenue. If you take one pricing lesson from this article, take this one: optimise for revenue per customer, not install count. Our piece on what micro SaaS actually charges and the pricing help page both start from the same principle.
The developer community answers this question the same way every time it is asked, and the answer is the opposite of most founders’ instincts.
“Site owners that DIY don’t pay for anything, target devs.” — r/Wordpress
“Devs don’t mind paying for licenses. We have dozens of developer licenses for the plugins we like to use. It’s not cheap, but we manage nearly 100 sites, so it’s worth it.” — r/Wordpress
An agency owner in the same ecosystem laid out the actual purchase criteria: “we spend a lot of money on licenses when they ... solve a business problem for a customer that increases their revenue or reduces their administrative / process driven people expenses. If we can code it for less than 2-4 years subscription ... then we will.” — r/Wordpress
That last sentence is your pricing ceiling, stated by the buyer. An agency will pay you up to roughly what it costs them to build it themselves, amortised over two to four years. Price above that and they build. Price far below it and you are leaving the entire surplus on the table.
A third voice makes the point about volume: “The money is made with other businesses, agencies with 50-100-200 licenses, multiple licenses, yearly steady revenue that would allow you to create new features, make the plugins lighter, etc.” — r/Wordpress. For the corpus-scale version of this argument, see who micro SaaS actually sells to.
Rather than guess which categories are viable, we read what is actually listed for sale with real trailing revenue. The WordPress products on the acquisition market cluster into a short list.
| Niche | Example economics from live listings | Why it holds a price |
|---|---|---|
| Memberships and affiliates | $303K revenue, $219K profit, 2.7x, 10+ years operating | Directly gates the customer’s revenue |
| Lead generation and email automation | $165K revenue, $160K profit, 4.3x | Measurable return, budget sits in marketing |
| Content automation and publishing | $169K revenue, $166K profit, 5K+ customers, 1.8x | High volume, but commoditising fast |
| Directory and job listing systems | $51K revenue, $29K profit, 3.6x | Replaces a whole product build |
| E-commerce compliance and shipping | Revenue-verified at $2,982/mo across 1,172 customers | Regulatory obligation, not preference |
| Site operations and staging | $33K revenue, $33K profit, 2.1x, solo operated | Sold to professionals who bill for time |
| Navigation, galleries and layout | $54K revenue, $43K profit, 2.5x and $18K revenue, 2.3x | Low switching cost, lowest multiples |
The pattern is consistent with everything else we see across software markets: the plugins that hold a price touch money or legal obligation for a business. The plugins that struggle touch appearance for a hobbyist. If you want to pressure-test a category before committing, how to find a profitable niche and validating niche viability lay out the checks, and low competition SaaS ideas shows how we score crowdedness.
The ecosystem is having this argument in public right now, and the honest answer is more specific than either side claims.
“Plugin marketplaces are just not it anymore. The audience of developers who would use that as a resource are also capable of building the plugin they need with agentic tools, just like you or I.” — r/Wordpress
A working plugin developer answering the same question was much calmer: “My plugins are super niche, so no.” — r/Wordpress. That is the whole distinction. Generic utility plugins are now a prompt away. Plugins encoding regulatory detail, carrier integrations, years of edge-case compatibility, or access to a system with a real barrier are not.
Our funded-company index reinforces how thin the venture interest is here: of 17,000+ tracked funded companies, only five describe themselves in WordPress terms. Capital is going elsewhere, which is a competitive gift to a solo operator and a warning about terminal value at the same time. We unpack the general version of this in what counts as a moat in the AI era and micro SaaS without API dependency.
Everything after this step is mechanical. This step decides whether the business works.
Three independent evidence types are worth triangulating, and they are exactly the ones we maintain:
When a category lights up in all three, you have something. When it lights up in only one, you have a hobby. Our full method is in how to validate a startup idea and how founders research markets.
Here is what the search actually turns up when you run it. Freelance demand analysis across WordPress-adjacent categories surfaces the same recurring, unsolved operational problems:
“Many businesses struggle with the ongoing maintenance and updates of their WordPress websites, which can be time-consuming and error-prone when done manually. This includes regular updates, security checks, and content modifications that require technical skills.” — freelance demand analysis
“With frequent updates to themes and plugins, businesses face challenges ensuring compatibility and functionality, which can lead to website downtime and performance issues. This is a recurring problem that can be costly to resolve manually.” — freelance demand analysis
On the review side, the complaints are sharper and more specific. From software reviews mentioning WordPress plugin integrations:
“Their custom WP plugin was full of bugs when we tried to install and run it on our WordPress installations... This was a huge risk to our business.” — Capterra review
“Some add-ons don’t work well; it feels like rolling the dice every time we add them.” — Capterra review
“It would be nice if it has a WordPress plugin to process the links while writing the post.” — Capterra review
That last one is the highest-value shape of complaint there is: an existing paying customer of another product asking for a WordPress bridge that does not exist. Our guides to mining Capterra reviews, turning G2 reviews into ideas and finding ideas in negative reviews all teach the same pattern-match.
Not every complaint is worth a product. We score pain points on severity, and the WordPress and plugin-tagged subset of our review corpus has a clear hierarchy.
| Pain point category | Distinct pain points | Average severity |
|---|---|---|
| Security | 3 | 4.23 |
| Customization | 3 | 4.17 |
| Technical performance | 4 | 4.13 |
| Pricing model | 3 | 4.10 |
| Usability issues | 5 | 3.94 |
| User experience | 18 | 3.93 |
| Integration | 9 | 3.73 |
| Functionality | 9 | 3.50 |
Performance is the other underrated one. From a review of a widely used WordPress security plugin: “Some of the options are difficult to find initially and the plugin can be heavy on a heavily trafficked site, impacting our customer experience.” — Capterra review. Plugin bloat is a durable, expensive, universally acknowledged problem, which is exactly the kind of thing worth building against. See how we score opportunities and how to find problems worth solving for the scoring logic.
Almost every pricing mistake in this ecosystem traces back to misunderstanding what you are legally permitted to sell.
WordPress is licensed under the GPL, and WordPress.org treats plugins and themes as derivative works. The directory guidelines require everything hosted there to be under the GPL or a GPL-compatible license.
The GPL does not stop you charging. It stops you restricting. From the clearest explanation in a long community thread on the subject:
“plugins can charge money but they can’t withhold or obfuscate source code, and they can’t stop you from redistributing. They can put in license restrictions that stop you from using it, but they can’t stop you from removing said restrictions yourself... Most choose to limit license restrictions to updates and support.” — r/Wordpress
“Vendors make money by selling convenience: packaged downloads, automatic updates, hosted services, support and customization, or gated update servers — not by creating enforceable closed-source versions of code that was distributed under GPL.” — r/Wordpress
Internalise this sentence, because it should shape your pricing page, your renewal email and your support policy:
“When you purchase a plugin, you buy access to support and updates, not the plugin itself.” — r/Wordpress
Everything that carries value in a WordPress plugin business is a service wrapped around freely licensable code: the signed, malware-free zip from a source the buyer trusts; the automatic update that arrives before their site breaks; the human who answers when it does; the confidence that the thing will still be maintained in two years. Price all four, not the code.
Every popular paid WordPress plugin is available for free on piracy sites. This is a structural feature of shipping interpreted source code under a permissive license, not a security failure you can engineer away.
“This is the reason why nulled themes and plugins exist. When you purchase a plugin, you buy access to support and updates, not the plugin itself.” — r/Wordpress
The commercial response is not stronger DRM, which the license does not support and which annoys paying customers. It is making the legitimate path obviously better: instant updates, real support, and the security assurance that the code has not been tampered with. One buyer described that calculus exactly: “I buy everything from the developer’s website, where I know it’s legit code, with a legit license key, and I can get legit support.” — r/Wordpress
There are three viable shapes, and they are not equally good for everyone.
| Model | How it works | Best for | Main cost |
|---|---|---|---|
| Freemium | Functional free plugin in the directory, paid pro version on your site | Founders with no existing audience | Support load from non-paying users |
| Premium only | No free version, sold from day one | Specialist or compliance-driven tools | You buy all your own traffic |
| Add-on ecosystem | Free or cheap core, paid modular extensions | Complex systems: commerce, memberships, directories | Combinatorial compatibility testing |
Freemium is the default recommendation everywhere, and it is usually right. It is also oversold, in two specific ways that the vendor guides never mention.
The directory is worth more for trust than for traffic: “WordPress.org alone brings almost zero organic traffic until you hit a certain install threshold. You still need external content, communities, outreach to get initial traction. The upside of WordPress.org is credibility — people trust it more than a random Gumroad link.” — r/Wordpress
And it creates a second front for unpaid support. This is the cost nobody warns you about, reported by a developer nine years into the model: “launched a free version on the wp repository thinking it would funnel people to premium. instead my paying customers from codecanyon started going to the wordpress.org support forum to get free support there. and if i didnt respond they threatened bad reviews. so now i had two platforms where people could pressure me instead of one” — r/Wordpress
Conversion from free install to paid customer runs in the low single digits for most plugins. Plan your install-to-revenue math on that basis, the way we do in getting to the first $1K MRR.
Skip the free version when your plugin solves a problem that is expensive, regulated, or narrow enough that the buyer is already searching for a solution. Compliance plugins, carrier integrations, industry-specific systems and agency tooling all fit. You trade the directory’s discovery for a much higher average price and a dramatically smaller support surface.
One listing in our acquisition data describes exactly this position: a WordPress food ordering and delivery system sold through a marketplace at “The regular License price is $49 and the Extended License price is $499. 5 add-ons regular License prices are $89, $99, $69, $49, and $19.” — acquire.com listing. Narrow vertical, layered pricing, no free tier. See single-feature micro SaaS ideas for more products shaped this way.
Add-ons are how the largest WordPress plugin businesses monetise. A free or cheap core wins the install, and paid extensions capture the customers with real needs. It also produces the best-looking acquisition listings we see, such as the membership and affiliate plugin business whose seller describes “Subscription Model: Offers annual subscription plans for access to all current and future plugins ... Add-Ons & Extensions: Monetizes through the sale of add-ons and extensions” — acquire.com listing, at $303K revenue and $219K profit.
This is the mistake that ends WordPress plugin businesses, and we have an unusually detailed account of it. A developer who built a community plugin published nine years of numbers: $461,634 total revenue, and a recent month at $38.50.
His diagnosis was not the market shrinking, though it did: “the buddypress decline killed the revenue but the broken business model is what made it impossible to survive that decline. if i had recurring revenue the shrinking market would have hurt but it wouldnt have taken me from five figures monthly to $38.50.” — r/Wordpress
A theme author replied in the same thread with a near-identical curve, reporting roughly $600,000 earned over ten years and about $200 in a good month now. He added the detail that should frighten anyone selling lifetime licenses: “when I ask them to renew support when they create a ticket, they told me that I am a scammer!” — r/Wordpress
The crucial nuance, which contradicts the popular reading of that thread, is that the model is not the problem. Switching to it late is. From a developer who launched with renewals from the start: “I offer monthly, annual and lifetime for my plugins, and 95% of my customers choose monthly/annual over lifetime, and they stick around as well, some even paid the equivalent of multiple lifetime purchases in recurring subscription fees.” — r/Wordpress
The instruction is unambiguous. Launch with renewals. If you must offer lifetime, price it at roughly three times the annual rate and cap what it entitles the buyer to. SaaS pricing strategies covers the mechanics of holding that line.
There is remarkable consistency in the figures WordPress professionals volunteer unprompted.
“I’ve been using WP and building websites for 15+ years. If the plugin is good and there is solid support, I have no issue paying $79-$100 per year for it. If the plugin helps my business, I’ll make that money back quickly.” — r/Wordpress
“I will happily pay annually for a decent plugin but wouldn’t pay monthly, I buy plugins at different times of the year to spread out the annual payments” — r/Wordpress
Three signals there. The comfort band for a single-site professional license is roughly $79 to $100 per year. Annual beats monthly for this buyer specifically, which is the opposite of standard SaaS advice and worth respecting. And the objection is never the amount, it is the perceived value of what the renewal buys.
The counter-position deserves airtime too, because it sets your ceiling for non-professional buyers: “Subscriptions for Wordpress plugins are ridiculous and overly priced in the majority of cases. £10 a month fair enough but £30 a month is pushing it, times that by 10 plugins you’re looking at £300 a month to run a simple website” — r/Wordpress. That person is not your customer.
Feature-gated tiers punish your best-fit users and invite the complaint that the free version is crippled. Site-count tiers scale with the customer’s own revenue and map directly onto the agency buyer who has budget.
There is one more wrinkle worth knowing. Agencies frequently have the client buy the license, not themselves: “professional developers have the client purchase the licenses for the plugins the client requested features require. This way if they ever move to another developer they own their licenses.” — r/Wordpress. Build license transfer into your customer area early; it removes a real objection.
Renewals are where WordPress plugin revenue actually lives or dies, and the honest expectation is low.
“people just dont renew. they use the plugin for years on whatever version they have and only come back when something breaks. and then they expect you to fix it for free even with an expired license.” — r/Wordpress
You do not need everyone to renew. As one developer put it: “Sell a license that expires and then the plugin no longer gets updates. Simple. You don’t need everyone to pay, just 20 percent of your overall client base.” — r/Wordpress. See SaaS metrics benchmarks and MRR vs ARR vs TTM revenue for how to track whether you are hitting it.
You have three options and the correct answer is almost always a combination with one of them clearly primary.
| Route | Cost | Who owns the customer | Verdict |
|---|---|---|---|
| WordPress.org directory (free version) | Free | You, weakly | Best trust signal available, weak traffic early |
| Marketplace, e.g. CodeCanyon | Up to roughly half of a non-exclusive sale | The marketplace | Secondary channel at best |
| Merchant of record, e.g. Freemius | Single-digit revenue share, handles global tax | Shared | Good default if tax scares you |
| Your own site, e.g. Easy Digital Downloads plus Stripe | Gateway fees only, 2.9% + 30¢ on US cards | You, entirely | Highest margin, most work |
The directory is the only free distribution channel in software with genuine institutional trust attached, and you should use it. Treat it as three things: a discovery surface inside the WordPress admin, a credibility marker, and a source of the reviews that make your paid page convert.
Treat the free plugin as a real product. The version that funnels well is genuinely useful on its own and leaves a clear, non-annoying upgrade path. As one developer put it: “as long as the free version can give a user good features that make the plugin useful, you’ll be able to set features in a pro version that users will want to upgrade to.” — r/Wordpress
For context on how crowded the shelf is, the directory’s most-installed plugins carry tens of thousands of ratings each, and a single page builder runs on 31.6% of all WordPress sites. You are not going to out-distribute the incumbents. You are going to out-specify them in a narrow slice, which is the same play we describe in the state of micro SaaS competition.
These are the ones that catch commercial plugin authors, taken from the official plugin directory guidelines. Read them before you architect your freemium split, not after.
A community member summarised the trialware rule in practical terms: “you can’t block any functionality in a plugin if the code is present in the plugin and then upload it at WordPress.org ... it would be against the plugin repository TOS and your plugin can be disabled and in extreme case removed.” — r/Wordpress
Marketplaces give you buyers on day one and take a permanent cut plus the customer relationship. On a non-exclusive listing the commission can approach half the sale price.
The strategic cost is larger than the commission. From the developer who ran this model for nine years: “the platform takes a huge cut, you cant install tracking pixels to run proper ads, you cant build a real relationship with your customers, and youre basically stuck with their model” — r/Wordpress
“If you can, I’d avoid hitching your wagon to any ‘marketplace’ and if you do, make it a short-term thing. I’ve seen far too many threads from burned out plugin devs saying they’re done and selling their product for pennies on the dollar” — r/Wordpress
Our acquisition data supports that last sentence numerically. The listing in our sample most explicitly dependent on marketplace distribution, a premium theme and page builder business described as a featured top seller on Envato, is priced at 1.2x profit on $57,000 revenue and $55,000 profit. Meanwhile an independent plugin business with its own distribution commands 4.3x on comparable revenue. Marketplace dependency costs roughly three turns of multiple.
Buyers vote the same way: “I’ve bought exactly one thing off a marketplace in 13 years of using WP.” — r/Wordpress
Running it yourself means assembling five components. This framing comes from the best of the competing guides and it is genuinely the right mental model.
Run the arithmetic before you decide. At $2,000 per month in sales, a 7% platform share is $140 a month and $1,680 a year, permanently. Gateway fees apply on every route; the platform fee only exists because you have not assembled the five pieces. At small scale the convenience is worth it. Past roughly $3,000 to $5,000 per month it stops being.
Developers who have run both are consistent about the outcome: “I’ve sold WordPress plugins outside CodeCanyon, and running sales on my own site ended up being the most profitable.” — r/Wordpress
This is the part that ambushes solo developers. Digital goods are taxed differently in almost every jurisdiction, and selling to EU consumers means VAT obligations from the first sale regardless of your revenue.
A merchant of record buys the product from you and sells it to the customer, taking on the tax liability. That is what the single-digit revenue share actually purchases, and it is real work you are not doing. If you run your own checkout, you own the calculation and the remittance, either through your accountant or through gateway tax tooling.
A useful middle path exists: route payments through a merchant of record while keeping licenses, updates and your customer area on your own infrastructure. You pay a platform fee on payments only and keep the customer relationship and the asset. Given what we saw about marketplace dependency and exit multiples, that is a good trade.
A licensing system does four jobs: it issues a key at checkout, activates that key against a site URL, counts activations against the plan limit, and tells your update server whether this site is entitled to the latest version.
Do not build this from scratch. Established WordPress licensing SDKs exist, several are compatible with the long-standing Easy Digital Downloads API shape, and adopting that shape means the update code most plugins already ship will work against your server unchanged.
Test the entire flow before launch, in this order: buy your own plugin, confirm the key arrives by email, activate on a clean install, trigger an update check, ship a minor version and confirm it auto-installs, deactivate, reactivate, exceed the site limit, let a license expire, and enter a deliberately invalid key. Each of those is a support ticket you will otherwise receive in week one.
Be realistic about what licensing enforces. Under the GPL you cannot prevent redistribution and you should not try to obfuscate. Licensing exists to deliver value to paying customers, not to punish everyone else.
The automatic update is the single most valuable thing you deliver, because it is the one thing the free copy does not get. It is also the thing customers refuse to value explicitly.
The developer from the nine-year post-mortem named this precisely: “the value was constant compatibility updates. wordpress would push updates that broke things regularly so i was basically firefighting all year to keep everything working... but the problem is users dont see compatibility fixes as value. they see it as ‘it should just work.’” — r/Wordpress
The marketing answer is to make maintenance visible. Publish a changelog with dates. Name the WordPress and PHP versions you tested against. Send a short note when you ship a compatibility fix, even a boring one. Invisible work does not renew.
Support quality is the most frequent differentiator in the review data we analysed, in both directions. The positive version is that people will pay a real price for responsiveness. The negative version dominates the complaint corpus.
“Most of the live support agents were very unhelpful. I wasn’t able to integrate my WordPress site successfully despite doing everything right.” — Capterra review
Across our whole review corpus, support responsiveness and pricing are the two themes that recur in almost every WordPress plugin product analysis. Documentation is the cheapest lever: every question you answer twice belongs in a docs page. See getting your first 100 users for how support and acquisition overlap early on.
Here is the structural problem with one-time pricing, stated as arithmetic. Every sale adds a permanent support obligation and a one-off payment. Revenue is a flow that stops; support load is a stock that accumulates.
The theme author quoted earlier offered a rare piece of good news about this: “I have 16k sales, but I get support requests from old buyers VERY rarely. And I also have some crazy buyers that bought a theme 10 years ago.” — r/Wordpress. Most old customers go quiet. But the ones who do not are unbounded, and they arrive at the worst moment, which is when a WordPress release breaks something.
Structural defences: tie support entitlement to an active license from day one, sell support in tickets rather than in months, publish a documented support policy, and price the renewal so that the twenty percent who do renew fund the support for everyone. One customer actively proposed the ticket model: “Support? Give it as support tickets, not ‘x months’. Pay for a year of updates and you get 3 support tickets.” — r/Wordpress
Plugin marketing has changed more in the last two years than in the previous ten. The developer complaint is already visible in the community: one plugin seller opened a thread titled “Decline in WordPress Plugin Sales and Organic Traffic” asking whether AI tools are changing how WordPress users search for solutions. They are.
The channels that still work, ordered by return for a solo operator:
Our guides to getting customers for a new product and growth levers founders never pull apply directly here.
One developer in our research nailed the current state of plugin marketing in a sentence: “Don’t go with the marketplace. Build products and make your own site. Write blogs, do better AEO SEO. Rank your site, gain your DR level.” — r/Wordpress
The practical shift is that WordPress users increasingly ask an assistant “how do I do X in WordPress” instead of searching and comparing plugins. To be the answer that gets cited you need content that states the answer first, carries specific numbers, and is structured cleanly enough to be quoted. That is the same discipline described in optimising for AI Overviews.
Documentation doubles as this content. A well-written docs page for each real user problem ranks, converts, and reduces support, which is a rare three-way win for a solo developer.
Given everything above, agency and developer outreach is the single highest-leverage activity available to a WordPress plugin business, and almost nobody does it systematically.
Agencies buy multiple licenses, renew as a cost of doing business, generate proportionally fewer support tickets because they are technical, and refer other agencies. The developer from the nine-year post-mortem identified this as his central regret: “the b2b angle and agency licenses is where the real money is. i see that now. i just didnt see it when i was 9 years deep in b2c selling $39 licenses to individuals one at a time.” — r/Wordpress
Practically: build an agency tier before you need it, offer license transfer to clients, publish a short partner page, and email fifty WordPress agencies that visibly serve the vertical your plugin targets. That is a week of work with a much better expected return than a month of feature development.
Install count is a vanity metric in this business, as the 1,172-customer example demonstrates. The numbers that predict whether you have a business are:
MRR tracking tools and our revenue benchmarks by category give you something to compare against.
Return to the 2.80x. If you intend to sell this business eventually, and most plugin developers eventually do, then the decisions that set your multiple are made years before the listing goes live.
The sellers in our acquisition data describe motivations that are almost always the same, attention rather than failure: “I want to focus on my WordPress membership plugin and WP to CRM automation plugin” — acquire.com listing. That means the buyer is assessing whether the asset runs without the founder, not whether you got bored.
The things that raise a WordPress plugin multiple, in rough order of impact: recurring revenue with a demonstrated renewal cohort, distribution you own rather than rent, documented operations, a clean and current codebase, multi-site tiers, and a product in a niche with regulatory or integration depth. Our guide to selling a SaaS, what transfers in a sale and the listings-as-validation help page go deeper.
From reading the listings and their AI-scored risk signals, four things consistently suppress WordPress plugin valuations.
| Multiple killer | What the buyer sees | Fix, and when to start |
|---|---|---|
| One-time license base | Revenue with no forward stream | Renewals from launch; migration later is brutal |
| Marketplace dependency | No customer list, no pixels, platform risk | Own-site primary from month one |
| Single-platform concentration | A plugin for a shrinking sub-ecosystem | Watch your host’s install trend annually |
| Zero reinvestment | 97% margin, no roadmap, coasting | Ship a visible major version before listing |
The third one is the quiet killer, and the nine-year post-mortem is a textbook case: the plugin depended on a sub-ecosystem within WordPress that stopped growing. One commenter was blunt about it: “that’s not a pricing problem, that’s a platform risk problem. Even if everyone renewed perfectly you’d still be fighting a declining user base.” — r/Wordpress. Check your foundation’s trajectory once a year, the same way you would check a dependency for deprecation. Our work on buying versus building and finding acquisition targets covers the buyer’s side of the same analysis.
Everything in this article after “pick the problem” is executable with tooling that already exists. The part that is not solved anywhere else is the first step, which is why BigIdeasDB is the tool we would use for it and the one we built.
We maintain 1M+ documented complaints from reviews, forums and support discussions, alongside revenue-verified products, live acquisition listings, funded-company records and a payment index of 30,000+ companies. For a WordPress plugin specifically, that means you can answer four questions before writing code:
Beyond BigIdeasDB, the honest list of generalist tools worth having in this workflow is short: ChatGPT or Claude for drafting and code, Google Trends for direction of travel, and Notion for keeping the research organised. None of them hold a complaint corpus, which is the input this particular decision needs. Start at the discovery tool, or read how the validation tool works and how complaint analysis works.
Every figure in this article was queried live on September 12, 2026. Nothing is carried over from an earlier draft. Here is exactly what each source can and cannot tell you.
| Source | What we used it for | Evidence type | Limitation |
|---|---|---|---|
| Acquisition listings (650+ live) | Exit multiples, margins, asking prices, niches | Seller-reported financials | Plugin product subset is n=11. Figures are asking prices and seller claims, not verified closed sales. Treat as directional. |
| Revenue-verified products (8,600+) | Revenue distribution, ARPU, median MRR | Connected payment data | WordPress subset is n=40, self-selected toward founders who publish revenue. Skews toward newer indie products. |
| Stripe payment index (30,000+ companies) | Services versus product split, micro SaaS share | Public directory plus AI classification | WordPress subset is n=127, identified by self-description. Companies that do not mention WordPress in their profile are invisible to this filter. |
| Review pain points (Capterra) | Severity ranking, customer complaint quotes | Analysed software reviews | Captures WordPress as an integration target more than as a plugin market. Review coverage by category is uneven. |
| Software insights (G2) | Complaint themes across CMS tool products | Analysed software reviews | 40 CMS Tools records. Thematic rather than quantitative; not a market share measure. |
| Freelance demand analysis | Paid demand signals for WordPress work | Job postings | Budget fields are unpopulated in this corpus, so we report frequency only and never dollar figures. |
| Idea validation swipes (78,000+ cards) | Human interest in WordPress problem statements | User behaviour | Only two WordPress cards cleared 20 impressions. Sample too thin to generalise; reported as supporting colour only. |
| Funded company index (17,000+) | Venture interest in the WordPress space | Funding announcements | Only 5 WordPress matches. Confirms absence of capital, cannot quantify it. |
| Product launch records (5,000+) | New WordPress product launches | Launch platform data | 16 WordPress matches. Small and biased toward launch-savvy founders. |
| Live community threads (r/Wordpress) | Pricing expectations, business model post-mortems | Self-reported developer accounts | Unverified individual claims. We quote them as sentiment and lived experience, never as measurement. Usernames stripped. |
| App store reviews (99,000+ negative) | Attempted mobile signal | App store reviews | Only 4 WordPress mentions. Effectively no coverage. We report the gap rather than hiding it. |
The honest caveat on the headline number. The 2.80x median profit multiple rests on eleven listings. It is consistent with the wider 38-listing WordPress average of 3.26x and with the marketplace-dependent outliers at 1.1x to 1.2x, so we are confident in the direction and the rough magnitude. We are not claiming precision. If you are valuing a specific business, treat this as the prior you argue against, not the answer.
What this data cannot tell you. It cannot tell you whether your specific plugin idea will work. Complaint volume is a demand signal, not a business plan. Plenty of well-evidenced problems have no viable price point, and plenty of profitable plugins solve something nobody ever wrote a review about. Use the data to eliminate bad ideas quickly, not to guarantee a good one.
External sources referenced: W3Techs for WordPress market share, the official WordPress plugin directory guidelines and WordPress.org license page, the GNU project’s GPL-compatible license list, and published platform fee schedules from Stripe, Envato, Freemius and Easy Digital Downloads.
Search 1M+ documented complaints, revenue-verified products and live acquisition listings to find a WordPress problem people already pay to solve.
Start with real complaints →The standard route is freemium: publish a genuinely functional free version in the WordPress.org plugin directory for discovery, then sell a paid version from your own site using a licensing system that gates updates and support rather than the code itself. You need five pieces to run it yourself: a checkout, license keys, an update server, a customer area and a payment gateway. Marketplaces bundle all five and charge a permanent cut for the convenience.
Less than the guides imply and more than the cynics claim. Across 8,600+ revenue-verified products we track, the 40 WordPress-related ones have a median of about $14 per month, 45.0% earn nothing at all, and 10.0% clear $1,000 per month. That last figure is almost exactly the rate for the whole corpus at 10.3%, so WordPress is not a worse place to reach revenue. It is a worse place to reach a premium exit.
Low. Among WordPress plugin and theme product listings on the open acquisition market, the median profit multiple is 2.80x and the average is 2.95x. Across all 650+ live listings we track, the average profit multiple is 7.35x. Buyers are not discounting WordPress revenue, they are discounting its durability, because a one-time license base with weak renewals has almost no forward earnings. Compare against profit multiples by SaaS category.
Start on your own site and treat any marketplace as a secondary channel. Marketplace commissions run as high as roughly half of a non-exclusive sale, you cannot install tracking pixels, and you never own the customer relationship. In our acquisition data, the listings most dependent on marketplace distribution carry the worst multiples, including one Envato-based theme and page builder business priced at 1.2x profit.
Yes. The GPL restricts how you distribute code, not whether you charge for it. What it does not let you do is withhold source, obfuscate it, or forbid a buyer from redistributing what they received. That is why the mature framing in the ecosystem is that a customer buys updates, support and trust rather than the code. WordPress.org treats plugins and themes as derivative works of WordPress and requires a GPL-compatible license for anything in the directory.
The repeatedly stated comfort band from working developers and agencies is roughly $79 to $100 per year for a single-site license on a plugin that genuinely saves them work, with agency and unlimited-site tiers priced several multiples higher. Tier on site count rather than features wherever you can, because the buyers with budget are the ones managing many sites. See what micro SaaS actually charges for the wider distribution.
It is the default for a reason: the directory is the only free distribution channel with real trust attached. But free-to-paid conversion is low single digits for most plugins, the directory brings almost no organic traffic until you pass a meaningful install threshold, and a free listing creates a second public venue where paying customers can demand free support. Budget for that cost before you publish.
In our live acquisition data the WordPress products that reach an exit cluster in memberships and affiliates, lead generation and email, directory and job listings, e-commerce compliance and shipping, staging and site operations, and content automation. The common thread is that the plugin touches money or legal obligation for a business, not aesthetics for a hobbyist. Related reading: boring industries begging for micro SaaS.
It is compressing the low end. Developers in the ecosystem now routinely say they can rebuild a simple plugin in an afternoon, and our own analysis of defensibility in the AI era points the same way. What survives is work AI cannot cheaply replicate: ongoing compatibility maintenance, regulatory correctness, integrations with systems that have real access barriers, and the trust of installing signed code on a production site. See what counts as a moat in the AI era.
Extremely, on paper. The WordPress plugin and theme product listings we analysed carry a median profit margin of 88.9% and an average of 85.4%. That is close to pure operating leverage. The catch is that the margin is high because almost nothing is reinvested, which is exactly the profile buyers assign a low multiple to.
In services. Of the WordPress-related companies taking payments on Stripe in our index, 48.8% are agency and service businesses against 27.6% classified as B2B SaaS, and only 10.2% are flagged as micro SaaS. The plugin is often the marketing asset; the retainer is the business.
If you want automatic updates and any enforcement of site limits, yes. Licensing cannot stop a determined user from removing the check, and nulled copies of every popular paid plugin exist. What it does reliably is deliver updates to paying customers, support renewal billing, and make the purchase feel like a supported product rather than a zip file.
Launch with renewals from day one. The consistent pattern in developer discussions is that customers accept subscriptions they were sold on originally and revolt against a switch imposed later. Lifetime deals convert well and then quietly become an unfunded support obligation, which is the single most cited cause of plugin businesses stalling out. See SaaS pricing strategies.
Work backwards from documented complaints rather than forwards from a feature you fancy. Search a corpus of real reviews and forum posts for the phrases that describe unmet WordPress needs, check whether an existing product already covers it, then confirm someone is paying for the problem in adjacent evidence such as freelance job demand or acquisition listings in the same niche. Our validation guide walks through it.
Selling to people who build their own sites. Those buyers have the smallest budgets and the loudest objections to paying. Agencies and professional developers buy licenses routinely, renew them as a cost of doing business, and open far fewer support tickets per dollar spent.
No. The directory guidelines prohibit trialware, meaning functionality that is present in the code but locked behind payment, and they prohibit serving updates or installing premium versions from servers other than WordPress.org. The compliant pattern is a fully functional free plugin in the directory and a separate paid add-on or pro plugin distributed from your own update server.
Long enough that you should plan the renewal model before the first release. The acquisition listings we see with meaningful revenue routinely describe eight to ten years of operation, and the developers posting post-mortems describe revenue that compounded for years and then decayed over a similar span once the underlying market shifted. See how long it takes to grow a SaaS.
A WordPress plugin is still one of the best first software businesses available to a single developer. The distribution is free, the margins are close to 90%, and the rate at which WordPress products reach $1,000 per month matches every other software category we track.
What it is not is a lottery ticket. The market prices these businesses at under 3x profit because most of them are built on one-time licenses, rented distribution and an unfunded support obligation. Every one of those is a choice you make in the first month and cannot easily unmake in year five.
So make the boring choices early. Renewals from launch. Your own site as primary. Agencies and developers as the customer. A niche that touches money or compliance rather than appearance. And, before any of that, a problem that somebody has already written a complaint about. Start with the complaint data, sanity-check it against what has actually sold, and build the plugin third.
If you have not committed to a platform yet, the hub for this whole question is Shopify app vs WordPress plugin, seven ecosystems measured identically. If you are weighing WordPress against the alternative, the direct comparison is how to sell a Shopify app, where the same analysis returns a 3.90x median multiple on near-identical margins, and how to monetize a Chrome extension, where only 6.3% of products ever clear $1,000 a month. If you are still choosing what to build, the adjacent research is micro SaaS ideas backed by complaints, low competition SaaS ideas and the most requested software features. If you have the idea and want to ship, how small your MVP should be and launching a micro SaaS in a weekend are the practical next reads, and the boilerplate is the shortcut. On the business side, how fast SaaS startups actually grow and why customers churn set expectations, and finding problems worth solving walks through the search itself.
BigIdeasDB Research. (2026). How to Sell a WordPress Plugin in 2026: Real Exit Data. BigIdeasDB. Retrieved from https://bigideasdb.com/how-to-sell-a-wordpress-plugin