| Posture |
| Primary use case | AI front door for complex catalogs: buyer or partner arrives with a task, receives a validated configuration and commercial quote without waiting on a rep. Full CPQ workflow in one deterministic engine. | Oracle CPQ is a cloud configure–price–quote engine for rep, partner, and channel quoting with CRM and ERP handoff — discovery is often rep-led, commerce-led, or custom-built on REST. | Coexistence |
|---|
| Primary user persona | Buyer self-serve (full / guided / sales-assisted); partner portals; internal presales paste-in. — Escalation target: < 10% of sessions. | Rep, deal desk, and partner users in CPQ UI by default. — External buyer UX typically requires Oracle Commerce for CPQ, REST headless builds, or co-configuration with the sales team. | Lean Talkulate AI CPQ |
|---|
| Deployment model | Standalone without an Oracle CPQ tenant: chat widget, iframe, JS snippet, embedded page, headless API, messengers. Connects to any CRM or ERP stack. | Cloud SaaS CPQ tenant; Fusion CPQ adds Fusion shell navigation and shared roles. — Requires Oracle CPQ subscription and modeling — standalone vs Fusion packaging is an AE decision. | Lean Talkulate AI CPQ |
|---|
| Entry UX | Plain-language task entry with optional persona routing (B2B technical / B2C / installer / fleet). — Contextual goals, not rigid decision trees. | Guided selling with step-by-step workflows in CPQ UI. — Quote Assist answers rep questions about quoting flows from Redwood Quote — you build buyer NL entry separately. | Lean Talkulate AI CPQ |
|---|
| Real-time option swaps | Buyer swaps a compatible alternative → Engineer Agent revalidates the full BOM and reprices instantly. Out-of-rule swaps are blocked at the engine level. | Real-time repricing on option change is supported when rules and UI latency allow; behavior depends on configuration models and integration timing. | Lean Talkulate AI CPQ |
|---|
| Self-serve modes | Three built-in modes: full, guided, and sales-assisted; benchmark < 10% escalation. | Oracle Commerce for CPQ and co-configuration on any device enable external journeys — typically commerce or SI-built portals, not a native buyer-conversation core in CPQ-primary docs. | Lean Talkulate AI CPQ |
|---|
| Discovery & pricing |
| Discovery model | Interviewer Agent: contextual goals — 6–10 questions, 4–8 minutes to validated BOM in reference case. | Guided selling and rep-led discovery in CPQ UI. — GenAI quote summaries and Quote Assist are rep-side drafting and process help — not buyer NL discovery for configured lines. | Lean Talkulate AI CPQ |
|---|
| CPQ workflow coverage | Entry → Discovery → Selection (Engineer + DB) → Pricing → Output (BOM + proposal + reasoning) → Handoff (CRM / ERP / exception routing) in one engine. | Configure, price, quote in CPQ tenant; subscription and service lines; proposals, SOWs, and contracts; downstream CRM, ERP, Commerce, and Subscription Management pairing. | Coexistence |
|---|
| Pricing engine depth | Volume tiers, bundles, regional lists, SLA adders, contract rebates, promotions, multi-currency — validated in the same Engineer Agent pass. | Multiple price books, promotions, localization, multitier and channel pricing, real-time discounting in workflow; Price Setup REST APIs for model and agreement import/export. | Lean Oracle CPQ |
|---|
| Subscription / asset ordering | Encodes subscription and service lines in the sales BOM when modeled in the tenant catalog — handoff to billing systems is scoped per integration. | Standard asset-based ordering (ABO) with REST v19 asset lifecycle actions; Package ABO tenants must stay on earlier REST for assets — migration-sensitive. | Lean Oracle CPQ |
|---|
| Output formats | Interactive commercial proposal + PDF + per-line reasoning + compatible swaps + branded PDF. | Automated document generation for proposals, SOWs, data sheets, and contracts — multilingual PDF and Word. GenAI summaries are drafting aids, not binding without human review. | Lean Talkulate AI CPQ |
|---|
| Approval & discount governance | Discount threshold approvals available as add-on scope per tenant. | Dynamic automated approvals with routing, notifications, and mobile-first approvals; Redwood Quote Process Steps Workflow in 26A readiness materials. | Lean Oracle CPQ |
|---|
| Validation |
| Validation method | Deterministic Engineer Agent against live PostgreSQL via MCP — no document retrieval for core compatibility. | Rules engine plus guided selling for configured products. — GenAI on quote text and admin rule descriptions is a separate layer from constraint proof. | Coexistence |
|---|
| Invalid configuration handling | Engineer Agent validates each configured line against the live tenant catalog (structured queries, not document similarity). Incompatible combinations are refused with per-line reasoning before any Oracle CPQ handoff. In one published hardware reference program (~3,400 SKUs), standard BOMs no longer required a separate engineering compatibility review after go-live. | Oracle CPQ quoting is rules-driven on the tenant catalog and price models. — Disallowed combinations are blocked when rules and master data are complete; closing gaps is modeling, testing, and governance work — a different mechanism than buyer-side document assistants. | Program-dependent |
|---|
| GenAI & Quote Assist on quotes | LLM only in Interviewer Agent; Engineer Agent is non-generative for configuration choices. | GenAI quote summaries (Oracle Sales integration required), Quote Assist agent for quoting-flow questions, AI-generated rule descriptions in Redwood Configuration Rules — rep and admin surfaces. | Coexistence |
|---|
| Dual-agent architecture | Interviewer and Engineer fully separated; Engineer only runs allowlisted DB queries. | Oracle CPQ core is rules-driven — not LLM-fronted for configuration. GenAI features require Fusion and MOS enablement paths where documented. | Lean Talkulate AI CPQ |
|---|
| Catalog source connectors | PostgreSQL, MySQL, MSSQL, SAP, NetSuite, Dynamics, Salesforce CPQ, Excel, PDF specs, XML, REST, file drops. | CPQ catalog plus CRM and ERP connectors; product page claims compatibility with 20+ leading ERP systems including Oracle E-Business Suite, JD Edwards, SAP, Infor LN, and Microsoft. | Program-dependent |
|---|
| Per-line audit trail | Per-line reasoning: which constraint triggered each selection — buyer and rep facing. | Workflow and approval audit in CPQ; GenAI summaries are explicitly non-binding drafting aids — not buyer-facing “why this line” for configured products. | Lean Talkulate AI CPQ |
|---|
| Observability & tracing | Langfuse per session (Interviewer and Engineer traces separately); rate limits on chat and overview endpoints. | REST API Services catalog published; per-endpoint SLOs and LLM trace layer not established in public CPQ materials reviewed here. | Lean Talkulate AI CPQ |
|---|
| Channels & time to value |
| Embed channels | Widget, iframe (~10 min deploy), JS snippet, embedded page, headless API, internal-tool mode. | REST API Services for configuration, pricing, commerce, and assets — SI builds the external shell. Commerce for CPQ uses pooled-session licensing. | Coexistence |
|---|
| Async messenger channels | WhatsApp, Telegram, Teams, Slack, Messenger, LinkedIn — same validation engine, scoped per channel. | Messenger-native CPQ intake is not documented as a standard Oracle CPQ feature. — Not established in Oracle CPQ public CPQ materials reviewed (May 2026); verify with Oracle CPQ. | Lean Talkulate AI CPQ |
|---|
| Time to production buyer surface | Envelope 5 days–6 weeks; typical 3–5 weeks; reference case 5 weeks. | Standard ABO migration, OIC and Order Management packages, and Fusion GenAI enablement are multi-workstream programs — calendar depends on catalog, ABO mode, and SI scope. | Lean Talkulate AI CPQ |
|---|
| Customer effort | 10–15 hours over 2–3 weeks (vendor claim for standard deployment). | Heavy stakeholder alignment, rule modeling, integration testing, and hypercare — effort scales with ERP, commerce, and Fusion prerequisites. | Lean Talkulate AI CPQ |
|---|
| "No structured catalog" path | Data structuring service ($3,450–$17,250 one-time) for Excel, PDF, and tribal knowledge. | Catalog and rule modeling are admin- and partner-scoped; no public fixed-fee structuring SKU on the CPQ product page. | Program-dependent |
|---|
| Verticals | Eight first-class vertical packs on one engine. | Manufacturing, high-tech, and subscription positioning on the product page — partner-led verticalization, not eight named packs. | Lean Talkulate AI CPQ |
|---|
| Security & governance |
| Error mode | Refuse: incompatible combinations are blocked before the buyer accepts output; the engine does not publish out-of-rule builds from document similarity. | Rules block disallowed combinations when modeled; gaps in rules can produce plausible but incorrect quotes. | Program-dependent |
|---|
| Regulatory constraint encoding | CE, FDA, UL, NSF, RoHS, and similar rules encodable in validation engine. | Implementation-dependent in product and price rules — depth depends on SI and customer team. | Program-dependent |
|---|
| Anti-prompt-injection | Engineer Agent allowlisted queries only; vendor does not need internal margin data. | Oracle CPQ core quoting is not LLM-fronted; GenAI is a separate layer with Fusion and Oracle Sales prerequisites — confirm in DPA. | Lean Talkulate AI CPQ |
|---|
| GDPR / PII posture | DPA; no training on client catalog or conversations; data minimization. | CPQ-specific SOC reports, residency selectors, and GenAI data-handling posture were not mapped to the CPQ service boundary in our public review (May 2026) — verify with Oracle. | Program-dependent |
|---|
| Multi-tenant isolation & hosting | Cloud AWS/Azure EU regions; per-tenant DB. — On-prem: $69,000 enterprise license. | Multi-tenant cloud CPQ positioning on the product page; CPQ-specific data residency selectors not established in this publication pass. | Program-dependent |
|---|
| Built-in analytics | Conversation funnel analytics and demand-sensing export. | Marketing themes include win probability and price optimization — operational analytics depth for buyer funnels not established in CPQ-primary docs reviewed here. | Lean Talkulate AI CPQ |
|---|
| Outcomes & commercial |
| Quote cycle (reference metrics) | See the reference deployment band below. | No matched public study on equivalent buyer self-serve catalog complexity in this publication pass. | Lean Talkulate AI CPQ |
|---|
| First-pass accuracy | See the reference deployment band below. | No matched public study on equivalent catalog complexity in this publication pass. | Lean Talkulate AI CPQ |
|---|
| Quote capacity | See the reference deployment band below. | Buyer-facing self-serve capacity uplift is not published in Oracle CPQ materials reviewed here. — Not established in Oracle CPQ public CPQ materials reviewed (May 2026); verify with Oracle CPQ. | Lean Talkulate AI CPQ |
|---|
| Conversion uplift | A separate buyer-facing pilot (not the server-reseller reference case) reported better web conversion and fewer “waiting for a quote” drop-offs versus that pilot’s own baseline — treat as directional; measure on your traffic. | Buyer-facing conversion uplift from external CPQ UX is not published in Oracle CPQ product page pass. Not established in Oracle CPQ public CPQ materials reviewed (May 2026); verify with Oracle CPQ. | Lean Talkulate AI CPQ |
|---|
| RFQ unit economics | Illustrative unit economics only (not a price quote for your tenant): manual complex RFQs are often cited around $230–$460 versus automated self-serve often cited up to about $12 per RFQ at volume — use Talkulate AI CPQ pricing and ROI tools for your case. | List economics combine Hosted Named User minimums, channel users, connector, and interaction add-ons on a three-year standard cloud term — net TCO requires AE and SI quotes. | Program-dependent |
|---|
| Pricing model | Implementation ($18,400) + monthly ($1,725, 600 dialogs) + per-dialog overage + integration ($115 / hour). Enterprise on-prem: $69,000. | Oracle CPQ Fusion global price list (Jan 2026): Hosted Named User USD 240/user/month (min 10, part B111751); channel user USD 35/user/month (min 50); e-commerce interactions USD 500/month per 1,000 (min 10); Salesforce connector USD 5/user/month; Commerce pooled sessions USD 450 per 1,000 (min 900). Standard subscription term three years. List only — not net TCO. | Program-dependent |
|---|