Collect what the business needs

The application portfolio is the queue of what the business is asking for: every submitted need, its department, its complexity, and the duplicates Maleus found on its own.

In the appApplication Portfolio

On this page

What you see
Duplicate detection
Three ways to read the backlog
Getting the backlog out
Where submissions come from

Most of the work of an internal software team starts before any project exists: somebody, somewhere in the company, has a painful task and no way to ask for a fix. The Application Portfolio is where those asks land, so they stop living in inboxes and hallway conversations.

It sits at the workspace level, under Control center › Application Portfolio › Requests.

What you see

The Application Needs page: the counters, the duplicate banner, and the list of submitted needs — Every need the business submitted, with what it is about and how far along it is.

The header counts the whole backlog: how many needs were submitted, by how many authors. Below it, five counters split that total by state.

Counter	What it means
Total submitted	Everything in the backlog, whatever its state.
New	Submitted, nobody has looked yet.
In review	Somebody picked it up.
With AI	The submitter thinks the solution would need artificial intelligence.
Duplicates	Needs that overlap something already submitted.

Each row carries the title, its author and date, the department it came from, an estimated complexity, an AI tag when relevant, and a status: New, In review, Accepted or Rejected.

The filter row narrows the list by department, complexity, AI and status.

Duplicate detection

Maleus compares submissions and groups the ones that overlap. When it finds any, a banner sits above the list: {n} overlapping groups detected automatically. Merge them before anyone starts building twice.

Follow See the analysis and you land on the Analytics tab.

The Analytics tab: needs per department on the left, the overlapping groups with their similarity scores on the right — Where the asks come from, and which ones are the same ask twice.

Overlapping needs lists each group with a similarity score and the submissions inside it. Merge these needs folds them into one, so the department sees a single thread instead of two half-answers.

Similarity is a signal, not a verdict. Two needs can score high and still be genuinely different. Read both before merging; merging is how you decide, not how Maleus decides for you.

Three ways to read the backlog

List is the working view: one row per need, filtered the way you like.
By department groups the same needs by where they came from. Useful when you are deciding who to go talk to.
Analytics is the distribution plus the duplicate analysis.

Getting the backlog out

Export backlog downloads every need currently matching your filters. Widen the selection first if you want the whole thing, since the export follows what is on screen.

Where submissions come from

Needs are not created here. They are submitted by the business through a separate, restricted surface, and reviewed here. Open the submission space takes you to it. See Submit an idea.