Create landing pages that match your campaign goals and convert visitors into customers
This flow helps your team go from campaign brief to full landing page copy and layout in a live prototype.
Edit the sample values in the prompt to match your situation, or hit "Try it" and adjust as you go.
What you'll get
A working landing page prototype you can open directly in the browser — headline, copy, layout, CTAs, all in place. From there, the team can refine the copy, adjust the structure, or hand it off to a designer with a clear starting point instead of a blank page.
The more comprehensive your context, the better your landing pages will be – Juma references everything you include to create more accurate and on-brand content.
Once you have your landing page, these prompts help you take it further. Use any of them in the same conversation — the full context of your campaign and page carries over.
The first version is the starting point, not the finish line. This creates alternative versions so the team can test different angles — useful when presenting options to a client or setting up an actual A/B test.
Sometimes the page already exists but isn't converting. This reviews a live or draft page and flags what to fix — prioritized by impact, so the team knows where to start.
Same product, different people. This reworks the page for a new audience segment — adjusting the headline, benefit framing, social proof, and CTA to match a different set of priorities.
The prompt above works well for a one-off landing page. But if your team builds pages regularly for the same client, like new campaigns, new product launches, seasonal pushes, you'll end up describing the same brand voice, product details, and audience every time.
A Juma project saves that context. You add the client's brand, product, and audience information once, and every conversation in the project starts with that context already loaded. The landing page copy matches the client's voice from the first draft, and spinning up a page for the next campaign takes a fraction of the time.
Here's what a project setup looks like, using "Client: Juma" as an example - specifically, a landing page for the upcoming Juma Superagent launch.
Client brief: Who Juma is, what the platform does, key differentiators, pricing context, and target market. Once this is in the project, Juma doesn't need the team to explain the product; it already has the full picture. This helps with landing pages, but also with any task that touches the client's product or positioning.
Superagent brief: What the Superagent is, why marketers care, key capabilities, and how it relates to the core platform. This is campaign-level context: the specific product being launched. For the landing page, this is what the copy is about.
Brand voice guide: How Juma sounds across channels, including web and landing pages. The guide covers tone, vocabulary, what to avoid, and formatting preferences. With this in the project, the AI writes landing page copy that sounds like Juma: direct, benefit-led, confident but not salesy.
Audience profile: Who the content is for, what they care about, what frustrates them, and how they talk. Includes named segments (agency content leads, in-house marketing managers, marketing directors) so the AI can target copy to a specific group, not just "marketing teams."
The project's custom instructions connect everything. They're short - just a few lines pointing Juma to the right files.
Each line references a document in the project. If the team updates the Brand Voice Guide or adds a new product brief, the output changes to match. The instructions don't teach Juma how to build landing pages; they tell it where to find the context that makes the output feel like the client's own team wrote it.
With a project set up, the prompt shrinks. No need to describe the brand, the product, or the audience — the project already has all of that.
What changes
Juma doesn't ask clarifying questions about the brand, the product, or the audience; instead, it goes straight to writing. The copy matches Juma's voice from the first draft because the Brand Voice Guide is already loaded. The product claims are grounded in real features from the Superagent Brief, not generic AI hype. And the next landing page, for a different campaign or a different segment, is even faster, because the client context is already there.
Click "Try it" on any prompt to get real results
