Generate structured campaign concepts for any launch: positioning angles, channel mixes, messaging, timelines, a comparison matrix, and an activation plan.
Describe what you're launching and your goals. Juma researches the brand and competitive landscape, then generates five distinct campaign concepts with angles, channel recommendations, core messages, and rough timelines. The output includes a comparison matrix to evaluate options side by side and a week-by-week activation plan for the winning concept.
Five distinct campaign concepts, each with a clear positioning angle, recommended channel mix, core messages, and rough timeline. A comparison matrix ranks every concept by reach, effort, and positioning fit, so the team can evaluate options side by side instead of debating from gut feel. The brainstorm also flags a couple of unconventional approaches in case the brief invites bigger swings. For the top concept, a week-by-week activation plan maps content milestones, media triggers, and the KPIs to track.
Most brainstorming sessions produce ideas that are hard to compare because they're described differently: one concept has a clear channel strategy but vague messaging, another has a sharp positioning hook but no sense of effort or reach. A shared structure for every concept — angle, channels, messaging, timeline — makes the tradeoffs visible before the team commits. The comparison matrix forces that structure and gives the planning conversation a concrete starting point.
The team picked a concept from the brainstorm. Now it needs a proper campaign brief to hand to a designer, media buyer, or agency partner.
Take concept 2 and develop it into a full campaign brief. Include: the campaign objective, target audience with a specific persona, key messages and proof points, channel strategy with budget split guidance, creative direction (tone, visual style, reference examples), a content calendar for the first 4 weeks, and success metrics with targets.
Good campaigns don't exist in a vacuum. This prompt pressure-tests the top concept against what competitors are likely doing and finds the gaps the team can own.
Look at our top campaign concept and stress-test it against likely competitor moves. Search for what competing products in our space are doing right now, identify where our campaign overlaps with their messaging, and suggest adjustments to make our positioning more distinctive. Flag any angles they're ignoring that we could own.
The concept works, but the budget just changed or the launch window moved. This prompt adjusts the activation plan without starting over.
Our timeline just shifted — we now have 6 weeks instead of 4, and the budget is 30% lower than planned. Rework the activation plan to fit the new constraints. Show me what to cut, what to phase differently, and where the reduced budget actually forces a smarter approach.
Campaign brainstorming improves when the AI has your brand's history. Without a project, every session re-explains the same context: your positioning, your audience, and what's performed before. A Juma Project stores it once, so every brainstorm builds from your actual data instead of generic best practices.
Brand Voice Guide
How the client sounds across channels: tone, vocabulary, what to avoid. With this in the project, campaign messaging comes out on-brand from the first draft without a revision pass.
Audience Profile
Who the team is marketing to: roles, pain points, buying journey, key objections. This shapes the angles, the channel recommendations, and the language across every concept.
Past Campaign Performance
What the team has run and how it performed. This is the file that changes concept quality the most. Instead of brainstorming from generic best practices, Juma builds on what's worked for the specific audience — which channels drove qualified results, which messages converted, which formats fell flat.
Platform Playbook
The full channel strategy: which platforms the client uses, at what cadence, and how they perform. Campaign concepts come with channel recommendations grounded in how the team actually operates, not general advice.
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:
