Building faster
Seven real builds took 221 to 616 seconds. Here is where that spread came from.
How long it actually takes
On 22 August 2026 we built seven businesses end to end from a real account. All seven finished.
The quickest was a language school at 221 seconds. The slowest was a hiking blog at 616. The average was 370.
Bigger requests take longer
More pages and more data means more time. That is the whole reason for the gap above.
If you are in a hurry, start with the three or four screens that matter and add the rest while looking at the result.
Starting from a design skips the build entirely
There are 336 finished designs in the gallery. Copying one gives you working screens with nothing to wait for, and no credits are used.
One thing does take time: if you want it in a language other than the one it was written in, a rewrite runs first.
One job at a time
Sending several requests does not make them run side by side. They queue up and take their turn.
So splitting work is not a way to make it finish sooner. It is a way to see the result partway and change direction.
You can close the tab
Nothing needs you sitting there. Close the window and it keeps going. Come back and it is exactly as far along as it should be.
Avoiding a second full build
Choose carefully from the three design directions shown before the first build. Changing the whole mood afterwards is a large job all over again.
For text and colour alone, click them in the preview instead of asking. That costs no credits.