August 6, 2026
Why deal desks still live in spreadsheets
Most revenue teams do not choose the spreadsheet. They inherit it. A new SKU arrives on a Friday, legal wants a footnote, and someone pastes last quarter’s file into a new tab. By Monday the “source of truth” is a workbook with three hidden sheets and a discount column that no longer matches the price book in the CRM.
The spreadsheet survives because it is the only surface that sales, finance, and the deal desk can all edit without a ticket. That flexibility is also the failure mode. There is no version lock. There is no floor. There is no record of who changed a ramp from twelve months to eighteen after the customer already nodded on a call. When billing asks which file to invoice from, the answer is a thread, not a system.
A catalog-first workspace does not remove judgment. It removes the argument about which number is current. Price books version SKUs. Quotes version line items. Approvals attach to a hash of the draft, not to a filename. If finance rejects a discount, the next revision is a new object, not a red cell in the same file.
Teams that move this work out of tabs usually start with a single product family—not the whole catalog. They publish one book, route one exception band, and force every new quote in that family through the same path. The rest of the spreadsheet can wait. The point is a weekly habit: Monday’s open quotes all sit in one queue, with the same totals the customer will see.
If your close review still opens with “which file is latest,” the problem is not effort. It is that the quote never became a record. Treat it like an order that has not been signed yet, and the spreadsheet becomes a scratch pad instead of the system of record.
July 17, 2026
Designing approval rules sales will actually follow
Approval graphs fail in two opposite ways. Too loose, and every quote is “standard.” Too tight, and reps route around the desk with a side PDF. The middle is a small set of rules that fire on numbers people already understand: discount over a band, nonstandard payment terms, a SKU that is not in the book, or a multi-year ramp that finance has not priced.
Write rules against the quote, not against the person. “If discount is above 10 percent, finance reviews” is teachable. “If the AE is new, legal reviews” is not. People change seats. Catalogs change weekly. A rule that names a role and a threshold can be explained in onboarding. A rule that names a personality cannot.
Show the path before submit. If a draft will skip finance, say so on the page. If it will wait on two owners, name them. Hidden routing is why reps send the file in chat “just to be safe.” Visibility is not a courtesy. It is how you keep the official path faster than the unofficial one.
Keep the first-pass rate honest. If more than a third of quotes bounce, the band is wrong or the book is stale. Do not celebrate volume of reviews. Celebrate quotes that leave the desk without a rewrite. That is the signal that the catalog and the rule still match how the team sells.
We recommend one owner per step and a 24-hour SLA on standard bands. Escalation should be a person, not a channel. When the timer expires, the quote should not vanish into a group inbox. It should land on the backup named in the rule. Sales will follow a path they can see. They will not follow a black box that delays a close.
June 26, 2026
Handing a signed quote to billing without a chat thread
Signature is not the finish line. It is the moment the quote must become an order. If someone retypes SKUs from a PDF into Stripe or NetSuite, you have a second quote—and it will drift. The customer signed version three. Billing invoiced version two with a friendlier ramp. Support inherits the argument.
A clean handoff is a payload, not a screenshot. SKU ids, quantities, discounts, start dates, and billing cadence should leave the deal desk in the same shape they entered the catalog. If your billing tool cannot accept a ramp, the quote builder should not offer one. Mapping gaps belong in the connector, not in a late-night spreadsheet.
Lock the version at signature. After the customer signs, the quote is read-only except for a formal amendment. Amendments are new objects that point at the parent. That sounds strict until the first dispute about what was included in year two. Then the audit trail is the product.
Notify billing with a status, not a file. “qt_1842 signed, ready to invoice” is enough if the payload is already in the system. Attachments can live in the deal room for humans. Machines should not parse them. If a human still has to open the PDF to invoice, the integration is unfinished.
Start with one billing target. Teams that try to sync Stripe, NetSuite, and a warehouse in the first month usually stall. Push the signed package to the system that collects cash. Confirm totals match. Then add the general ledger. The goal is a Monday morning where ops does not ask sales which file to trust.