A traditional custom WordPress project runs 6 to 10 weeks and $7,500 to $15,000. Agencies using AI design tools are delivering the same result in a day. The workflow is not complicated. The gap between those outcomes is mostly tooling and one step most people skip.
The problem with how agencies use AI tools today
Most agencies and freelancers are using Lovable, v0, and Bolt wrong. Not technically wrong. Strategically wrong.
The common approach: generate a design in Lovable, show it to the client, then spend two weeks manually rebuilding it in WordPress because the client needs a CMS. The AI tool saved you an hour on design. You lost it on the rebuild. Net gain: zero.
The better approach treats AI design tools as a design acceleration layer, not the final product. You prototype in minutes, capture the rendered output, and turn it into a WordPress theme in under a minute. The client gets an editable WordPress site. You get your time back.
Why clients always end up wanting WordPress
AI-generated apps built on Lovable or Bolt are impressive to look at. They're less impressive for clients to maintain. Here's what comes up every time.
- Content editing. Clients need to update text, swap images, and publish blog posts without calling you. Lovable's interface is built for developers. WordPress's Gutenberg editor is built for everyone.
- Plugin ecosystem. WooCommerce, Yoast SEO, Gravity Forms, booking systems, membership plugins. WordPress has 60,000 plugins. Lovable and v0 have none.
- Existing WordPress setups. Most clients already have a WordPress install for something. They don't want to manage two systems.
- Hosting familiarity. Clients on SiteGround, WP Engine, or Kinsta don't want to learn Vercel billing or Supabase row limits. They want to stay where they are.
This is not a failure of AI tools. It's a scope mismatch. AI tools are excellent at producing a design. WordPress is excellent at letting non-developers manage it. The workflow that works uses both.
The workflow
Step 1: Design in your AI tool (20 minutes)
Take the client brief and generate the design in Lovable, v0, or Bolt. Aim for a full homepage and two or three inner page layouts. The goal is a published URL, not a finished product.
Work in tight iteration loops. Describe what you want, review the output, refine. Most homepage designs reach a presentable state in three to five prompts. Don't spend more than 20 to 30 minutes here on the first pass.
Publish to a public URL. All three tools give you one:
- Lovable publishes to a
lovable.appsubdomain - v0 deploys to a
vercel.apppreview URL - Bolt deploys to a
stackblitz.ioURL
You don't need a custom domain. You need a URL that's publicly accessible.
Step 2: Get client approval on the design
Send the live URL to the client. This is a real, working design in a browser, not a Figma mockup they can't interact with. Clients respond faster to something they can click through.
Collect feedback. Go back to the AI tool, make adjustments, re-publish. Repeat until the design is approved. This stage might take one round or three. Either way, you're iterating on a live URL instead of arguing over static mockups.
Step 3: Convert to WordPress (60 seconds)
Once the design is approved, paste the URL into StaticToWP. The tool renders your page in a real browser, captures the fully computed HTML, CSS, fonts, and assets, and packages everything as a wp-theme.zip.
This step works because AI tools render standard HTML and CSS in the browser. By the time the page is fully loaded, the React components, Tailwind classes, and animation libraries have all been resolved to standard web primitives. The capture happens at that point. What goes into the WordPress theme is not React. It's HTML and CSS.
The resulting theme includes WordPress template files, properly enqueued styles and scripts, and ACF-compatible field structure for editable content areas. It installs and activates like any other theme.
Step 4: Install and configure WordPress (1 to 2 hours)
Upload the theme zip to the client's WordPress install. Go to Appearance → Themes → Add New → Upload Theme, upload it, activate it.
Standard configuration from here:
- Set the homepage under Settings → Reading
- Install ACF Free and connect the editable content fields
- Install Yoast SEO or Rank Math and configure meta titles
- Install a caching plugin (W3 Total Cache, WP Super Cache)
- Set up the client's navigation menus
- Configure contact forms with WPForms or Gravity Forms
- Test across Chrome, Safari, and Firefox
- Check mobile at 375px and 768px widths
Two hours is a realistic estimate for a standard marketing site. Complex setups with WooCommerce or custom post types take more, but the design work is already done.
Step 5: Client handoff
Record a 5-minute Loom walkthrough showing the client how to edit content in the WordPress admin. Show them the ACF fields for text and images. Show them how to publish a blog post. That video replaces most support requests.
Hand off hosting credentials, WordPress admin access, and a one-page reference sheet covering the most common editing tasks. Include your contact info for questions.
Which AI tool for which project
All three tools produce a public URL that converts to WordPress. But they're not identical.
- Lovable: Best for projects with complex layouts and multiple inner pages. Lovable's Agent Mode scaffolds navigation, inner page structure, and some backend logic automatically. Good starting point for service businesses with 5 to 10 pages.
- v0 by Vercel: Best for component-level design. If you need a specific hero section, a pricing table, or a features grid to look exactly right, v0 produces tighter output. Deploy to a Vercel preview URL and convert from there.
- Bolt: Fast iteration. Good for exploring multiple design directions quickly. If you want to show a client three different homepage approaches in one meeting, Bolt generates them faster than the other two.
In practice, many agencies use v0 for component refinement and Lovable for full-page structure. You can mix: design individual sections in v0, assemble them in Lovable, then convert the full-page URL.
How to price this workflow
The workflow above reduces your delivery time from weeks to days. That creates a pricing decision: do you pass the savings to the client, or keep your rate and increase your margin?
Most agencies land on a middle path. They price the project at market rate for a custom WordPress site (a reasonable starting range is $3,000 to $8,000 for a standard marketing site depending on your market). They deliver faster. They take on more projects per month. The margin improvement compounds.
If you charge $5,000 for a WordPress site and it takes you 40 hours manually, your effective rate is $125/hr. If you deliver the same quality in 12 hours using this workflow, your effective rate is $416/hr. The client pays the same. You earn more per hour worked.
Some agencies do pass partial savings to clients. A $3,500 quote that delivers in 3 days is a competitive offer. That can win projects you'd otherwise lose to lower-cost freelancers.
Common objections
"The client will notice it's AI-generated"
The design looks like what you built in the AI tool. If you prompt well and refine in a couple of iterations, the output is indistinguishable from a custom-designed site. Use the AI tool for structure and layout. Apply your creative direction to typography, color, and copy. The combination doesn't read as generic.
Clients care about whether the site represents their brand and whether it's easy to update. They don't audit the build process.
"What if the client wants significant changes after launch?"
Go back to the AI tool, make the change, re-run the conversion, reinstall the theme. Each reconversion takes about 60 seconds. For minor text and image updates, the ACF fields in the theme let the client edit directly in WordPress without any reconversion.
For structural layout changes (adding a new section, reordering the page), reconverting is faster than manually editing PHP templates. The AI tool is your design source of truth.
"I need WooCommerce. Does the theme support it?"
The theme handles the design layer. WooCommerce handles the commerce layer. Install WooCommerce after activating the theme, configure it for your client's products, and use WooCommerce's own shop templates. You can style those templates to match the converted theme using the captured CSS as a reference. This requires some additional work, but the design groundwork is done.
What this workflow doesn't replace
Not every project fits this approach. Here's where it doesn't work.
- Large multisite setups. Network installs with shared themes across dozens of sites have configuration complexity that goes beyond theme generation.
- Heavily custom PHP functionality. If the project requires custom post types with complex business logic, custom REST API endpoints, or deep plugin integrations, the design layer is a small part of the work. This workflow handles the design layer only.
- Authentication and gated content. The conversion captures what the browser can load without logging in. Membership sites and paywalled content need WordPress membership plugins configured independently.
- High-volume editorial sites. A site with hundreds of article templates, category archives, and author pages benefits from a more systematic WordPress setup. The workflow works well for the homepage and key pages. Full blog templating may need additional manual work.
For a standard marketing site, portfolio, service business, or lead-generation site, this workflow covers the full project scope.
The delivery math
Traditional WordPress project timeline:
- Discovery and brief: 2 to 4 hours
- Wireframes: 4 to 8 hours
- Design mockups in Figma: 8 to 20 hours
- Client review rounds: 3 to 6 hours
- WordPress theme development: 16 to 30 hours
- QA and launch: 3 to 5 hours
- Total: 36 to 73 hours. 4 to 10 weeks elapsed.
AI-accelerated workflow timeline:
- Discovery and brief: 1 to 2 hours
- AI design and iteration: 1 to 3 hours
- Client review: 1 to 2 hours
- WordPress conversion and configuration: 2 to 3 hours
- QA and launch: 1 to 2 hours
- Total: 6 to 12 hours. 1 to 3 days elapsed.
The output is comparable. A marketing site with a polished design, an editable WordPress CMS, and standard plugins. The delivery time is not comparable.
FAQ
Do I need to be a developer to use this workflow?
No. The AI design step requires prompting skill, not coding skill. The WordPress configuration step requires basic WordPress familiarity: installing themes, setting up pages, and configuring plugins. If you've built a WordPress site before, you have the skills. The workflow reduces the developer time required, not the designer or project manager time.
Can I use Cursor or Claude Code instead of Lovable or v0?
Yes, if the output is deployed to a public URL. Cursor and Claude Code are code editors, not no-code builders, so the design generation step requires more coding knowledge. But if you're comfortable using those tools to generate a site, deploy it, and convert the URL, the workflow is identical from the StaticToWP step onward. See the related guides on Next.js to WordPress and v0, Lovable and Bolt to WordPress for specifics.
What if my client has an existing WordPress site they want redesigned?
Same workflow. Design the new look in a Lovable or v0, get it approved, convert to a theme zip, install as a new theme on the existing WordPress site. The existing content stays in WordPress. Only the theme changes. Swap the theme, remap the ACF fields to existing content, and the redesign is done.
How do I handle the SEO handoff?
Install Yoast SEO or Rank Math before launch. Re-enter meta titles and descriptions for all pages. If the client is migrating from an existing site, match the URL structure and set up 301 redirects for anything that changes. Submit the WordPress sitemap to Google Search Console. Most of this is 30 minutes of configuration work, not development work.