B2B SaaS Homepage & Landing Page Prompt

A full B2B SaaS page runs from the hero to the FAQ:

• Header and hero: headline, subheadline, CTA, visual and trust logos.
• Why teams choose you: a short intro and three key advantages.
• Core features: three to five product areas.
• For each area: what it does, what it replaces and the outcome.
• Who it's for, a mid-page CTA and use cases.
• Comparison or consolidation, testimonials and results.
• Setup steps, pricing and an FAQ.

Most pages need only some of these. Keep the sections that matter most for the page's goal, and order them by the questions your buyers ask. The Landing Page Builder Prompt includes this structure with example headlines.

A homepage tells the full story of your product to every kind of visitor, so it uses most sections, from features and use cases to pricing. A campaign landing page serves one audience and one goal, so it keeps only the sections that move that visitor to act.

A demo request page, for example, might keep the hero, key advantages, proof, setup steps and FAQ, and drop the use case grid and pricing. The Landing Page Builder Prompt works for both: start from the full structure and remove what the page does not need.

Web-ready copy grouped into labeled sections, such as hero, social proof, benefits, how it works, proof and CTA, so it maps straight onto a wireframe:

• Paragraphs of one to three lines.
• Bullets where they help.
• H1 to H3 headlines and subheads.
• CTA button copy.

The Landing Page Builder Prompt asks for this format, so you can compare the draft with your design and swap sections in or out.

Start with your customer or niche fundamentals and any survey data, since landing page copy works best when it uses the persona's own language, pains and goals. Anchor each section in a pain point from that research.

If you have them, add case studies, testimonials and performance data too, so the assistant can use real proof in place of placeholders. Our Customer Persona Template gives that research a structure.

Give the assistant real proof and check every claim. Ask for metrics, case studies, testimonials and logos, and have the assistant use placeholders where none are available. Treat example figures, such as savings or adoption stats, as illustrations only.

Watch for urgency and selectivity lines, such as how many teams you work with each quarter. Keep those only if they are true for your product, and replace every placeholder with real proof before the page goes live. The Landing Page Builder Prompt uses placeholders this way.

Yes. WeGrowth's Landing Page Builder Prompt is free. It is a Google Doc: make a copy, fill in the placeholders and paste the prompt into your AI assistant. You can also download your copy as a Word file with File > Download > Microsoft Word (.docx).