Define target audience segments with per-segment messaging, competitive positioning, platform targeting, and budget allocation for any campaign launch.
Describe the campaign and the product. The flow returns audience segments with per-segment messaging, competitive positioning, platform targeting, and a budget split.
This flow builds a complete audience strategy for a specific campaign. Each segment gets a full profile: demographics, behavior-grounded psychographics, and the specific pain point the campaign solves for them. Every segment also gets a messaging framework with a core message, proof point, CTA, and messaging do-nots, so the team can brief creative directly from the document. Segments are ranked by size, conversion potential, and strategic importance, with budget weighting tied to audience priority. Platform targeting and competitive alternatives round out each segment, but the audience drives the strategy, not the channels.
Most campaign briefs allocate budget by platform: "40% to Meta, 30% to Google, 30% to YouTube." That logic follows channel economics, not audience value. An audience-first brief allocates by segment priority: "45% to Segment 1 because they represent the largest addressable group with the highest purchase intent." The platforms follow from the audience, not the other way around. When budget decisions start with who matters most, spend concentrates where conversion potential is highest, and underperforming segments get flagged before a dollar goes out.
After the full brief, sometimes one segment stands out. This prompt deep-dives into your top-priority segment with expanded messaging, detailed competitive positioning, and specific creative angles ready for a brief.
Take the top-priority segment from the brief and go deeper: expanded messaging with 3 headline variations, detailed competitive positioning against the 2 closest alternatives, and 3 creative angles we could brief to the production team.
Different budgets change which segments are worth pursuing and how aggressively. This prompt builds a side-by-side view showing how segment prioritization, platform mix, and expected reach shift between two spend levels.
Build a comparison of two budget scenarios: the original $200K and a scaled-back $120K version. Show how segment prioritization changes, which segments get cut or deprioritized, and how the platform mix shifts at the lower spend level.
The same campaign often runs in multiple regions. This prompt takes the existing audience brief and adjusts segments, messaging, and competitive positioning for a new geography, keeping what translates and flagging what needs to change.
Adapt this audience brief for the UK market. Research local competitors, adjust segment demographics and messaging for the UK audience, and flag anything from the original brief that doesn't translate. Keep the same campaign structure where it works.
A Juma Project is a shared space where the team stores everything Juma needs to know about a client. Create one project per client, add context as you go, and Juma will use what's relevant every time the team runs a flow. The more the team adds over time, the sharper every output gets.
Brand Voice Guide
How the client sounds across channels: tone, vocabulary, and what to avoid. Messaging frameworks come out in the right voice from the first draft, instead of needing rounds of tone adjustment.
Audience Baselines
Existing personas, known segments, and demographic data from past research. New campaign briefs start from proven audience knowledge instead of rebuilding segments each time.
Past Campaign Performance
What worked: top-performing segments, engagement data, conversion benchmarks by channel. This is the data that turns a research-based brief into an evidence-based one.
Channel Playbook
Which platforms the client uses, typical budget ranges, and historical benchmarks. Platform targeting sections will pull from real performance data instead of industry averages.
Brief Template
If the team's audience briefs need to follow a specific structure, sections, or formatting, upload a template or a past brief as a reference. Juma will match the structure instead of using its default layout.
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:
