Predictika · Security software license quantity and add-on configuration

An AI sales agent's Tenable One license quote, checked before it goes out

An AI sales agent prepares a quote for a Tenable One license pool: the customer's assets across several products converted to Tenable One assets, the licenses bought, consoles and add-ons. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of Tenable's public licensing guide and returns a verdict, every reason and the figures it computed.

Scope: Tenable One platform license quotes: converting assets of each product to Tenable One assets, the 300-license minimum, Security Center consoles, add-ons and license reallocation. See everything this validator covers

This validator models Tenable One license-pool quotes, not just the scenarios shown below.

  • Asset conversion — Vulnerability Management, Security Center+, Web App Scanning and Cloud Workload Protection count 1 Tenable One asset each; Identity Exposure and third-party assets 0.5; Cloud Exposure CIEM 3, Standard 5 and Enterprise 7.5; OT Exposure 1.5; Attack Surface Management 0.25 per object fortnightly or 0.5 daily. The converted total the quote states and the licenses it buys are compared with the computed total.
  • Purchase rules — at least 300 licenses bought at a time, and licenses reallocated at most once per 90 days.
  • Included and add-on items — up to 3 Security Center consoles are included and more are an add-on; daily Attack Surface Management frequency and on-premises Identity Exposure each need their add-on; third-party assets without the connectors add-on go to a person to confirm.

Any Tenable One license-pool quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Tenable One platform pricing is by quote, so no price build-up or line-item quote is produced), Nessus, other Tenable products sold separately, Web App Scanning concurrency quantities, and support terms. Assumptions: that daily Attack Surface Management and on-premises Identity Exposure each require their add-on, and that third-party assets need the connectors add-on, are read from the guide's add-on list, not from an explicit rule.

The AI sales agentBuilds the license 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.

8 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
Several products converted to one license pool with different ratiosOnly with care
Each product needs its own multiplier, including fractional ones, and the totals have to be rebuilt whenever a count changes.
Every count is in one request and the converted total is computed and compared on every call.
A stated converted total that disagrees with the usageOnly with workarounds
The total is derived from many counts; checking a figure stated on the quote against it takes extra formulas.
The stated figure is one more field in the request and is compared with the computed total on every call.
A minimum purchase of 300 licenses at a timeEasy
A simple quantity rule; routine in a product-rules CPQ.
The same rule, checked together with all the others on every call.
Add-ons that only some choices need: consoles beyond three, daily frequency, on-premises identityOnly with care
Each add-on depends on a choice elsewhere on the quote, so the rule has to be written and kept in step for every pairing.
The choices and add-ons are in one request and every dependency is checked together.
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 quote buys 299 licenses; Tenable One requires buying at least 300 licenses at a time.
2The quote buys 1,100 licenses; the quoted usage converts to 1,200 Tenable One assets.
3The quote states 1,100 Tenable One assets in total; the quoted usage converts to 1,200.
4Attack Surface Management at daily frequency needs the Attack Surface Management Daily Frequency add-on, which is not on the quote.
5The customer needs 4 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.
6Identity Exposure on-premises needs the Identity Exposure On-Premises add-on, which is not on the quote.
7Licenses can be reallocated once per 90 days; the last reallocation was 45 days ago.
8The quote counts third-party assets but has no Third-Party Connectors add-on; a person should confirm how the assets are ingested.
9The quote buys 250 licenses; Tenable One requires buying at least 300 licenses at a time.
10The quote buys 250 licenses; the quoted usage converts to 650 Tenable One assets.
11The quote states 500 Tenable One assets in total; the quoted usage converts to 650.
12The customer needs 5 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.
13Licenses can be reallocated once per 90 days; the last reallocation was 30 days ago.

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. Licenses and consoles: A quote for 3,100 Tenable One assets with 2,800 licenses and five consoles

The agent's request. Please prepare a Tenable One quote for a customer with 1,500 scanned targets for Vulnerability Management, 2,000 identity assets and 120 Cloud Exposure Standard billable assets. The quote buys 2,800 licenses and states 3,100 Tenable One assets in total, with 5 Security Center consoles. It is ready to send.

Verdict: Blocked.

  • Licenses do not cover the usage. The quote buys 2,800 licenses; the quoted usage converts to 3,100 Tenable One assets.
  • Security Center consoles beyond the included three. The customer needs 5 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.

2. Licenses and consoles: The agent resubmits after fixing the errors

The agent's request. Please prepare a Tenable One quote for a customer with 1,500 scanned targets for Vulnerability Management, 2,000 identity assets and 120 Cloud Exposure Standard billable assets. The quote buys 3,100 licenses and states 3,100 Tenable One assets in total, with 5 Security Center consoles. It is ready to send.

Verdict: Blocked.

  • Security Center consoles beyond the included three. The customer needs 5 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.

3. Licenses and consoles: The agent resubmits after fixing the errors

