Build a complete landing page from any campaign brief with hero headline, benefit sections, social proof, CTAs, and copy structured for designer handoff.
Share the product, the campaign goal, and the target audience. The flow produces a complete landing page: hero headline, benefit sections, social proof placement, and CTAs tied to the conversion goal. The output is structured for handoff to a designer or direct import into a page builder.
A landing page built with this flow covers the full structure: a hero headline and subheadline, a benefit section that speaks to the target audience's specific priorities, a social proof section with placement recommendations, and a final CTA tied to the conversion goal. The output arrives section by section, formatted as copy ready to hand off to a designer or drop into a page builder like Webflow or Unbounce. If details are missing, the flow asks before writing, so the page is grounded in the actual campaign rather than generic assumptions.
A landing page converts when every element closes the message-match gap: the headline mirrors the ad or campaign that brought the visitor there, the benefit copy speaks to the specific objection that audience brings to the page, and the CTA names the action clearly. "Buy the Education set" outperforms "Shop now" because it tells the visitor exactly what they're agreeing to. The flow surfaces these distinctions for each specific audience and goal rather than applying a one-size-fits-all formula.
The first version is the starting point, not the finish line. This prompt generates two alternative versions with different headline angles, hero approaches, and CTA copy — useful when presenting options to a client or setting up an actual split test before committing to a direction.
Create two alternative versions of this landing page for A/B testing. Change the headline angle, the hero section approach, and the CTA copy. Keep the same offer and audience — we want to test messaging, not strategy. For each variant, note what hypothesis we're testing.
When the page already exists but isn't hitting conversion targets, this prompt reviews a live or draft page and returns a prioritized list of fixes across copy, layout, CTA, and trust signals. Changes are ranked by impact so the team knows where to start.
The client's current landing page is getting traffic but converting at around 1.2% — our benchmark is 3%. Review the page and give us a prioritized list of fixes — copy, layout, CTA, trust signals — with the highest-impact changes first. Here's the page: [paste URL or page copy]
Same product, different people. This prompt reworks the page for a new audience segment, adjusting the headline, benefit framing, social proof, and CTA to match a different set of buying priorities. It flags anything from the original that doesn't translate.
Take the landing page we built and adapt it for a different audience: teachers and school administrators buying classroom supplies. Adjust the headline, benefit framing, social proof, and CTA to speak to their priorities — curriculum alignment, bulk purchasing, and measurable learning outcomes. Flag anything from the original that doesn't translate.
Landing pages repeat throughout the year: new campaigns, product launches, seasonal pushes, all for the same client. Without a shared foundation, every new page means re-explaining the voice, the positioning, and who the page is for. A Juma project saves that context once, so every page after that starts with what's already there.
Client Brief
Who the client is, what they do, and how they position themselves. With this in the project, the page copy uses the right product language and competitive framing from the first draft, without the team having to explain the basics each time.
Campaign or Product Brief
What the specific launch or campaign is about: the product, the offer, the angle, and any messaging constraints. This context changes per campaign, so the project loads the current brief before each build.
Brand Voice Guide
How the client sounds on web and landing pages: tone, vocabulary, what to avoid. With this in the project, the copy matches the client's voice from the first draft and doesn't need tone corrections before handoff.
Audience Profile
Who the page is for: roles, priorities, objections, and how they talk. This shapes the benefit framing, the social proof choices, and how direct or technical the copy should be.
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
