Skip to content

CPQ software: when you need it and how to link it to CRM and ERP

What will you find in this article?

CPQ software (configure, price, quote) is worth it when quotes depend on many variants, rules and prices that are put together by hand today, and when the quote data has to reach the CRM and the ERP without being retyped. The link is designed before the software: you decide which data passes, which system owns it and who keeps it up to date. Below are the four steps to decide.

CPQ software: when you really need it

A CPQ pays off when preparing a quote takes time and produces mistakes: many product combinations, prices that change with quantity and terms, compatibility rules known only to people who have worked at the company for years. With a simple price list, a spreadsheet or the quoting module of the ERP is enough. The term is explained in the Decode entry CPQ; here we deal with the decision and the data.

The software alone solves little. A quote starts from a catalogue, goes through a negotiation and ends in an order, and each of these steps lives in a different system. If the CPQ is not linked to the other two, the salesperson retypes the same data several times and the figures stop matching.

How common CRM and ERP are among SMEs

According to Istat, in 2025 CRM is used by 21.1% of small and medium firms against 56.5% of large ones, and ERP software by 48.8% of SMEs against 85.9% of large firms (firms with 10 or more employees). In 2025, according to Istat, 56.0% of firms use management software, about seven points more than in 2023.

CRM and ERP: the gap between SMEs and large firms

Firms with 10 or more employees using each software, by size, 2025

CRM and ERP: the gap between SMEs and large firmsPaired horizontal bars. ERP software: SMEs 48.8%, large firms 85.9%. CRM software: SMEs 21.1%, large firms 56.5%.Small and medium firms (10-249)Large firms (250 or more)ERP softwareERP software, Small and medium firms (10-249): 48.8%48.8% SMEsERP software, Large firms (250 or more): 85.9%85.9% largeCRM softwareCRM software, Small and medium firms (10-249): 21.1%21.1% SMEsCRM software, Large firms (250 or more): 56.5%56.5% largeCRM and ERP: the gap between SMEs and large firmsPaired horizontal bars. ERP software: SMEs 48.8%, large firms 85.9%. CRM software: SMEs 21.1%, large firms 56.5%.Small and medium firms (10-249)Large firms (250 or more)ERP softwareERP software, Small and medium firms (10-249): 48.8%48.8% SMEsERP software, Large firms (250 or more): 85.9%85.9% largeCRM softwareCRM software, Small and medium firms (10-249): 21.1%21.1% SMEsCRM software, Large firms (250 or more): 56.5%56.5% large
Source: Istat, Enterprises and ICT, 2025 (press release of 15 December 2025).

For an SME this means that one of the two systems is often missing or little used: by difference, our own calculation, 78.9% of SMEs do not use a CRM. If there is no CRM, the CPQ becomes the first place where requests arrive in an orderly way, and it is worth deciding right away where they will end up. If the ERP is partial, the price list lives in scattered files and needs sorting out before configuring anything.

Step 1: which quotes justify a CPQ

A quote justifies a CPQ when it has three features together: many possible combinations, rules that can be written down (compatibility, discounts, minimums) and a volume that makes redoing it by hand expensive. If the second is missing, the problem is commercial, not software. If the third is missing, a well-made spreadsheet costs less.

The starting calculation uses the company’s own numbers: average time to prepare a quote, multiplied by the quotes per month and by the hourly cost of whoever prepares them, plus the hours spent fixing errors or clarifying incomplete requests. If the total is small, the CPQ does not pay for itself.

As a hypothetical example, take a shelving company. Each request brings dimensions, load capacity, accessories and delivery, and the salesperson puts the items together from the price list. The variants are many and the rules can be written down, so a CPQ pays off here. A company that sells three products at a fixed price, instead, does not need one.

Step 2: which data goes to the CRM and the ERP

The commercial context goes from the configurator to the CRM: who is asking, what they chose and where the negotiation stands. The data needed to produce, invoice and ship goes to the ERP. One rule prevents duplicates: each piece of data has a single owner system, and the others either read it or receive a copy with a reference to the original.

