WRITER, an enterprise AI platform with roughly 400 employees in San Francisco, shifted from seat-based software pricing to consumption-based AI pricing. Its legacy quoting tool could not handle the change. The company adopted DealHub CPQ. Sellers who had only ever quoted software seats were active and quoting usage-based contracts within 24 hours of training.
2 ICs held flat while ARR and the sales organization grew.
Minor changes ship without becoming IT projects, so pricing keeps pace with the market.
Before DealHub CPQ, WRITER's RevOps team ran quoting through a legacy CPQ that locked pricing and packaging into a fixed structure, at the exact moment the company needed to move from seat-based licenses to consumption-based AI pricing. Sellers who had spent their careers quoting traditional SaaS seats now had to quote platform access and usage in the same deal, with no system built to teach them how, and WRITER's previous tool could not flex to support it.
How do reps quote AI consumption when they have only ever quoted software seats?
How much configuration flexibility does the business need before locking in a pricing model it may still overhaul?
How does a brand-new pricing motion reach sellers without slowing deals down?
How does Deal Desk stay out of the way as pricing changes on a rolling basis, whether that is tokens, credits, or playbook runs?
| Before | After |
|---|---|
A legacy CPQ locked pricing and packaging into a fixed structure. | DealHub CPQ keeps pace as WRITER's pricing model changes. |
Sellers quoted software seats only, with no built-in path to learn consumption pricing. | DealHub's Guided Playbooks guide sellers through consumption-based quoting in the context of each deal. |
Pricing and packaging changes took weeks. | WRITER's RevOps team deploys them in hours. |
Quotes were built in spreadsheets and slide decks, then re-entered in the CPQ late in the deal. | Sellers quote directly in DealHub CPQ from the start. |
Quote approvals ran through email threads. | Every approval routes through Slack, with email notifications off. |
WRITER's RevOps team encoded consumption logic, tokens, credits, and playbook runs into DealHub CPQ, so sellers quote the right structure instead of guessing at one they'd never sold.
WRITER’s RevOps team captures usage entitlements on the front end in DealHub CPQ and passes them to Orb, the marriage of data that unlocks downstream, usage-based expansion.
Approvers clear every quote in Slack, with email notifications off. WRITER's Deal Desk uses DealHub DealRoom to generate and send renewal quotes automatically.
DealHub AI gave WRITER's RevOps team pricing and packaging it can change without re-engineering the system. Previously, every change to the model started with whether the tool could support it at all. Now minor pricing and packaging changes ship in hours instead of running as projects.
WRITER’s RevOps team owns CPQ administration, the full rollout, and every pricing and packaging change, investing more in administration upfront so the rest of the revenue organization can move faster.
WRITER’s Deal Desk owns renewals, using DealHub DealRoom to generate and send renewal quotes automatically, and held at 2 ICs, with zero hires added, as ARR and the sales org grew.
January kickoff to March go-live. The business led implementation internally, with two weeks of intensive launch support. DealHub DealRoom for renewals deployed as a second phase.
Sellers own quoting from their first deal. DealHub’s Guided Playbooks give them context and enablement in real time, and sellers were actively quoting within 24 hours of training.
Salesforce CRM, Orb for usage entitlements and billing, and Slack for approvals.
WRITER's RevOps team passes quote-level entitlement data from DealHub CPQ into Orb, so customer usage entitlements are set at the moment of quoting rather than pieced together after the deal closes.
Approvers clear every quote approval in Slack, with each message structured to give them the right information for that discount approval type.
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.









