Three choices that are actually different
Compare navigation and hero directions as real HTML. For deeper work, select style tokens and a complete page direction before conversion.
WordPress AI website builder
From a real brief to WordPress—without approving a mystery box.
WPbyAI separates exploration from conversion. You compare distinct directions first, freeze the selected design rules, then move into editable WordPress and a stated verification scope.
Private Pilot: self-service checkout and unlimited automatic generation are not open yet.
Editable, versioned WordPress work
The approved specification becomes WordPress work with clear commits, previews, and a path back to the last accepted version.
A result tied to a real stack
The agreed flows are checked in a locked WordPress, PHP, database, theme, and plugin combination before a C-verified handoff.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Describe the result
Give the business, audience, pages, conversion goal, constraints, and any content or brand materials you already have.
- 02
Choose a direction
Review distinct, clickable directions. Approve one visual and structural specification; rejected directions remain history, not hidden overwrites.
- 03
Build and revise
Convert the approved direction to WordPress, review a stable preview, and make scoped changes against a known parent version.
- 04
Verify and deliver
Run the agreed browser and stack checks, record limitations, and hand off the editable source. Production launch remains a separate choice.
Included in this route
- Living Brief and explicit project assumptions
- Three navigation + hero directions for the approval gate
- Versioned preview and scoped change rounds according to the selected offer
- Editable WordPress source and ownership boundary
- Search Foundation checks for canonical, robots, sitemap, schema, links, and indexability in formal delivery
Not assumed or promised
- A guarantee of rankings, traffic, leads, or AI citations
- Unlimited revisions, unlimited premium-plugin licenses, or unlimited hosting
- Silent production changes before an explicit launch approval
- A claim that every plugin, host, language, and commerce stack is already verified
Frequently asked questions
Scope first. Promises second.
What should I put in the first brief?
State your audience, pages, primary action, available content, and required integrations. For example: “A five-page local repair business site; visitors should request a quote; I have service descriptions and licensed photos; online payments are not needed.” This is an illustrative brief, not a customer case study. Do not include passwords or private customer records.
How should I review a direction before approving it?
Check whether the first screen explains the business and next action, whether navigation reaches the planned pages, and whether the layout works on a phone. Flag invented addresses, testimonials, prices, or services before approval. A convincing preview is a design decision, not proof that every integration works.
When does a project need a separate scope review?
Tell us early about an existing site, customer accounts, checkout, bookings, paid plugins, multilingual content, or custom integrations. Do not assume that a design starting point includes these capabilities. Confirm the pages, working flows, licenses, hosting responsibilities, and acceptance checks before accepting a price.
Find your starting point
More choice at the beginning. A clearer decision before the build.
Use the builder review worksheet
Record the preview, repeat edits, WordPress access, ownership, and limitations before choosing a builder.
View this route →100+ WordPress templates
Explore template options for business, SaaS, agency, portfolio, ecommerce, blogs, local services, and more.
View this route →Delivery methodology
See how approval, versioning, WordPress conversion, and C verification fit together.
View this route →Current pilot pricing
Compare the present build and verification scope without assuming production hosting or unlimited work.
View this route →Limited private pilot
Describe the site. Choose the direction. Approve the build.
Start with the audience, pages, conversion goal, and any constraints. The current private pilot reviews fit before accepting a build.