AI CPQ Software: The 2026 Guide to Configure, Price, Quote with AI Agents

A mid-sized enterprise software vendor we worked with last year processes about 1,700 commercial offers per year. They have four people in the back office whose job is to take an incoming offer template, transcribe it into the CRM, cross-check the signing authority against the finance system, validate the payment terms against the customer's master data, and chase the sales rep when something does not match.

They do this manually. Every offer.

Their CRM is V-Tiger. Their finance system is SAP. Their offer template is a Word document with thirty-two fields, half of which the sales rep guesses at and half of which the back office rewrites. The sales reps complain that approvals take too long. The back office complains that the reps keep submitting offers that violate the company's own signing-authority matrix. Both sides are right.

This is the problem CPQ software was invented to solve. And in 2026, it is the problem AI agents on top of CPQ are quietly redefining — not by replacing the CRM or the ERP, but by sitting between them and catching the discrepancies before they cause rework.

This guide is for sales operations leaders, CFOs, and revenue operations architects evaluating their CPQ stack in 2026. It covers what CPQ software actually does, how the category has split between legacy enterprise platforms and AI-native entrants, what changed when AI got embedded in the workflow, and — critically — how to think about CPQ when your reality is a heterogeneous stack of SAP, a CRM that is not Salesforce, and a Word template nobody wants to migrate.

What is CPQ software?

Configure, Price, Quote (CPQ) software is a category of sales technology that automates the three steps a complex enterprise sale goes through between "the customer is interested" and "we have a signed order": configuring the right product bundle, pricing it correctly under the right discount and approval rules, and producing a quote document the customer can sign.

Each of the three letters is doing real work.

Configure means turning customer requirements into a valid product configuration. For a manufacturer of industrial machines this might mean validating that the chosen motor fits the chosen frame; for an enterprise SaaS company it means making sure the customer is not trying to buy a tier-2 module without the tier-1 license that depends on it. Configuration enforces the business rules of "what we sell" so the rest of the quote does not start from an invalid premise.

Price means applying the company's pricing rules to that configuration. List price, volume discount, customer-tier discount, regional override, partner margin, channel-conflict logic, and the inevitable "the VP said we could give them another 3%" — all of these are rules a CPQ system encodes, applies, and (where required) escalates for approval. The hardest pricing problems in B2B are not arithmetic; they are governance.

Quote means generating the document the customer signs. That document has to reflect the configured products and the calculated price, but it also has to encode the legal terms (signing authority, payment terms, liability caps, SLA references) that the company's legal team has approved. A quote is a binding commercial document; a wrong number on a quote is a wrong number on a contract.

Before CPQ existed as a category, sales reps did all three steps in spreadsheets and Word documents. The result was the situation our reference customer still lives in: 1,700 offers a year, four people in the back office cleaning up the configurations, prices, and terms that came out wrong on the way to a signature.

CPQ as a software category formalized this workflow into a single system. The first generation (Apttus, BigMachines, Cameleon — most of which were eventually acquired by Salesforce, Oracle, or Conga) ran inside the CRM and turned the spreadsheet into a structured pipeline. The current generation increasingly runs on a different premise: that the structured pipeline itself is a substrate AI agents can validate, score, and improve in real time.

The CPQ market in 2026: who actually competes

The CPQ category in 2026 is shaped by three forces that have not fully resolved. It is worth being honest about all three before recommending any vendor or pattern.

The first force is consolidation among the legacy enterprise CPQ platforms. Salesforce CPQ (the old Steelbrick, since absorbed into Revenue Cloud), Oracle CPQ (formerly BigMachines), SAP CPQ, and Conga CPQ (the merged Conga + Apttus business) anchor the high end. They are deeply integrated into the underlying CRM or ERP, they are expensive, they require specialized implementation partners, and they have seen most of their innovation budget redirected from "is this a better CPQ" to "we have added AI features." For an organization already standardized on Salesforce, Oracle, or SAP, the path of least resistance in 2026 is still to deploy the CPQ module from the same vendor and accept the trade-offs.

