Optimize product mix

Optimize one discrete quantity option per product across a shared cash budget and multiple capacity pools using aligned contribution scenarios, expected value, CVaR downside, and an explicit exact or heuristic solver boundary.

What it's for

Turns product strategy into an executable mix: which quantities to fund, what shared capacity they consume, and how much downside the plan carries.

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
cash_budget number ≥ 0 Your calibration Yes
max_detail_rows integer ≥ 1, ≤ 500 Numerical control Optional
maximum_exact_states integer ≥ 2, ≤ 16777216 Numerical control Optional
mix_options array of objects (6 fields) ≥ 1 item Evidence Yes
resources array of objects (2 fields) ≥ 1 item Evidence Yes
risk_aversion number ≥ 0 Your calibration Optional
scenario_probabilities array of number ≥ 2 items Evidence Yes
tail_probability number ≥ 0.001, ≤ 0.5 Your calibration Optional

Each mix_options record

Field Type Required
cash_cost number (≥ 0) Yes
contribution_scenarios array of number (≥ 2 items) Yes
id string (non-empty) Yes
product_id string (non-empty) Yes
quantity number (≥ 0) Yes
resource_requirements object Yes
Example input
{
  "cash_budget": 500000,
  "mix_options": [
    {
      "cash_cost": 0,
      "contribution_scenarios": [
        0,
        0,
        0
      ],
      "id": "core-zero",
      "product_id": "core",
      "quantity": 0,
      "resource_requirements": {}
    },
    {
      "cash_cost": 300000,
      "contribution_scenarios": [
        200000,
        500000,
        800000
      ],
      "id": "core-growth",
      "product_id": "core",
      "quantity": 100,
      "resource_requirements": {
        "engineering": 5,
        "go_to_market": 3
      }
    },
    {
      "cash_cost": 0,
      "contribution_scenarios": [
        0,
        0,
        0
      ],
      "id": "enterprise-zero",
      "product_id": "enterprise",
      "quantity": 0,
      "resource_requirements": {}
    },
    {
      "cash_cost": 400000,

Truncated for display — the full payload is 75 lines.

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
{
  "assumptions": [
    "Each product has a true do-nothing option; exactly one submitted option is chosen per product, and quantity, cash, resource use, and contribution share one planning horizon.",
    "Scenario contribution is incremental after variable operating effects but its treatment of submitted cash cost must be finance-governed consistently; shared scenario columns preserve cross-product dependence.",
    "Only submitted shared resources constrain the mix; demand substitution, minimum lots, ramp timing, tax, working capital, and product interactions require explicit options or a richer model.",
    "Exact mode certifies only the represented discrete search; coordinate heuristic mode has no global optimality certificate and should be benchmarked on smaller exact instances before consequential use."
  ],
  "configuration": {
    "cash_budget": 500000,
    "maximum_exact_states": 262144,
    "option_count": 4,
    "product_count": 2,
    "represented_state_count": 4,
    "resource_count": 2,
    "risk_aversion": 0.5,
    "scenario_count": 3,
    "solver_mode": "exact_cartesian_enumeration",
    "state_count_is_capped": false,
    "tail_probability": 0.1
  },
  "decision": "product_mix_optimized_exact",
  "method": "discrete_shared_capacity_product_mix_cvar_v1",
  "product_diagnostics": [
    {
      "cash_cost": 400000,
      "expected_contribution": 730000,
      "is_safe_zero_option": false,
      "product_id": "enterprise",
      "selected_option_id": "enterprise-launch",
      "selected_quantity": 20
    },
    {
      "cash_cost": 0,
      "expected_contribution": 0,
      "is_safe_zero_option": true,
      "product_id": "core",
      "selected_option_id": "core-zero",
      "selected_quantity": 0
    }
  ],
  "resource_diagnostics": [
    {
      "capacity": 10,
      "resource_id": "engineering",

Truncated for display — the full payload is 73 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 Freeze products, a true zero-production option for each, feasible discrete quantity alternatives, cash cost, shared resource consumption, and aligned incremental contribution scenarios.
  2. 2 Enumerate the Cartesian product within the governed state limit and maximize expected contribution minus the CVaR-loss penalty subject to cash and every shared capacity; otherwise run visible coordinate-ascent screening.
  3. 3 Return product quantities, cash slack, resource utilization, expected contribution, loss tail, and negative-contribution probability without promoting the fallback to an optimum.

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.
  • All option fields use one horizon, scenario columns preserve cross-product dependence, the do-nothing options are genuine, and omitted substitution, lots, ramp timing, working capital, or product interactions are immaterial or modeled elsewhere.
  • The recommendation is optimal only for its stated objective, feasible set, evidence, and solver guarantee; it is not a universal management optimum.
  • The result is conditional on submitted option economics and constraints, not a demand forecast, pricing authorization, staffing prescription, or global-optimality claim in heuristic mode.

Minimum evidence

  • resources: at least 1 rows/items
  • mix_options: at least 1 rows/items
  • scenario_probabilities: at least 2 rows/items
  • cash_budget: 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

  • aligned option-level contribution paths and resource requirements including zero-production alternatives
  • product/quantity semantics, option feasibility, contribution and cash perimeter, shared capacity units, scenario identity/probabilities, risk aversion, tail, omitted interactions, and solver promotion

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": "optimize one discrete quantity option per" }
  → finds "optimize_product_mix"

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

gitrevio_capability_run
  { "capability_id": "optimize_product_mix", "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

Audit budget constraint binding

Audit whether a claimed budget constraint genuinely blocks value after dependency-feasible portfolio reallocation, separating current-plan inefficiency from scarcity with scenario CVaR and a discrete budget shadow price.

Constrained optimization

Solve distributionally robust product portfolio

Solve a budgeted product portfolio under ambiguity in scenario probabilities, acyclic dependencies, mutually exclusive choices, and governed pairwise cannibalization or synergy using a total-variation uncertainty set.

Constrained optimization

Allocate budget with CVAR constraint

Maximize expected portfolio return while keeping probability-weighted loss CVaR below a finance-owned tail-risk ceiling across aligned joint scenarios.

Constrained optimization

Audit financing term sheet integrity

Audit startup financing terms as exact share, price, proceeds and ownership identities: include pre-money option-pool increases and converting instruments in the pricing denominator, keep secondary purchases out of company cash and post-money share creation, reconcile primary issuance, post-money equity value and reported investor ownership, and retain evidence failures and impossible fees or secondary sales.

Statistical audit & measurement

Audit fundraising pipeline integrity

Audit a fundraising pipeline as point-in-time evidence rather than CRM theater: reconstruct monotone stage events, terminal status and primary proceeds, retain open opportunities as censored, reject forecasts made after resolution, detect duplicate active investor accounts, and gate the portfolio on mature-forecast support, Brier loss and calibration gap.

Forecasting & survival

Audit technology diligence evidence integrity

Audit a frozen technology diligence case against buyer-declared system/domain/claim scope, management assertions and fresh, rights-cleared, independently reviewed point-in-time evidence.

Statistical audit & measurement

See every tool in Investment & portfolio choice →

Ready to See Your Engineering work clearly?

Request a free demo