THE SHORT ANSWER
Choose a white label Divi partner by checking real Divi 5 work (presets, design variables, native modules, migrations on staging), keeping the Divi license in your own account, giving them a Divi Teams seat and a named WordPress user instead of your password, signing an NDA, and testing them on one paid pilot page before any client project.
Hiring a white label partner for Divi work is not the same as hiring any WordPress developer. Divi 5 changed how good sites are built, with design variables, presets, flexbox and grid layouts, and a migrator that can leave pages stuck on the old framework. A partner who has not kept up will hand you sites your team has to rebuild.
This guide is for agencies that sell Divi sites and want more hands without hiring. It covers the Divi 5 skills to check, how to set up the license and access safely, the red flags that only show up in Divi work, pricing models, NDA and brand rules, and a paid pilot and weighted scorecard you can use to compare partners side by side.
01What a white label Divi partner does
A white label Divi partner builds, migrates and fixes Divi sites for your agency, under your brand. Your client sees your name on the proposal, the invoice, the staging link and the handoff video. The partner never appears.
That sounds like any outsourced developer, and for general WordPress work the vetting questions are much the same (we cover those in How to vet a white label WordPress partner: 12 questions to ask). Divi adds its own layer. A partner can be a good WordPress developer and still leave you a Divi site full of inline styles, legacy modules and third-party plugins your team cannot maintain. This guide covers the Divi-specific part: the skills, the access setup, the red flags and how to test a partner before a real client project.
| Work type | What the partner does | What you keep |
|---|---|---|
| New builds | Turns your Figma file or sitemap into a Divi site with presets, variables and Theme Builder templates | The client relationship, the design sign-off, the price |
| Divi 4 to Divi 5 migration | Runs the migrator on staging, rebuilds modules that stay in backward compatibility mode, checks templates | The upgrade conversation with the client |
| Fixes and changes | Layout bugs, mobile issues, speed cleanup, Theme Builder problems | The ticket intake and the client update |
| Care plans | Updates, backups, security scans and reports with your logo | The monthly retainer and the margin |
The point of a partner is capacity, not just cheaper hours. A good one lets you say yes to the next Divi project without hiring, and hands back work your own team can pick up later without rebuilding it.
Want to test a white label partner first?
Start with one page for $199. Built in 3 working days, under your agency brand.
02Divi 5 skills to check before you hire
Divi 5 launched on February 26, 2026, according to Elegant Themes' migration guide. Divi 4 still gets security patches and critical bug fixes, but no new features, and Elegant Themes says it will be fully supported for at least 12 months after the Divi 5 release. In practice, any partner you hire now will be building new sites in Divi 5 and moving old ones off Divi 4. Check that they can do both well.
| Divi 5 skill | Why it matters to you | How to check it |
|---|---|---|
| Design variables (colors, fonts, sizes, images, strings, URLs) | One change in the variable updates the whole site. Without them, a brand color change means editing every module. | Ask to see the variable list on a recent build. Expect named colors and a type scale, not 40 hex codes. |
| Design presets | Presets keep buttons, headings and cards consistent and make pages lighter to edit. | Open a page and inspect three buttons. They should share a preset, not carry their own inline styling. |
| Flexbox and CSS Grid layouts | Cleaner responsive behavior with fewer custom breakpoints and less custom CSS. | Ask how they built a card grid that reflows on tablet. "Custom CSS for each breakpoint" is a weak answer. |
| Loop Builder | Lets you build post, term and user listings visually, including ACF repeater content, without a plugin. | Ask for a blog or case study archive they built with it. |
| Interactions | No-code animations and toggles replace jQuery snippets and extra plugins. | Ask what they would use for a tabbed pricing toggle. A plugin should not be the first answer. |
| Theme Builder templates | Headers, footers, post templates and archive layouts are where most client sites break after updates. | Ask how they structure global headers and footers across templates. |
| Divi 5 Migrator and backward compatibility mode | If a page has even one legacy module, Divi loads the Divi 4 framework for the whole page. | Ask how they find pages still in compatibility mode and what they do about third-party modules. |
The last row is the one that separates people who have done real migrations from people who clicked the button once. Elegant Themes' guide describes the menu path as Divi, Dashboard, Enable Divi 5 Updates, then Divi, Divi 5 Migrator, with a Restore Divi 4 Content button for rollback, and recommends running it on staging first. A good partner will tell you all of that without being asked, plus what they check after the migration finishes. Our guide to Divi 5 backward compatibility mode explains why this matters for speed.
Do they still need Divi 4 skills?
Yes, for now. Most agencies have a back catalog of Divi 4 sites, and some will stay there until the client pays for the move. Your partner should be comfortable fixing a Divi 4 site without "upgrading" it by accident, and should ask before running the migrator on any live client site.
03Access and licensing: set it up before the first project
Most problems with Divi partners are not about skill. They are about access: shared passwords, a license in the wrong account, or a partner who still has admin access to a client site two years later. Settle these four things before you send a file.
1. Who holds the Divi license
Your agency should hold it. Elegant Themes says a membership covers unlimited websites for unlimited clients, and that if a membership is canceled, client sites keep working but stop getting new Divi updates and support. If the partner installs Divi from their own account, the client's updates depend on a company the client has never heard of. Keep the license in your account, or in the client's, never the partner's.
Current Elegant Themes pricing, from the official join page: Divi yearly is $89 a year, Divi lifetime is $249 once, and Divi Pro (Divi plus Divi AI, Divi Cloud, Divi VIP, Divi Teams and Divi Dash) is $277 a year. Divi Pro includes 4 team members.
2. Give the partner a Divi Teams seat, not your password
Divi Teams gives each team member their own Elegant Themes account, with permissions you control, including what they can see in billing and whose API keys they can view or manage. Extra seats cost $1.50 a month billed yearly ($18) or $2 a month billed monthly, and you can remove a seat at any time. Elegant Themes also lets you create separate API keys for each client. Use a separate key per client site, so ending a client or a partner relationship never means rotating the key on every site you run.
3. One WordPress user per person
Never share your own admin login. Create a named account for each person at the partner, on staging first, and delete it when the work ends. With WP-CLI that takes two commands:
# Create a named admin account for the partner on staging
wp user create partner-dev [email protected] --role=administrator --display_name="Partner Dev"
# When the project ends, remove it and give their content to your main admin (user ID 1)
wp user delete partner-dev --reassign=1Named accounts mean the activity log shows who changed what, and removing one person does not lock out everyone else. If your host or security plugin logs admin activity, check it once after the first project.
4. Staging first, always
The partner should build and migrate on staging, and the live site should stay untouched until you approve. Agree who pushes to live and who purges the cache. On Divi sites, an unpurged static CSS file is a common reason a finished change "did not work" on the live site.
04Divi-specific questions to ask a partner
These sit on top of the general partner questions. Ask them on the first call and listen for specific answers, not "yes, we can do that."
- How many Divi 5 builds and migrations have you shipped since February 2026? Ask for two staging links or redacted screenshots of the Divi 5 variable manager.
- How do you set up presets and variables before building pages? The right answer starts with global styles, then pages.
- Which third-party Divi plugins do you use by default, and why? Every plugin is a future update, license and compatibility question for you.
- What do you do with a module the migrator cannot convert? Look for "rebuild it natively" or "replace it with a native module", with the trade-offs explained.
- How do you handle the Theme Builder on a site with WooCommerce? Product, cart and checkout templates need their own checks.
- Who holds the Divi license on sites you build? If the answer is "ours", stop and fix that before anything else.
- Do you sell your own Divi plugins or child themes? That is not bad in itself, but you want to know if your client's site will depend on them.
- How do you hand over to the client? Ask for a sample handoff video and edit guide, branded as an agency.
- What hours overlap with ours, and how fast do you reply? Divi fixes are often small and urgent. A two-day reply cycle turns a 20-minute fix into a week.
- What happens if a Divi update breaks something you built? Agree on a fix window after launch, and whether it is free.
05Red flags specific to Divi partners
Some warning signs only show up with Divi work. Any one of these is worth a direct question. Two or more and you should keep looking.
| Red flag | Why it hurts you later |
|---|---|
| Every module has its own font, size and color settings | No presets or variables means every brand change is a manual edit across the whole site |
| A long list of "must-have" Divi plugins | More licenses, more update conflicts, more pages stuck in backward compatibility mode |
| Large custom CSS blocks in every module | Hard for your team to edit, easy to break, often there to fix a layout that flexbox or grid would handle |
| Divi installed from the partner's own Elegant Themes account | Updates stop when the relationship ends, and the client has no license on record |
| Migrations run straight on the live site | No safe rollback while the client watches their site change |
| "Divi 5 ready" with no Divi 5 examples | A badge is not a build. Ask to see one. |
| Credits, footer links or the partner's name in the code | Breaks the white label promise and can reach your client |
| Agency rankings where the publisher lists itself first | Fine as a starting list, not as evidence |
The fastest check is to open one finished page in the Visual Builder and click around for two minutes. Clean Divi work looks boring in the settings panels: presets applied, few overrides, no mystery CSS. Messy work looks busy.
06Pricing models and what to expect
White label Divi work is priced in four common ways. None is right for every agency. Pick the one that matches how predictable your pipeline is.
| Model | Best for | Watch out for |
|---|---|---|
| Fixed price per page or per site | Agencies that quote clients fixed prices | A tight scope definition: sections per page, revision rounds, what counts as a new page |
| Fixed price per migration | Divi 4 to Divi 5 upgrades across a portfolio | What is included when a third-party module has to be rebuilt |
| Hourly | Fixes and small changes | Minimum billing increments and who approves hours before work starts |
| Monthly hours or a dedicated developer | Steady pipelines with regular Divi work | Unused hours: do they roll over, and how much notice to cancel |
Payment terms vary too. Some partners ask for 50% up front, others bill on delivery or monthly. Whatever the model, get the price, scope and delivery date in writing before work starts.
What we charge
For reference, these are the current prices on our pricing page, all billed to your agency in USD:
| Service | Turnaround | Price |
|---|---|---|
| Pilot page (1 page, up to 6 sections, one per agency) | 3 working days | $199 |
| New Divi build (landing page) | 3 working days | From $400 |
| Brochure site, 3 to 5 pages | 5 to 7 working days | From $500 |
| Divi 4 to Divi 5 migration, per site, on staging | 2 to 7 working days | From $399 |
| Changes outside scope on projects we built | As needed | $30/hour |
| Dedicated developer, 40 hours a month | Month to month | $1,000/month |
| White label care plans | Monthly | From $25/site/month |
See Divi and Elementor development and Divi 4 to Divi 5 migration for what each one includes. For a wider view of how partners charge, read White label WordPress development: how it works and what it costs.
07NDA, brand rules and client contact
White label only works if the rules are written down. A short NDA and a one-page brand brief cover almost everything.
What the NDA should cover
- Mutual confidentiality covering designs, code, logins, pricing and the identity of your clients.
- A white label clause: the partner does not reveal its involvement to your clients and puts no credits, links or branding in delivered work.
- Non-solicitation: the partner will not offer services directly to clients you introduced, for a set period.
- Return or deletion of confidential information, including logins, at the end of the work.
- Code ownership: the code is yours, or your client's, on payment.
Our mutual NDA covers these points with a 3-year term and a 24-month non-solicitation period, and we sign yours instead if you prefer.
The one-page brand brief
Give the partner a short brief before the first project: your agency name as it should appear in handoff videos and docs, the email signature or alias they may use if they ever write to your client, whether they may join client calls (and as what title), and your file naming and staging conventions. Divi-specific additions: the default Divi version for new builds, your approved plugin list, and whether they may use Divi AI or Divi Cloud items on client sites.
Who talks to the client
The safest default is that the partner never contacts your client unless you ask. When you do want them on a call, introduce them as part of your team. Decide this once, in writing, so nobody improvises it in the middle of a project.
08Test the partner with a paid pilot
A paid pilot tells you more than any sales call. Pick one real page, ideally from a project you would otherwise build yourself, and send the same brief you would send for a full site.
What to send
- A Figma (or XD) file with desktop and mobile frames for one page, up to six sections
- Your brand brief and approved plugin list
- A staging site, or permission to use theirs
- One revision round, the same as a real project
What to check when it comes back
| Check | Pass looks like |
|---|---|
| Design match at desktop, tablet and mobile | Spacing, type and alignment match the Figma frames, with sensible tablet behavior even if no tablet frame was supplied |
| Presets and variables | Brand colors and fonts live in variables, buttons and headings use presets |
| Native Divi 5 modules | No page left in backward compatibility mode, no unnecessary plugins |
| Custom CSS | Little or none, and commented where it exists |
| Speed | PageSpeed Insights mobile result in line with your other sites, images sized and compressed |
| Accessibility basics | One h1, logical headings, alt text, visible focus states, readable contrast |
| Handoff | Staging link, a short edit video under your brand, notes on what was built |
| Communication | Questions asked early, the date kept, updates without chasing |
Our $199 pilot is built for exactly this test: one page, up to six sections, live on staging in 3 working days, in Divi 5, Elementor or Gutenberg, with one revision round and a handoff video branded as you.
09A scorecard for comparing Divi partners
Score each partner from 1 to 5 on each line after the first call and the pilot, then multiply by the weight. A partner below 60 out of 100 is a risk for client work. Above 80 is a partner you can grow with.
| Criterion | Weight | 1 looks like | 5 looks like |
|---|---|---|---|
| Divi 5 build quality (presets, variables, native modules) | 5 | Inline styles everywhere, legacy modules | Clean global styles, no compatibility mode |
| Migration experience | 3 | Has not run the migrator on a client site | Explains rollback, staging and third-party module rebuilds unprompted |
| Design accuracy | 3 | Close on desktop, guesses on mobile | Matches every breakpoint, asks about missing frames |
| Access and licensing hygiene | 3 | Asks for your password, uses their own license | Asks for a Teams seat and a named WP user |
| Communication and time-zone overlap | 3 | Replies in two days | Same-day replies in your working hours |
| White label discipline | 2 | Credits in the footer, own branding in videos | Nothing that points back to them |
| Pricing clarity | 1 | "Depends", no written scope | Fixed quote with scope and date |
The weights add up to 20, so the maximum score is 100. Adjust them to your business. A migration-heavy agency might weight migration experience at 5 and design accuracy at 2. Write the scores down for every partner you trial. Six months later, when you are deciding who gets the big project, you will be glad you did.
If you want to run this scorecard on us, read how our process works, then start with the pilot.
10FAQ
What is a white label Divi partner?
A white label Divi partner is a developer or agency that builds, migrates and maintains Divi sites for your agency under your brand. They work on your staging, deliver work with your name on it and never contact your client unless you ask. You keep the client, the pricing and the relationship.
How much does a white label Divi developer cost?
It depends on the model. Partners charge per page, per site, per migration, by the hour or as monthly retained hours. With us, a landing page starts at $400, a 3 to 5 page site at $500, a Divi 4 to Divi 5 migration at $399 per site, changes at $30 an hour, and a $199 pilot page lets you test us first.
Who should own the Divi license on client sites?
Your agency or the client, never the partner. Elegant Themes memberships cover unlimited sites, and if a membership ends, sites keep working but lose updates and support. If the partner's account powers the license, updates depend on a company the client does not know.
How do I give a partner access to Divi without sharing my account?
Add them as a Divi Teams member. Each member gets their own Elegant Themes account with permissions you set, and Divi Pro includes 4 seats. In WordPress, create a named user for each person on staging and delete it when the work ends.
Should my white label partner build in Divi 4 or Divi 5?
New builds should be in Divi 5, which launched on February 26, 2026. Divi 4 now gets only security and critical fixes. Existing Divi 4 sites can stay until the client approves a migration, which should run on staging first.
How do I test a Divi partner before a client project?
Run a paid pilot on one real page. Send a Figma file with desktop and mobile frames, then check design accuracy, use of presets and variables, native Divi 5 modules, speed, accessibility basics, the handoff video and how well they communicated.
Should a white label Divi partner sign an NDA?
Yes, before you share any files. It should cover confidentiality of designs, code, logins and client identities, a no-credits white label clause, non-solicitation of your clients, deletion of logins at the end, and code ownership on payment.



