Cofense sells phishing defense and email threat detection to global enterprises and government agencies. Its reps used to build a quote from Salesforce checkboxes, generate a PDF through a third-party tool, and edit that PDF before sending it, with nothing standing between a discount and a customer. DealHub AI replaced that chain with one governed workflow: guided selling playbooks, locked output documents and parallel approvals wired to Slack and email. Cofense's sales operations team now sees every quote before it leaves, and ships its own changes to the system every month.
The team stopped triaging daily quotes and took on larger projects.
Every discount and legal term routes to its owner before the quote ships.
Cofense quoted out of Salesforce checkboxes and a third-party tool that turned the selections into a PDF. Nothing in that chain approved a discount or a piece of custom legal language, and a rep could open the generated PDF and change it before it reached the customer. In Salesforce reporting the sales operations team watched list price and sales price drift apart deal after deal. The only quotes that got a second pair of eyes were the ones a rep chose to bring to contract admin, and the reps who did not bring theirs were the reps whose quotes needed the check.
Our list price and our sales price are far apart in every Salesforce report. Why do we find out about a discount instead of approving it?
A rep can generate a PDF and edit it before it goes out. What stops a customer receiving legal language nobody in legal has read?
Only the reps who come to contract admin get a second pair of eyes. Why does governance depend on who volunteers?
Our admin left mid-implementation and the rollout landed on sales ops. How do we take over a CPQ nobody here configured without stalling the sales team?
| Before | After |
|---|---|
Reps guessed which products paired with which services, and contract admin caught the mismatches by hand. | Guided selling asks the questions and populates the products, so the wrong pairing is never offered. |
Nobody could see who still had to sign off, so a quote stalled without anyone knowing where. | Parallel approvals fire on submit, name every approver at the top of the quote, and alert them in Slack and email. |
Renewal and uplift pricing was recalculated by hand against last year's closed opportunity. | DealHub AI carries the per-user price forward and calculates the uplift in Subscriptions. |
The original admin left mid-rollout and nobody left on the team had configured a CPQ. | Sales ops runs the system itself and ships version releases monthly, at its own pace. |
Reps expected visibility into their quotes to slow them down. | Reps raise changes and get them in the next version release, and new hires call it the easiest CPQ they have used. |
DealHub AI locks every output document at the moment it is created. Previously a rep could generate a quote in Salesforce, export the PDF and change any line in it before the customer saw it. Now the document that leaves is the document that was approved.
Jaida Galeas, Senior Sales Operations Specialist, who is also on the contract admin team and took the rollout over mid-implementation when the original admin left.
Guided playbooks with parallel approvals. Discount thresholds trigger their own workflows, finance approves net payment terms, and contract admin approves the quote comments section.
100% of quotes are created in DealHub AI today, with offline modifications only after creation. Every subscription runs through it.
CRM (Salesforce), plus Slack and email for approval alerts.
One sales ops administrator ships monthly version releases at her own pace, down from several a month during stabilization. Weekly calls with DealHub AI customer success covered the handover.
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.









