A Divi licence is a bet on how long the agency keeps building sites

The renewal for a Divi licence is a small invoice that asks a large question: pay for another year, or pay once and stop renewing. The arithmetic is public. Elegant Themes' pricing page, as published on 2026-10-19, lists Divi at $89 billed yearly and Divi Lifetime at $249 as a one-time payment, and both cover unlimited websites. Two yearly payments come to $178; the third takes the total to $267, past the lifetime price. The lifetime option pays for itself somewhere in year three.

The price is the easy part. An agency buys a licence to build and hand over client sites, and once the work is billed the licence is a rounding error per site. The cost that is not a rounding error is the second interface every client has to learn, and the support that follows when a client edits something they did not mean to edit.

This piece is arithmetic on published prices, not a review. Nobody at WPSifero has installed Divi or built a site in it, and nothing here claims otherwise. Every product statement is taken from Elegant Themes' own pages and named where it is used. The prices are the ones the pricing page carried on 2026-10-19; they change, so check the page before a figure goes into a budget.

Disclosure: WPSifero earns a commission on sales made through the Elegant Themes link in this article. The price you pay is the same, and the commission has not changed the argument: the case for paying yearly is made below as plainly as the case for paying once. Nothing here is a review: nobody at WPSifero has built a site in Divi, and every statement about the product is taken from Elegant Themes' own published pages, cited where it is used.

The method is dull: divide the published prices by the number of sites the agency expects to run, then set the answer against how long it expects to keep building WordPress sites and how much of a client's learning curve it will support.

The two plans differ by a date, not a discount

Both plans buy the same thing: the Divi theme and builder, with unlimited websites. Yearly is $89 every year; lifetime is $249 once. The comparison table on Elegant Themes' pricing page sets one year at $89 against ten years at $249, which makes the gap visible in the vendor's own numbers: ten yearly payments would come to $890.

                 Yearly   Lifetime
After year 1      $89      $249
After year 2      $178     $249
After year 3      $267     $249

The break-even is a date, not a discount threshold. An agency that stops building WordPress sites in year two was right to pay yearly; one still building in year four was right to pay once. The prices are fixed and published, while the horizon is a guess about the business. The useful question is not which plan is cheaper but how long the agency expects to keep doing this work.

The uncomfortable consequence is that a lifetime licence is a commitment to a stack. An agency that might move to another builder, sell the maintenance book, or stop taking WordPress work should not buy one. The saving is only collected by an agency still using the licence years later, which makes an uncertain year the wrong time to buy it.

Divide by sites and the licence stops mattering

Unlimited websites is the clause that changes the arithmetic. Because both plans cover any number of sites, adding a site does not add a licence line. At twenty sites the yearly plan works out at $4.45 per site per year and lifetime at $12.45 once; at five sites, $17.80 and $49.80. The division settles how much attention the licence deserves.

Not much is the honest answer. A few dollars per site per year is not a line an agency should optimise for its own sake. The optimisation with money in it sits in the handover, in the first month of support, and in who edits the site after the invoice is paid.

The per-site figure also treats every site as equal. A site the client edits twice a year costs less to maintain than one they redesign every quarter, and the licence does not distinguish between them. A plan that looks cheap per site can still be expensive to operate if it puts an unfamiliar interface between the client and the page.

The second interface is the cost that lands on support

A client who edits their own site already has to learn the WordPress admin. Divi adds a builder with its own vocabulary of sections, rows and modules, so the client learns two systems. The trade is deliberate: layout ends up in the client's hands, and the price is a system the agency has to teach. That interface is a cost, paid in support hours rather than licence fees.

Elegant Themes' documentation supplies a good example of the concept a client has to absorb. A global library item is defined there as a Module, Row or Section that appears the same on whatever pages it is added to, and editing it changes every page that uses it. A client who changes one expecting to change a single page has changed the whole site, and the agency gets the call. Explaining that before the first edit is cheaper than repairing it afterwards.

The same documentation explains why the handover needs a storage line. Elegant Themes' page on the Divi 5 Migrator states that Divi 4 stored a page as shortcodes in the post content, for example a text module wrapped in [et_pb_text ...], and that Divi 5 uses a block-based framework which does not use shortcodes. A site can be in either storage world, and the next developer will ask which.

One caveat from that page belongs in the handover too. Elegant Themes states that modules not yet supported continue to run wrapped in the Divi 4 framework, and that a page containing one loads the Divi 4 framework for that page, which they say can affect performance. That is the vendor's sentence, not this article's measurement.

