Optimize license seat portfolio

Choose integer license packs across aggregate seat pools under coherent demand, on-demand price and capacity scenarios; explicitly price unused and unserved seats, enforce budget, coverage and CVaR gates, and disclose exact versus deterministic supported-set search.

What it's for

Converts license sprawl into an auditable purchase portfolio that balances committed discounts against overflow capacity, unused seats and business interruption.

What you give it

Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

Field Type Role Required
license_offers array of objects (6 fields) ≥ 1 item Evidence Yes
max_detail_rows integer ≥ 1, ≤ 500 Numerical control Optional
maximum_cvar_total_cost number ≥ 0 Your calibration Optional
maximum_exact_states integer ≥ 2, ≤ 1000000 Numerical control Optional
maximum_license_budget number ≥ 0 Your calibration Optional
minimum_demand_coverage_probability number ≥ 0, ≤ 1 Your calibration Optional
risk_aversion number ≥ 0 Your calibration Optional
scenarios array of objects (2 fields) Evidence Yes
seat_pools array of objects (5 fields) ≥ 1 item Evidence Yes
tail_probability number > 0, ≤ 0.5 Your calibration Optional

Each license_offers record

Field Type Required
cost_per_pack number (≥ 0) Yes
id string (non-empty) Yes
maximum_packs integer (≥ 0, ≤ 100) Yes
minimum_packs integer (≥ 0, ≤ 100) Yes
pool_id string (non-empty) Yes
seats_per_pack number (> 0) Yes
Example input
{
  "license_offers": [
    {
      "cost_per_pack": 450,
      "id": "annual-50",
      "maximum_packs": 3,
      "minimum_packs": 0,
      "pool_id": "engineering",
      "seats_per_pack": 50
    }
  ],
  "minimum_demand_coverage_probability": 0.95,
  "scenarios": [
    {
      "id": "base",
      "probability": 0.7
    },
    {
      "id": "growth",
      "probability": 0.3
    }
  ],
  "seat_pools": [
    {
      "id": "engineering",
      "on_demand_seat_capacity_scenarios": [
        100,
        100
      ],
      "on_demand_seat_cost_scenarios": [
        12,
        15
      ],
      "seat_demand_scenarios": [
        80,
        120
      ],
      "value_per_unserved_seat": 200
    }
  ]
}

What you get back

This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.