The second force is the rise of AI-native CPQ entrants. Servicepath, Hyperline, Subskribe, Salesbricks, Everstage, and a handful of younger Y-Combinator-funded names (alguna among them) have positioned themselves explicitly against the legacy stack. Their pitch is that CPQ should be configurable in days rather than months, that AI should be in the core of the configuration and pricing logic rather than bolted on, and that the deployment should be light enough for a midmarket sales-ops team to own without a six-figure implementation engagement. Some of these will be acquired by the legacy players within the next eighteen months; some will become genuine alternatives at midmarket scale; and some will not survive the next downturn. Buyers should evaluate them as serious options but with the caveat that vendor longevity is a real factor in a system that lives at the heart of revenue operations.

The third force is the wedge category — AI agents that operate alongside an existing CPQ rather than replacing it. This is where most enterprise reality lives in 2026. An organization has Salesforce or SAP CPQ already; they cannot rip it out; they also cannot accept the rework loops, the discrepancy rate, or the FTE cost of running it without intelligent validation. The agents in this wedge category do not configure or price products; they validate that what was configured and priced is consistent with the company's master data, signing authority, and contractual doctrine — and they fire alerts when it is not. The 1,700-offer reference engagement above sits squarely in this category. We will return to the architecture in the section on Knowlee's approach.

The relevant landscape for a 2026 buyer is therefore:

The buyer question is which of these four tiers is the right entry point. A net-new sales-ops investment with no incumbent CPQ usually starts at the AI-native tier; an enterprise on Salesforce or SAP rarely benefits from switching CPQ vendors and instead benefits from the wedge category running validation on top of what they already have.

For a deeper comparison of CPQ versus the broader category of quoting software (which is a different and easier question), see CPQ vs quoting software.

What changed when AI got embedded in CPQ

The AI features now standard on most CPQ platforms split into four real categories, plus a fifth one that is mostly marketing.

Guided selling uses AI to recommend the right configuration for a given customer based on past deals, similar customer profiles, and the current pipeline. The recommendations are imperfect but useful — they bias the rep toward configurations that historically closed and away from configurations that historically stalled. Salesforce Einstein, Conga AI, Tacton AI, and Servicepath all ship a version of this. The quality varies more by training-data quantity than by model architecture; an AI guided-selling layer trained on six months of midmarket deals is genuinely worse than one trained on five years of enterprise deals.

Pricing optimization uses AI to suggest discount levels that balance close probability against margin erosion. PROS and Vendavo built their businesses on this before the LLM era — their approach is statistical price elasticity, not generative AI. The newer entrants ship LLM-flavored versions that are more conversational ("the AI will explain why it suggested 12% rather than 15%") but the underlying optimization is still a pricing-science problem, not a language problem.

Document drafting uses generative AI to draft the quote text, the cover letter, the SOW, and (sometimes) the legal terms based on the configured deal and the customer profile. PandaDoc, DocuSign CLM, and a long tail of newer document tools all do this. The output is usually editable, often acceptable, and occasionally embarrassing — most enterprise sales teams keep a human in the loop on the final document for the same reason most legal teams keep a human in the loop on a contract.

Discrepancy detection is the category our reference engagement turns out to need. An AI agent reads the incoming offer (whether from a CPQ output, a Word template, or an email attachment), retrieves the relevant evidence from the company's master data systems, and produces a structured report of every field that does not match. Signing authority, payment terms, customer master record, contractual clauses, pricing rules. This is not configuration; it is validation. It does not replace the CPQ; it stands in front of the CRM and says "this offer is internally inconsistent, here are the eleven fields that need attention before you submit."

Conversational sales assistants is the fifth category, and it is mostly marketing. A chatbot in the CPQ that answers "what is the discount cap on this product line" is helpful but not transformative. Most of the conversational-assistant features shipped by CPQ vendors in 2025 are thin wrappers on the same retrieval logic the platform was already running. Useful, but evaluate them as features rather than as buying decisions.

The honest summary is that AI in CPQ in 2026 is a feature surface, not a category disruption. The legacy platforms have integrated AI into their existing flows and the newer entrants have built AI into their core. The genuinely new architectural pattern is the wedge — discrepancy-detection agents that operate beside the CPQ rather than within it — and that is the pattern our reference customer needed.

For a closer look at how discrepancy-detection works architecturally, see CPQ discrepancy detection with AI.

