← All guides

One prompt or a conversation: two ways to build a site with AI

Short answer: There are two ways to build a site with AI. One prompt gives you a whole site in minutes but no way to ask for changes afterwards. A conversation gives you exactly what you describe but takes hours and costs tokens per instruction. Pick by whether the site has to be specifically yours or merely has to exist.
One prompt or a conversation: two ways to build a site with AI

Two published walkthroughs, two completely different methods, both ending in a working WordPress site. Watching them back to back is more useful than watching either one alone, because the differences are the actual decision you have to make.

The first is Ferdy Korpershoek building a site through Elementor's MCP integration, instructing Claude step by step over several hours. The second is a Hostinger tutorial using ZipWP, where one description of the business produces a complete site in minutes.

Neither is the better tool. They are answers to different questions, and choosing the wrong one is what wastes the weekend.

1. What each method actually is

The one prompt method asks for a description of your business, refines that description, then generates everything at once: pages, copy, images, contact form, blog. You watch a progress bar. What comes out is what you get.

The conversation method has no generate button. You describe one thing, it appears, you correct it, you describe the next thing. In the recorded build that meant screenshotting a layout, handing it over, asking for a rebuild, then asking for the counter animation to run in a different order.

The difference is not speed. It is whether you can still ask for something after the site exists.

2. The comparison that matters

QuestionOne promptConversation
Time to a live siteMinutes, once setup is doneHours, and it stays open ended
Cost shapeCredits, roughly fixed per siteTokens per instruction, so it depends on you
Changing it laterBy hand, in the page builderAsk again in plain words
Where the design comes fromPreset previews you pick fromReferences you supply
Where the images come fromStock library, chosen at setupWhatever you upload
Where the words come fromWritten for you from a descriptionWritten for you, then argued with
Skill assumedNone, until you want a changeEnough to know what to ask for

The row that decides it is the third one. Everything else is preference. Whether you can change the site by asking, or have to open a builder and do it yourself, is the difference you will live with for as long as the site exists.

3. Setup is not counted in either claim

Both walkthroughs open with a number. Five minutes for one, around twenty one dollars for the other. Neither number includes what happens before the AI runs.

In the one prompt tutorial, the steps before any AI ran were: buy hosting, register a domain, install WordPress, install a specific theme, then bulk deactivate and delete the default plugins the host had installed, because they interfere with the builder. Then create an account with the AI service, install its plugin, and connect the two.

In the conversation build, setup was smaller but the interruptions were larger: custom post types the AI could not create, three empty templates that had to exist before it could fill them, and JavaScript it wrote but a person had to paste in.

We counted those in detail in what AI website builders actually leave for you to do. The short version is that the AI is fluent inside its own surface and blocked everywhere outside it, and that holds for both methods.

4. Myths and facts

Myth

The fast method has no downside

It produces a real site quickly. It also decides the layout, the words and the images for you, and hands you a page builder when you disagree. That is a fair trade if you would not have opened a builder anyway, and a poor one if you have specific ideas.

Myth

The conversation method is only for developers

The recorded build was done by someone who says plainly he is not a coder. What it needs is not code, it is the ability to describe what you want precisely. Vague instructions produce vague results, which is a writing skill, not a technical one.

Myth

You can start fast and switch later

You can, but not for free. A site generated in one pass is a normal site afterwards, so switching to a conversational tool means it now has to read and edit somebody else's markup rather than its own. Easier to choose once.

Fact

Stock photography is a real cost

The fast method asks you to pick at least ten stock images during setup. For a local business that is a visible weakness: the photographs on the site are of somewhere else, and customers notice before search engines do.

Fact

Description quality decides output quality

Both methods rise and fall on how well you describe the business. One asks for it once at the start, the other asks continuously. Neither invents a good answer from a thin brief.

Fact

Both leave you with WordPress

Whatever built it, you end up owning a WordPress install with a theme, plugins and updates. That is a genuine advantage over a closed platform, and it is also work that does not disappear because AI wrote the pages.

5. Which one to choose

Answer these honestly rather than optimistically.

  1. Do you already know what the site should look like? If you can point at a reference, the conversation method uses that directly. If you cannot, the preset previews of the fast method will get you further than a blank prompt will.
  2. How often will it change? A site you revise monthly is worth the slower setup, because changing it stays conversational. A site that goes up once and sits there is not.
  3. Do you have real photographs? If yes, that alone argues against a stock library. If no, stock images are honest enough for now, and worth replacing later.
  4. Who maintains it in six months? If that is you and you are comfortable in a page builder, either works. If it is you and you are not, choose the one where changes are a sentence.
  5. What is your actual budget shape? Fixed credits are easier to predict. Tokens per instruction reward being decisive and punish fiddling, which is worth knowing about yourself before you start.

6. What neither method solves

Both produce pages. Neither produces the thing the pages exist for.

Still yours to supply

The facts about your business. Real address, real hours, real prices, real services. Invented ones are worse than missing ones, because a wrong phone number sends calls nowhere and damages local search at the same time.

Proof that you are any good. Reviews, credentials, photographs of actual work. No generator has these.

A reason to choose you. Both methods write competent copy about what you do. Neither knows why a customer should pick you over the business down the road.

Still work afterwards

Getting found. A generated site is not an optimised site. See AI SEO for WordPress for what actually has to be true on the page.

Being cited by AI engines. Ranking and being quoted are now separate problems, covered in getting cited by ChatGPT and Perplexity.

Publishing anything after launch. A site with six pages and no new content stalls. That is the case for publishing on a schedule.

7. The honest summary

If you need a site to exist by Friday, want the decisions made for you, and will not be changing much, the one prompt method is the correct answer and the speed is real.

If the site has to look like something specific, and you expect to keep changing it, the conversation method is worth the extra hours, because those hours buy you the ability to keep asking rather than keep editing.

What both share is the part nobody puts in a thumbnail: the generation is the quick bit. The setup around it, the facts only you have, and the work of getting the thing found afterwards are where the time actually goes.

Where we sit. wptaskify is the conversational kind, with the setup removed: no plugins to configure, no templates to pre create, no code to paste, because the AI controls the whole site rather than one builder inside it. You bring your own Claude or ChatGPT, so the usage is on your account and you choose what to spend on which task. What you give up is the WordPress plugin ecosystem. If you need a specific plugin, one of the tools above is a better fit than we are, and we would rather say so now.

Sources: Ferdy Korpershoek's published walkthrough of the Elementor MCP integration, and Hostinger's published ZipWP tutorial. Setup steps, costs and limitations above are taken from those recordings. Both tools are actively developed and some of these limits will move.

Related guides

WPTASKIFY

Put your WordPress site on autopilot

Bring your own Claude or ChatGPT and let AI write, optimize and publish for you.

100+ WordPress tools Your own AI, no extra bill Nothing goes live without approval
Get started free →
Free forever plan · No credit card

← All guides