A mutual action plan (MAP) or joint business plan (JBP) keeps you and your partner aligned on what needs to happen, who owns it, and by when. With Introw Tasks and Journeys you can build exactly that inside the partner portal: a shared, structured plan that runs from onboarding through every recurring milestone — visible to the right people and tracked automatically.
This article walks you through the full setup. Watch the video below for a complete walkthrough, then use the sections underneath as a reference.
Add a Tasks section to your partner portal
Your joint business plan lives in a Tasks section inside the partner portal. To add it, open your partner portal experience, click Add section, and select the rich section named Tasks.
This is a smart section: Introw dynamically fills it with the tasks linked to whichever partner the portal experience is assigned to. Each partner sees their own plan, and both you and your partner can update tasks or create new ones directly from the portal.
When you add the section you can choose which tasks to show:
A predefined set of tasks from a journey (like a set or template of tasks) — for example a complete partner onboarding flow that is identical for every partner.
Ad-hoc or standalone tasks created on the fly during the partnership — such as the follow-up items that come out of a QBR or joint business plan.
You can display both task types together in a single section so partners see one unified plan, or organize them into distinct sections of the experience — placing marketing tasks under the Marketing page and commercial or sales tasks in their respective areas.
Tip: to keep the experience clean, you can automatically hide completed tasks after a set number of days. Finished items stay visible long enough to confirm they are done, then drop off so the partner only sees what still needs attention.
Predefined plans with journeys
A journey is a predefined set of tasks you build once and apply to one or many partners. Journeys are ideal for the repeatable parts of a partnership that are the same for every partner or partner type, like for example most commonly partner onboarding.
A typical onboarding journey might include:
Agreeing on the terms & conditions
Watching a tutorial video on how to use the portal
Registering their first deal
Scheduling a QBR
Once the journey is assigned, Introw rolls out the same structured experience to every partner automatically, so nobody falls through the cracks and onboarding stays consistent at scale.
Ad-hoc and standalone tasks
Not everything in a partnership is predefined. Standalone tasks are ad-hoc items created outside a journey, perfect for one-off actions that come up while you work together — for example the follow-ups agreed during a QBR, a specific document you need from the partner, or a unique request.
With standalone tasks you can:
Create and manage tasks independently from journeys
Handle unexpected or unique partner requests as they arise
View them alongside journey-based tasks in the same plan
Filter by assignee so everyone focuses on what is relevant to them
Let partners create and assign tasks too
A joint business plan is a two-way commitment. Introw lets your partner create their own tasks inside the portal and assign them to your team members. This turns the plan into a genuinely shared workspace — if a partner needs something from you, they can capture it as a task and route it to the right person, rather than chasing it over email.
The task detail: powerful options
Beyond a name and description, every task carries a few powerful options that make your plan precise and automated.
Relative due dates
Instead of a fixed calendar date, you can set a relative due date — a number of days after the task is assigned to the partner.
Use case: the "Sign T&Cs" task should be due 3 days after assignment. If you assign it on 10 January, the due date is automatically set to 13 January, and the partner is nudged to complete it as the deadline approaches.
Relative dates are what make journeys work at scale: the same plan adapts to each partner's own start date.
Assignee — internal or partner-facing
Each task can be owned by your side or the partner's side, and partner-facing tasks can target the right people automatically based on the partner persona (role or segment):
Internal team — the task belongs to your team members.
All partner contacts — visible to every contact at the partner organisation.
Specific role — choose a role as a dynamic assignee, and only the partner contacts with that role are assigned. For example, a "Complete tax form" task can automatically land with the partner's finance contact, while a "Watch the sales enablement video" task goes to their sales reps.
Visibility
Visibility controls who can see a task, which matters in a shared plan where some items are for the partnership team only:
Public — visible to the relevant external contacts and your internal team.
Internal — visible only to your team. Use this for tasks that are key to managing the partnership but that the partner should not see.
Assignee only — on the partner side, only the assigned contact sees the task. As an Introw user you still see these tasks and can follow up on progress.
Choosing the right visibility keeps sensitive information with the right audience while keeping everyone who needs to be informed in the loop.
Running the partner journey at scale
The real power of journeys is consistency across your whole partner base. Build a journey once — agree on T&Cs, watch a portal tutorial, register a first deal, schedule a QBR — and Introw delivers that same structured experience to every partner, with relative due dates adapting to each partner's start.
You can then track completion across all partners from the Tasks overview, so you instantly see who is on track, who needs a nudge, and where onboarding is stalling — without managing each plan by hand.
To go deeper on any part of this, see Partner journeys.