A one-page site for one offer

One page, one job

Tell the in-app assistant three things: the offer, who it is for, and what happens after someone sends the form. The page is written from a conversation, not a template: a headline, a lede, an answer capsule near the top, the details, and the form.

Keep the offer to one sentence when you describe it. If you cannot say it in one sentence to the assistant, a visitor will not get it in one glance either. The answer capsule is where that sentence ends up, and the AI answer engines like ChatGPT and Google's AI answers read it the same way a person does.

It is still a page, so it still passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards. One main heading, a title and description, structured data. Landing page design covers what the page itself should look like.

Its own domain, or a free address today

A campaign often wants a fresh domain that matches the offer. Connect it with one DNS record, a CNAME, and the SSL certificate is issued for you. The assistant walks you through the record for your registrar.

If the campaign starts before the domain is sorted, the page is already live on a free address. Point the ads there and switch later.

A subdomain of your main site works too, and connects the same way. Pick whichever the offer reads better on.

Every form lands in the CRM the same minute

Each submission is delivered to HubSpot, Salesforce, Zoho CRM, Pipedrive, GoHighLevel, Mailchimp, Kit, ActiveCampaign, Slack, Microsoft Teams, SMS, email, or any webhook. Connecting needs no sign-in screen: paste one credential you generate yourself, then press Send test lead to prove it.

Every delivery is signed. HubSpot, Zoho and Pipedrive deliveries update an existing contact by email instead of creating a duplicate, which matters when the same person answers two campaigns. On the Leads screen each lead has a status and a note, and one click exports the lot to a spreadsheet.

The second version, without a cookie

Ask the assistant to start an A/B test and the site gets a second version with an alternate headline, lede and answer capsule. Visitors are split in a stable way, so the same person sees the same version, and no cookie is used to do it.

Everything else on the page stays the same, which is the point. You are comparing the words at the top, not two different pages.

Give the test time before you judge it. A campaign that runs for an afternoon has not shown you much, and the assistant will not pretend otherwise when you ask it to read the numbers.

Counting that happens on the server

Page views and conversions are counted on the server, so no analytics script and no cookie are added to your page. The in-app assistant can read your analytics and explain what it sees.

If your ad platform wants Google Analytics 4, add your measurement ID in one field. On sites that show a banner, the tag loads only after a visitor accepts cookies.

A Google Search Console verification token goes in its own field the same way. Neither field is required; the server-side count works with both of them empty.

Timing the launch and tidying up after

Schedule the page to publish at a date and time in your own time zone, so it goes live when the ads do. Every publish keeps a version you can roll back to, so a wrong headline is one click away from being the right one.

When the campaign ends, roll the page back, replace it, or leave it. Any address that no longer exists returns a branded not-found page served with a real 404 status.

Plan facts and one honest limit

A campaign page counts as one website on any plan. Starter at $99 per month allows 10 websites, so ten campaigns can run at once. Every plan starts with a 15-day free trial with a card.

There is no online store checkout on the page today. Nobody can buy the offer on the page itself; they send the form, book a time, or call, and the sale happens with you.