Guide

AI to WordPress for Agencies: Pitch, Build and Hand Over Client Sites

One delivery workflow for every client job, whether it starts as a brief, a Figma file or a Lovable build: pitch real directions, land native WordPress on the client's host, and hand over with roles already set.

Client briefUiChemyWordPress
Run one paid client job end to end before moving the whole roster

The short answer

Agencies use UiChemy to run a client job from brief to a WordPress site the client owns. AI Website Creator turns the brief into a sitemap and pitch variations, Figma to WordPress and AI to WordPress bring in client designs or AI builds, and the UiChemy Composer role manager decides what the client can edit after handover. The Agency plan lists unlimited site projects, Figma seats and Composer sites.

What you need

  • A client brief in any state. A paragraph, a call transcript or a client document is enough for AI Website Creator to start from.
  • One WordPress install per client, ideally on the client's own hosting account so ownership is settled before the first invoice.
  • Elementor on each client site if you plan to export from AI Website Creator. Gutenberg and Bricks exports are listed as coming soon.
  • A UiChemy account. The Free plan includes 1 site project, 5 pages per site and 1 pitch variation, which is enough to run one real pitch before you pay.
  • Claude with the UiChemy MCP connected, or a WordPress MCP you already run, for the jobs that arrive as an AI build.
  • A staging copy of each client site for reviews. Staging and local sites don't count against Composer site limits.

Step by step

  1. Turn the brief into a scope

    Paste whatever the client sent into AI Website Creator. Its guided questions produce a structured brief with goals, requirements, constraints and positioning. Correct it here, because the sitemap, the designs and the copy all read from this brief. A wrong audience line now becomes six wrong pages later.

    Create a website for [client name], a [type of business] in [city]. Use the attached call notes and brand guidelines. Audience: [who buys]. Main goal: [enquiries / bookings / sales]. Required pages: [list]. The client rejected: [styles or competitors to avoid].
  2. Get the sitemap signed off

    The tool plans pages, sections and hierarchy before anything is designed. Reorder, add or remove pages, then send the sitemap to the client as its own approval step. Catching a missing Careers page at this stage takes a minute. Catching it after design costs a revision round you probably didn't quote for.

  3. Pitch two or three directions

    Generate pitch variations from the same brief so the client picks a direction instead of approving the only one on the table. The pricing page lists 1 variation on Free, 1 on Designer (2 during the early-bird offer), 3 on Studio (6 early bird) and unlimited on Agency. Send one review link and the client's feedback comes back pinned to the section it's about.

  4. Bring in the client's own files when they exist

    Plenty of clients show up with something already made. A Figma file goes through the UiChemy Figma plugin in AI Express Mode or Classic Mode. A Lovable, Bolt, v0 or Claude build goes through the ZIP and MCP route. The entry point changes; the output is the same native WordPress your team already maintains. For prototypes that also contain an app, read migrating a Lovable app to a client website first.

    Convert the attached project ZIP to WordPress with the UiChemy MCP, using Elementor. Create one page per route, keep every line of copy exactly as written, put the header and footer in theme builder templates, and end with a list of anything you could not convert.
  5. Export to the client's WordPress

    Install the UiChemy plugin on the client site and log in with your account. Projects import page by page, and imported pages arrive as new pages, so nothing already published on a live site gets overwritten. Each section lands as a Composer widget holding real HTML, CSS and JS, scoped so its styles can't leak into the client's theme.

  6. Review on staging, not on the live domain

    Hold the client review on a staging copy. Because staging sites don't count toward Composer site limits, a review copy per client costs nothing extra. Fix copy and spacing on the page in Design Mode, or ask AI Agent Chat on a paid plan to make the change for you.

  7. Set roles before you send the login

    Open the UiChemy Composer role manager and decide what each WordPress role can see. A setup that works for most retainers: the client's marketing lead gets Design Mode on the front end for text, images and links, and structure and code stay with your team. Role Manager and White Label are on every paid plan and on neither Free plan.

  8. Choose the plan by client count

    Count live client sites and the pitches you run each month. Designer lists 5 Composer sites and 5 site projects (10 each during the early-bird offer). Studio lists 25 sites and 10 projects (50 and 20 early bird). Agency lists unlimited sites, projects and Figma seats for $44 a month, billed $528 a year. If you only need Composer, the lifetime Pro plan covers 25 live sites for a one-time $199, and Unlimited covers any number for $349, both early-bird prices.