How to evaluate CPQ software in 2026

The standard CPQ buyer's guide checklist is well-trodden — pricing-engine flexibility, approval-flow configurability, CRM integration, document templates, mobile support. We will assume you can find that checklist on Capterra, G2, and DealHub, all of which do this part well. What follows is the part most CPQ buyer's guides skip: the diligence questions that actually predict whether the deployment will work in year two.

Question 1: What is your ground truth? A CPQ system is only useful if the master data it relies on is reliable. If your customer master record is split between SAP (finance) and a CRM (sales), with the two systems disagreeing about who the legal contracting entity is for thirty percent of accounts, no CPQ will save you. The first question is which system holds the truth for which fields, and what the reconciliation pattern is when the two disagree. This is a data-governance problem, not a CPQ problem, and a CPQ deployment that does not surface the answer to this question will surface it later as a series of escalations the back office cannot resolve.

Question 2: What is the discrepancy cost in your current process? Count the rework loops. How many offers per quarter come back to sales because something did not match? How many were submitted with the wrong signing authority? How many produced a contract amendment within ninety days of signature because the price escalator was wrong? The number is usually larger than the leadership team thinks. If the number is small, you have a configuration problem and a CPQ in the traditional sense will solve it. If the number is large, you have a validation problem, and a CPQ alone will not.

Question 3: How many ERPs and CRMs do you actually run? The marketing brochure assumption is one ERP, one CRM, one CPQ. The reference engagement reality is SAP for finance, V-Tiger for CRM, a proprietary customer-success platform for renewals, and a Word template for the offer itself. CPQ vendors will tell you they integrate with all of these; the question is how. A real-time bidirectional sync between SAP and a third-party CPQ is a multi-quarter integration project. A periodic batch reconciliation is a different project with a different cost profile. The implementation timeline you are quoted assumes one of these — confirm which.

Question 4: What is the AI Act classification of your CPQ outputs? In the EU, an AI system that generates pricing or contractual terms which materially affect a B2B customer falls into a regulatory grey zone that the AI Act and its implementing acts have not fully resolved. Pricing recommendations probably do not qualify as high-risk in most readings. Automated approval of credit terms might. Automated generation of terms that touch employment, citizen, or healthcare data does. The classification is a use-case question, not a vendor question, and it should be answered before procurement signs the contract — not afterwards.

Question 5: Will this deployment displace people? This is not a regulatory question; it is a change-management question, and it is the question CPQ implementations slip on more than any other. Our reference engagement has four people in the back office. A CPQ that fully automates their job creates a re-deployment problem the executive committee has to plan for in advance. An agent-based discrepancy-detection layer that frees up two FTE worth of capacity creates a different problem (where to redeploy the released time) but a more tractable one. The right answer depends on the company's growth profile and willingness to absorb organizational change.

The five questions above are usually more predictive of CPQ implementation success than any feature-comparison matrix. We have seen feature-rich enterprise CPQ deployments fail because the master-data ground-truth question was never resolved, and we have seen deliberately narrow agent-based discrepancy projects succeed because they were scoped against an answerable question.

For a structured framework on the broader build-vs-buy decision (which underlies this entire analysis), see our AI build vs buy framework.

The discrepancy-detection wedge: SAP + CRM + offer-template doctrine

The most interesting AI pattern in CPQ in 2026 is not in the CPQ vendors at all. It is in the wedge: an AI agent that sits beside an organization's existing offer-creation workflow, retrieves the relevant evidence from the company's systems, and produces a structured discrepancy report when something is internally inconsistent.

The architecture has four moving parts.

The offer ingestion layer parses the incoming offer document, whatever its shape — Word template, PDF, CPQ-generated quote, email attachment, scanned document — and extracts the structured fields that need to be validated. This is where document-intelligence tooling (UiPath Document Understanding, Hyperscience, Azure Document Intelligence) historically lived, and it is the part most teams underestimate. Heterogeneous templates evolve, scanning quality varies, and the parser has to be tolerant of the messy reality without silently dropping fields it failed to extract.

