Hand Juma a campaign brief and get a phased project plan: tasks, owners, due dates, and dependencies, ready to review and push straight to your board.
Describe the campaign or point Juma at the brief, and it builds the project plan: phases from kickoff to wrap, tasks under each phase, suggested owners, due dates back-timed from the launch, and the dependencies that set the critical path. It returns a branded plan and the exact task list it would set up on your board, then creates those tasks on Basecamp, Asana, monday, ClickUp, Notion, or Jira once the team confirms. More than 400 marketing teams use Juma to turn the tools they already run on into finished work, and a 10-week plan that takes an afternoon to build by hand comes back in minutes, with the critical path already flagged.
Get the plan as a network, not just a list. Juma marks which tasks can't start until others finish, then traces the longest chain to the launch date and names it the critical path. It calls out the single dependency most likely to sink the timeline, like paid social that can't build until both creative reviews are signed off. The team sees exactly which dates to protect and which delays are survivable, instead of finding out when something slips the week before launch.
Map the dependencies in this plan and show me the critical path. Which one slip would put the launch date at risk?
Juma reads the team roster in the project and assigns each task to the person whose role fits, so the plan arrives with owners already in place instead of a wall of unassigned work. A key visual goes to the designer, the hero video to the producer, paid social to the media buyer. The team reviews the suggestions and swaps names where the fit is off, then those assignments carry through to the board when the plan is pushed. New hires or freelancers can be added to the roster so they show up in the next plan.
Assign an owner to each task based on our team roster, and show me the ones you weren't sure about so I can confirm.
Once the plan looks right, Juma creates it on the board for you: phases become lists or sections, tasks land under them with owners and due dates, and dependencies carry across where the tool supports them. It shows the full task list first and waits for a yes, so nothing appears on the board until the team approves it. What usually takes an hour of copying a plan into Asana or Basecamp card by card happens in one step, and the board matches the plan exactly instead of drifting from it.
Set this plan up on our board: create the phases, add each task with its owner and due date, and show me the list before you create anything.
When a date shifts, the whole plan shifts with it. Tell Juma the new launch date or the slipped task, and it recalculates every dependent due date, keeps the phases in order, and flags any task that no longer has enough runway. The team gets an updated plan and a short note on what changed and what's now at risk, rather than editing thirty dates by hand. Push the revised plan back to the board and every owner sees their new dates in one update.
The launch moved two weeks later. Reflow the plan, update the dependent dates, and tell me what's now at risk.
A Juma Project is a shared space where the team keeps everything Juma needs to know about a client. Build one project per client and every plan Juma builds uses the same team, the same phase template, and the same working rules. Add these once and each new campaign starts from a plan that already fits how the team works.
Team Roster & Roles
Who's on the account and what each person does. With this in the project, Juma assigns owners by role instead of leaving tasks unassigned, and the plan arrives ready to review rather than ready to staff.
Project Plan Template
The standard phases and task checklists the team uses for a campaign of this type. Juma follows the template so the plan matches how the agency actually delivers, then adapts it to the specific brief.
Working Cadence & Calendar
Working days, holidays, and how much lead time each stage needs. Juma back-times the plan around real availability, so the dates hold up instead of landing review deadlines on a public holiday.
Brand Voice Guide
How the agency writes to this client. Task names and the plan summary come out in the right voice, so the plan is ready to share with the client without a rewrite.
Add a short description to each knowledge item in the project's info field so Juma knows what each file is and when to use it. For example:
Building a full campaign plan by hand takes half a day: breaking the brief into phases, writing out every task, back-timing dates from the launch, mapping dependencies, then copying it all into the board card by card. Juma returns the structured plan in minutes and sets up the board in one confirmation step. On a ten-week, multi-track campaign that's most of a working day recovered per kickoff.
The bigger gain is consistency. Every plan follows the same phase template and gets the same dependency check, so a plan built under deadline pressure is as thorough as one built with time to spare. Strategy and judgment stay human: the team reviews the plan, adjusts owners and dates, and approves it before anything lands on the board.
The plan groups the work into phases from kickoff to wrap, with tasks under each phase carrying a suggested owner, a due date back-timed from the launch, and the dependencies that connect them. It includes a milestone table of the dates that matter most, a roles list, and a critical-path callout naming the one slip most likely to move the launch. The board task list is organized by track so it maps cleanly onto lists or sections.
Because the plan is built from the brief, the level of detail matches what the brief specifies. A brief with five deliverables and three channels produces a task tree that covers each one, and the more the brief pins down, the more precise the dates and owners.
Juma creates the plan in the board the team already uses. It connects to Basecamp, Asana, monday, ClickUp, Notion, and Jira, and builds phases, tasks, owners, and due dates in whichever one is connected. There's no need to standardize the whole agency on one tool: one client can run on Asana and another on Basecamp, and the same Flow plans both.
Where a tool supports dependencies or start and due dates, Juma sets those too. Where it doesn't, the plan still carries them in the summary so the information isn't lost, and the team can add them manually if the tool needs it.
No. Juma always shows the full task list first and waits for the team to confirm before it writes anything to the board. Nothing is created until someone approves it, so the Flow is safe to run on a live client board without risk of a surprise pile of tasks appearing.
This propose-then-push pattern means the review happens where it should, before the plan becomes real work. The team edits owners, dates, or scope in the proposed list, then approves, and Juma sets up exactly what was approved. Human review sits on every change that reaches the board.
Yes. Paste the brief into the chat, or connect Google Drive or Notion and name the document, and Juma reads it directly to build the plan. It pulls the goals, channels, deliverables, and any dates the brief specifies and turns them into the task tree.
If there's no written brief yet, a short description in the chat is enough to start. Juma builds a first-pass plan from the campaign type and the launch date, and the team fills in specifics from there. Either way the plan is a starting point the team shapes, not a finished artifact to accept blindly.
Connect the client's Google Ads, Meta Ads, and GA4 accounts, name the period, and get a branded multi-channel report with scorecards, benchmark context, and a prioritised action plan.
.webp){kind=icon}
.webp){kind=icon}
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
