Craftable is the back-office platform hospitality operators use to connect purchasing, inventory, accounting and analytics in one system. Its own sales team sells that platform to restaurant and hotel management groups that run several brands and dozens of locations under a single agreement, and it used to quote them as open text in a signature tool with no SKUs and no approval rules. DealHub AI replaced that with guided selling, location groups and pricing tables that separate subscription fees from one-time fees. A fractional RevOps lead now reconfigures nine SKUs and 72 pricing variables in an afternoon, and reps quote a multi-brand group in under ten minutes.
RevOps deploys a full SKU and pricing revision with no consultant and no IT
Billing rules run inside the quote, so contracts reach finance execution-ready
Craftable was hiring fast and its finance and billing team was tightening what a contract was allowed to say. The billing requirements reps had to honour lived in a Google Doc, and quoting itself happened as open text in a signature tool with no defined SKUs, no pricing structure and no approval rules. Deals closed, and then two or three weeks into implementation finance came back to say something had been sold that should not have been, or something had been left off the contract. Each one became a change order, and a change order three weeks into onboarding is the first thing a new hospitality operator learns about working with Craftable.
Our billing requirements live in a Google Doc that reps are supposed to remember. Why are we finding out three weeks after signature that a contract missed one?
One management group can run three brands across a dozen locations on a single agreement. How does a rep split subscription fees by location and implementation fees to corporate without getting it wrong?
We have rebuilt our SKUs twice and launched two promotional offers in six months. Why should the next pricing decision need an outside consultant and a multi-week project?
Finance assumes half of what we sell will come back as a repaper. What has to change before they can trust the forecast?
| Before | After |
|---|---|
A rep hand-built the split between fees billed to a corporate account and fees billed per location, and the buyer saw it for the first time in the contract. | Location groups carry a pricing table per brand, and the buyer selects the billing split themselves in the DealRoom before signing. |
Adding a pricing dimension meant a new SKU for every combination, or a manual workaround nobody had written down. | RevOps configures conditional pricing variables against nine SKUs and deploys the change without IT or an outside consultant. |
Reps rebuilt each quote as open text, working from memory or from whatever past deal they could find. | Reps answer the playbook's required questions, and the approved price, discount tier and approver come back automatically. |
Quoted line items lived outside the CRM, so finance could not report on what was sold, what was discounted or what was due to implement. | Finance and leadership read SKU, quantity, discount and location group from HubSpot line items without asking a rep. |
Proposals went out as static documents, with prior MSAs and supporting files chased separately over email. | Buyers redline, upload documents and sign inside one branded DealRoom that carries both pricing tables. |
DealHub AI holds the billing structure a multi-brand hospitality agreement needs. Previously a rep hand-built the split between fees charged to a corporate account and fees charged to each location, and the buyer could not see that split until the contract arrived. Now location groups carry a pricing table per brand and the buyer selects the split before signing.
A fractional revenue operations lead owns the configuration today, working with the assigned DealHub AI customer success manager. He inherited the system rather than deploying it.
Business-owned. RevOps configures SKUs, conditional pricing variables, discount thresholds and approval routing directly. Approval routing differs by team, with new business and CS expansions escalating to different managers.
The implementation predates the current RevOps owner, who inherited the configuration, so no deployment duration is on record. The first measured milestone is finance reporting no ongoing billing issues, six months after go-live.
Full adoption across account executives selling new business and CSMs selling upgrades and expansions. Reps report fewer issues than under the previous process, and complaints are minimal.
HubSpot (CRM, native line-item sync carrying SKU, net price, discount percentage, discount amount, gross and quantity, specified by location group). A separate billing platform downstream of quote entry. DealHub AI replaced a standalone e-signature tool.
Low. One fractional RevOps lead runs configuration and pricing changes with no developer, no IT ticket and no outside consultant. A full nine-SKU revision takes an afternoon.
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.