The retrieval layer pulls the relevant evidence from the company's master data systems. For our reference engagement that means: the customer master record from SAP, the customer's commercial history from V-Tiger, the company's signing-authority matrix (typically a policy document or a structured table), the canonical offer template for the customer's segment, and the company's contract doctrine (the preferred-language clauses, redline patterns, and prior-renewal terms). Each of these lives in a different system; the retrieval layer is where the integration cost shows up. This is essentially retrieval-augmented generation applied to a sales-ops corpus.

The validation layer compares the parsed offer fields against the retrieved evidence. Signing authority: does the rep submitting this offer have authority for this discount level? Payment terms: are the proposed terms consistent with what the customer has been billed in the past? Master data: does the customer name on the offer match the legal entity in SAP? Clauses: does the offer reference the current version of the SLA template? Each comparison produces a structured result — match, mismatch, or "needs human review."

The output layer produces the discrepancy report and routes it. The report is usually a structured document with severity-ranked items. Critical mismatches (signing authority violation, master-data inconsistency that would cause an invoicing failure) trigger immediate alerts to the responsible sales rep and to the back office. Soft mismatches (a clause that is consistent with the prior renewal but not with the current standard template) produce a warning that lets the human decide. The output should be auditable: every flagged item ties back to the retrieved evidence that triggered the flag, so the rep responding to the alert can see why it was raised.

This architecture has three properties that make it different from a traditional CPQ deployment.

It is non-rip-and-replace. The customer keeps SAP, V-Tiger, the Word template, the existing CRM, and the existing offer-creation workflow. The agent runs alongside, reading from each system. The deployment risk is correspondingly lower — there is no migration, no configuration of pricing rules, no retraining of the sales team on a new tool.

It is governance-shaped. Every flagged discrepancy has a citation back to the evidence that triggered it. Every release of the agent ships with an updated set of validation rules versioned against the current version of the signing-authority matrix and contract doctrine. The audit trail is the primary output — operators can show a regulator (or an internal auditor) exactly which offer was flagged for which reason, and what the resolution was.

It compounds across use cases. The retrieval substrate that powers offer-validation is the same substrate that powers contract review, RFP response, and HR Q&A in our cross-functional architecture. Adding the second use case (contract clause validation, say) does not require a new retrieval pipeline — it is another agent reading from the same Enterprise Brain. The unit economics flip from "expensive single-purpose deployment" to "shared infrastructure paying off across departments."

The reference engagement that motivated this entire architecture has four people in the back office today. The pilot scope was a 3-to-4-week deployment validating the agent on a sample of historical offers, with the explicit ROI target of freeing up two of the four FTEs for higher-value work. The bottleneck on the deployment was — as predicted — not the AI; it was negotiating read access to SAP and V-Tiger. Once the integration was open, the agent shipped on schedule.

We unpack this pattern in detail in CPQ discrepancy detection with AI.

CPQ for manufacturing, SaaS, and other verticals

CPQ is not one product; it is several. The vertical you operate in changes which platform is the right anchor and where the AI value sits.

Manufacturing CPQ is dominated by Tacton, Epicor CPQ, Infor CPQ, and a long tail of vertical-specific players. The configuration complexity is mechanical — does this motor fit this chassis, does this valve handle this pressure rating, does this cable length fit this rack-unit footprint — and the underlying engine is rules-based with increasingly heavy AI overlays for guided selling. The pricing logic is often tied directly to a manufacturing ERP (BOM, cost-of-goods, capacity), which is why manufacturing CPQ tends to live inside or close to an ERP rather than a CRM. AI value here is concentrated in guided selling (recommend the right configuration faster) and in cost-prediction (forecasting the actual production cost of a configured machine before quote signature).

