--- title: "How to get AI to build me a website as a marketer" url: https://howtogetaito.com/build-me/a-website/as-a-marketer/ published: 2026-09-16 updated: 2026-09-16 author: "Jack Stovell" author_profile: https://i.hilyt.it/jack publisher: "Adapt Progress Evolve" summary: "A landing page live in an afternoon without a developer: Lovable builds it from your brief, Tally emails you every lead, Cloudflare Web Analytics counts honestly without a cookie banner, and the copy sounds like your brand, not a template." tools: ["Lovable","GitHub","Tally","ChatGPT","Claude","Google Search Console"] ours: ["ScriptGrain"] disclosure: "ScriptGrain is made by the publisher." language: en-GB --- # How to get AI to build me a website as a marketer > A landing page live in an afternoon without a developer: Lovable builds it from your brief, Tally emails you every lead, Cloudflare Web Analytics counts honestly without a cookie banner, and the copy sounds like your brand, not a template. Published 2026-09-16 · Last updated 2026-09-16 · By Jack Stovell (https://i.hilyt.it/jack) · Canonical page: https://howtogetaito.com/build-me/a-website/as-a-marketer/ ## What you'll be able to do By the end of this you'll have a landing page live at a real address. It'll have a lead form that actually emails you when someone fills it in, analytics that tell you the truth about who's turning up, and the basics that let Google find it. No developer, no ticket in a queue, no "can we get to it next sprint". Just you, an AI tool, and about an afternoon. I'm not promising a masterpiece. I'm promising something that works, that you can improve, and that you own. ## Before you start Get this bit right and everything after it is faster. Get it wrong and you'll spend the afternoon arguing with a chatbot about wording instead of shipping. You need four things clear in your head before you open any AI tool: Your audience, in one sentence. Not "small businesses". Something like "freelance photographers who hate admin". Your offer, stated plainly. What do they get, and what do they have to do to get it. The words you'd actually use. Not brand-guideline words, real ones, the kind you'd say to a mate over a pint if they asked what you do. And a definition of day-one success. Is it five email signups? One call booked? Know the number, even roughly, before you build the page that's meant to hit it. If you've got a brand voice already, say from a newsletter or old website copy, keep a few paragraphs of it handy. You'll need it later. ## Get set up Three things need to exist before you write a single prompt: somewhere for the page to live, somewhere for the form to send its answers, and a way to see who's turning up. For the page itself, I'd use Lovable. It builds a working website through chat, no code required, and publishes it at a lovable.app address to start. You can point a proper domain at it later. Usage runs on credits with a free tier to get going, so check lovable.dev/pricing rather than trust a number I might get wrong here. Sign up, and before you do anything else, connect GitHub from the project's settings. This matters more than it sounds like it should: it means the actual code behind your page belongs to you, sitting in a repository, not locked inside someone else's app. Do this early. Retrofitting it later is more hassle than it needs to be. For the form, Tally is the fastest route. Free plan, no faff, and it emails you every time someone submits. It also embeds neatly inside a Lovable page. If you'd rather have leads land in something spreadsheet-like that you can filter and sort, Lovable can store form entries in a Supabase table instead, but that's more setup for not much extra benefit if you're starting out. Tally first, always. For analytics, Cloudflare Web Analytics is free and needs no cookie banner, because it doesn't track individuals. That's the one I'd start with. Plausible and Fathom are paid alternatives with the same privacy-friendly approach if you want more detail later. Google Analytics is also free, but it identifies visitors, which means you need a consent banner under UK and EU law. That's a real cost in complexity for a first page. Skip it for now. Set up a Google Search Console account too, it's free, and you'll need it in a few minutes. ## Try it yourself Right, this is the part people wait weeks for a developer to do. You're going to do it in an afternoon. Open Lovable and describe the page you want in one go. Be specific about the sections. Here's a prompt that works: ``` Build a one-page landing page for [offer] aimed at [audience]. Sections: headline stating the outcome, subhead, call-to-action button linking to #form, three short proof quotes I will paste in, a four-question FAQ, and an embedded form at #form. Real text everywhere, mobile-first, no stock photos. ``` Fill in the brackets with your own offer and audience, obviously. Lovable will build something. It won't be perfect. That's fine. From here, change one thing at a time, and describe the change as an outcome, not a technical instruction. So instead of "make the button bigger", say "make the call-to-action stand out more on mobile, it's getting lost". Lovable responds better to intent than to pixel instructions, and one change per message means you can see exactly what broke if something does. The anatomy worth insisting on: one headline that says the outcome plainly, one subhead that adds context, a call-to-action repeated at the top and the bottom of the page (people scroll, then leave, catch them both ways), proof, a short FAQ, and the form itself. Proof means real quotes or real logos. Never ask the AI to invent a testimonial. That's not proof, that's a lie with a nice font. Now, the words. This is where most AI-built pages fall flat, they sound like nothing, like a template wearing your logo. If you've got existing brand writing, feed it in. ``` Here are three pieces the brand has published. Rewrite the headline and subhead in this voice: [paste] ``` This is the bit where I'll mention ScriptGrain, which we make. It does one specific job well: it reads writing your brand has already published and works out the actual voice, then drafts new copy that sounds like it came from the same place. There's a free Reader tier, one voice profile, one analysis, one draft, no card needed, so you can see if it's useful before paying anything. Paid tiers start from £12 a month if you want more than the one draft. You don't need it, to be clear. Pasting three examples into ChatGPT or Claude with the prompt above does a decent job too, and costs nothing extra if you're already paying for one of those. ScriptGrain is worth it if you're doing this often, multiple pages, multiple campaigns, and want the voice consistent without re-explaining it every time. If this is a one-off page, the paste-and-prompt approach is honestly fine. Once your headline and copy are in, ask Lovable to wire up the form and the analytics. Cloudflare gives you a small snippet of code when you add the site in its dashboard; paste that into the prompt. ``` Embed this Tally form at #form: [paste the embed code]. Add this Cloudflare Web Analytics snippet to every page: [paste the snippet]. Make sure the call-to-action button scrolls to #form. ``` Tag any campaign links you'll be sharing (email, social, ads) with utm_source, utm_medium and utm_campaign, so when someone lands on the page you know where they came from rather than guessing. For being found, keep it simple. Make sure the page title and the first paragraph say, in plain words, what the offer is and who it's for. Search engines and humans both want the same thing here, clarity up front. And build one page per offer. Don't try to cram everything you sell onto a single landing page hoping it'll rank for everything. It'll rank for nothing. ## Check the result Don't take Lovable's word for it that this works. Test it yourself, properly, before you send anyone a link. Submit the form yourself, with a real email address you control, and confirm the notification actually lands in your inbox. Not "should land". Lands. Open the page on your phone. Not a simulated mobile view in a browser, an actual phone. Read every section. Tap the buttons. Read the headline aloud. Genuinely, out loud, to yourself or whoever's nearby and willing to listen. If it doesn't say what the product does, in words a stranger would understand, it needs rewriting before anything else matters. Then run it through Lighthouse. In Chrome, right-click the page, choose Inspect, find the Lighthouse tab, run the audit. It'll flag speed and accessibility issues you'd never spot by eye. If all four of those pass, you're genuinely ready to send traffic to it. ## If it doesn't work Three things go wrong more than anything else, and none of them mean starting again. Form submits but no email arrives. Almost always the notification setting is switched off in the form tool, or the address you typed has a typo. Check Tally's notification settings first, they're usually the culprit. Page looks broken on a phone even though it looked fine on your laptop. Don't ask Lovable to "fix the mobile version" in general terms, that's too vague and you'll get a vague fix. Go section by section: "fix the mobile layout on the FAQ section, the text is overlapping." One section, one message, one outcome. Analytics shows zero visitors even though you know people have been on the page. The script is very likely sitting on a draft version that hasn't been published yet. Republish and check again. One more thing, and it matters more than any of the above: leads are personal data under UK GDPR. Say on the form, plainly, what you'll do with someone's details. Link to a privacy policy. Keep your list somewhere with a login, not in a random spreadsheet anyone with the link can open. And never paste real leads into an AI chat. Not names, not email addresses, not anything a person gave you in confidence. If you need help analysing form responses, anonymise them first or don't use AI for that step at all. ## Keep exploring Once this page is live and working, the same approach applies almost anywhere else in your marketing that's currently stuck waiting on someone else's time. "How to get AI to build me a website" covers the wider set of routes if a landing page turns into a whole site. "How to get AI to sound like my brand" goes deeper on getting the voice right every time, and "How to get AI to teach me SEO" is the next step once the page is live and you want it found. ## Sources and review notes https://lovable.dev/pricing https://tally.so https://developers.cloudflare.com/analytics/web-analytics/ https://plausible.io/docs https://usefathom.com/docs https://support.google.com/analytics/ https://www.legislation.gov.uk/ukpga/2018/12/contents (Data Protection Act 2018) https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/ https://search.google.com/search-console/about Review date: 2026-09-16