Example output
{
  "decision": "purchase_governed_license_seat_portfolio",
  "failed_gates": [],
  "guardrails": [
    "Seat demand must mean privacy-safe eligible aggregate usage under one product/feature definition and forecast vintage; named-user surveillance, presence, keystrokes, or commit volume are not license need.",
    "Pool-specific offers avoid double-counting shared entitlements; enterprise pools, transfer rights, minimums, true-ups, tiers, taxes, credits, and termination terms must match executable quotes.",
    "Unserved value is an organization-owned opportunity or continuity cost, not permission to force adoption or a score of employees who do or do not use a tool.",
    "Heuristic mode has no global certificate, and the output does not authorize purchase, renewal, cancellation, access removal, employee monitoring, or vendor action."
  ],
  "method": "stochastic_integer_license_seat_portfolio_v1",
  "scenario_diagnostics": [
    {
      "probability": 0.3,
      "scenario_id": "growth",
      "total_cost": 1200,
      "unserved_seats": 0,
      "unused_reserved_seats": 0
    },
    {
      "probability": 0.7,
      "scenario_id": "base",
      "total_cost": 900,
      "unserved_seats": 0,
      "unused_reserved_seats": 20
    }
  ],
  "selected_license_offers": [
    {
      "committed_cost": 900,
      "offer_id": "annual-50",
      "pack_count": 2,
      "pool_id": "engineering",
      "reserved_seats": 100
    }
  ],
  "solver": {
    "evaluated_plan_count": 4,
    "global_optimality_certificate": true,
    "maximum_exact_states": 100000,
    "method": "exact_integer_enumeration",
    "nominal_state_count": 4
  },
  "summary": {
    "committed_license_cost": 900,

Truncated for display — the full payload is 59 lines.

How it works

Constrained optimization — Pick the best feasible option under real limits — budget, headcount, dependencies, capacity — rather than ranking a list and hoping it fits.

  1. 1 Define privacy-safe aggregate entitlement pools, coherent demand and on-demand scenarios, business value of unserved demand, and executable pack offers with minimum and maximum quantities.
  2. 2 Enumerate integer portfolios inside the declared state boundary or use deterministic forward addition, dispatch committed seats before bounded on-demand supply, and price commitment, overflow and denied demand.
  3. 3 Select expected-plus-tail-risk cost subject to purchase budget and demand-coverage policy, and expose unused seats, unserved seats, solver coverage and bounded scenario evidence.

Before you trust it

Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.

Assumptions & guardrails

  • Objectives use commensurable locally governed value units, constraints reflect real feasibility, and uncertainty covers plausible adverse inputs.
  • Demand means eligible aggregate use at a consistent grain; offers are executable and pool-specific; transfer, tier, true-up, tax and termination terms are represented; on-demand capacity and unserved value are locally governed.
  • The recommendation is optimal only for its stated objective, feasible set, evidence, and solver guarantee; it is not a universal management optimum.
  • Seat demand must not be inferred from surveillance, presence or commit volume; heuristic mode lacks a global certificate; this output does not authorize purchase, cancellation, access removal or individual performance action.

Minimum evidence

  • seat_pools: at least 1 rows/items
  • license_offers: at least 1 rows/items
  • scenarios: required and organization-defined

How to validate it

Backtest the chosen action against simple feasible baselines on held-out scenarios, sweep costs/constraints/risk tolerance, and require constraint feasibility under adverse inputs.

Calibrating it to your org

Same for everyone

The mathematical kernel, validation rules, method version, and JSON output semantics are organization-independent; no tenant-trained coefficients or company benchmark is embedded in the function.

Specific to you

  • privacy-safe tenant application-usage forecast joined to eligibility, entitlement rights, transfer/true-up mechanics, executable quotes, continuity requirements and finance-approved business impact
  • aggregate pool and active-use definitions, privacy floor, forecast vintage/scenario law, quote/currency/tax/term, transfer and tier semantics, unserved value, purchase budget, coverage/CVaR/tail/risk gates, exact-search boundary and procurement authority

Calibration workflow

  1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
  2. 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
  3. 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
  4. 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
  5. 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
  6. 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.

Call it from your AI

You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.

gitrevio_capabilities_search
  { "q": "choose integer license packs across aggregate" }
  → finds "optimize_license_seat_portfolio"

gitrevio_capability_describe
  { "capability_id": "optimize_license_seat_portfolio" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "optimize_license_seat_portfolio", "arguments": { ... } }
  → returns the result shown above

Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.

Related tools

Calculate procurement negotiation range

Calculate an uncertainty-aware procurement bargaining zone from independently governed buyer and supplier BATNA economics; protect both reservation prices at explicit confidence levels, derive a bargaining-weight target, quantify ZOPA probability and tail overpayment, and abstain when evidence cannot support an overlap.

Decision analysis

Optimize discount policy

Optimize one aggregate discount option per commercial segment against scenario purchase, retention, service-cost and contribution economics; enforce expected discount spend, delivery capacity, cross-segment rate-gap and downside gates, compare with an explicit zero-discount baseline, and disclose exact or heuristic search.

Constrained optimization

Audit recurring revenue bridge integrity

Audit recurring revenue as a continuous stock/flow ledger: reconcile opening revenue through new, expansion, reactivation, contraction, churn, FX and acquisition/divestiture movements to closing revenue; require each next opening to equal the prior close; and recompute GRR and NRR on an organic existing-customer perimeter that cannot be inflated by new business, reactivation, FX or M&A.

Statistical audit & measurement

Calculate churn prevention break even

Calculate the absolute churn reduction an intervention must cause to break even, then test aligned baseline/treated scenarios against probability-of-positive-value and portfolio CVaR gates.

Constrained optimization

Estimate cannibalization adjusted feature value

Estimate feature value after posterior cannibalization of legacy contribution, using aligned adoption scenarios, beta-binomial substitution uncertainty, and value plus substitution-risk gates.

Sequential Bayesian & bandits

Estimate feature incremental value

Estimate rollout value from segment-level treated/control outcomes with beta-binomial uplift posteriors, finance-owned contribution economics, and a probability-of-positive-value gate.

Causal inference & experiment design

See every tool in Customer, revenue & pricing →

Ready to See Your Engineering work clearly?

Request a free demo