--- title: "WordPress Plugin Licensing for Agencies and Freelancers, Explained" date: 2026-07-08 author: "Imtiaz Rayhan" featured_image: "https://wpblocksuite.com/wp-content/uploads/2026/08/featured-wordpress-plugin-licensing-for-agencies.png" categories: - name: "WordPress Plugins" url: "/blog/category/wordpress-plugins.md" --- # WordPress Plugin Licensing for Agencies and Freelancers, Explained Per-site licences multiply. Unlimited licences divide. That’s the entire economics of plugin licensing for client work — everything else is contract detail. But the contract detail is where agencies get hurt. Who owns the licence key after handoff? Who renews it next year? What happens to the client’s site when the relationship ends? Skip those questions at kickoff and they resurface later. As awkward emails with a former client CC’d. This guide covers both halves: the multiplication math. And the ownership questions worth settling in writing. As always on this blog, the only prices quoted are our own . Every figure sits on a public pricing page. ## The four licence shapes you’ll meet Nearly every WordPress plugin licence is one of four shapes. Learn the shapes and pricing pages get much faster to read. Shape How the cost behaves Watch out for Per-site Multiplies with every project Quiet totals: ten sites means ten licences Site packs (3, 10, 25) Steps up in tiers Outgrowing a tier mid-year; counting staging sites Unlimited sites Divides across every project Ownership at handoff still needs deciding Lifetime vs annual A separate axis — any shape can be either Annual needs a renewal owner, forever *Table rendered with Tableberg, running in this post — dogfooding, as usual.* Note that lifetime-versus-annual is not a shape — it’s an axis across all of them. A per-site lifetime licence still multiplies. An unlimited annual licence still divides, but adds a renewal to own every year. Read both dimensions before comparing anything. ## The multiplication math, with real numbers Our suite is the worked example, because we can verify it. $299 One-time. Unlimited sites, no separate agency tier. The standard licence is the agency tier. $299 1 site — the licence, once $59.80 per site across 5 sites $29.90 per site across 10 sites $11.96 per site across 25 sites One $299 unlimited-site licence, divided by site count. Price as of July 2026; the division is just arithmetic.Now run the same table for any per-site licence you’re comparing. A $49-per-site plugin across ten client sites is $490 — per year, if it’s annual. The licence that looked cheaper on one site crosses over fast. Neither answer is universally right; the crossover point is. Find yours before the proposal goes out, not after. The crossover formula is one division. Unlimited price ÷ per-site price = the site count where unlimited wins. Our $299 against that $49 example crosses at seven sites . Six sites favours per-site, seven favours unlimited. If the per-site licence is annual and the unlimited is lifetime. The crossover drops every year you keep building. Do this arithmetic once per tool; it settles most licensing debates in a minute. One honest caveat on our own math. It assumes you’d use two or more of the suite’s four categories across your sites. If your client work only ever needs one. A standalone licence is cheaper — the [full pair-by-pair breakdown](https://wpblocksuite.com/blog/how-much-do-premium-gutenberg-blocks-cost/) covers exactly when. ## Price the whole stack, not one plugin Agencies don’t license one plugin — they license a standard stack. Forms, SEO, backups, security, blocks, maybe a builder or theme framework. Five to ten paid tools, each with its own licence shape. Each multiplying or dividing on its own schedule. So run the shape audit across the whole stack, once. List every paid tool. Mark each one’s shape: per-site, pack, or unlimited. Mark each one’s axis: lifetime or annual. The per-site annuals are your compounding costs — every new client makes them permanently more expensive. Those are the lines worth renegotiating, replacing, or upgrading to unlimited tiers first. The exercise takes an evening and usually pays for itself on the next proposal. Not because everything should be unlimited — it shouldn’t . But because you’ll finally know which lines scale against you. ## Who owns the licence? The handoff question Here’s the question that outlives every project. When you hand a site to the client, whose licence is it running on? **If the agency holds the licence**, the client’s site depends on your account for updates. That’s fine during the retainer. When the relationship ends, the dependency doesn’t . The client needs their own licence, or their premium plugins stop updating. An awkward conversation, at the worst time, unless it was agreed at kickoff. **If the client buys their own licence**, handoff is clean and the exit costs nothing. The trade is price: no agency-side dividing, every client pays retail. Some agencies split the difference — agency licence during the build, client licence at launch. **A third option exists at some vendors:** transferring the licence itself. Agency account to client account. Where it’s supported, it combines the cheap build with the clean exit. Whether it’s supported is exactly the kind of thing to confirm before standardising . See the vendor questions below. There’s no universally right answer, but there is a universally wrong one: not deciding. Ours is a short email away at . And pre-sales questions like this are exactly what the inbox is for. ## Five questions for any vendor, before you standardise Standardising on a plugin puts it on every site you build . Which makes the vendor a long-term supplier, not a checkout. Suppliers get vetted. One email covers it: - Can a licence, or a single site under it, be transferred to a client? - Do staging and development sites count against any site limit? - What’s the renewal price — and does it match the first-year price? - What exactly stops working if an annual licence lapses? - Is there an agency programme, or is the public tier the whole offer? Keep the reply with your licence records. Written answers from pre-sales outlive support-chat folklore. And they’re what you’ll cite if policy ever drifts. The same test from [our vetting guide](https://wpblocksuite.com/blog/are-wordpress-lifetime-deals-safe/) applies here too. How they answer is data, not just what they answer. ## Lifetime vs annual, through an agency lens For a single site owner, lifetime-versus-annual is a cost curve — [we’ve charted it](https://wpblocksuite.com/lifetime-deal-vs-subscription/). For an agency, it’s also an operations question. Annual licences create a recurring liability someone must own. Every year, for every client, forever: budget it, invoice it through, or eat it. Agencies with good systems handle this fine. Agencies without them discover expired keys during an unrelated support call. Lifetime licences trade that liability for vendor risk. One payment, no renewal calendar — but the licence is only as durable. As the company behind it. Vet accordingly; [our checklist](https://wpblocksuite.com/blog/are-wordpress-lifetime-deals-safe/) exists for precisely this. The first project absorbs the cost, and every project after runs on margin. A defensible default: lifetime for the tools on every site you build — your standard stack. Annual for client-specific tools you might not need next year. The stack earns the commitment; the one-offs don’t. ## Put it in the proposal The handoff question belongs in your client agreement, not in your memory. Three lines cover it. State which premium plugins the build uses, and whose licences they run on. State what happens at handoff — client purchases their own. Or continues under yours during any care plan. State who owns renewals, with the yearly cost named, if anything is annual. We’re plugin makers, not your lawyers . Treat this as a checklist for the conversation, not contract language. The point is that every later dispute about licences traces back to. One missing paragraph at kickoff. Write the paragraph. Renewals deserve the most explicit line, because they recur after everyone’s forgotten the kickoff. Name the amount, the month it lands, and whose card it hits. If the client owns renewals, add the vendor’s reminder emails to their inbox, not yours. Future-you will send exactly one fewer awkward invoice per year. ## Care plans: where licensing meets recurring revenue If you run maintenance retainers, licences are already part of the product — name them. “Premium plugin licences included” is a real line item clients understand. And it justifies part of the monthly fee. Your unlimited licences cost you nothing extra per client. The value to each client is retail. That spread is legitimate margin. Two honest cautions. First, included licences deepen the handoff question . A client leaving the care plan loses the licences with it. So say that upfront, in the agreement. Second, the margin only exists while the vendor does. A care plan built on a dead plugin is a liability with a monthly fee. Vet what you standardise on; [watch for abandonment](https://wpblocksuite.com/blog/what-happens-when-a-wordpress-plugin-is-abandoned/) yearly. ## Keep a licence inventory Past a few clients, memory stops scaling. One spreadsheet fixes it: plugin, licence tier, key location. Lifetime or renewal date, sites using it, and who owns it — agency or client. Six columns, ten minutes to set up. Review it yearly, and also at two triggers: every new client. And any tier you’re approaching. It catches renewals before they lapse. Spots per-site licences that crossed the unlimited threshold. And doubles as the abandonment pulse-check from [our plugin-abandonment guide](https://wpblocksuite.com/blog/what-happens-when-a-wordpress-plugin-is-abandoned/). Boring, effective, ten minutes a year. ## The freelancer edition Everything above scales down, with one shift: at two to five sites. The crossover math is close, so run it honestly rather than assuming. The ownership question actually gets more important, not less. A solo freelancer’s clients are more exposed to one person’s holidays. Illness or career change than any agency’s. Clean licence ownership — client buys, you build — is the kindest structure you can leave behind. Bill it through transparently; nobody resents a line item they can verify. At the vendor’s own pricing page. ## When unlimited isn’t the answer The concede-the-weak-case section, as usual. A freelancer with one ongoing client doesn’t divide anything . Unlimited sites is paying for headroom you may never use. Buy for the sites you actually have; upgrade thinking when the third client shows up. And if your projects never repeat a stack. Per-project licensing may genuinely fit better than standardising. Unlimited licences reward repetition. No repetition, no reward. The same honesty applies to our own suite. It earns its place in a standard stack that reuses two. Or more of its categories across builds. Outside that shape, buy smaller — the standalone plugins exist for a reason. And so do their free versions. ## Agency licensing questions, answered Can I use WP Block Suite on client sites? Yes. The licence covers unlimited sites, client sites included. There’s no separate agency tier — $299 one-time is the whole price list. What happens to a client’s site when we part ways? The plugins keep working; updates depend on whose licence the site runs. Decide ownership at kickoff and write it into the agreement. Vendor transfer policies differ — ask each one in writing. Ours is answered at hey@dotcamp.com. Is one licence across many client sites even allowed? It depends entirely on the licence terms. Unlimited-site licences allow it explicitly — that’s the product. Per-site licences don’t; reusing one key across clients violates the terms you agreed to. Read the shape before you scale it. The obligations are set out in [licence compliance for agencies](https://wpblocksuite.com/blog/wordpress-plugin-licence-compliance-agencies/). Should agencies buy lifetime or annual licences? Lifetime for your standard stack — the tools on every build — after vetting the vendor. Annual for one-off, client-specific tools. The stack earns the commitment. Can I include plugin licences in my maintenance plans? Usually yes with unlimited licences — that’s a normal agency model. Name it in the plan, and state what happens to the licences. If the client leaves. The licence terms, not the plugin’s [GPL](https://wpblocksuite.com/blog/gpl-paid-wordpress-plugins-explained/) code, govern keys. Updates and support — read them per vendor. Do staging and development sites count against site limits? Vendor-specific — many exempt staging, some don’t, and unlimited licences make the question moot. Check before a site-pack tier surprises you. It’s a fair pre-sales question anywhere. ## Confirm the handoff record - Purchasing entity. - Account owner. - Client rights. - Site assignments. - Update responsibility. - Support responsibility. - Service-end changes. - Transfer process. - Recovery contacts. - Final acceptance. Match the record to current terms and contracts. Do not promise unsupported licence transfers. ## Final agency licence questions - Can the agency prove every active site’s licence eligibility? - Can clients understand ownership, updates, support, and service-end effects? - Can authorised staff recover accounts after departures or role changes? ## The verdict Verdict **The math:** per-site licences multiply, unlimited licences divide — find the crossover for your site count. **The contract:** decide licence ownership at kickoff, in writing, renewals included. **The ops:** a six-column inventory, reviewed yearly, prevents every expensive surprise in this post. If your standard stack needs tables, galleries, sliders or content blocks. One suite licence covers every client site you’ll ever build. $299 one-time. Unlimited sites, 30-day money-back guarantee. [See the pricing](https://wpblocksuite.com/#pricing) — and yes, the free versions are how to pilot. It on the next build.