How much to charge for a WordPress plugin
How much to charge for a WordPress plugin comes down to one question: what problem does it solve for the business, and what is that problem costing them today? Nobody buys a plugin for the PHP. They buy it so orders stop getting copied by hand into their stock system, so members see the right content without someone checking every account, or so a booking form stops sending leads into a dead inbox. Price the build on a share of that value, add lines for the plugins and systems it has to work with and for the client's site setup, and quote a monthly plan for upkeep. Do not price it on lines of code or hours.
WordPress plugins are good work to sell with Claude Code because WordPress already gives you the login, the database, the admin screens and the theme. Your plugin only adds the missing behaviour. That is also the trap. The first version can be small and quick, so builders price it like a favour, and then a WordPress update, a PHP upgrade on the host or an update to another plugin breaks it, and nobody is paid to fix it.
Why the code is the wrong yardstick
A plugin that adds one shortcode to a hobby blog and a plugin that sends every order from a busy shop into the warehouse system can be close to the same amount of code. Charging the same for both makes no sense. The shop is paying for what the plugin does to their business, not for how many files are in the folder.
Hours are worse. Claude Code makes the first build fast, so if your price follows your hours, every bit of speed you gain becomes a pay cut. I covered this in why I stopped charging hourly for AI builds. The real costs of a plugin sit around the code: fitting it into a site you did not build, testing it next to everything else installed there, and keeping it working as WordPress moves.
The CCC Plugin Quote
Five parts of a WordPress plugin quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Base build | The value of the problem the plugin solves | What happens today without it, how often, and what does it cost you? |
| Integrations | Each plugin or outside system it has to work with | Which plugins does it need to talk to, and which outside tools? |
| Site setup | Fitting it into the client's theme, hosting and existing plugins | Who built the site, where is it hosted, and is there a staging copy? |
| Testing and launch | Testing on a copy of the site and going live safely | When is the quietest time to switch it on? |
| Keep plan | Monthly checks, fixes and compatibility updates | What does it cost you if this stops working for a day? |
Base build. Work out with the client what the problem costs today. That is the hours someone spends doing the task by hand multiplied by what their time costs, plus the sales lost or the mistakes made when it goes wrong. Price the build at a fraction of one year of that value, so the client can see it pay for itself early.
Integrations. Every plugin or system yours has to work with is its own line. A plugin that only adds something to a page is one job. One that hooks into the shop plugin, the membership plugin and an outside CRM is three more lines, each with its own updates and its own way of breaking. If it calls a paid API, the key lives in the server settings, never in the page, with a spending limit, and that setup is part of the quote. How to build a WordPress plugin with Claude Code shows what a single integration involves.
Site setup. You are building inside someone else's house. An old theme, a crowded plugin list or a host that limits what you can change all add work you will not see until you look. Ask for access to a copy of the site before you send the final number, and price this line on what you find.
Private plugin or WordPress.org listing
Settle where the plugin will live before you quote, because it changes the job. Most client work is a private plugin: it is installed on their site only, and nobody else ever sees it. That is the simple case.
- Listing on WordPress.org: the plugin directory's guidelines require GPL-compatible licensing for everything hosted there, and they do not allow trialware, meaning locked or expiring features inside the plugin. Paid features have to live in a separate service or add-on. If the client wants a public listing, quote that as its own line, along with answering support questions from the public.
- Ownership: the code and any listing should be the client's. Hand over the code in their repository and any accounts in their name. How to hand off a Claude Code project covers the checklist.
- Selling it to others: if the client wants to sell the plugin to other businesses, it is no longer a plugin job. It is a product, and how much to charge for an MVP is the right post.
Always quote the Keep plan
Plugins break for reasons that have nothing to do with your code. WordPress releases updates. Hosts move sites to newer versions of PHP. The shop or membership plugin yours depends on changes how it works. None of that is your fault, and all of it can take the client's site or checkout down.
Quote a monthly plan in the original proposal. Say what it covers: checking the plugin after WordPress and major plugin updates, fixing breakages from those updates, keeping it working on newer PHP versions, and small tweaks. Say what it does not cover: new integrations and new features, which are quoted separately. How to price a maintenance retainer covers the structure. A plugin that sits in the middle of a client's orders or bookings is one of the easiest retainers to justify, because they feel it the first day it stops working.
How to present the WordPress plugin quote
- Lead with the problem in their words. One line on what it costs them today, then the price.
- Itemize it. Base build, each integration, site setup, testing and launch, then the Keep plan. Itemized quotes get trimmed, not rejected.
- Gate payments on proof. A deposit to start, a payment when it works on a copy of their site, and the final payment once it is live. How to structure milestone payments for an AI project covers the schedule.
- Name what breaks it. Say plainly that WordPress, PHP and plugin updates will break it at some point, and that the Keep plan is how it gets fixed fast.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a custom WordPress plugin?
Price it on the problem it solves: the hours it saves, the sales it unlocks or the mistakes it stops. Charge a fraction of one year of that value for the build, add a line for each plugin or system it works with, add site setup and testing, and quote a monthly plan for upkeep.
Should I charge hourly for a WordPress plugin?
No. Claude Code makes the first build fast, so hourly pricing turns every gain in speed into a pay cut, and it ignores the site setup, testing and upkeep that come with the code. Price on the value of the problem instead.
Should I charge a monthly fee for a WordPress plugin?
Yes. WordPress updates, hosts move to newer PHP versions, and the plugins yours depends on change. A monthly plan covers checks, fixes and compatibility updates, with new integrations and features quoted separately.
Can a client's plugin be listed on WordPress.org?
Yes, if it follows the directory's guidelines. Everything hosted there has to be GPL-compatible, and locked or expiring trial features are not allowed in the plugin itself. Most client plugins stay private and are installed on the client's site only.
Who owns a custom WordPress plugin I build for a client?
Agree it in writing before you start. The usual setup is that the client owns the code once they have paid, it lives in their repository, and any accounts or listings are in their name.
Last reviewed by Duncan Rogoff on October 9, 2026
