3 min read
Why Blockora shows you a plan before it builds
An AI website builder could go straight from a prompt to a finished site. Blockora stops in between to show a plan, and that pause is the most important step in it.
The obvious way to build an AI website builder is to take a description and return a website. One prompt in, one site out. It demos well.
Blockora doesn't work that way. After you describe your business, it shows you a plan first: the pages it intends to make, the sections on each page and a design to build them in. You can change any of it. Only when you press Build does it write the site.
It's a small pause in the flow. We think it's the most important decision in the product.
A finished site is an expensive way to ask a question
When someone describes a website, they leave most of it unsaid. A restaurant owner who asks for "a site for my café" probably wants a menu page. Do they want online booking? A page for private events? Are the photos of the food or of the room?
A builder that goes straight to a finished site has to guess all of that. When it guesses wrong, the person's only way to say so is to look at a complete website, work out what's wrong with it and ask again. Every correction costs a full rebuild, and every rebuild changes things they were happy with.
A plan asks the same questions at the point where answering is cheap. Removing a page from a list takes a second. Removing it from a built site means checking navigation, links and every page that mentioned it.
The plan is also what keeps pages consistent
Blockora writes several pages at the same time instead of one after another, which is a large part of why a whole site is ready in about a minute.
Writing pages in parallel raises a problem. If each page is generated independently, nothing guarantees the home page and the contact page agree on the business's name, its tone or what the navigation contains. Pages written one after another can at least read what came before. Pages written at once can't.
The plan solves this. Every page is written from the same agreed outline and the same chosen design, so they share structure without having to wait for each other. So the pause does two jobs. It gives the person a cheap moment to correct things, and it's what lets the pages be written at once.
Design comes before content
The plan includes a design, and you see your own site in it before anything is built. That order is deliberate.
Most site builders start from a template and ask you to fill it in. The result looks like the template, and like every other site made from it. Choosing a design first, from a description of your business, means the content is written for that design. Headlines are the right length for the layout, and there are enough photos for the sections that need them. You can switch designs later without rewriting anything, because the content and the design are kept separate.
What it costs
The plan adds a step, and some people want to skip it. They typed a sentence and expected a website. For them, a plan can feel like a form to fill in.
We think the trade is worth it, for a reason that has more to do with trust than speed. A site that appears fully formed from one sentence is impressive the first time. It's frustrating the third time, when you realise you can't predict what the builder will do with your next request. A plan makes the builder's intentions visible before it acts on them. You stay in charge of what gets built.
The general lesson
This applies beyond websites. When an AI system produces something large from a short request, the cheapest place to catch a misunderstanding is before it starts. Show what you're about to do in a form people can edit quickly, let them correct it, then do the work. It's slower by a few seconds and faster by every rebuild it avoids.
More notes