microsoft / microsoft/Power-CAT-Copilot-Studio-Kit

Feature request: Associate Multiple Value Drivers to Agents

Open
#820 0 comments 0 reactions 1 assignee View on GitHub

@psimolin is already working on this.

Since Aug 25, 2026.

enhancement
Dominant language
TypeScript
Stars
450
Forks
95
Avg merge
26m
Merged PRs (30d)
5

Description

Problem statement

User Story

As an Agent Owner or Business Sponsor, I want to define measurable value drivers against an agent so that I can demonstrate business outcomes and ROI.

Problem

Most agent implementations struggle to demonstrate realised value.

Organisations frequently build agents for:

  • Time savings
  • Cost reduction
  • Revenue growth
  • Risk reduction
  • Improved customer experience

Today these outcomes are often tracked manually outside the Agent Kit.
Or sadly not tracked at all!

Justification

Executive stakeholders frequently ask:

  • Why does this agent exist?
  • What benefits are being generated?
  • Is the investment justified?
  • Which agents are delivering the most value?

This will allow the CoE to calculate the total benefit to the business that Copilot Studio is bringing. This can further justify additional M365 Copilot and Copilot Credit uplift.

Proposed solution

Proposed Approach

Tables

Create a 2 new Dataverse tables

Value Driver Definition

  • Name
  • Description
  • Unit
  • Currency
  • Active Flag

Agent Value Driver

  • Agent
  • Value Driver
  • Value Per Execution
  • Confidence Level
  • Measurement Method
  • Approved By
Features
  • Drill into an Agent to set these values within the Power App
  • Set by Makers and approved by Admins - avoid any silly value drivers that are not accurate
  • Multiple value drivers per agent
  • Custom value drivers
  • Historical revisions
  • Changes to value that are point in time. Eg, Agent is updated and now saves more time. Don't skew the value numbers prior.
Additional context

Suggested Value Types

Productivity

  • Hours Saved
  • Task FTE Reduced

Cost

  • Cost Saved
  • Operational Cost Avoided

Revenue

  • Revenue Generated
  • Revenue Influenced

Risk

  • Incidents Avoided
  • Compliance Improvement

Customer Experience

  • Customer Satisfaction Improvement
  • Response Time Reduction

Custom

Tenant-defined value types.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.