SaaS CPQ is dominated by Salesforce CPQ, the AI-native entrants (Subskribe, Hyperline, Salesbricks), and PandaDoc-class proposal tools that have crept into CPQ territory. The configuration complexity is licensing — module dependencies, tier upgrades, usage-based metering, multi-year ramp pricing, channel partner overlays. AI value is concentrated in usage-prediction (forecast what a customer will actually consume so the quote ramp matches reality) and in deal-desk automation (pre-validate non-standard terms against the company's approval matrix before they reach the human deal desk).

Distribution and channel CPQ sits between manufacturing and SaaS — partner-tier discounts, channel-conflict logic, regional pricing, and stock-availability checks dominate. ConnectWise CPQ owns the IT-channel niche; Apparound is strong in the European channel sales space; QuoteWerks is a long-running player at the SMB end. AI value here is concentrated in margin protection (flagging when a partner discount is structurally unprofitable) and in cross-sell suggestion (which adjacent SKU has the highest historical attach rate at this channel tier).

Industrial services CPQ — utilities, telecommunications equipment, industrial maintenance — has its own dedicated platforms (FPX, Servicepath, ServiceNow CPQ on the IT-services side). Configuration complexity is service-bundle composition; pricing logic is tied to service-delivery cost; and the AI value is in service-utilization forecasting that improves the quote's profitability prediction.

Italian and EU-specific CPQ considerations show up in three places. First, multilingual document generation is a non-trivial requirement — most US-born CPQ platforms ship adequate English templates and brittle Italian/French ones, and the legal team will not accept a quote with a poorly translated signing clause. Second, the SAP-native shops common in Italian midmarket and large enterprise will gravitate toward SAP CPQ for integration reasons, even when its UX is materially weaker than the AI-native entrants. Third, ISTAT (Italian inflation index) escalators and the related EU consumer-price-index logic that govern multi-year contract pricing are encoded in ways most US CPQ platforms do not handle natively. We covered the renewal-side of this in our work on recurring revenue management, but the offer side carries the same complexity.

The takeaway for a 2026 buyer is to start with the vertical anchor (your ERP, your sales motion, your geography) and only then evaluate the CPQ vendors that are credible in that anchor. A general-purpose feature comparison across all CPQ vendors will produce a list that does not actually map to your reality.

The Italian / EU compliance angle

CPQ outputs interact with EU regulation in two specific ways that are worth being explicit about.

The first is the AI Act classification of automated quote generation. The current reading of the EU AI Act is that B2B commercial pricing recommendations are generally low-risk — they affect a business decision, not a fundamental right. But the specifics matter. An AI-generated quote that includes payment-term recommendations affecting a customer's credit terms is closer to high-risk than a quote that recommends a configuration. Enterprises deploying generative-AI features in CPQ should classify the use case explicitly, document the classification, and operate the agent under the corresponding governance regime. This is rarely a procurement-stage question and frequently a pre-production-stage question; it should be the former.

The second is data residency. Many European enterprises require the master data (customer records, pricing, contract corpus) to remain inside EU data borders. This affects vendor selection — a US-only managed CPQ that does not offer an EU region is often disqualified at the procurement stage by a security or compliance review the sales team did not anticipate. It also affects the AI architecture: if the CPQ runs in a US cloud and the AI agent runs in an EU cloud, the integration design has to make explicit which data crosses which border on each request. Most operators we have worked with end up choosing EU-region foundation-model providers (Mistral, the EU regions of Anthropic and OpenAI, or self-hosted open models) specifically to keep the residency story clean.

A third point that is operational rather than regulatory: multilingual quote generation. Italian and French quote documents have specific legal-language requirements that an English-trained generation model will produce inadequately. The signing clause, the jurisdiction-and-arbitration clause, and the price-escalation clause all need locale-specific phrasing the legal team has approved. CPQ vendors that have invested in localization (PandaDoc, DocuSign, the Italian-localized players like Apparound) handle this well; some of the AI-native entrants currently treat localization as a year-two roadmap item. Confirm before you sign.

How Knowlee's architecture sits in the CPQ landscape

Knowlee is not a CPQ. We do not configure products, we do not run the pricing engine, and we do not produce the customer-facing quote document. What Knowlee does is the wedge category we described above — it runs an AI agent that sits beside the existing CPQ (or beside the existing offer-creation workflow when there is no CPQ), retrieves the relevant evidence from the company's master data systems, and produces a discrepancy report that closes the rework loop between the back office and the sales team.

The architecture is built on three pieces. The first is a shared retrieval substrate — what we call the Enterprise Brain — a Neo4j knowledge graph that captures the relationships between customer master data, signing-authority rules, offer templates, and contract doctrine. The graph is queried with hybrid retrieval (vector search for semantic relevance, structured graph traversal for relationship reasoning) so that a question like "does this customer's signing authority on this product line cover this discount level under the current policy" produces a structured answer, not a fuzzy paragraph.

The second piece is the discrepancy-detection agent itself. The agent is a session that runs against an incoming offer, calls the retrieval substrate for each field that needs validation, and produces a structured report. The agent's reasoning is captured in a streamed JSON transcript so the audit trail is real — every flagged item ties back to the retrieved evidence that triggered the flag.

The third piece is the governance layer — the automation registry that records each agent run, classifies it for AI Act risk, ties it to a human-oversight requirement when the use case warrants it, and produces the audit logs that compliance requires. This is the part of the architecture that turns "we have an AI agent" into "we have an AI agent that the executive committee can defend to the regulator."

The cross-functional consequence — and the genuine architectural advantage — is that the same retrieval substrate that powers offer-validation also powers contract review, RFP response, and HR Q&A. A fact added by one agent (a renewed contract, a new approved security answer, an updated CCNL article, a discontinued product line) is immediately available to all other agents reading from the same graph. The unit economics flip: instead of one specialist tool per use case, the substrate compounds across departments and the marginal cost of the next use case approaches zero.

We are deliberate about positioning this as the wedge category rather than as a CPQ replacement. For a customer on Salesforce CPQ or SAP CPQ, the right answer is not to switch CPQ vendors. The right answer is to leave the CPQ in place and add an agent that catches the discrepancies the CPQ alone does not catch — the master-data drift, the signing-authority violation, the clause that is inconsistent with the prior renewal. That is the reference engagement, and it is the architecture we describe in detail in the discrepancy detection guide.

Frequently Asked Questions

What does CPQ software do?

CPQ software automates the three steps a complex enterprise sale takes between customer interest and signed order: configuring the right product bundle (validating that what the customer wants to buy is internally consistent), pricing it correctly (applying list price, discounts, regional overrides, and approval thresholds), and generating the quote document the customer signs. The category exists because doing this in spreadsheets and Word documents at scale produces a steady stream of errors — wrong prices, invalid configurations, signing-authority violations, contract terms inconsistent with the company's standards — that cost the back office significant time to correct.

What is the difference between CPQ and quoting software?

Quoting software is a narrower category focused on producing the quote document — fast, branded, sometimes with e-signature. CPQ adds the configuration logic (what is a valid product bundle) and the pricing logic (what is the right discount and approval flow) on top. A SaaS sales team selling three SKUs at list price needs quoting software; a manufacturer selling configurable machines or a software vendor selling complex multi-module licenses needs CPQ. We unpack the trade-off in detail in CPQ vs quoting software.

What is AI CPQ?

AI CPQ is the term vendors use for CPQ platforms with AI features baked in or bolted on. The genuinely useful AI categories are guided selling (recommending configurations based on past similar deals), pricing optimization (suggesting the discount that balances close probability and margin), and document drafting (generating the quote and SOW text). A more architecturally interesting use of AI in the CPQ space is discrepancy detection — agents that validate an offer against the company's master data and contractual doctrine before submission — but that is a wedge category that operates beside CPQ rather than within it.

How much does CPQ software cost?

For a midmarket deployment with one CRM integration and standard configuration, expect Salesforce CPQ to land in the €100,000–€250,000 range for licenses plus implementation in year one, with similar annual licensing thereafter. Oracle CPQ and SAP CPQ are typically in the same range or higher for enterprise scope. AI-native entrants (Subskribe, Hyperline, Salesbricks) are materially cheaper at the low end (€15,000–€60,000 per year for licenses, with shorter implementations). The wedge-category discrepancy-detection agent typically prices as a focused engagement — €40,000–€120,000 for a 3-to-4-week pilot validating against a historical offer sample, with ongoing license cost shaped by the underlying retrieval and foundation-model usage.

Do I need CPQ if I have Salesforce?

Salesforce CRM does not include CPQ functionality natively. Salesforce CPQ (formerly Steelbrick, now part of Revenue Cloud) is a separate licensed module. Whether you need it depends on the configuration and pricing complexity of your sales motion: if you sell a small number of well-defined products at consistent pricing, the Salesforce CRM plus a quoting tool is sufficient; if you sell configurable bundles with non-trivial pricing rules and approval flows, you will end up with CPQ either from Salesforce or from a third party. The integration depth is the main argument for staying inside the Salesforce stack.

What is CPQ for manufacturing?

CPQ for manufacturing is a specialty subsegment of the category dominated by Tacton, Epicor CPQ, and Infor CPQ. The configuration complexity is mechanical — does this motor fit this chassis, does this valve handle this pressure rating — and the pricing logic is typically tied to a manufacturing ERP (bill of materials, cost of goods, production capacity). Manufacturing CPQ tends to live inside or close to an ERP rather than a CRM, and AI value here is concentrated in guided selling and cost-prediction more than in document drafting.

Can CPQ work with SAP and V-Tiger?

Yes, but the integration depth varies. SAP CPQ is the obvious answer for SAP-native shops because it is integrated into the SAP ecosystem. Third-party CPQ platforms (Salesforce CPQ, Conga CPQ, the AI-native entrants) integrate with SAP through standard connectors that are mature for finance/billing and progressively less mature for the CRM-side master-data sync. V-Tiger is rarer in CPQ vendor integration matrices because its deployment base is smaller — most CPQ vendors will quote a custom integration for V-Tiger, which is a multi-quarter project. An alternative pattern: keep SAP and V-Tiger as the systems of record, do not migrate to a new CPQ, and run a discrepancy-detection agent that validates against both. This is the wedge architecture described in this guide.

What is the AI Act classification of CPQ AI features?

For B2B commercial use, most CPQ AI features (configuration recommendations, pricing suggestions, document drafting) sit in the low-risk category under the EU AI Act. AI-generated outputs that touch credit-term decisions affecting a customer move closer to high-risk and warrant explicit classification. Generated outputs that touch employment, citizen, or healthcare data are high-risk and require the full governance regime — audit trails, human oversight, transparency obligations. The classification is a use-case question, not a vendor question, and it should be answered before procurement signs the contract. We cover the broader regulatory context in our EU AI Act business guide.

How long does CPQ implementation take?

Salesforce CPQ, Oracle CPQ, SAP CPQ, and Conga CPQ implementations land in the 4-to-9-month range for midmarket scope and 9-to-18-month range for enterprise scope, with the variance driven mostly by the complexity of pricing-rule encoding and the number of integrated systems. AI-native entrants (Subskribe, Hyperline, Salesbricks) cite 4-to-12-week implementations and largely deliver them at the midmarket end. Discrepancy-detection agents on top of an existing CPQ are typically 3-to-6 weeks for a focused pilot, with the bottleneck almost always being the negotiation of read access to the underlying master data systems rather than the agent itself.

Should I replace my existing CPQ to get AI features?

Usually no. If you are running Salesforce CPQ, Oracle CPQ, SAP CPQ, or Conga CPQ already, the AI features your incumbent vendor ships in 2026 are typically sufficient for guided selling and document drafting, and the cost of switching CPQ vendors is rarely justified by AI features alone. The architecturally interesting move is to leave the CPQ in place and add an AI agent layer that catches the discrepancies your CPQ alone does not catch — master-data drift, signing-authority violations, clause inconsistency. That is the wedge architecture we describe in CPQ discrepancy detection with AI.

Related concepts

• CPQ vs quoting software — the narrower-tool comparison
• CPQ discrepancy detection with AI — the architectural wedge for SAP / non-Salesforce CRM shops
• Quote-to-cash automation — the broader workflow CPQ sits inside
• Sales operations AI — the function that owns CPQ in most organizations
• RAG AI: the enterprise guide — the retrieval pattern under the discrepancy-detection agent
• Knowledge graph for enterprise AI — the substrate the agent reads from
• AI build vs buy framework — for the platform-vs-wedge decision
• EU AI Act business guide — for the classification question
• AI governance enterprise playbook — for operationalizing oversight

If you are running an enterprise CPQ stack with a non-trivial discrepancy rate — back-office FTE going to rework rather than to growth — our team reviews CPQ stacks at no charge for qualifying engagements. The first hour is usually enough to expose whether you have a configuration problem (CPQ replacement is the right move), a validation problem (the wedge architecture is the right move), or a master-data problem (which neither CPQ nor an AI agent will fix until it is addressed first).