The agent's request. Please prepare a Tenable One quote for a customer with 1,500 scanned targets for Vulnerability Management, 2,000 identity assets and 120 Cloud Exposure Standard billable assets. The quote buys 3,100 licenses and states 3,100 Tenable One assets in total, with 5 Security Center consoles (2 beyond the included three). It is ready to send.

Verdict: Allowed.

  • License summary. The quoted usage converts to 3,100 Tenable One assets; the quote buys 3,100 licenses.

4. Add-ons for daily scans and on-premises identity: A 4,000-asset quote with daily attack surface scans and on-premises identity, no add-ons

The agent's request. Please prepare a Tenable One quote for a customer with 1,000 scanned targets for Vulnerability Management, 1,000 identity assets and 5,000 observable objects for Attack Surface Management scanned daily. The quote buys 4,000 licenses and states 4,000 Tenable One assets in total, with Identity Exposure on-premises. It is ready to send.

Verdict: Blocked.

  • Daily attack surface scans need the add-on. Attack Surface Management at daily frequency needs the Attack Surface Management Daily Frequency add-on, which is not on the quote.
  • On-premises identity needs the add-on. Identity Exposure on-premises needs the Identity Exposure On-Premises add-on, which is not on the quote.

5. Add-ons for daily scans and on-premises identity: The agent resubmits after fixing the errors

The agent's request. Please prepare a Tenable One quote for a customer with 1,000 scanned targets for Vulnerability Management, 1,000 identity assets and 5,000 observable objects for Attack Surface Management scanned daily. The quote buys 4,000 licenses and states 4,000 Tenable One assets in total, with the Attack Surface Management Daily Frequency add-on and Identity Exposure on-premises with its add-on. It is ready to send.

Verdict: Allowed.

  • License summary. The quoted usage converts to 4,000 Tenable One assets; the quote buys 4,000 licenses.

6. Reallocation and third-party assets: A 2,300-asset quote that reallocates licenses 40 days after the last reallocation

The agent's request. Please prepare a Tenable One quote for a customer with 600 scanned targets for Vulnerability Management, 800 OT devices and 1,000 third-party assets. The quote buys 2,300 licenses and states 2,300 Tenable One assets in total, and reallocates licenses 40 days after the previous reallocation. It is ready to send.

Verdict: Blocked.

  • Reallocation within 90 days. Licenses can be reallocated once per 90 days; the last reallocation was 40 days ago.
  • Third-party connectors to confirm. The quote counts third-party assets but has no Third-Party Connectors add-on; a person should confirm how the assets are ingested.

7. Reallocation and third-party assets: The agent resubmits after fixing the errors

The agent's request. Please prepare a Tenable One quote for a customer with 600 scanned targets for Vulnerability Management, 800 OT devices and 1,000 third-party assets. The quote buys 2,300 licenses and states 2,300 Tenable One assets in total, and reallocates licenses 120 days after the previous reallocation. It is ready to send.

Verdict: Needs approval.

  • Third-party connectors to confirm. The quote counts third-party assets but has no Third-Party Connectors add-on; a person should confirm how the assets are ingested.
  • License summary. The quoted usage converts to 2,300 Tenable One assets; the quote buys 2,300 licenses.

8. Reallocation and third-party assets: The agent resubmits after fixing the errors

The agent's request. Please prepare a Tenable One quote for a customer with 600 scanned targets for Vulnerability Management, 800 OT devices and 1,000 third-party assets. The quote buys 2,300 licenses and states 2,300 Tenable One assets in total, with the Third-Party Connectors add-on, and reallocates licenses 120 days after the previous reallocation. It is ready to send.

Verdict: Allowed.

  • License summary. The quoted usage converts to 2,300 Tenable One assets; the quote buys 2,300 licenses.

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 a Tenable One license pool: the customer's assets across several products converted to Tenable One assets, the licenses bought, consoles and add-ons. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of Tenable's public licensing guide and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please prepare a Tenable One quote for a customer with 1,500 scanned targets for Vulnerability Management, 2,000 identity assets and 120 Cloud Exposure Standard billable assets. The quote buys 2,800 licenses and states 3,100 Tenable One assets in total, with 5 Security Center consoles. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. The quote buys 2,800 licenses; the quoted usage converts to 3,100 Tenable One assets. The customer needs 5 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.
  6. The validator returned two 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 add-ons that only some choices need: consoles beyond three, daily frequency, on-premises identity, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the licenses bought to 3,100.
  10. It calls the validator again.
  11. Still blocked, with one finding, all in one answer. The customer needs 5 Tenable Security Center consoles; the platform includes up to 3 and the quote adds 0 more.
  12. One finding cleared; still blocked on Security Center consoles beyond the included three.
  13. The agent resubmits once more.
  14. The revised request. It changes the additional consoles on the quote to 2.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The earlier finding is cleared.
  18. Two problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer.