Platform

Product landing page generator

You fill in a form about the product and get a live page on your own domain, ready to take orders and run ads.

90 to 120 secondsThat is how long the whole page takes: text, sections, photos in the right places. Before, a page took a day or two and was paid for one at a time.

14 sectionsGallery, benefits, specifications, bundles, reviews, questions, order form. Built for a phone, because that is where the buyers come from.

What they came with

A seller needs a page for every product. He ordered them from a developer, waited a day or two and paid for each one separately. There are a lot of products, and every new one repeats the same work: text, sections, photos in the right places, an order form, wiring up the leads.

What was built

The seller fills in one screen: name, prices, description, photos and video with their roles, his own terms, the available bundles. The page then builds itself and opens for editing in two ways: through a panel of blocks, or straight in the preview by double clicking the text. The finished page goes out to its own domain, orders arrive in the owner's Telegram and CRM, and the page can be exported as an archive. This work grew into the next direction: private generators for a specific client, with their own integrations, domain and hosting. What people actually wanted was not a shared service but a build of their own.

Input screen and editorFields on the left, the real template inside a phone frame on the right. Name, prices and photos drop into it live, before anything is generated.

DatabasePages, profiles, orders, payments and a library of blocks. Access is row by row: an owner sees only their own.

IntegrationsAn order goes to the owner in Telegram and into a CRM: LP-CRM, KeyCRM, SalesDrive or a custom endpoint. Meta, TikTok and Google Analytics pixels are set up in the settings.

GenerationUp to eight photos go into the model as images, and the answer comes back as data.

Accounts and balancesSign in with Google, separate generation and publishing balances for everyone. Billing is built in and switched off during the beta.

PublishingThe page goes out to its own domain, and video uploads straight to storage, around the request size limit.

Stack

Next.jsTypeScriptSupabaseOpenRouterVercelCloudflareTelegram Bot APISentry

What turned out to be hard

A whole page is not something to trust a model with

Almost every generator asks the model for the page itself, and then each one is a lottery: its own markup, broken layout, wasted spend. Here the model returns text only, as data, and the app builds the page from a proven fourteen section template. It comes out cheaper, faster and predictable: the model physically cannot break the layout.

The model answered "success" with an error inside

The response is validated before it is parsed: on truncated data the person gets a clear message instead of a broken page.

Telegram or the CRM is unreachable

The order is written to the database regardless of delivery, and every delivery failure is recorded separately. A buyer is never lost to somebody else's outage.

An internal address typed into the custom CRM field

Only external addresses are accepted: local networks and internal hostnames are rejected before anything is sent.

Two pages ask for the same address

The address is checked for availability at publish time, and on a clash a suffix is added.