Project portfolio management, end to end
Eight areas covering delivery, benefits, strategy, governance, capacity, cost and change. All of it reads from the tools your teams already use, and none of it asks them to work differently.
What Portavi does
All included in the product rather than sold as separate modules.
Projects & Agile
Projects synced read-only from the tools your teams already use, read through whichever delivery method each one runs: sprints, phases, milestones or work in progress.
All plansPrograms & benefits
Group projects into programs and give each program the benefits it exists to deliver. A benefit carries a target metric, so a program is measured by what it changed rather than by whether its projects closed.
All plansPortfolios & strategy
Roll programs and projects up into portfolios, set strategic objectives against them, and run structured strategy reviews that leave a record of what was decided.
Growth plan and aboveGovernance & Risk management
Risks, lessons learned, benefits, decisions and change requests, each with its own register, above a risk heatmap and a ranking of the riskiest projects.
All plansCapacity planning
One view of everyone’s open work across every connected tool. Overload shows up before the dates slip, and what-if scenarios let you model moving work without ever writing back to your tools.
All plansBudgeting & EVM
A cost baseline with contingency inside it and management reserve outside, planned value against earned value and actual cost, cost and schedule performance indices, and a forecast at completion.
All plansChange management
Change requests raised by the owner and decided by approvers, with baselines and tolerances that turn an out-of-tolerance edit into a request instead of a silent change.
All plansAI summaries & rewriting
Written summaries on reports, an explanation of why a project is at risk, a morning digest on My Focus, and rewriting in any text field. It only ever reads figures Portavi already holds.
Growth plan and aboveProjects & Agile
Portavi reads the way each project actually runs, rather than forcing every team into one shape.
Read-only, from the tools you already use
Projects and boards, tasks and subtasks, assignees, due dates, status and completion, and sprints and phases all sync from Jira, Asana, Monday.com, Azure DevOps, ClickUp, GitHub Projects and Microsoft Planner. Portavi cannot modify anything in the source tool.
Every delivery method, one health model
A Scrum project is read through its active sprint, a Waterfall project through its current phase, a Kanban board through its work in progress, and any project through its next milestone. However a team works, the project still rolls up to the same on track, at risk or delayed.
Date suggestions
When the children of a project or program run past its own dates, a ribbon on the page proposes a new start or finish date. You accept it or you do not. Portavi never moves your dates for you.
Programs & benefits
A program is measured by what it changed, not by whether its projects closed.
Benefits with an owner and a date
Each benefit a program exists to deliver carries an owner, a target date, the projects contributing to it, and its own status. The program then reports how many of its benefits have actually been achieved, not just how many of its projects closed.
Rolled up, never averaged
Cost and schedule figures roll up across a program from summed values rather than averaged ones, so one large project in trouble cannot be hidden behind several small healthy ones.
Change control reaches program level
A program carries its own baseline finish date and budget, and a change request raised against it follows the same approval path as one raised on a project.
Portfolios & strategy
Group programs and projects into portfolios, set objectives against them, and run strategy reviews that leave a record. Objectives can be written in Portavi or mirrored from the tool your teams already keep them in.
Four goals tools
Atlassian Goals through your Jira connection, Asana Goals, ClickUp Goals, and Tability. Tability connects with a personal API token, and needs a Tability workspace on a Premium plan with API access enabled for that user.
Mirrored, not synced
Mirroring reads one way. An objective and its key results refresh on the same schedule as that tool’s projects, and on demand from the portfolio page. Edits happen in the tool, and every mirrored objective links back to it.
Key results and progress
Each key result shows one progress chart. An objective with no key results shows its own progress as a bar instead. Atlassian success metrics are read as key results.
Straight into the strategy map
Mirrored progress feeds the Strategy map and strategy reviews, where a mirrored objective is read-only and carries a link to open it in its own tool. Integration cards show how many portfolios use each goals tool.
Governance & Risk management
Five registers on one page, and one of them keeps itself.
Five registers, one page
Risks, lessons learned, benefits, decisions and change requests each get their own register on Governance, above a heatmap plotting risk impact against likelihood and a ranking of the riskiest projects by open risks and exposure.
A decisions log that writes itself
The decisions log fills from strategy reviews, sprint reviews and cadence reviews, and from risk events, so the record of what was decided is a by-product of the meetings you already run rather than a document somebody has to remember to write.
Risks raised where the work is
Every project and program page carries its own Risks, Lessons and Changes tabs, so a risk is raised beside the delivery it threatens rather than in a separate system somebody has to remember to open.
Capacity planning
Who is carrying too much, across every connected tool at once.
One person, not five accounts
The same person arrives as a separate account in Jira, Asana and the rest of your PM tools. Portavi spots the likely duplicates by name and email and suggests the merge; a PMO manager confirms it. Cross-tool capacity only works once identities do.
Overload before the dates slip
Open tasks are counted per person across every project, so someone carrying too much shows up early, alongside what is already overdue. A workload heatmap shows where the load sits.
What-if, without touching your tools
Model moving work between people and see the projected load before you commit. Scenarios are plans: Portavi never writes back to your PM tools.
Budgeting & EVM
What the delivery cost, against what it was supposed to cost.
A baseline with real reserves
Contingency sits inside the cost baseline and management reserve outside it, the way PMBOK arranges them. Every spend entry records which pot paid for it, so you can see what is left of each.
CPI, SPI and a forecast
Planned value, earned value and actual cost, with cost and schedule performance indices and an estimate at completion. Rolled up across a program or portfolio from summed values, never averaged.
Check-ins that freeze the numbers
A budget check-in snapshots budget and spend at that moment, so the trend is a record of what you reported at the time, not a recalculation after the fact.
Change management
Change requests on projects and programs: raised by the owner of the thing being changed, decided by approvers, then applied.
Five kinds of change
Scope, schedule, budget, resourcing, and other. Each request is raised by the owner of the project or program it affects.
Approvers decide in parallel
The policy is set per workspace: parent component owners, any PMO manager, or both. A project inside a program inside a portfolio needs both the program owner and the portfolio owner. Everyone decides at the same time, and one rejection closes the request.
Baselines and tolerances
Every project and program carries a baseline finish date and budget. Edit past the workspace tolerance and the edit becomes a pre-filled change request, with the field locked until that request is applied or withdrawn. Applying writes the new value and resets the baseline.
It arrives where you already work
Change requests get their own register on Governance, with search, grouping and sorting, plus a Changes tab on every project and program, actions in My Focus for decisions and applies, notifications, and an Approved changes section in status reports. Every decision is written to the Decisions log automatically.
On every plan. New workspaces start with it on; existing workspaces start with it off, and a PMO manager can switch it on at any time.
AI summaries & rewriting
Written for the reader, from the numbers already on the page.
Executive summaries, when you ask for them
On the Health snapshot and Executive summary reports, a written account of where the portfolio stands, what changed and what needs attention. It is generated when you press the button and then stored, so a report never quietly rewrites itself between two readings.
Why a project is at risk
A sentence or two under an at-risk project, connecting the actual signals (overdue ratio, sprint pace, blockers raised in chat, schedule and cost indices) into a cause. It speaks each delivery method's language: the active sprint for Scrum, the current phase for Waterfall, the next milestone, or the WIP load for Kanban.
A morning digest on My Focus
Two sentences at the top of your own page: what needs you today, and what moved on your projects overnight.
Rewrite in any text field
Rephrase, shorten or expand any Markdown field (status notes, risk descriptions, retrospectives) across a selection or the whole field, undoable in one step.
See it on your own portfolio.
Every trial runs on Growth for 14 days. No credit card required.
Start free trial