RFQ to CPQ
Your CPQ can configure the job. Someone still has to read the RFQ first.
An RFQ for custom equipment arrives as many documents: technical specifications, commercial terms, drawings and single line diagrams, sometimes in more than one language. Mavlon's AI Quoting Engine reads all of it and hands your CPQ a configuration that your engineer has already checked.
By Atishay Jain, founder of Mavlon · Updated November 2026
What arrives
A real RFQ is a stack of documents, and your CPQ needs answers
A CPQ such as Tacton or Salesforce CPQ works from answers. It asks how many sections you need, which ratings apply, which options to include, and which accessories to add. When a customer picks from your catalogue, the answers come straight from the order. When a customer sends an RFQ for custom equipment, the answers are spread across every document in the package.
Technical documents
You get the specification, the data sheets and the standards it points to. This is where ratings, materials, tests and options are written, often over a hundred pages or more.
Commercial documents
You get the bid form, payment terms, delivery dates, penalties and warranty. These change the price even when they do not change the product.
Drawings and single line diagrams
The single line diagram tells you how many sections to build and what goes in each one. Layout drawings and notes often add things the specification never mentions.
Other languages
European tenders often mix a German or French specification with English data sheets, and Canadian federal tenders come in English and French.
Addenda
These are changes issued during the bid, which can move a rating, a date or the whole scope after the first reading is done.
Today an application engineer reads all of this, makes notes, and types the answers into the CPQ. The CPQ prices in seconds, but the reading takes days, and the CPQ's reports never show those days because they happen before anyone opens it.
How it works
The engine reads the RFQ, and your CPQ does what it already does well
The whole RFQ goes in as it arrived. You upload the specifications, drawings, single line diagrams, commercial terms, addenda and the covering email, in whatever language they came in.
The engine reads every document and lists every requirement with the page it came from, including the count from the single line diagram, cell by cell.
Where two documents disagree, the engine prices both readings and shows the difference, so your engineer makes the call with the numbers in front of them. Open points become questions for the customer.
Your engineer checks and approves the draft. Nothing reaches the CPQ until a person has signed off.
The approved configuration and quote lines go into your CPQ. Mavlon can connect to Tacton, Salesforce and other CPQ systems, so nobody types the answers in again.
Your product model, your rules and your pricing logic stay in the CPQ. The engine adds the step in front of it by turning the customer's documents into answers someone has checked.
A real example
A 177-page switchgear tender, read before anyone configured it
We worked through a public Government of Canada tender for a new 13.8 kV switchgear lineup. It has 177 pages in English and was also published in French. Only one drawing shows the new lineup, and only fourteen pages describe the switchgear itself.
The single line diagram shows eleven cells, while the written overview asks for ten. The overview and the specification also give two different system voltages, and two pages give different head counts for the factory test trip. A CPQ would accept any of those answers without complaint, which is why the reading has to happen first.
The full walkthrough, including the single line diagram read cell by cell, is in our guide to Tacton CPQ and AI.
What stays with your team
The engine drafts, and your engineers decide
Your engineer still decides which reading of a conflict to carry, which margin to use and when to call the customer. The difference is that they decide on a complete list on the first day, instead of on whatever they found by the end of the week.
This is not catalogue pricing. The engine does not match part numbers to a price list or apply list-price discounts. It prices custom equipment from the customer's own documents, using your own rates and rules.
Bring one past RFQ, and we will show you what your CPQ would have received.
On a short call, we take an RFQ your team has already quoted and show the configuration and draft quote the engine produces from it.
Book a Demo
Frequently asked questions
Does Mavlon replace our CPQ?
No, it does not replace your CPQ. Your product model, rules, approvals and quote documents stay in your CPQ. Mavlon's AI Quoting Engine reads the RFQ in front of it and passes the approved configuration and quote lines into it.
Which CPQ systems can it connect to?
Mavlon can connect to Tacton, Salesforce and other CPQ systems. After your engineer approves the draft, the configuration and the quote lines go into the CPQ, so nobody retypes them.
Can it read single line diagrams and drawings?
Yes, it can read them. It reads drawings and single line diagrams along with the specification, counts what the drawing shows cell by cell, and ties each answer to the page it came from.
Does it read RFQ documents in other languages?
Yes, it reads them. The engine reads documents in other languages, so an RFQ in German or French, or one that mixes languages, goes through the same steps as one in English.
What if we have no CPQ, just spreadsheets?
Then the priced draft quote comes to your team directly, priced from your own rates. You can see
AI estimating for custom manufacturing. The CPQ connection is one place the same answers can go.
Is this catalogue pricing?
No, it is not catalogue pricing. It does not match part numbers to a price list or apply list-price discounts. It prices custom equipment from the customer's documents, using your own rates and rules.