10.218 min read

Enterprise CPQ & Solution Design

In B2C, Configure-Price-Quote (CPQ) is relatively simple: the customer selects a product, the system calculates the price, and a real-time quote is presented at checkout. The entire process takes seconds and requires no human intervention.

Enterprise CPQ is a completely different discipline. It involves designing multi-product, multi-site solutions; checking technical feasibility at each location; applying negotiated contract pricing with volume discounts; routing quotes through multi-level approval workflows; and managing a quote lifecycle that can span days or weeks. Enterprise CPQ is where commercial intent meets technical reality — and it is one of the most complex capabilities in B2B BSS.

Enterprise CPQ

A specialised capability for configuring complex, multi-product, multi-site solutions for enterprise customers; applying negotiated and rule-based pricing; generating formal quotations with contractual terms; and managing the quote through approval, negotiation, and acceptance stages before it becomes an order.

Solution-Level Quoting

B2C quoting is product-level: one product, one price. B2B quoting is solution-level: a single quote may combine connectivity (MPLS, SD-WAN), unified communications (SIP trunking, UCaaS), cloud services (IaaS, DRaaS), managed security, and hardware (CPE) — all deployed across dozens of sites with site-specific configurations.

Intermediate

Solution-Level Quoting

An enterprise quote is not a list of products — it is a structured solution that bundles multiple products, services, and configurations across multiple sites, with interdependencies, shared discounts, and a unified commercial wrapper.

For example, a quote for "Managed Connectivity" might include: SD-WAN overlay across 30 sites (each with site-specific bandwidth and CPE), internet breakout at 10 sites, MPLS underlay for 15 critical sites, a centralised firewall-as-a-service, and 24/7 managed service wrap. The pricing combines per-site recurring charges, one-time installation fees, volume discounts on bandwidth, and a flat monthly management fee. All of this is one "solution" in the quote.

Multi-product bundling — A single quote combines products from different catalog domains (connectivity, voice, cloud, security, hardware)
Multi-site deployment — Each product may be configured differently per site (bandwidth, CPE model, SLA tier)
Cross-product dependencies — Some products require others (e.g. SD-WAN requires an underlay circuit at each site)
Solution-level pricing — Discounts may apply at the solution level, not just per product (e.g. 15% off the total if the customer commits to all three product families)
Phased delivery — The quote may specify rollout waves, with different sites going live in different phases

Feasibility Checks and Site Surveys

Before an enterprise quote can be finalised, the CSP must verify that the requested services can actually be delivered at each site. This is the feasibility check — a process that ranges from automated network lookups (for simple broadband) to full physical site surveys (for complex fibre or microwave installations).

Feasibility Check Process

Site Address Capture

CRM / Enterprise Portal

Enterprise provides addresses for all sites requiring service. Addresses are validated and geocoded against the CSP's address reference database.

Automated Serviceability Check

Product Offering Qualification (POQ)

System queries network inventory and coverage databases to determine what services are available at each address. This may use TMF679 Product Offering Qualification.

Feasibility Classification

POQ / Network Planning

Each site is classified: Green (service available, standard install), Amber (service possible with additional work), or Red (not currently serviceable).

Desk-Based Assessment (Amber Sites)

Network Planning

For Amber sites, a network planner reviews the gap: can existing infrastructure be extended? Is there a nearby PoP? What civil works are needed?

Physical Site Survey (if required)

Field Operations

For complex or Red sites, a field engineer visits the location to assess fibre routes, building entry points, power availability, and equipment space.

Cost and Timeline Estimation

CPQ / Pricing Engine

Based on feasibility results, per-site installation costs and delivery timelines are calculated and fed back into the CPQ.

Quote Update

CPQ

The enterprise quote is updated with per-site feasibility status, delivery timelines, and any non-standard installation charges.

Feasibility Is a Revenue Gate

Slow or inaccurate feasibility checks are one of the biggest causes of lost enterprise deals. If it takes 3 weeks to tell a customer whether you can serve their sites, they will go to a competitor who can answer in 3 days. Investing in automated serviceability checks (using TMF679) dramatically reduces quote-to-order cycle times.

Custom Pricing Models

Enterprise pricing is not a lookup in a price list — it is a negotiation governed by rules, approval thresholds, and competitive dynamics. The CPQ pricing engine must support multiple pricing models simultaneously, often within the same quote.

