UAE · ENBook a demo
Procure AIProductInvestigator

Feature Adoption Agent

Tracks uptake of new features and flags gaps.

Feature Adoption AgentDiscovery and Delivery
Industry
Procure AI
Department
Product
Team
Discovery and Delivery
Kind
Investigator
Approver
Head of Product
Code
PRD-10

It tracks uptake of newly released platform features, such as guided buying, catalogue punch-out, supplier self-onboarding or automated match exceptions, against their adoption targets by client and role. Where a feature lags it finds the stage users drop (discovery, trial, adoption, retention) and explains why, including client configurations that hide it, and opens a follow-up on each lagging feature. **The problem it solves:** Why a newly released platform feature lags its adoption target: at which stage users drop, for which clients and roles, and whether configuration, enablement, discovery or the feature itself is the cause.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the spend analytics warehouse: feature usage by client and role, with client configuration and enablement dates..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Weighs competing explanations against the evidence and shows which one holds up.

  5. 05Asks a person

    Hands the work to Head of Product with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the issue tracker: it opens a follow-up on each lagging feature with the cause and fix. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The feature adoption targets, release notes, client enablement status, configuration switches per client, and past adoption diagnoses.

Reads from

the spend analytics warehouse: feature usage by client and role, with client configuration and enablement dates.

Acts in

the issue tracker: it opens a follow-up on each lagging feature with the cause and fix.

Hands back

A list with one entry per feature, each with feature, target_percent, actual_percent, eligible_users, drop_stage (discovery, trial, adoption or retention), causes (a list with cause, evidence and confidence) and proposed_fix.

Asks a person when

The diagnosis proposes removing a feature, changing what a fee tier includes, or contacting client users about the feature.

ApproverHead of Product

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Default adoption target (%)25The share of eligible users expected to adopt.
Evaluation window (days)45Adoption is read this long after release or client enablement.
Lag that counts (%)25A feature this far below target is lagging.
Eligible users needed100Fewer eligible users and the read is skipped.
Count from client enablementOnWhen on, the window starts when the client switched the feature on, not at release.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • A feature is lagging when adoption is 25 percent or more below target after 45 days.
  • When on is true, each client's window starts when it enabled the feature.
  • A feature switched off in a client's configuration counts as not eligible, not as not adopted.
  • Features with fewer than 100 eligible users are not read.
  • Every cause names the stage, the evidence and the fix most likely to close the gap.

See the Feature Adoption Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Feature Adoption Agent · Procure AI | Basinwright Industries