Can a prompt replace Umso?

Build a landing-page generator that starts from a questionnaire rather than a blank canvas.

The questionnaire, which is the entry point: what the product does in one sentence, who it is for, the three things it does best, the main objection a visitor will have, the action you want them to take, and a tone (plain, confident, playful, technical). Six questions, no more — the point is to get to a draft in two minutes.

Generation: from those answers, produce a complete page. Ask the model for structured output, one field per section slot, not for a page of HTML — the layout comes from the section library and only the words come from the model. Generate: a headline and subheadline, three feature blocks with a title and a sentence each, a section answering the stated objection, a short social-proof placeholder with instructions on what to put there, a call to action, and page meta title and description.

Section library: hero, feature trio, feature with image, objection or FAQ accordion, logo strip, testimonial, pricing table, call to action, footer. Each section has two or three visual variants and consumes theme tokens only — no per-instance styling.

Theme: a token file with a type scale, palette, spacing and radius. Three starting palettes. Changing the palette restyles everything.

Editing after generation: inline text editing on every generated field, section reordering by drag, adding and removing sections, and a regenerate action per section that keeps the questionnaire answers and produces a fresh variant of just that section's copy. Per-section regeneration matters more than whole-page regeneration, because the usual case is that five sections are fine and one is wrong.

Honesty about the draft: mark generated copy visibly as generated until the user has edited or confirmed it, and refuse to export while any social-proof or metric placeholder is still unedited. Publishing a page containing an invented customer quote or an invented number is the specific failure this guard exists to prevent, and it should be a hard block rather than a warning.

Output: static HTML with one generated CSS file, responsive images, and no client-side JavaScript beyond the accordion and mobile menu. A contact form emitting a plain HTML form posting to an endpoint the user configures — do not build a submission backend, document connecting one.

Deployment: a build command producing a folder of static files, with one target documented end to end including a custom domain.

Use Anthropic for generation. With no key, the section library, theme system, editor and export must all work — only the questionnaire's generation step is unavailable.

Out of scope: hosted publishing, a template marketplace, a CMS or blog, memberships, and ecommerce.