Enterprise Pricing Models

Pricing Model	Description	Typical Use Case	Complexity
Volume Discount	Price per unit decreases as total quantity increases across defined bands	Per-site recurring charges where more sites = lower per-site price	Medium
Tiered Pricing	Different rates apply to different tiers of usage or commitment	Data usage: first 10TB at rate A, next 50TB at rate B, beyond 60TB at rate C	Medium
Contract-Term Discount	Longer contract commitment yields lower pricing	12-month vs 36-month vs 60-month terms for managed services	Low
Bundled Discount	Discount applied when customer takes multiple product families together	10% off total if customer takes connectivity + voice + security	Medium
Negotiated Rate Card	Custom price list agreed for a specific enterprise, overriding catalog prices	Large strategic accounts with long-term framework agreements	High
Cost-Plus	Pricing based on actual delivery cost plus a margin, typically for bespoke builds	Non-standard installations requiring civil works or custom engineering	High
Outcome-Based	Pricing tied to business outcomes or performance metrics rather than units consumed	Managed service with SLA-linked pricing: lower fee if SLA targets are met, penalties if not	Very High

Pricing Approval Thresholds

Most CSPs define discount thresholds that require escalating levels of approval. For example: up to 10% discount — sales rep can approve; 10-25% — sales manager; 25-40% — regional director; above 40% — VP or commercial board. The CPQ must enforce these thresholds automatically and route to the correct approver.

TM Forum Standards for Enterprise CPQ

TMF648 — Quote Management API

TMF648 defines the standard API for managing the lifecycle of a quote. It supports creating quotes, adding quote items (each representing a product offering with pricing), managing quote states (inProgress, approved, accepted, rejected, cancelled), and linking quotes to customers, contracts, and agreements. In B2B, TMF648 is extended with solution-level structures, multi-site line items, and approval workflow states.

TMF679 — Product Offering Qualification API

TMF679 provides the standard API for checking whether a specific product offering can be delivered at a given location. It answers the question: "Can you provide this service at this address?" The API supports both instant (synchronous) qualification for simple checks and deferred (asynchronous) qualification for complex assessments that require manual review or site surveys. It is the API backbone of the feasibility check process.

Enterprise Quote Lifecycle

Unlike B2C (where a "quote" is just a real-time price displayed at checkout), an enterprise quote has a formal lifecycle with distinct stages, state transitions, and human touchpoints. A single quote may go through multiple revision cycles before acceptance.

Enterprise Quote Lifecycle

Request

Enterprise Portal / CRM

The enterprise customer (or their account manager) requests a quote for a specific set of services and sites. This may come via the enterprise portal, a partner portal, or a sales interaction.

Qualification

CPQ / TMF679 POQ

The CPQ system qualifies the request: Is the customer eligible? Are the requested products available in the required geography? Are there any contract or credit constraints?

Feasibility

POQ / Network Planning

Technical feasibility is assessed for each site. Automated checks run first; manual assessment follows for complex sites. Results feed back site-specific availability, lead times, and any non-standard costs.

Solution Design

CPQ / Solution Design Tool

The solution is designed: products are configured per site, dependencies are resolved, CPE is selected, SLA tiers are assigned, and the overall solution architecture is validated.

Pricing

CPQ / Pricing Engine

The pricing engine calculates charges: base prices from catalog, contract-specific overrides, volume discounts, bundle discounts, one-time charges, and any cost-plus elements for non-standard work. Total contract value (TCV) and monthly recurring charges (MRC) are computed.

Internal Approval

CPQ / Workflow Engine

The quote is routed through the CSP's internal approval workflow based on discount levels, contract value, and deal risk. Approvers may request pricing adjustments or scope changes.

Customer Presentation

CPQ / Document Generation

The approved quote is formatted and sent to the enterprise customer. This typically includes a commercial proposal document, per-site pricing breakdown, SLA commitments, and contractual terms.

Negotiation

CPQ / Sales Console

The customer may request changes — different pricing, additional sites, modified SLAs, or alternative configurations. The quote is revised (possibly returning to the Pricing or Design stage) and re-approved.

Customer Acceptance

CPQ / Contract Management

The customer formally accepts the quote — typically by signing the associated contract or purchase order. The accepted quote becomes the basis for order creation.

Order Generation

CPQ → COM (TMF622)