Yearly is right when the agency is still deciding

At one site, yearly is $89 and lifetime is $249, and lifetime only wins if the site is still on Divi in year three. An agency that is not sure it will still be maintaining that site should keep the commitment to one year.

A pilot is a first site built to see whether the builder fits the agency's process. A pilot tests the process, not the product, and paying yearly keeps the test reversible. If the builder is wrong for the way the agency works, the lesson costs $89 rather than $249.

If the site may move to another agency, or the maintenance contract may not renew, yearly matches the length of the relationship. Lifetime is a bet that the site stays in the portfolio for years, and a client shopping for a cheaper retainer is not that bet.

The less comfortable case is an agency without a repeatable process. It should not buy lifetime, because it is buying a commitment the process has not earned. If every project starts with a fresh argument about which builder to use, the plan is not the expensive part; the stack decision behind it is.

Lifetime is right when the process repeats

Lifetime becomes the easy call when the agency can point at the third site it will build on the same stack. That is the signal, not the headcount. A two-person studio that builds every site with the same theme, builder and handover document can justify $249 once. A fifteen-person agency that lets each lead choose a builder cannot, because the licence would be bought for a process that does not exist yet.

The arithmetic is identical; the horizon is not. Lifetime covers unlimited websites with one payment, so its value rises with every year of use and every site added. An agency with a maintenance retainer and a build checklist is buying for a pipeline it can see. One without is buying an option on a pipeline it hopes to have.

A test costs nothing. Write down the next three sites, with client names if they exist, and the stack each will use. If all three name the same stack, lifetime is the purchase. If the list contains a question mark, yearly is the honest plan.

The pro tier is a bundle question, not an upgrade

Elegant Themes' pricing page, as published on 2026-10-19, lists Divi Pro at $277 billed yearly, described as Divi plus the pro services, and Divi Lifetime plus Pro at $297 as the first payment followed by $212 per year for the pro services. The gap between yearly and pro is $188 a year; the gap between lifetime and lifetime plus pro is $48 up front and then $212 a year.

Over three years, Divi Pro costs 3 x $277, or $831. Lifetime plus Pro costs $297 plus two payments of $212, or $721. The bundle costs $20 more at the first payment and $65 less at every renewal, so it is cheaper from the second annual payment. At that point the question becomes whether the pro services are wanted at all.

Divi Pro, three years:        3 x $277 = $831
Lifetime + Pro, three years:  $297 + 2 x $212 = $721

That is why "is pro worth it?" is the wrong question. A bundle is worth its price only to a buyer who would otherwise purchase the components separately. The exercise is to read what the pro tier includes and put each part next to an invoice the agency already pays. If the description is vague, that is the question to put to Elegant Themes before paying. If the list replaces nothing, the base plan is right. If it replaces two or three line items, the comparison is between two real costs.

Lifetime plus pro follows the same logic: cheapest from the second payment, but cheap is not the same as useful. A solo developer with no team and no client-facing service may find the base licence covers the work.

The rule is to price the horizon, not the licence

Yearly and lifetime differ by $160; yearly and pro by $188 a year, neither enough to decide anything on its own. What decides it is the horizon the agency can defend and the number of clients it will teach.

So the rule is this: buy yearly until the agency can name the third site it will build on the same stack, and buy lifetime once it can. Buy the base plan until the pro services replace invoices the agency already pays, and buy pro once that list is concrete. An agency that cannot name the third site should treat the renewal date as the next decision point, not as a bill to be minimised.

1. Name the next three sites the agency expects to build, and the stack for each.
2. Read the renewal line and the plan name on the current invoice.
3. List the invoices the pro services would replace before paying for pro.

The limitation is worth stating plainly. This arithmetic treats the licence as the only variable and the client's editing habits as fixed. It cannot say whether a given client will prefer the builder to the block editor, or whether the agency will still be building WordPress sites in five years. Those are questions about the client and the business, and no pricing page answers them.

What the pricing page answers is the arithmetic, and the arithmetic is the least interesting part. The money goes to the second interface, the global item edited by accident, the migration note missing from the handover, and the support hour that follows. Price those, and the $160 difference stops being the argument.

The decision rule in one line: match the licence to the horizon the agency can defend, and match the pro tier to the invoices it replaces. Everything else is a discount in search of a reason.