Predictika · Knee replacement constructs: femur, articular surface, tier pricing and discount authority

An AI sales agent's knee construct quote, checked before it goes out

An AI sales agent prepares a knee replacement construct quote for a fictional hospital. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the component, fit and pricing rules, compares the net price per knee the agent states with the one it computes, and returns a verdict with every reason.

Scope: Persona knee construct quotes (femur, articular surface, tibia, patella and cement) priced per knee with GPO tiers and ROSA Knee robotics. See everything this validator covers

This validator models knee construct quotes in the style of Zimmer Biomet's Persona line: femur and surface pairing, sizes, thickness, fixation, tier pricing with a construct cap, ROSA placement and discount terms. It handles any quote made of these parts and rules, not just the scenarios shown below.

  • Components — Persona CR and PS femurs, CR, UC, MC and PS articular surfaces, tibial components, patella and bone cement, with the sizes and thicknesses each is offered in.
  • Fit and fixation — Which articular surface goes with which femur, the femur and tibia size ranges and the two-size window between them, surface thickness limits, and which femurs can be used cementless.
  • Commercial terms — GPO tier pricing with a construct cap, ROSA Knee robotics placement approvals by annual volume, discount ceilings with a rep authority, and a check that the net price per knee the agent states matches the price the validator computes.

It does not cover other Zimmer Biomet implant families, real prices or contracts, or clinical advice.

The AI sales agentBuilds the quote from the conversation and says it is ready.
Predictika validatorChecks the quote against the product and contract rules and returns every finding it has.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based CPQ gets it wrong

Click to expand

Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator catchesTypical rules-based CPQPredictika
Femur and articular surfaceOnly with care
Each femur accepts only certain surfaces, which tends to become one rule per pairing.
The pairing is a property of the catalog items, checked on every call.
Sizes across componentsOnly with workarounds
A femur size must sit within two sizes of the tibia and inside each range, which product rules express awkwardly.
The size ranges and the two-size window are evaluated together.
Tier pricing with a construct capOnly with care
List price, tier percentage and a cap per tier interact, and price rules must keep the order straight.
Tier price, cap and construct price are derived in the model on every call.
Discount authorityOnly with care
Rep authority, the maximum and the approval route are separate rules that interact.
The maximum and the authority are evaluated together with the requested discount.
The net price the agent statesOnly with workarounds
Comparing a stated price with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures.
The stated net price is a field in the request and is checked against the computed price.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved, so a rep often fixes one error and meets the next.
All findings come back together, whatever order the choices arrived in.

What this validator catches

Click to expand

Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

RuleEffectWhat it checks
Femur and articular surfaceblockPS femurs need the PS surface; CR femurs need a CR, UC or MC surface
Size rangeblockFemur sizes 1 to 12 and tibia sizes 1 to 9
Femur and tibia sizesblockFemur and tibia sizes may differ by at most two sizes
Surface thicknessblockThe articular surface thickness must lie within the range of the chosen surface
FixationblockCementless fixation is not offered with the PS femur
ROSA roboticsblockA ROSA case at a site without ROSA needs a placement, which requires 150 or more knees a year
Discount ceilingblockRequested discount may not exceed 8 percent below the construct price
Net price the agent statedblockThe net price per knee in the request must match the price the validator computes
ROSA roboticsneeds approvalA ROSA placement at a site with 150 or more knees a year needs robotics program approval
Discount authorityneeds approvalA discount above 3 percent, up to the maximum, needs approval

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. Femur and articular surface: PS femur with MC surface

The agent's request. Persona PS femur size 6 with the Persona MC articular surface (12 mm) and tibia size 6, cemented, GPO Tier1, 200 knees a year for Lakeshore Orthopedic Hospital. Net price per knee USD 4,200. Ready to send.

Verdict: Blocked.

  • Femur and articular surface. Persona MC articular surface does not articulate with Persona PS femur; PS femurs need the PS surface and CR femurs need CR, UC or MC surfaces.

2. Femur and articular surface: PS femur with PS surface

The agent's request. Persona PS femur size 6 with the Persona PS articular surface (12 mm) and tibia size 6, cemented, GPO Tier1, 200 knees a year for Lakeshore Orthopedic Hospital. Net price per knee USD 4,200. Ready to send.

Verdict: Allowed.

3. The net price the agent states: Stated price below computed

The agent's request. Persona CR femur size 6 with the Persona MC articular surface (11 mm) and tibia size 5, cemented, GPO Tier1, 300 knees a year for Lakeshore Orthopedic Hospital. Net price per knee USD 3,906. Ready to send.

Verdict: Blocked.

  • Net price the agent stated. The stated net price per knee of $3906.0 does not match the $4200.0 the validator computed.

4. The net price the agent states: Stated price corrected

The agent's request. Persona CR femur size 6 with the Persona MC articular surface (11 mm) and tibia size 5, cemented, GPO Tier1, 300 knees a year for Lakeshore Orthopedic Hospital. Net price per knee USD 4,200. Ready to send.

Verdict: Allowed.

5. Discount authority: 12 percent discount

The agent's request. Persona CR femur size 9 with the Persona CR articular surface (10 mm) and tibia size 8, cemented, GPO Tier2, 120 knees a year, with 12 percent below the construct price, for Lakeshore Orthopedic Hospital. Net price per knee USD 4,089.80. Ready to send.

Verdict: Blocked.

  • Discount ceiling. 12 percent below the construct price exceeds the 8 percent maximum.

6. Discount authority: 6 percent, needs approval

The agent's request. Persona CR femur size 9 with the Persona CR articular surface (10 mm) and tibia size 8, cemented, GPO Tier2, 120 knees a year, with 6 percent below the construct price, for Lakeshore Orthopedic Hospital. Net price per knee USD 4,368.65. Ready to send.

Verdict: Needs approval.

  • Discount authority. 6 percent below the construct price is above the 3 percent rep authority.

7. Discount authority: 3 percent, within rep authority

The agent's request. Persona CR femur size 9 with the Persona CR articular surface (10 mm) and tibia size 8, cemented, GPO Tier2, 120 knees a year, with 3 percent below the construct price, for Lakeshore Orthopedic Hospital. Net price per knee USD 4,508.07. Ready to send.

Verdict: Allowed.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a knee replacement construct quote for a fictional hospital. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the component, fit and pricing rules, compares the net price per knee the agent states with the one it computes, and returns a verdict with every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Persona PS femur size 6 with the Persona MC articular surface (12 mm) and tibia size 6, cemented, GPO Tier1, 200 knees a year for Lakeshore Orthopedic Hospital. Net price per knee USD 4,200. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with one finding, all in one answer. Persona MC articular surface does not articulate with Persona PS femur; PS femurs need the PS surface and CR femurs need CR, UC or MC surfaces.
  6. The validator returned one blocking finding in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
  7. What this shows: for femur and articular surface, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the bearing to Persona PS articular surface.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. The validator also returns the line-item quote. It starts with Persona PS femur and Tibial component; the other three lines are on screen.
  13. The earlier finding is cleared, and the validator's total, USD 4,200, matches the quote.
  14. One problem caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.