The accepted quote is converted into one or more commercial orders (potentially phased by site or rollout wave). The quote-to-order conversion must preserve all pricing, configuration, and contractual terms.

Quote Cycle Time Matters

A typical B2B quote lifecycle takes 5-15 business days for standard services and 4-8 weeks for complex, multi-site solutions. Best-in-class CSPs aim for under 5 days for standard quotes by automating feasibility (TMF679), pricing, and approval routing. Quote cycle time is a key competitive differentiator in enterprise sales.

CPQ Architecture Considerations

CPQ helps the sales team build a valid, priced proposal for an enterprise customer. Think of it as a "deal builder" that ensures: (1) the products selected are compatible, (2) the services can actually be delivered at the customer's locations, (3) the pricing follows the rules, and (4) the right people approve the deal before it goes to the customer.

Without CPQ, sales teams build quotes in spreadsheets — leading to pricing errors, impossible configurations, and deals that cannot be fulfilled.

Enterprise CPQ sits at the intersection of multiple systems. It reads from the Product Catalog (what can be sold and how it is configured), queries the Pricing Engine (what it costs, with contract-specific overrides), invokes TMF679 POQ (can it be delivered at this address), references Contract Management (what terms apply to this customer), and hands off to COM (TMF622) when the quote converts to an order.

Product Catalog → CPQ: Available offerings, configuration rules, product relationships
Pricing Engine → CPQ: Base prices, discount rules, volume bands, contract overrides
TMF679 POQ → CPQ: Site-level feasibility, lead times, non-standard costs
Contract Management → CPQ: Applicable pricing agreements, term constraints, SLA commitments
CPQ → COM (TMF622): Accepted quote converts to commercial order(s)
CPQ → Document Generation: Formatted proposals, statements of work, contracts

Advanced enterprise CPQ platforms employ guided selling — rule-driven wizards that help sales reps design valid solutions without deep technical knowledge. The rules engine encodes product compatibility constraints (e.g. "SD-WAN requires at least one underlay circuit per site"), mandatory components (e.g. "every WAN site must include a CPE"), and upsell triggers (e.g. "if customer selects Premium SLA, recommend 24/7 monitoring").

The rules engine also enforces commercial constraints: minimum contract terms, maximum discount thresholds per product family, geographic availability restrictions, and end-of-sale dates. These rules prevent invalid quotes from entering the approval pipeline, reducing rework and accelerating cycle times.

In TM Forum terms, the CPQ rules engine draws from the Product Specification (TMF620) for configuration constraints and Product Offering for commercial rules. The relationship between Product Offering and Product Specification defines what is configurable vs what is fixed.

CPQ in the Vendor Landscape

Enterprise CPQ is offered both as a standalone capability and as part of integrated BSS suites. Standalone CPQ platforms (such as Salesforce CPQ, Oracle CPQ, and Conga) provide deep quoting and pricing functionality but require integration with telco-specific catalogs and fulfilment systems. Integrated BSS vendors (Amdocs, Netcracker, Cerillion, Comarch) include CPQ as part of their end-to-end offering, with native integration to product catalogs and order management.

CPQ Selection: Standalone vs Integrated

Standalone CPQ tools often have superior user experience and CRM integration but lack native understanding of telco product models (CFS/RFS decomposition, network feasibility). Integrated BSS CPQ understands the telco domain natively but may lag in UX sophistication. Many CSPs adopt a hybrid: a CRM-native CPQ for the sales front-end, integrated via APIs to the telco product catalog and pricing engine in the BSS back-end.

Enterprise CPQ — Key Takeaways

Enterprise CPQ is solution-level, not product-level — it designs multi-product, multi-site proposals with interdependencies
Feasibility checks (TMF679) are a critical part of the quote process — they determine what can be delivered, where, and at what cost
Enterprise pricing is multi-model: volume discounts, tiered rates, contract terms, bundles, negotiated rate cards, and cost-plus
The enterprise quote lifecycle spans 8-10 stages and can take days to weeks — it is not a real-time checkout
TMF648 (Quote Management) and TMF679 (Product Offering Qualification) are the key TM Forum APIs for enterprise CPQ
CPQ must integrate with Product Catalog, Pricing Engine, Contract Management, and COM (TMF622)
Approval workflows with discount thresholds are mandatory — the CPQ must enforce commercial governance automatically