Zapier grew from a three-tier self-serve product into an enterprise sales motion, and its quoting stack did not come with it. Two people in Deal Desk hand-edited Word and PDF templates for every concession and carried a 100-node HubSpot approval workflow that only one of them fully understood. DealHub AI replaced both with one configuration that holds the product rules, the approval paths and the document logic together. Revenue Operations now publishes a product, pricing or approval change the same day it is asked for, without a developer and without an IT ticket.
Down from multi-day routing, measured from the moment a quote enters approval.
Product and pricing changes ship same-day, and the longest launch ran a week.
Buyers update their own POs and signers in the DealRoom instead of over email.
HubSpot was never built to run a full approval flow, so Revenue Operations built one on top of it. A single workflow grew to roughly a hundred conditional nodes routing legal, finance and sales sign-offs one after another, and one person wrote all of it. A Deal Desk admin then had to chase each approver by hand and confirm agreement before anyone could close the loop. Nothing was timestamped, so no one could say where an approval was sitting or how long it had been there. When a new teammate reviewed the flow, her first question was what the team would do if its author left.
Our entire approval path is one HubSpot workflow with a hundred nodes, and one person wrote it. What happens to enterprise deals the week she is out?
Sales has more than tripled and Deal Desk is still two people. Why is a change to a quote template still a multi-week project for us?
We cannot see where an approval is sitting or how long it has been there. How do we hold anyone to a turnaround we do not measure?
Every product we launch needs a quoting change before a rep can sell it. Why is Revenue Operations the last team able to say yes?
| Before | After |
|---|---|
Deal Desk hand-edited a Word or PDF template for every concession, renewal and custom term | Deal Desk publishes one template that assembles its own pricing tables, content blocks and legal language per deal type |
Any new product attribute, discount rule or package meant re-engineering a HubSpot workflow and a handoff to IT | Two Deal Desk admins prototype in the sandbox and publish to production themselves, without a developer |
Forecast accuracy depended on reps filling HubSpot fields by hand, and auditing a quote meant reading it | Every playbook writes structured fields into HubSpot standard objects and line items, so Revenue Operations audits by search |
Buyers changed purchase orders and signers over email, and reps pulled Legal in after the quote was out | Buyers update their own POs and signers in the DealRoom, and reps request custom legal wording inside the quote without leaving it |
A new Finance or renewal automation needed a custom script, and the request sat in a Slack thread | Revenue Operations fires a DealHub webhook into Zapier and stood up a Finance credit check in 20 minutes |
Revenue Operations answered every launch request with a technical estimate and a queue position | Revenue Operations commits in the cross-functional launch meeting, because the configuration is theirs to change |
“We have to be able to very quickly add products into our tech stack and have the flexibility for reps, with guardrails… We need to have our products in a consistent way where reps don’t have to guess when to loop someone in.”
Dyan Meahl
Revenue Operations Manager
DealHub AI gave Zapier's Revenue Operations team one place to encode which questions a rep sees and which approvals a deal triggers. Previously the rules lived in a rep's judgment, so a concession could reach Legal late or not at all. Now the segment and the deal type decide, and the template follows.
The Revenue Operations Manager, working with a DealHub AI customer success manager and a technical support engineer through implementation.
Business-owned configuration. Two Deal Desk admins hold the product, pricing, approval and document logic and edit it without a developer. Concurrent editing is supported, so neither blocks the other.
Training first, then a full-team enablement. Sandbox self-training for the admins, a two-part course for reps, and a post-rollout survey that returned no negative feedback.
HubSpot CRM (native, quotes created from the deal record, data written back to standard objects and line items), Zapier (webhook and event triggers for Finance workflows), Ironclad (MSA redlining, signed PDF pulled into the quote).
Low. Two Deal Desk admins run the platform. No engineering involvement and no code step in any workflow, which is why the team went looking for a logic engine in the first place.
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
