Predictika · Quote-to-cash commitments

An AI sales agent's Everpure FlashArray quote, checked for what it promises before it goes out

After the configuration is right, a quote still promises things: a delivery quarter, a lead time, a price that holds for a number of days. An AI sales agent prepares such a quote for an Everpure FlashArray order, and states the supply and lead-time figures it relies on. Before it goes out, the agent sends it to Predictika, which checks the promise against the unbooked supply, the family's lead times and the quote's age and validity, compares the figures the agent states with its own, and returns a verdict and every reason.

Scope: Everpure (formerly Pure Storage) FlashArray//X, //XL, //C and //E quote commitments: delivery quarter against unbooked supply, lead time, quote validity, cost drift and Evergreen//One ramp dates. See everything this validator covers

This validator models the commitments an Everpure FlashArray quote makes, not just the scenarios shown below.

  • Delivery promise — the order size against the unbooked supply left in the delivery quarter, and a thin fit inside the safety margin, which goes to supply planning as an approval.
  • Lead time — the requested weeks against the family's standard and minimum lead times: below the minimum is a hold, between the minimum and the standard needs an expedite approval.
  • Quote validity and cost — quote age against validity, the 30 day standard validity, and a cost move above 10 percent on a quote that is still valid, which needs a margin review.
  • Evergreen//One ramp — delivery after the subscription start date, when the reserve would not be physically available.
  • Stated figures — the unbooked supply and the standard lead time that the agent states against the figures in the model.

Any FlashArray quote that touches these rules is in scope, not only the scenarios pictured here. Supply per quarter, lead times and ramp dates are invented for illustration and are not Everpure data; the model does not cover other products, price, regions, or quarters after Q3 2027.

The AI sales agentBuilds the quote and its delivery promise from the conversation, states the supply and lead-time figures it relied on, and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 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) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtTypical rules-based CPQPredictika
A delivery date promised without checking what supply is leftOnly with workarounds
Supply lives in a planning or order system outside the quote. A rules-based CPQ can check it only if that data is integrated and kept current; otherwise it quotes the standard lead time whatever is booked.
Unbooked supply per quarter is part of the model, and the order is compared with it on every call.
An order that fits supply by a hairOnly with workarounds
A safety-margin rule sits on top of the same supply data, so it needs the same integration plus one more rule to build and keep in step.
A safety margin per quarter routes a thin fit to supply planning as an approval.
A supply or lead-time figure the agent merely statesOnly with care
A validation rule can compare a stated figure with a calculated one, but only if the stated figure is a field on the quote, which it rarely is.
The stated figures travel with the quote and are compared with the validator’s own on every call.
Cost moved since the quote, on a quote that is still validOnly with workarounds
The cost change is not on the quote. It has to be copied in from another system before a rule can see it.
The cost change travels with the request and routes a margin review above the threshold.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is completed, so a rep often fixes one error and meets the next.
All findings come back together, blocks first, then approvals.

What this validator catches: findings from its test cases

Click to expand

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

17,000 TB is above the 6,000 TB of unbooked supply left in Q4 2026; the delivery cannot be promised.
2This order leaves under the 4,000 TB safety margin of supply in Q4 2026; confirm with supply planning.
34 weeks is below the 6 week standard lead time for the FlashArray//X; expedite needs approval.
42 weeks is below the 3 week minimum even with expedite for the FlashArray//X.
5The quote is 100 days old and its validity is 30 days; re-price it.
6A validity of 120 days is above the 30 day standard.
7Component cost has moved 18 percent since the quote; honoring it needs a margin review.
8Delivery in Q2 2027 is after the Evergreen//One subscription start; the reserve would not be physically available.
98 weeks is below the 10 week standard lead time for the FlashArray//E; expedite needs approval.
105 weeks is below the 6 week minimum even with expedite for the FlashArray//E.
11The quote states a standard lead time of 5 weeks for the FlashArray//E, but it is 10 weeks.
123 weeks is below the 4 week minimum even with expedite for the FlashArray//XL.
136,001 TB is above the 6,000 TB of unbooked supply left in Q4 2026; the delivery cannot be promised.
14Delivery in Q3 2027 is after the Evergreen//One subscription start; the reserve would not be physically available.

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. Supply, lead time and validity: A 7,000 TB FlashArray//E quote for delivery in Q4 2026 in 5 weeks, 100 days old, with figures of its own

The agent's request. Please quote 7,000 TB of FlashArray//E for delivery in Q4 2026 in 5 weeks. The supply table shows 8,000 TB unbooked in that quarter, and the standard lead time for FlashArray//E is 5 weeks. The quote is 100 days old with 90 days validity; the Evergreen//One subscription starts in Q1 2027. It is ready to send.

