Custom project portfolio management software development
Most organisations don't lack good project proposals; they lack the people to carry them out. Yet everything shows green: every proposal was approved separately, every project plan holds up on its own, and halfway through it turns out that the same architect, the same data provision and the same department have been booked into four plans. Portfolio management is the level at which that clash is resolved: which projects do we take on, in what order, where is the capacity, and do they deliver what the business case promised? Appfront builds custom software for that decision process, from request and scorecard to stage gate, benefits realisation and reporting to the board and supervisors.
Portfolio management starts where project control ends
Decisions about work are made at three levels, and each asks a different question. On the shop floor, it's about flow: which work do we pick up now, what is blocked, how long does it take for something to get from left to right. In a project, it's about control within a defined assignment: planning, budget, risks, milestones and delivery. At portfolio level, it's about composition: which projects are allowed to exist, which get priority, what gets pushed back, what do we stop, and are we keeping our promise to the organisation.
That last level is missing from most toolkits. There is project tooling, there is a spreadsheet with a list of projects, and there is a board meeting where that list is reviewed. What doesn't exist is a place where the request, the weighted assessment, the requested effort per role, the phase decision and the benefits after delivery are all attached to the same record. The result is predictable: the project list lives in four versions, the board sees figures that are already out of date by the time they are read out, and a decision to stop something is hard to take because nobody can see what would be freed up.
Portfolio management also only becomes interesting when resources are scarce. As long as everything is possible, there is no need to choose and a list will do. As soon as there are more proposals than delivery capacity, the question becomes one of allocation: every yes is a no to something else, even if that no is never explicitly stated. Software that makes this visible isn't administration, it's a decision-making tool.
In practice, there are four kinds of users of such a system, and each wants something different. The requester wants to know where their proposal stands and what is still expected of them. The portfolio manager or PMO maintains the list, gathers assumptions and prepares the decision round. The team lead or resource manager is asked to commit capacity that they also need for line work. And the board makes the decision, and wants the shortest view that is still usable. A portfolio system that serves only one of these four well will be bypassed by the other three, and then the list is incomplete again after a single round.
Are you in the right place? This page is about the level above the project. If you want to control a single project, with planning, budget, milestones and time tracking within that one assignment, you belong at custom project management software. If it's about the shop floor, about boards, columns, blockers and how long individual work items are in progress, that is the level below the project and not what is described here. This page is about the question of which projects exist, not about how you execute one.
The sheer number is the problem
Each proposal is defensible on its own. The damage lies in the sum: too much concurrent work slows everything down and nothing gets finished.
Capacity is a shared pool
Projects share the same specialists with each other and with line work. That pool is allocated at portfolio level, or not at all.
Benefits come after delivery
The project ends at go-live; the promise made in the business case only begins then. Someone has to keep measuring whether it comes true.
Choosing between projects that all seem urgent
Ask a board which of the current projects has the highest priority and the answer is often that all four are important. That isn't unwillingness; it's the absence of a shared yardstick. Without one, whatever comes in loudest wins: the customer threatening to leave, the regulator with a deadline, the manager who presents best. Urgency crowds out importance, and the maintenance nobody turns up to defend slips to the back by default, until it returns as an outage.
A portfolio also consists of more than projects that someone wants. It contains work that has to happen because a rule or a contract demands it, work that has to happen because a system has reached end of life, and work that moves the organisation forward. These three categories compete for the same people, but can't be compared using the same arguments. A mandatory project loses every discussion about return and wins every discussion about risk. As long as that difference isn't built into the assessment, you are comparing apples with obligations.
A scorecard that steers the conversation rather than settling it
What works in practice is a scorecard that is agreed in advance, away from the heat of any individual proposal. It contains the criteria your organisation genuinely applies: contribution to strategic goals, expected benefits and how firm they are, risk if it doesn't happen, dependence on other projects, mandatory basis, and feasibility given the people who have to do the work. Each criterion gets a weighting, and that weighting is a strategic decision the board takes once rather than anew for every proposal.
The software doesn't calculate the decision. What it does is make the assessment reproducible: who gave which score, what assumption it rests on, and what happens to the ranking if an assumption changes. That last part is the most valuable. Halve the estimated benefit of the highest-scoring proposal and see whether it still tops the list; double the estimated effort and see what falls out of the plan. A sensitivity view like that moves the discussion from opinions to assumptions, and assumptions can be discussed.
Just as important, the scorecard shows where assessors disagree. Two people who give the same total based on opposing scores appear to agree but don't. A portfolio round that only shows totals misses exactly the place where the conversation is needed. That is why the system keeps the scores per criterion and per assessor, with the rationale alongside, even after the decision has been made. In a later round you can then trace why a proposal did or didn't go ahead at the time.
Dependencies determine the sequence
A ranking by score alone is not yet an executable sequence. Projects are linked to one another. One delivers an integration that another is waiting for, two initiatives touch the same core system and can't go live at the same time, and a third can only start once a register has been cleaned up. If you don't record those links, you end up planning a portfolio that fits on paper but keeps stalling in delivery, after which the delay is laid at the door of the project managers.
Every proposal should therefore come with two questions that, together, go a long way: which project must be finished before this one can start, and which project gets into trouble if this one is postponed or stopped. The answers sometimes shift the ranking considerably, because a middling-scoring proposal that blocks three others belongs at the front, while a high-scoring proposal that is waiting on something else does not. Here too, the system calculates nothing. It makes the chain visible, including the point where a delay ripples through to projects nobody associated with that decision.
Saying no without alienating the requester
A portfolio that can only give the green light is not a portfolio. Yet saying no is organisationally expensive, which is why it often happens in disguise: the proposal is approved and then gets no people. That is the worst outcome, because the requester keeps counting on something that is not happening, and the project takes up a slot in the reporting without making any progress. A better approach is an explicit status: rejected with a reason, put on hold until a named condition is met, or under review with an expected start round.
Putting something on hold requires its own administration. A proposal waiting for the replacement of a core system should automatically return to the agenda as soon as that replacement is complete, together with the original justification and the question of whether it still holds. Without that mechanism, good work disappears into an archive and comes back as a new proposal, reassessed by people who were not part of the first round. Finally, reprioritising needs a fixed rhythm. A portfolio that is only reviewed at budget time is a snapshot for the rest of the year that nobody dares touch.
What portfolio management software needs to do
These six components are not separate modules but a chain. A scorecard without a capacity view produces a ranking that cannot be delivered. Capacity without stage gates gives insight without intervention. Stage gates without a benefits register lead to decisions whose outcome is never fed back. Without the reporting layer, everything stays stuck in the system and leadership keeps relying on a spreadsheet.
What you do not want to build here is just as important. A portfolio layer does not need to be a task list, document management or a second time-tracking system. It should read project data from the systems where the work already happens, and store only what arises at portfolio level: the request, the assessment, the decision, the committed resources and the benefits. That separation keeps the data-entry burden low, and data-entry burden is the main reason portfolio systems fall into disuse after the first round. Every piece of data a project manager has to enter twice is a piece of data that will eventually be wrong in at least one of the two systems.
Single point of intake
Every idea comes in the same way, with a minimal justification, a requester and a category, so the list is complete before choices are made.
Weighted scorecard
Criteria with an agreed weighting, scores per assessor with justification, and a ranking that can be recalculated when an assumption changes.
Capacity demand per role
The requested effort of all projects and line work added together per role and per person, with overbooking visible before the plan is fixed.
Stage gates with a decision file
The same questions, the same documents and a recorded decision at every gate: proceed, adjust, put on hold or stop, with who signed off.
Business case and benefits register
Every benefit with an owner in the line organisation, a measurement definition and a baseline, so the promise can still be checked after delivery.
Portfolio reporting and scenarios
One view for leadership and oversight, with the ability to run a scenario before anything changes in the actual planning.
Capacity is the real constraint, not the budget
In many organisations, money is the scarcest resource in the portfolio. Budget can be shifted, people cannot. An approved amount does not produce an enterprise architect, an experienced product owner or an administrator who will take over later. Yet in most cases the portfolio is steered by money, because money has a unit everyone understands and the availability of people does not seem to have one. That is precisely where the delay arises that is later blamed on the projects.
The pattern is a familiar one. Each project budgets neatly for the effort it thinks it needs, and every plan holds up on its own. Add them together, though, and you find that five plans each claim a fifth of the same specialist, that the same specialist also handles maintenance, and that nothing has been set aside for incidents. A portfolio like that isn't tight, it's demonstrably unachievable, and that was visible before the start. Adding things up is technically trivial and organisationally hard, because it makes visible that choices have to be made.
There is another loss that nobody plans for. Someone working on four projects at once loses effort to switching, to catching up and to getting back up to speed after every interruption. At portfolio level, that is an argument for doing less at the same time and more in sequence: the same work, the same people, but finished sooner and with fewer half-completed projects on the books. Software helps by showing concurrency per person, not just total utilisation.
Almost every portfolio also has a handful of people everything runs through: the architect who has to see every design, the sole administrator of a core system, the lawyer who reviews every contract. They determine what the portfolio can actually handle, and they are precisely the ones missing from a capacity overview built around departments. Such an overview reports spare room in the team while the person holding the key is already overloaded. It pays to track these roles separately and to have the same conversation about them as you would about money: who gets them, for what, and what gets pushed back as a result. That conversation also leads to the only structural fix, which is making what currently sits in one person's head transferable.
From available hours to actual availability
A capacity picture based on gross availability promises effort that isn't there. Leave, sickness absence, training, meetings and the line work that carries on while the project runs all come off the contractual time. What remains is net project time, and in practice that is well under half for people with a maintenance role. A portfolio built on gross hours will therefore fall behind structurally, even if nothing has gone wrong.
In practice it works at two speeds. For proposals that haven't started yet, you plan at role level: so much effort from an integration specialist, so much from a tester, no names. Once a project is through the gate, that is replaced by the people who will actually do the work. Both views need to exist side by side, because the first is needed to choose and the second to deliver. Then compare planned effort with the effort actually booked: that difference tells you whether your estimates are right, and it corrects the next portfolio round better than any resolution can.
For the detailed side of planning, rostering and scheduling operational work, a portfolio system is the wrong tool. That belongs in custom planning and scheduling software, or, for rosters, in workforce planning software. The portfolio doesn't need to know who is on duty on Tuesday afternoon, only whether the whole thing fits.
- Effort required per role, summed across all projects
- Line work and maintenance included, not just project hours
- Net availability instead of contractual hours
- Key people tracked separately as a portfolio constraint
- Concurrency per person visible, not just totals
- Planned effort set against booked effort as a correction
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Stage gates, benefits and the decision to stop
In most organisations, the business case is an entry ticket. It is produced to get approval, and after that nobody looks at it again. That is a pity, because the assumptions on which approval rests change during delivery: the scope shifts, a supplier drops out, the market moves, the benefit turns out smaller or larger than expected. A business case that is recalculated at every stage gate with what you know now is a steering instrument. A business case that disappears into a folder after approval is just paper.
Stage gates give that recalculation a place to happen. The idea is old and proven: split a project into phases and put an explicit decision at the end of each one, always with the same questions and the same documents. Is the original rationale still valid, does the estimate still hold, are the risks manageable, is the capacity there, and does it still deliver enough to justify the rest of the investment? Methodological frameworks work this out differently, from the phased decision model used in product development to the stage transitions in common project methods and the international guidelines on portfolio management. The form matters less than the discipline: the same questions, every time, even when the answer is bad news. In the public sector, external review comes on top of this. The Adviescollege ICT-toetsing (the Dutch Advisory Board on ICT Assessment) is an independent body established by law that advises the cabinet and parliament on the risks and chances of success of ICT projects within central government, and its advice is public.
A gate with only one possible outcome is not a gate. The decision has to be a real one: continue as planned, continue with an adjusted scope, hold until a condition is met, or stop. That last option is the hardest decision in any portfolio, and not because the figures are unclear. Money has already been spent, people are tied to the project and someone has put their name to it. Software does not take that pain away, but it can frame the question cleanly: not what it has cost so far, but what it will still cost compared with what it will still deliver, and which people become available for the projects now waiting. That makes stopping a portfolio decision with an upside rather than a loss announcement.
Between two gates, the forecast should keep moving. A project that issues an estimate at the start and leaves it untouched until delivery is not reporting a forecast but a wish. A revision at every round is more useful, with the reason alongside it and what the figure said last time next to it. That builds a learning dataset that makes the portfolio smarter: which types of project are structurally estimated too optimistically in your organisation, where bad news is reported late, and which risks recurred across several projects. Risk also deserves its own view at portfolio level. Five projects that each take an acceptable risk on the same supplier, the same platform or the same department together form a concentration that none of the five project risk registers shows. Adding up similar risks like this is typical portfolio work.
Benefits realisation starts after delivery
The promise in a business case is almost never about software. It is about less manual work, fewer errors, faster response, lower absenteeism, better-founded decisions. Those outcomes only materialise once the organisation starts working differently, and so after the moment at which the project proudly closes. That is why the project manager is the wrong owner for a benefit: they are no longer there when it is supposed to appear. Benefits land in the line organisation, so each benefit needs an owner in the line.
Three things make a benefit verifiable: a measurement definition that leaves no room for interpretation, a baseline measurement taken before anything changed, and an agreed moment at which you measure again. Without a baseline, every later result is merely an assertion. Watch out for double counting here: if three projects all claim the same saving in the same department, that saving appears three times in the portfolio report and once in reality. A benefits register that records where each benefit lands prevents this. Soft benefits are welcome to take part, provided they are labelled as soft and not quietly added to a total that contains hard figures.
Finally, benefits realisation only works if the benefit lands somewhere it will be noticed when it fails to appear. In practice, that means a link to the budget of the department claiming the benefit: what the business case lists as a saving should come back in the next budget round as lower costs or as headroom that is deployed elsewhere. If that link is missing, the benefit is an argument used only at approval and binds no one afterwards. Software cannot enforce that link, but it can keep the promise, the owner and the measurement together, and put the question to the right person at the right time.
What executives and supervisors actually need
Executives do not ask for more detail, they ask for meaning. A portfolio report that mostly shows coloured dots invites optimism: nobody puts their own project on red, so everything stays amber until it is too late. A more useful view shows movement: what has changed since the previous round, which forecast has been revised, which assumption no longer holds, and which decision is now being asked of the board. That calls for a single set of figures drawn from the same system as the project administration, not a presentation assembled by hand whose origin can no longer be traced after two steps.
For a supervisory board, traceability comes on top of that. It must be able to establish which decision was taken when, on the basis of which documents and with what justification, even after the people involved have left. A portfolio system that stores decisions and versions delivers that trail as a by-product. If you want to tackle the reporting layer as a topic in its own right, a custom KPI dashboard is the natural fit. If it is specifically about large capital investments with contract management and forecasts per investment, software for investment projects is the closer match.
When an off-the-shelf package is the better choice
Portfolio management is not a blank spot in the software market. Mature packages exist in three forms: a portfolio module on top of project tooling you already use, a standalone portfolio suite, and portfolio functionality within a broader package for administration or IT management. For some readers of this page, such a package is the wiser route, and we would rather say so here than halfway through a quoting process.
If your decision-making follows the usual pattern of request, weighted assessment, capacity check, stage gate and portfolio reporting, you buy that off the shelf, including maintenance and new versions. Your effort shifts from building to configuring, and with portfolio software that is a considerable effort. Be honest, though, about the cause of the problem. If the core issue is that the board does not make choices, that requesters present their benefits as better than they are, or that nobody prepares the portfolio round, no system will fix that. Software makes discipline visible and enforceable, but it does not create it.
Custom software pays off in fewer situations than vendors suggest. The strongest reason is a weighting model that is genuinely your own. Think of a healthcare organisation that weighs projects against available treatment capacity, a grid operator bound by statutory deadlines and safety obligations, or an organisation where grant conditions and co-financing help determine what may start and when. Forcing that kind of logic into an off-the-shelf form removes precisely the distinctive part of the decision.
The second reason is a portfolio that has to weigh more than projects. If project work competes with operations, production capacity, a fleet or the staffing of a primary process, the assumption behind many packages, that everything can be modelled as a project, is exactly the problem. The third reason is integration: portfolio figures are only reliable if they come from the source, such as the financial administration, time registration, HR data and project tooling. If the package has to be the leading system in all those cases, you end up building integrations against the grain. If the trade-off mainly hinges on control and risk, IT risk management software is a related starting point.
With us, such a conversation usually starts not with a functional list but with your current project list on the table. In one round, that usually shows where the pain is. If it contains work that should have been stopped long ago, the decision process is the issue. If the benefits of most projects cannot be expressed in a number, it starts with the business case. If the list is accurate but nobody dares to reprioritise it, the issue is reporting and authority, not functionality. Starting from the complaint rather than the module list prevents you from building a system that neatly records what is not happening.
The downside is part of the picture too: with a custom build, further development and keeping up with changing reporting requirements fall to your own organisation. The middle road is often the best answer: the package for project administration and delivery, custom software for the portfolio layer where choices are made, weighed and accounted for.
- Package if your decision process follows the usual pattern
- Package if portfolio discipline still has to grow
- Custom if you have your own weighting or prioritisation logic
- Custom if not all work is a project
- Custom if the figures must come from your own source systems
- Middle road: package for delivery, custom for the portfolio layer
Frequently asked questions about portfolio management software
Project management is about delivering a project that has already been approved: planning, budget, risks, quality and delivery within that single assignment. Portfolio management is about which projects are allowed to exist, in what order and at what cost, given scarce people and a strategy. The portfolio chooses and reprioritises, the project delivers. If you are looking to manage a single project, custom project management software is a better fit.
With a scorecard that is set in advance and gives each criterion an explicit weighting: contribution to strategic goals, expected benefits, risk, dependencies, mandatory basis and whether the people needed are available. Software does not calculate that decision for you, but it shows where the scores diverge and which assumptions drive the outcome. The discussion then focuses on those assumptions rather than on who lobbies the hardest.
Because every project counts on people it doesn't have exclusively. Five plans that each ask for a fifth of the same architect add up on their own, but together they become unworkable as soon as someone drops out or line work takes priority. Portfolio software adds up the requested effort per person or role across all projects and line work, and shows the overbooking before the portfolio plan is approved.
Not the project manager, because they are gone as soon as the project is delivered. Benefits land in the line organisation, so each benefit should have an owner there, with a measurement definition, a baseline and an agreed measurement point. Without those three, benefits realisation is just an intention. Software helps by keeping the benefit open after delivery and continuing to prompt the owner, even when the project has already been closed administratively.
Often yes, and for some organisations it is the wiser route. Mature PPM packages exist, from portfolio modules on top of existing project tooling to standalone portfolio suites. If your decision-making follows the usual pattern of request, scorecard, stage gate and portfolio reporting, you buy it in and your effort shifts from building to configuring. Custom software pays off if you have your own prioritisation logic, or a portfolio that has to weigh other work alongside projects.
The source code and documentation belong to the client and are kept in a repository you have access to yourself. Handover includes a description of the architecture, the data models, the integrations and the deployment, so that another party can take over without having to reverse-engineer anything first. We work with mainstream technology, because that determines how many parties can pick up the maintenance.
Related services
Custom project management software
If you don't want to choose between projects but to deliver one well, with planning, budget control, milestones and time tracking within that assignment, then custom project management software is the right level.
Software for investment projects
If it is mainly about large capital investments, with budget control per investment, contracts and forecasts up to delivery, then software for investment projects is a closer fit.
Custom KPI dashboard
If the reporting layer is your real question, with a single view for management and supervisors drawn from the source systems, then a custom KPI dashboard is the direct way in.
Compare your portfolio with your capacity
Tell us how a project proposal gets approved at your organisation, who allocates the scarce specialists, and what happens when a project no longer achieves its business case. Those three answers usually show whether a package, custom software or a combination fits best, and which part of the portfolio process you want to put in place first.