What carries over and what does not

What you get

  • Every client site runs on WordPress hosting the client controls, built from native, editable content instead of an embed or a locked export.
  • Clients choose between real directions before you build, and their comments arrive attached to the section they mean.
  • Brief-only jobs, Figma jobs and AI-build rescues all finish as the same kind of WordPress site, so one team can support all of them.
  • Clients change their own copy, images and links inside the limits you set, which removes most of the small tickets from your queue.
  • A lapsed Composer license doesn't take client sites down. The plugin keeps working; updates and support pause until renewal.

What does not carry over

  • AI Website Creator exports to Elementor only today. Gutenberg and Bricks are listed as coming soon, so a Bricks-only shop should wait or use Classic Mode for Figma jobs.
  • AI builds convert as pages and sections. Logins, databases, payments and server functions are not documented as converted.
  • White Label and Role Manager are missing from both Free plans. You need Designer, Studio or Agency, or a paid Composer lifetime plan.
  • Credits refresh monthly and don't roll over. AI Express conversions and full site plans cost more Credits than Classic Mode work, so a busy month can need a top-up.
  • Sandbox Sites and MCP access for AI Website Creator are marked Soon on the pricing page. Don't sell them to a client yet.
  • The higher early-bird limits are a limited-time offer. Build your quotes on the standard limits if your margin depends on them.

Troubleshooting

The client keeps asking for one more direction

Lock the sitemap before design and write the number of pitch variations into the quote. The plan caps variations per project anyway, from 1 on Free to unlimited on Agency.

An imported section looks wrong inside the client's theme

Composer sections are scoped so their own styles stay inside them. If it still looks off, look for custom CSS the client's theme adds globally, then adjust the section in Developer Mode.

The client broke a layout while editing

Tighten that role in the role manager. Front-end Design Mode only lets them change text, images and links without touching structure.

You hit the Composer site limit halfway through a month

Check whether a counted site is really a staging or local copy, since those don't count. If you still need room, upgrade: new limits apply immediately and you pay only the prorated difference.

A Figma conversion failed on a client file

A failed conversion doesn't spend Credits. Try the frame again, or switch to Classic Mode and tag the layers AI Express misread.

Frequently asked questions

Who owns a site we build for a client?

It's standard WordPress content on whichever install you build it in. UiChemy's pricing page says a finished site can be handed off like any WordPress site and the client can keep editing it in their own builder. Build on the client's hosting if you want ownership to be beyond argument.

Does UiChemy offer white label?

Yes, on paid plans. The pricing page lists White Label on Designer, Studio and Agency, and on Composer Solo, Pro and Unlimited. It isn't on either Free plan.

Which plan fits an agency?

Count client sites and monthly pitches. Under roughly 25 live sites, Studio usually covers it. Above that, or when pitches pile up, Agency's unlimited projects, pitch variations, Figma seats and Composer sites stop you watching limits. Composer-only shops can buy Pro or Unlimited once instead.

Does every client site use a Composer licence?

Live sites that use Composer do. The pricing FAQ says a handed-off site that uses Composer runs on one of your Composer site licences. Staging and local copies don't count.

Can several designers convert Figma files for one client?

Yes. Share the Connection Link and the team converts into the same site from your shared plan. Figma seats are 1 on Free, 2 on Designer (4 early bird), 10 on Studio (20 early bird) and unlimited on Agency.

Do client sites keep working if we stop paying?

Yes. Pages are real HTML, CSS and JS stored in the client's WordPress, not loaded from UiChemy's servers. What pauses is the AI side and new conversions beyond the Free plan.

What if the client is still choosing between AI tools?

Point them at our Figma Make vs Lovable comparison or the list of Bolt alternatives. Whatever they pick, the build can come into WordPress the same way.

We're a one-person studio. Is this overkill?

Probably. The solo version of this workflow is at AI to WordPress for freelance designers, and it starts on the $8 Designer plan.