
Composable API Based CPQ Architecture
Veloce’s composable API based CPQ architecture is an agile platform that enables our customers to implement new CPQ processes and adapt to the constantly changing business requirements quickly.
Veloce’s composable API based CPQ architecture is an agile platform that enables our customers to implement new CPQ processes and adapt to the constantly changing business requirements quickly.
Shaowei Mao, Co-founder and CEO of Veloce, writes about the innovation in the development of Veloce CPQ.
We work with Salesforce customers to help them to augment Salesforce CPQ. There are five areas where Veloce can help companies get the value that they were expecting from Salesforce CPQ.
The R word. The signs are all around us it seems — from large layoffs at tech companies to slowdowns in manufacturing and a potential new round of supply-chain disruptions brought on by pandemics. What is the best course of action when fighting economic headwinds?
If the CPQ fits, wear it! But much of the time — let’s be honest — the CPQ doesn’t fit. Here’s an insider look at how to successfully choose a CPQ partner, from a seasoned executive who has seen it all when it comes to companies looking for the right fit (okay, maybe I haven’t seen it ALL, but pretty close!)
Not only have you NOT seen an ROI since you deployed your new CPQ application—assuming you were actually able to deploy, the CPQ has not brought the desired results to your sales and quoting process.
We have many cases where the enterprise customers use our CPQ platform to develop CPQ solutions that are so unique that only Veloce CPQ can solve their problems.
The Veloce team works hard to develop solutions that simply work and require no coding for the customer’s admin team. We take care of the CPQ development, so our customers can take care of business. However, for Systems Integrators and Developers, I’m providing a glimpse of the tool our team uses behind the scenes.
Are you with a SaaS company in the market for a CPQ solution? Beware a common sales tactic of advising you to deprioritize more complex use cases for phase two deployment. We hear stories from customers that have been told by a CPQ vendor that you should solve simple problems first and leave complex use cases for later.
When evaluating CPQ solutions, you may hear about constraint-based vs. rule-based configuration engines. This post will help make sense of the pros and cons of both. Veloce CPQ is exceptional in that it makes use of both constraint-based versus rule-based technologies. Read on to see why this is a benefit.