Verdict: Blocked.

  • Order above unbooked supply. 7,000 TB is above the 6,000 TB of unbooked supply left in Q4 2026; the delivery cannot be promised.
  • Lead time below the minimum. 5 weeks is below the 6 week minimum even with expedite for the FlashArray//E.
  • Quote past its validity. The quote is 100 days old and its validity is 90 days; re-price it.
  • Validity above the 30 day standard. A validity of 90 days is above the 30 day standard.
  • Quoted supply does not match. The quote states 8,000 TB unbooked in Q4 2026, but the supply table shows 6,000 TB.
  • Quoted lead time does not match. The quote states a standard lead time of 5 weeks for the FlashArray//E, but it is 10 weeks.

2. Supply, lead time and validity: The agent resubmits after fixing the errors

The agent's request. Please quote 7,000 TB of FlashArray//E for delivery in Q1 2027 in 10 weeks. The supply table shows 15,000 TB unbooked in that quarter, and the standard lead time for FlashArray//E is 10 weeks. The Evergreen//One subscription starts in Q1 2027. It is ready to send.

Verdict: Allowed.

  • Computed figures. Q1 2027 has 15,000 TB unbooked supply with a 4,200 TB safety margin; the FlashArray//E has a 10 week standard and 6 week minimum lead time; the quote is 0 days old with 30 days validity.

3. Evergreen//One ramp: A 5,000 TB FlashArray//X quote for Q2 2027 on an Evergreen//One ramp, in 4 weeks, with component cost moved 18 percent

The agent's request. Please quote 5,000 TB of FlashArray//X for delivery in Q2 2027 in 4 weeks. The supply table shows 30,000 TB unbooked in that quarter, and the standard lead time for FlashArray//X is 6 weeks. The quote is 10 days old with 30 days validity; component cost has moved 18 percent since the quote; the Evergreen//One subscription starts in Q1 2027. It is ready to send.

Verdict: Blocked.

  • Delivery after the subscription start. Delivery in Q2 2027 is after the Evergreen//One subscription start; the reserve would not be physically available.
  • Expedited delivery. 4 weeks is below the 6 week standard lead time for the FlashArray//X; expedite needs approval.
  • Cost moved since the quote. Component cost has moved 18 percent since the quote; honoring it needs a margin review.

4. Evergreen//One ramp: The agent resubmits after fixing the errors

The agent's request. Please quote 5,000 TB of FlashArray//X for delivery in Q1 2027 in 6 weeks. The supply table shows 15,000 TB unbooked in that quarter, and the standard lead time for FlashArray//X is 6 weeks. The Evergreen//One subscription starts in Q1 2027. It is ready to send.

Verdict: Allowed.

  • Computed figures. Q1 2027 has 15,000 TB unbooked supply with a 4,200 TB safety margin; the FlashArray//X has a 6 week standard and 3 week minimum lead time; the quote is 0 days old with 30 days validity.

5. Thin supply margin: A 5,000 TB FlashArray//C quote for delivery in Q4 2026

The agent's request. Please quote 5,000 TB of FlashArray//C for delivery in Q4 2026 in 12 weeks. The supply table shows 6,000 TB unbooked in that quarter, and the standard lead time for FlashArray//C is 6 weeks. It is ready to send.

Verdict: Needs approval.

  • Thin supply margin. This order leaves under the 4,000 TB safety margin of supply in Q4 2026; confirm with supply planning.
  • Computed figures. Q4 2026 has 6,000 TB unbooked supply with a 4,000 TB safety margin; the FlashArray//C has a 6 week standard and 3 week minimum lead time; the quote is 0 days old with 30 days validity.

6. Thin supply margin: The agent resubmits after fixing the errors

The agent's request. Please quote 5,000 TB of FlashArray//C for delivery in Q1 2027 in 12 weeks. The supply table shows 15,000 TB unbooked in that quarter, and the standard lead time for FlashArray//C is 6 weeks. It is ready to send.

Verdict: Allowed.

  • Computed figures. Q1 2027 has 15,000 TB unbooked supply with a 4,200 TB safety margin; the FlashArray//C has a 6 week standard and 3 week minimum lead time; the quote is 0 days old with 30 days validity.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. After the configuration is right, a quote still promises things: a delivery quarter, a lead time, a price that holds for a number of days. An AI sales agent prepares such a quote for an Everpure FlashArray order, and states the supply and lead-time figures it relies on. Before it goes out, the agent sends it to Predictika, which checks the promise against the unbooked supply, the family's lead times and the quote's age and validity, compares the figures the agent states with its own, and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote 7,000 TB of FlashArray//E for delivery in Q4 2026 in 5 weeks. The supply table shows 8,000 TB unbooked in that quarter, and the standard lead time for FlashArray//E is 5 weeks. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with six findings, all in one answer. 7,000 TB is above the 6,000 TB of unbooked supply left in Q4 2026; the delivery cannot be promised. 5 weeks is below the 6 week minimum even with expedite for the FlashArray//E. The quote is 100 days old and its validity is 90 days; re-price it. The other three are on screen.
  6. The validator returned six blocking findings 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 a supply or lead-time figure the agent merely states, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the delivery quarter to Q1 2027, the requested delivery to 10 weeks, the stated unbooked supply to 15,000 TB and the stated standard lead time to 10 weeks. It removes the quote age and quote validity.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All six earlier findings are cleared.
  13. Six problems 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.