santiago362

Great thread. One thing I'd separate: you've got two different problems wearing one coat. Quote speed is a process/tooling problem; the billing errors are a data and handoff problem (CRM to contract to billing). A CPQ helps the first, but on dirty upstream data it just generates wrong quotes faster, it won't close the billing leak by itself. Before buying anything, I'd instrument where it actually breaks: pull your last 20-30 problem deals and trace which field or handoff introduced the error. It usually clusters in 2 or 3 spots, and once you see them the fix is often process + clear data ownership, not a new platform. On vibe-coding: agree with Wilma, the pricing engine has to be deterministic and explainable, so I wouldn't let an LLM be the system of record for pricing or billing. A thin internal quote helper for speed is fine if your pricing logic is simple and version-controlled; the moment discounting rules and edge cases pile up is when a real CPQ earns its keep. Happy to share the simple quote-to-cash error map we use if it helps.