Predictika · Edge cloud platform packages

An AI sales agent's Fastly platform packages quote, checked before it goes out

An AI sales agent prepares a quote for Fastly platform packages: Deliver for web and API delivery, Compute for edge code, and Observability, together with the traffic, domains, support level and monthly price the customer expects. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the allowances and conditions Fastly publishes and returns a verdict, every reason and the figures it computed.

Scope: Fastly Deliver, Compute and Observability package quotes: the included requests, domains and services, traffic conditions, support level and the published monthly prices. See everything this validator covers

This validator models quotes for Fastly's Deliver, Compute and Observability packages, not just the scenarios shown below.

  • Deliver packages — Basic, Starter, Advantage and Ultimate: included monthly requests, TLS domains, Image Optimizer requests, Mutual TLS domains, WebSocket minutes and support level, plus the conditions that Deliver is for web pages and web APIs, not streaming, and that no more than 10 percent of traffic may originate in the African, Indian or South Korean billing regions.
  • Compute packages — Starter, Advantage and Ultimate: included requests, vCPU milliseconds, services and Config Stores, and entries per Config Store.
  • Observability packages — Starter, Advantage and Ultimate: included requests and which tools each includes. Origin Inspector, Domain Inspector and Log Explorer and Insights are not in Starter.
  • Prices — the monthly prices Fastly publishes (Deliver Basic and Starter, Compute Starter, Observability Starter) are added up and compared with the total the quote states. Advantage and Ultimate packages are priced by Fastly sales, so a quote that includes one goes to a person for approval.

Any quote for these Fastly packages that touches these rules is in scope — not only the scenarios pictured here. Not covered: usage-based (pay as you go) pricing, Security packages, AI products, overage charges, discounts and contract terms. Package details were read from Fastly's published pricing page. Where the page was inconsistent between readings (which of Advantage and Ultimate include Domain Inspector and Log Explorer and Insights), the validator sends the quote to a person rather than deciding.

The AI sales agentBuilds the package quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

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) 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
Package allowances that differ by package: requests, domains, services, Config StoresOnly with care
Each allowance is a separate limit for each package, and the limits for three package families have to be kept in step with the pricing page.		All allowances are looked up from the package and checked together on every call.
Traffic conditions: no streaming, no more than 10 percent from restricted billing regionsOnly with workarounds
These are conditions on the customer's traffic rather than on a product choice, so they need extra fields and rules that interact with the package rules.		The traffic facts are in the same request and are checked with the rest.
A support level that only some packages includeOnly with workarounds
The needed support level depends on the Deliver package on another line, so it needs a cross-line rule.		The support level the customer needs is compared with the quoted package on every call.
A tool that only some Observability packages includeOnly with workarounds
Which tool belongs to which package is a lookup that has to be written for each package and kept up to date.		The tools needed are in the request and are checked against the quoted Observability package.
A stated monthly total, when some packages have no published priceOnly with care
A price rule needs a published price for every item; a package priced by sales has to be handled as a special case.		The stated total is compared with the published prices, and any package priced by sales sends the quote to a person.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, 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: 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.

    
1The customer needs 101 million Deliver requests per month; the quoted Deliver package includes 100 million.
2The customer needs 21 TLS domains; the quoted Deliver package includes 20.
3The customer needs 31 million Image Optimizer requests per month; the quoted Deliver package includes 30 million.
4The customer needs 101 million WebSocket minutes; Deliver packages include 100 million.
5Deliver packages are intended for web pages and web APIs, not for streaming services; the customer needs streaming delivery.
6No more than 10 percent of Deliver traffic may originate in the African, Indian or South Korean billing regions; the customer expects 11 percent.
7The customer needs a higher support level than the quoted Deliver package includes (Basic: Standard; Starter and Advantage: Gold; Ultimate: Enterprise).
8The customer needs 5,001 million vCPU milliseconds per month; the quoted Compute package includes 5,000 million.
9The customer needs 501 million Compute requests per month; the quoted Compute package includes 500 million.
10The customer needs 21 Compute services; the quoted Compute package includes 20.
11The customer needs 6 Config Stores; the quoted Compute package includes 5.
12The customer needs 501 entries in a Config Store; Compute packages allow 500 entries per Config Store.
13The customer needs 501 million Observability requests per month; the quoted Observability package includes 500 million.
14The customer needs Origin Inspector; the Observability Starter package does not include it.
15The customer needs Domain Inspector or Log Explorer and Insights; the Observability Starter package includes neither.
161 quoted package(s) have no published price (contact sales); a person should confirm the price before the quote goes out.
17The customer needs Domain Inspector or Log Explorer and Insights on the Observability Advantage package; a person should confirm with Fastly that the package includes them.
18The quote states a monthly price of 7,500 USD; the published monthly prices of the quoted packages total 8,000 USD.
19The quote has no Deliver, Compute or Observability package.
20The customer needs 3 domains with Mutual TLS; the quoted Deliver package includes 2.

  

  

    
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. Deliver package allowances: Basic Deliver package for a larger site

    
The agent's request. Please quote a Fastly Deliver Basic package for 150 million requests a month, 35 TLS domains, 60 million image requests, 4 domains with Mutual TLS and 40 million WebSocket minutes, with Standard support and 4 percent of traffic from the African, Indian or South Korean billing regions. The quote states a monthly price of $1,500. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Deliver requests above the package. The customer needs 150 million Deliver requests per month; the quoted Deliver package includes 100 million.
    • 
      
  • TLS domains above the package. The customer needs 35 TLS domains; the quoted Deliver package includes 20.
    • 
      
  • Image requests above the package. The customer needs 60 million Image Optimizer requests per month; the quoted Deliver package includes 30 million.
    • 
      
  • Mutual TLS domains above the package. The customer needs 4 domains with Mutual TLS; the quoted Deliver package includes 2.
    • 
    

    
