Prompt to site is the base of the pyramid. You describe a website, a landing page, a portfolio or a product page, and a tool builds it. There is no repository until the tool makes one, and you may never see it. The structure, the markup and the conventions belong to the tool.
Two categories sit here.
- AI website builders, where a description becomes a marketing site or a landing page.
- Screenshot to app, where an image becomes an interface. It sits on this rung because it has become one more way into a site builder rather than a product of its own.
The base is not the easy end of a scale. It is the end where you take on the least engineering, and for a lot of work that is the right trade. A page that has to exist by Friday and say one thing clearly does not need a codebase you maintain.
What this rung is for
Pages, not behaviour. A site whose job is to explain something, take an enquiry and be found. A launch page for an idea, so you can test whether the message lands before anything is built behind it.
The output is usually good. The ceiling is just as real: the moment you need behaviour rather than pages, such as accounts, saved data or payments, you are on a different rung.
Who it suits
- Founders and small businesses who need a credible presence this week.
- Freelancers and small agencies who sell websites, for whom these tools are both a faster way to build and a threat to the cheapest end of the work.
- Anyone testing a message before building a product behind it.
It suits a site that has to carry real search traffic, load on a mid-range phone over metered data, or meet an accessibility obligation only if someone checks those things rather than trusting the preview. A generated site can be all of them. None of them is visible in a screenshot.
How to tell you are on this rung
- What you deliver is pages. Nobody signs in, and nothing a visitor does is kept except perhaps a form submission.
- Changes go through the tool. To move a heading, you open the builder, not a file.
- There is no repository you work in, or there is one you have never opened.
If visitors sign in, or the site keeps data on their behalf, you are on the rung above.
What it costs you later
- The ceiling arrives as a rebuild. A site built as pages does not grow into an application. When the business needs accounts or payments, the usual path is to start again on a higher rung and carry the content across.
- The structure is the tool's. Whether you can take the site elsewhere depends on what the tool lets you export. Find out before the site matters, not after.
- What a preview cannot show is still yours. Generated meta tags are not search engine optimisation. Page weight, keyboard access, alt text, heading order and colour contrast do not show up in a preview, and nobody checks them unless someone decides to. Core Web Vitals explained covers the performance half.
- The change request in month six. Someone will ask for a change long after launch, and whoever holds the account and knows the tool is the person who makes it. On client work, decide at the start who that is and write it into the handover.
- A screenshot copies the picture, not the behaviour. An image shows one state. Focus, hover, empty, loading, error and the narrow viewport are not in it, so the tool invents them or leaves them out. And a screenshot of someone else's product is reverse engineering and cloning, which is a different practice with problems of its own, covered under Cross-cutting practices.
The step up
The next rung is Prompt to app, where the tool builds behaviour as well as pages: sign-in, saved data, a deploy. It looks like a small step. It is a large one in what you take on, because an application holds data, and data has to stay right for as long as the application lives.
Not every site needs to climb. A site that does its job on this rung should stay on it. The signal to move is a need the tool cannot meet, not a feeling that a higher rung is more serious.