Allot builds converged cybersecurity and network intelligence for service providers and enterprises worldwide, selling hardware, software and services across regions and currencies. For years its quoting ran on a rigid, developer-owned CPQ, and a configuration error surfaced only once the purchase order arrived and five downstream teams had to unwind it. Allot replaced that system with DealHub AI and moved product rules, P&L calculation and approval routing into the quote itself. Its business applications team now deploys a pricing change without an engineering release.
Approvers decide on one notification that already carries the deal's P&L.
Up from 70 to 80% under manual review by every team.
For years Allot's sales engineers could assemble any combination of part numbers the price list allowed, including combinations the company could not ship together. The mistake did not surface in the quote. It surfaced when the customer's purchase order arrived, on an order that had already been prepared and was needed fast, and by then finance had to reopen the Salesforce opportunity, operations had to cancel the ERP order, and supply chain, planning and logistics all stopped to unwind work that was already done. A single wrong line could cost a week.
Our supply chain and planning teams keep stopping to fix quotes that were already approved. Why is a configuration error ours to catch after the purchase order arrives?
Every pricing change we want sits in a developer queue for weeks. Why does a business rule need an engineering release?
Our approvers will not sign without margin. Why is the P&L in a spreadsheet nobody in the approval chain can open?
| Before | After |
|---|---|
Allot's finance team rebuilt deal margin in an Excel model after the proposal was already assembled. | Allot's finance team adds cost elements inside the quote and reads cost, net price and P&L as the rep configures. |
Building a clean bill of materials for a hardware, software, CapEx or OpEx deal could take weeks. | Allot's sales engineers build every commercial model from one guided flow, with each opportunity's currency and conversion rate read from Salesforce. |
Every pricing update, workflow change and new business model waited on a developer release. | Allot's business applications team writes, tests and deploys pricing and approval logic itself, in a sandbox. |
Approvers left the request to search Salesforce and ask the deal team before they could decide. | Allot's approvers decide on one notification that already carries the deal's margin and its approval path. |
DealHub AI gave Allot's business applications team one place to encode every commercial model it sells. Previously, sales engineers assembled hardware, software, CapEx and OpEx deals by hand, and a wrong combination surfaced only once the order reached supply chain. Now a guided flow allows only the combinations Allot can supply, and reps quote at roughly 100% accuracy.
Allot's Core Business Applications Manager, inside the IT department, who moved across from Sales Operations specifically to lead the CPQ build.
Business-owned configuration. Allot's business applications team writes and tests configuration, pricing and approval rules in a sandbox, with no developer release.
Allot has quoted on DealHub CPQ since 2019, starting with standard deals.
Phased. Standard deals first, then renewals and expansions, with approval routing moved into DealHub CPQ in a second phase.
Salesforce, bi-directional. Allot reads each opportunity and its currency into DealHub CPQ and syncs P&L and deal fields back for reporting and forecasting.
No engineering release for a pricing or workflow change. Allot's business applications manager owns the rule set and holds a monthly working session with the DealHub CSM.
DealHub is ISO 27001, ISO 27701, ISO 22301, and ISO 42001 certified, holds SOC 1 Type II and SOC 2 Type II attestations, and is GDPR and CCPA compliant, alongside additional security, privacy, and compliance frameworks.









