Verbit sells AI transcription and captioning into education, legal, media and live events, and it has grown by buying the companies whose products it now sells. Every acquisition used to arrive as an engineering project: a design doc, a development queue, a QA cycle, and weeks before sellers could quote the new products. DealHub AI moved that work to the revenue operations team, which now builds the price book, the packages and the approval rules itself. A pricing change ships in hours and a new package reaches sellers in two or three days.
Down from two weeks when the same change ran through Salesforce development.
Product and package data reaches the onboarding team straight from the quote.
Directors approve across time zones, and delegate when one is out of office.
Verbit's revenue operations team could not change its own quoting logic. A price adjustment, a new bundle, a rule for a product line the company had just acquired: each one started as a written design document, joined the Salesforce development queue, waited behind whatever else that team had been given that quarter, and came back for a round of QA. Two weeks was normal for a change the business had already decided on. Meanwhile the acquisitions kept arriving, each with its own products, its own price book and its own way of selling, and sellers had no single place that told them what was now on the list.
We acquire a company and its products sit outside our price book for weeks. What is that costing us in pipeline we could already be quoting?
Our pricing has to stay competitive and it changes constantly. Why does a decision we made on Monday need a development cycle before a seller can quote it?
Deals that close outside DealHub AI come back with contracts nobody here agreed to support. How much legal exposure are we carrying from acquired quoting processes?
Every product manager, operations lead and legal reviewer wants a change in the CPQ. If one person cannot make those changes directly, who absorbs the queue?
| Before | After |
|---|---|
Acquired companies arrived with their own products, price books and selling motions, and sales had no single list of what it could now sell. | Acquired product lines merge into one governed price book, and DealHub AI makes them available to any sales team that needs them. |
A catalog where, in the customer's words, "every customer has its own flavors" made every packaging change a rebuild. | RevOps creates a master package with its products nested inside. Sellers pick the package and the correct line items expand behind it. |
Quoting and approvals lived in disconnected systems, so reps re-entered the same opportunity data and chased approvers by hand. | Quotes pre-populate from the Salesforce opportunity and sync back both ways. Required approvals appear on the draft, before the quote is published. |
Onboarding teams provisioned products by hand, and a deal closed outside the system triggered a chase for what had actually been sold. | Structured product and package data flows from the quote into onboarding, and FP&A can compare what was sold with what customers use. |
Once a quote was sent, nobody could see whether the buyer had opened it, shared it, or stalled. | DealRoom is the default, and DealStream shows who viewed or shared a deal, so reps call while the buyer is still reading. |
“When I’m having something in Salesforce, it will take probably two weeks… And in DealHub, again, I’m getting the requests, I’m able to do it on my own… It’s, again, hours versus weeks.”
Omer Goldman
Senior Business Operations Manager
The change Verbit had already decided on used to wait behind a design document, a development queue and a QA round. It now ships the same day the business asks for it.
Senior Business Operations Manager, inside the revenue operations team. The same person writes the requirement and implements it.
Business-owned configuration. RevOps holds pricing, packaging and approval logic. Approvals route to directors with SLA tracking and delegation.
Around three months end to end, 1.5 months to build the initial structure and another 1.5 months to go live.
Around 90% of deals run through DealHub AI, and the exceptions are named contract types the team is still working to bring in.
Salesforce (native bi-directional sync, quotes pre-populate from the opportunity), NetSuite, and Verbit's own delivery platform downstream of the quote.
Low. One revenue operations owner configures changes directly, with DealHub AI professional services available for larger projects.
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.
Eliminate the
Friction between Quote-to-Revenue
Stay up to date with the latest news and events