2. Deliver package allowances: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Fastly Deliver Starter package for 150 million requests a month, 35 TLS domains, 60 million image requests, 4 domains with Mutual TLS and 40 million WebSocket minutes, with Standard support and 4 percent of traffic from the African, Indian or South Korean billing regions. The quote states a monthly price of $6,000. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. The published monthly prices of the quoted packages total 6,000 USD; 0 quoted package(s) are priced by sales only.
    • 
    

    
3. Traffic and support: Streaming, restricted-region traffic and Enterprise support on a Starter package

    
The agent's request. Please quote a Fastly Deliver Starter package for 400 million requests a month, 38 TLS domains, 120 million image requests, 8 domains with Mutual TLS and 60 million WebSocket minutes, with Enterprise support and 15 percent of traffic from the African, Indian or South Korean billing regions, delivering live video streams. The quote states a monthly price of $6,000. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Streaming on a Deliver package. Deliver packages are intended for web pages and web APIs, not for streaming services; the customer needs streaming delivery.
    • 
      
  • Too much traffic from restricted regions. No more than 10 percent of Deliver traffic may originate in the African, Indian or South Korean billing regions; the customer expects 15 percent.
    • 
      
  • Support level above the package. The customer needs a higher support level than the quoted Deliver package includes (Basic: Standard; Starter and Advantage: Gold; Ultimate: Enterprise).
    • 
    

    
4. Traffic and support: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Fastly Deliver Ultimate package for 400 million requests a month, 38 TLS domains, 120 million image requests, 8 domains with Mutual TLS and 60 million WebSocket minutes, with Enterprise support and 8 percent of traffic from the African, Indian or South Korean billing regions. The price is to be confirmed with Fastly sales. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Price available only from sales. 1 quoted package(s) have no published price (contact sales); a person should confirm the price before the quote goes out.
    • 
      
  • Price summary. The published monthly prices of the quoted packages total 0 USD; 1 quoted package(s) are priced by sales only.
    • 
    

    
5. Traffic and support: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Fastly Deliver Starter package for 400 million requests a month, 38 TLS domains, 120 million image requests, 8 domains with Mutual TLS and 60 million WebSocket minutes, with Gold support and 8 percent of traffic from the African, Indian or South Korean billing regions. The quote states a monthly price of $6,000. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. The published monthly prices of the quoted packages total 6,000 USD; 0 quoted package(s) are priced by sales only.
    • 
    

    
6. Compute and Observability: Compute and Observability Starter packages with larger needs

    
The agent's request. Please quote a Fastly Compute Starter package for 800 million requests, 6,000 million vCPU milliseconds, 25 services and 6 Config Stores, together with a Fastly Observability Starter package for 450 million requests with Origin Inspector and Log Explorer and Insights. The quote states a monthly price of $2,000. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Compute requests above the package. The customer needs 800 million Compute requests per month; the quoted Compute package includes 500 million.
    • 
      
  • vCPU time above the package. The customer needs 6,000 million vCPU milliseconds per month; the quoted Compute package includes 5,000 million.
    • 
      
  • Compute services above the package. The customer needs 25 Compute services; the quoted Compute package includes 20.
    • 
      
  • Config Stores above the package. The customer needs 6 Config Stores; the quoted Compute package includes 5.
    • 
      
  • Origin Inspector not in the package. The customer needs Origin Inspector; the Observability Starter package does not include it.
    • 
      
  • Domain Inspector or Log Explorer not in Starter. The customer needs Domain Inspector or Log Explorer and Insights; the Observability Starter package includes neither.
    • 
    

    
7. Compute and Observability: The agent resubmits after fixing the errors

    
The agent's request. Please quote a Fastly Compute Starter package for 450 million requests, 4,800 million vCPU milliseconds, 18 services and 5 Config Stores, together with a Fastly Observability Starter package for 450 million requests. The quote states a monthly price of $2,000. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. The published monthly prices of the quoted packages total 2,000 USD; 0 quoted package(s) are priced by sales only.
    • 
    

  

  

    
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 quote for Fastly platform packages: Deliver for web and API delivery, Compute for edge code, Observability, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the allowances and conditions Fastly publishes and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a Fastly Compute Starter package for 800 million requests, 6,000 million vCPU milliseconds, 25 services and 6 Config Stores. The quote states a monthly price of $2,000. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with six findings, all in one answer. The customer needs 800 million Compute requests per month; the quoted Compute package includes 500 million. The customer needs 6,000 million vCPU milliseconds per month; the quoted Compute package includes 5,000 million. The customer needs 25 Compute services; the quoted Compute package includes 20. The other three are on screen.
    6. 
      
  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. 
      
  7. What this shows: for package allowances that differ by package: requests, domains, services, Config Stores, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the compute requests to 450, the vCPU milliseconds to 4,800, the services to 18 and the Config Stores to 5. Two more changes are on screen.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All six earlier findings are cleared, and the validator's total, $2,000, matches the quote.
    13. 
      
  13. Six problems caught in one call, fixed in one pass, and a clean $2,000 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.