This is the list to fill in, item by item:

  • From the configurator to the CRM: contact and company, using the existing identifier so as not to create duplicates, the chosen configuration in readable form, the quote value, number and version, status, date and origin of the request (campaign or channel).
  • From the configurator to the ERP, only after acceptance: item codes, quantities, prices and discounts applied, payment and delivery terms, reference to the quote.
  • From the ERP to the CPQ: price list, availability, delivery times, customer records and reserved terms.
  • From the CRM to the CPQ: if the customer is already known, the history of negotiations and the status of the current one.

The quote stays in the CRM while it is a negotiation and becomes an order in the ERP when it is accepted. A common key is needed to recognise the same customer in all three systems, for example the VAT number or a customer code. When a transfer fails the quote must not disappear: a retry queue and an alert to a person are needed. The Decode entry CRM quote sync describes this step.

Step 3: who keeps the data up to date

A CPQ is correct as long as the price list, rules and compatibility are, and if nobody has written responsibility for them, the first price list that changes produces wrong quotes. One person is needed for each piece of data: price list and availability to whoever manages the ERP, configuration rules to whoever knows the product (technical or sales department), CRM fields to whoever administers it.

It also needs deciding who approves a change before it goes live and how often the rules are reviewed. For exceptions, such as an off-scheme discount or an unforeseen variant, a planned path is needed: a person approves and records them, instead of working around the system. The Custom quote flow is the name for this path.

Step 4: how to measure the result

Before starting, three measures are set and read for a few months after release: the time between the request and the quote sent, the share of requests that reach the CRM already complete, the share of quotes that become orders. They are compared with the starting situation, measured by hand for a few weeks: without that baseline you cannot know whether the CPQ changed anything.

You also look at the points where people configuring leave the flow, and at synchronisation errors between systems. These signals tell you whether the problem lies in the questions asked, in the rules or in the link.

A complex catalogue: the Metalsistem case

The closest case at LU3G is Metalsistem Lombardia, an industrial shelving and logistics company: a platform with over 100 pages, navigation by application, sector, service and product, Google Ads campaigns and GTM tracking. It is neither a configurator nor a CPQ, and we do not present it as one.

It does show where you start: from an orderly catalogue, where it is clear which products exist, for which applications and how they relate to each other. That map comes before the configuration rules: a CPQ built on a confused catalogue carries the same problems.

Five mistakes to avoid

Five wrong choices take away the advantage of a CPQ. All of them are made before any code is written, and each one corresponds to a step in this method, listed in the order in which they usually go wrong.

  • Choosing the software before describing the quotes made today.
  • Having the same data entered in two systems, hoping someone will realign them.
  • Linking the systems in one direction only: the CRM receives the quotes but the price list does not flow back to the configurator.
  • Not naming who updates the price list and rules.
  • Not measuring the starting situation, and then not knowing what changed.

Where to start

The step to take now is to collect about twenty recent quotes in a sheet: items, rules applied, the system each piece of data came from, who updates it. The list of data to pass between systems comes out of it, and you can see whether a CPQ is justified.

LU3G can work alongside you: it builds custom web configurators, also CPQ. In projects we map catalogue, rules, exceptions and dependencies together with your team and check the calculations on real cases before launch. The configurator can send configurations, leads and summaries to the CRM, email, e-commerce or external software; data, permissions and error handling are defined in the project. For the CRM side there is the page marketing automation and CRM.

More from LU3G

Sources

  1. Istat – Enterprises and ICT, 2025 (press release, 15 December 2025): firms with 10 or more employees using CRM and ERP, by size, and the share of firms with management software in 2025 compared with 2023.
Photo of Giordano Vinci

Giordano Vinci

Giordano Vinci is CEO of LU3G, a digital agency that works alongside companies and SMEs on websites, SEO strategy, advertising campaigns and online growth. His approach combines consulting, method and strategic vision, with the aim of turning digital into a practical business tool.

Photo of Giordano Vinci

Giordano Vinci

Giordano Vinci is CEO of LU3G, a digital agency that works alongside companies and SMEs on websites, SEO strategy, advertising campaigns and online growth. His approach combines consulting, method and strategic vision, with the aim of turning digital into a practical business tool.

More stories, ideas and insights from the Magazine.