Revenue-weighted Demand Agent

Each week, the agent refreshes the values across the backlog. The pipeline and ARR behind a request can change as deals progress, so the ranking needs to move with them.

• Schedule: Weekly
• Scope: Every request in the backlog

Next, the agent pulls every open deal attached to a request. This connects each requested capability with the pipeline that depends on it.

• Include: Every open deal linked to a request
• Pull: The pipeline value for each linked deal

The agent then pulls ARR and pipeline from the linked accounts. Keeping existing revenue alongside open pipeline shows when a request matters for retention as well as new business.

• Fields: ARR and pipeline
• Include: Accounts linked to the requested capabilities

For each request, the agent totals the pipeline and ARR attached to it. It keeps the two figures separate, so product can see whether the value comes from open deals, existing customers, or both.

Using those figures, the agent ranks the backlog by combined pipeline and ARR. It also names any request whose position changes most when the backlog is ranked by frequency alone, keeping loudness and revenue value visible as separate signals.

Finally, the agent emails the ranking to product leadership with pipeline and ARR shown separately. They can compare how often a capability is requested with the revenue behind it before deciding what moves up the backlog.

• Recipients: Product leadership
• Include: The ranked backlog with pipeline and ARR for every request
• Include: Any request whose rank changes most based on frequency alone