MotorK builds the software car manufacturers and dealers run their customer lifecycle on, and it sells that software in six countries and six languages, as single services and as packages, to buyers who are entirely digital and buyers who are not. For years its sellers quoted from their own Excel files, so what a customer was promised depended on which file the seller opened and whether anyone had checked the promise internally. MotorK's operations team replaced those files and its disconnected billing tools with DealHub CPQ and DealHub Billing on one record. The same team now approves what goes out at the proposal stage, and a closed-won deal in Salesforce raises its own subscriptions, billing lines and invoices.
Every contract enters MotorK's systems validated, so delivery starts without rework or renegotiation.
Live on January 1, on schedule and on budget, with existing invoicing never interrupted.
MotorK quoted out of Excel. Each salesperson kept a file with their own formulas and their own prices, and over a decade there were as many versions as there were sellers. The spreadsheet offered no control and no structure around what a customer was being promised, so contracts went out carrying deliverables nobody had checked internally. The delivery team found out afterwards. Onboarding turned messy, project starts slipped, and MotorK was discovering what it had signed instead of deciding it. By the time it went to market for a replacement it needed one system that could quote and invoice across six countries and six languages, and it needed the January 1 date it had already committed to.
Each of our salespeople quotes from their own spreadsheet with their own prices. How do we know what we are charging in each market?
We sign contracts with deliverables nobody checked internally. How much delivery time are we losing to cleaning that up afterwards?
We sell in six countries and six languages, the same services individually and as packages, to digital and non-digital buyers. Which vendor can price all of that in one place?
We have more than a decade of contracts created outside any CPQ or CRM. Can we move them without missing an invoice cycle?
We committed to a January 1 go-live and the management team around the project is changing. Who keeps this on schedule?
| Before | After |
|---|---|
A closed deal was re-keyed by hand before anything could be billed, so quoting and billing ran as two disconnected processes. | A closed-won opportunity in Salesforce raises its own subscriptions, billing lines and invoices without re-entry. |
More than a decade of contracts sat outside any structured CPQ or CRM, with pricing, terms and billing logic scattered across systems. | MotorK's finance team invoices existing customers through the new system while new deals are quoted and billed from it too. |
A customer holding five products received five separate invoices in a cycle, and finance carried the chasing. | Each customer's product lines consolidate into one invoice per cycle through the ERP connection. |
Six countries, six languages, and services sold both individually and as packages needed a different workaround in every market. | MotorK's operations team runs all six markets, both selling models and both buyer types from one environment. |
Sellers worked with minimal oversight, and adding required fields at the proposal stage was expected to meet resistance. | Sellers work inside guided playbooks and reach an approved proposal on the first attempt, after roughly two weeks of friction. |
Billing data sat across several tools and commercial patterns had to be assembled by hand, so nobody could say what was invoiced, to whom, or at what discount. | MotorK's leadership reads proposal volumes, discount levels by rep, product and country, and committed delivery times, and runs quarterly reviews from them. |
A new approval step or a new document rule was a request with an unknown answer and an unknown date. | MotorK's operations team adds an approval step or a delivery sign-off itself, in hours, without a vendor release. |
MotorK's operations team got one vendor for quoting and subscription billing instead of two. Previously, six countries, six languages and a service suite sold both individually and as packages meant no single tool covered the whole commercial motion. Now DealHub CPQ and DealHub Billing run that motion from one environment.
MotorK's strategy and operations lead, with an implementation manager from DealHub AI embedded through the build and on site in Milan.
Business-owned. MotorK's operations team sets the required fields, approval steps and delivery sign-offs at the proposal stage, and adds new ones itself as the go-to-market model changes.
DealHub CPQ was live on January 1, on schedule and on budget, with billing implemented against the CPQ structure and existing invoicing never interrupted.
Sellers were socialised well in advance and hit roughly two weeks of friction before full adoption. CPQ adoption was counted in days and billing adoption in billing cycles.
Salesforce as the CRM, and MotorK's ERP connected to DealHub Billing for invoice consolidation.
MotorK's operations lead was in contact with the implementation manager daily from mid-September to the end of December. Ongoing approval and document changes are made by MotorK's own team in hours, without a vendor release.
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.









