Fresh out of the oven
Spot a bug? These tools are new, so the odd thing may still wobble. If something looks wrong, it probably is. Tell us and we will sort it..
Fresh out of the oven
Spot a bug? These tools are new, so the odd thing may still wobble. If something looks wrong, it probably is. Tell us and we will sort it..
Fresh out of the oven
Spot a bug? These tools are new, so the odd thing may still wobble. If something looks wrong, it probably is. Tell us and we will sort it..
Pinnora's landing page generator turns one brief into a finished page. You name the conversion job, the traffic arriving on it and the single action, then pick the frame style and up to six sections. What comes back is one HTML file, previewable at mobile, tablet and desktop, with any section regenerable on its own.
The tool is open above. This is the short version of what to do with it.
Frame style covers SaaS classic through Data-driven. Leave Palette on Brand palette to lock the page to your hex, then pick how the headline opens.
The only required field. About 60 to 100 words: the traffic arriving on the page, the audience, and the single action you want from them.
Pages runs 1 to 8, so a variant test is one run rather than eight separate ones.
Up to six blocks from Hero, Social proof, Features, Testimonials, Pricing, FAQ, CTA band and Footer. What lands is one HTML file.
Short answers to what people ask before they start.
You get one HTML document: Tailwind pulled from its CDN, a system font stack, single-column sections that widen into grids at the md breakpoint, and your copy in place. The viewer has a Copy button and a Download button that saves it as a .html file named after the page. Nothing is locked in a page-builder format, so it goes to whatever host you already use.
One brief. The What the page must do box is the only required field, minimum 8 characters and up to 4000. Everything else ships with a default: Pages 1, Frame style SaaS classic, Palette Brand palette, Hook style Question, and six sections. If you would rather not write it yourself, type one line and press Build configuration.
Before writing, the run loads your project grounding: the pains, objections, offer and proof from the earlier research and strategy work. The hero leads with the sharpest pain in the customer's own words, the FAQ and objection sections answer the real objections, and the writer is told never to invent a price, statistic or testimonial that is not in that grounding.
Yes. The run resolves a brand snapshot from the project: logo, voice, and up to three brand colors mapped onto the six swatches the composer uses for background, surface, primary, text on primary, accent and muted text. That is what Brand palette means on the Palette control. If the brand load fails, the page still renders on a fallback palette.
Every row in the viewer's section rail has a regenerate button. It rewrites that one section, re-reads your current brand, and forks a new artifact, so the page you already approved stays intact. That pass keeps the section's existing image. There is also an edit path that takes a written instruction, rewrites the copy in one pass and recomposes the HTML.
Only sections that come back with an image brief get one. Those render at 16:9 and upload to storage, so the HTML links the file instead of carrying a base64 blob, and a section whose image fails records the error instead of dropping it quietly. The progress estimate for a landing page run is about five minutes.
The rest of the family. Every one is free to try and runs on the same engine.