I like how seamlessly ServiceNow CPQ integrates with our core ServiceNow task uploads and asset database. Once a customer's enterprise hardware package is quoted and signed, the system automatically generates orchestration tasks directly inside our provisioning queues. There's no need for us to manually re-enter service specifications or verify purchase tiers across different domains because everything draws from a single unified source of data. The end-to-end automation keeps our engineers completely in sync with the sales pipelines and eliminates manual handoffs and delays entirely. It's really convenient how the platform bridges the gap between sales agreements and daily operations, ensuring data alignment across our tech stack. Review collected by and hosted on G2.com.

What bothers me the most about ServiceNow CPQ is that the pricing engine and workflow configuration can have a steep learning curve and require highly specialized knowledge to maintain and modify. A simple task like updating contract price rules can become a complex development effort, taking too much time to implement. Additionally, the user interface feels heavy and clunky when managing large amounts of items, leading to frustrating page load delays during high-volume periods. The platform would be much better if it included a simplified drag-and-drop rule builder and lighter client-side caching to speed up the interface. Review collected by and hosted on G2.com.