Picture one opportunity that includes a configured machine, installation and commissioning labor, a three-year service agreement, and a connected-monitoring subscription with usage tiers. Your quoting tool has to price all of it in one governed document, and that is where many Salesforce CPQ configurations start to strain. This article explains why quoting products and services together is hard, what good hybrid quoting looks like, and how to evaluate a Salesforce CPQ alternative built for mixed revenue.
TL;DR
- Salesforce stopped selling Salesforce CPQ to new customers in March 2025. This is end of sale, not end of life. Existing customers can keep using it, renew, add users, and receive support, and Salesforce has not announced an end-of-life date.
- Quoting products and services in one deal is where many Salesforce CPQ configurations show strain. One-time equipment, labor, projects, subscriptions, and usage charges each carry different pricing math, term logic, and approval thresholds.
- The usual workarounds are separate quotes, spreadsheets for services scoping, and Quote Calculator Plugin (QCP) customizations that only a developer can maintain.
- You have three paths: stay on Salesforce CPQ, reimplement on Revenue Cloud Advanced (RCA), or keep Salesforce CRM as the system of record and replace the quoting layer. Experlogix CPQ supports the third path. One-time equipment, recurring subscriptions, usage-based fees, and multi-year services and support can sit on a single quote, each with its own tiers, contract terms, and regional rules applied automatically.
- Bottom line: test your hardest real hybrid deal, not a demo catalog. If one quote can't hold every revenue stream with visible margin, the problem is architectural, not a training issue.
Why Quoting Products and Services Together Breaks Quoting Tools
Mixed revenue is hard because each revenue stream follows different rules. Salesforce CPQ (configure, price, quote) was designed around a subscription-first model, and that model does not stretch evenly across hardware, labor, and projects.
Here is that representative industrial deal, line by line:
- A configured machine with options, priced one time and built to order
- Installation and commissioning labor, scoped in hours and roles
- A three-year service and support agreement billed annually
- A connected-monitoring subscription with a usage tier above a threshold
- Spare parts, priced from a regional price list
Each line needs different math:
- The machine needs configuration rules.
- The labor needs a scoping model and a rate card.
- The service agreement needs term and start-date logic.
- The subscription needs recurring revenue treatment, proration, and co-terming.
- The usage component needs tiers.
When one engine handles only part of that well, the rest moves into spreadsheets, manual line items, or custom code. That is where quote-to-contract drift begins, because the number the customer signs no longer matches what any system calculated.
Where Salesforce CPQ Runs Into Design Limits on Hybrid Deals
Salesforce CPQ handles moderate-complexity quoting well, especially for catalogs that are mostly subscriptions or mostly standard SKUs. The constraints appear when a quote mixes revenue types and product complexity at the same time.
Managed-package architecture and rule maintenance
Salesforce CPQ ships as a managed package with its own objects and rule types: product rules, price rules, and constraint rules. As a hybrid catalog grows, the number of rules grows faster than the catalog, because services and subscriptions need their own rule sets on top of configured products. Maintaining that logic increasingly becomes specialist work rather than admin work.
QCP and custom code for pricing that does not fit the model
When pricing logic falls outside the native model, teams turn to the Quote Calculator Plugin, a JavaScript extension point for custom calculations. QCP solves the immediate problem but creates a long-term one. Pricing behavior now lives in code, regression testing gets harder, and any future platform change means re-validating that code.
Services and labor modeled as products
Professional services, labor, and project work rarely behave like catalog items. They are scoped, estimated, and rate-driven, often with custom engagements, multi-tiered pricing, and bundled deliverables. Forcing that work into a product-bundle structure usually means the real scoping happens somewhere else and gets pasted back in. For the deeper mechanics of rate cards and project scoping, see labor pricing and project-based quoting.
Nested bundles and performance on large hybrid quotes
When a large configured quote with nested bundles also carries dozens of service and subscription lines, line counts and calculation passes rise together. As catalogs grow to thousands of SKUs or hybrid offerings that combine physical products, services, and subscriptions, teams may see performance issues, rigid workflows, and a rules engine that is hard to manage at runtime.
What Good Hybrid Quoting Actually Requires
Good hybrid quoting means one governed quote, one calculation engine, and one set of guardrails covering every revenue stream in the deal. Use these as evaluation criteria rather than feature checkboxes:
- One quote, many pricing models. One-time, recurring, and usage-based charges coexist on a single document with correct totals for each.
- Term and date accuracy. Start dates, co-terming, proration, and ramped multi-year pricing calculate consistently across services and subscriptions.
- Services scoping inside the quote. Labor, roles, rates, and project deliverables are quoted in the same flow as the configured product.
- Margin visibility across the bundle. You can see margin on the whole solution and on each line, not just a blended total.
- Governed discounting. Floors, ceilings, stacking rules, and threshold-based approvals apply across revenue types, with exceptions routed automatically.
- One document out. The proposal reflects every stream accurately, without manual assembly.
- Admin ownership. Business administrators can change rates, rules, and thresholds without a developer.
Your Three Realistic Paths, and When Each Fits
No one is forcing you to migrate. Pick the path that matches your complexity and how much project risk you can take on.
Stay on Salesforce CPQ
Staying is a legitimate choice. You can keep using Salesforce CPQ, renew, and add users, with support, and no end-of-life date has been announced. Staying makes sense when hybrid deals are a small share of your volume, your rule set is stable, and the workarounds are tolerable. The trade-off is that Salesforce CPQ is no longer receiving meaningful new feature development, so the gap on mixed revenue will not close on its own.
Reimplement on Revenue Cloud Advanced
Revenue Cloud Advanced, now part of Agentforce Revenue Management, is where Salesforce's strategic investment has moved. Treat the move as a reimplementation, not an upgrade. RCA uses a different data model and configuration approach, so your catalog, pricing logic, and custom code get redesigned rather than lifted across. This path fits organizations that are committed to a single Salesforce revenue platform for quoting, billing, and revenue recognition, and that are willing to fund a redesign.
Keep Salesforce CRM and replace the quoting layer
If Salesforce CRM works and the quoting engine is the constraint, you can change only the quoting layer. Accounts, opportunities, forecasting, and reporting stay intact while you replace the engine that handles configuration, pricing, and mixed revenue. It is the narrowest-scope option, and it is the one most often overlooked.
How Experlogix CPQ Approaches Mixed-Revenue Quoting
Experlogix CPQ is one way to take the third path: keep Salesforce CRM as the system of record and replace the quoting layer.
With Experlogix CPQ, one-time equipment, recurring subscriptions, usage-based fees, and multi-year services and support can all sit on a single quote. Each line gets its own tiers, contract terms, and regional rules, applied automatically. Margin stays visible across the whole bundle and on each line.
Several capabilities make that single quote work in practice:
- A rules engine that evaluates thousands of options in real time to prevent invalid builds and capture engineering constraints, so the product side of a hybrid deal stays valid.
- Pricing logic for list, contract, and tiered structures, with region-specific rules, currency conversions, and volume-based breaks applied automatically.
- Discount guardrails with ceilings, floors, and stacking rules. Standard deals pass instantly, approvals trigger only when a deal crosses a threshold, and every pricing decision is logged.
- Special pricing agreements applied automatically and documented per quote, in concert with your CRM.
- Document generation for configured quotes and proposals from the same flow.
- Low-code administration, so business users can maintain logic instead of filing developer tickets.
- For manufacturers, handoff to ERP (enterprise resource planning) with complete bill of materials (BOM), work breakdown structure (WBS), and routing data. This matters when the product half of a hybrid deal has to be built.
Experlogix CPQ is built natively for Salesforce and Microsoft Dynamics 365. Because it works directly with CRM and ERP data rather than through middleware, integrations hold up through platform updates and data stays consistent across systems. This architecture matters to RevOps and IT. When quoting doesn't depend on copying CRM data into a separate platform and syncing it back, you avoid:
- Stale or mismatched records
- Sync failures and latency
- Duplicate records and reconciliation work
- Reporting that reflects a copy rather than the source
- The governance exposure of storing the same data in more places
Reps also stay in the opportunity and account context they already know.
Experlogix isn't the right fit for everyone. Salesforce CPQ can still be a solid fit for straightforward and moderately complex quoting, with low to mid-level configuration demands and limited complex workflow needs. A quoting-layer replacement may not be the right move if:
- Your catalog is simple.
- Your sales motion is pure self-service SaaS.
- You are already committed to an RCA reimplementation.
The Bottom Line on Quoting Products, Services and Subscriptions in One Deal
Salesforce CPQ's end of sale doesn't force a decision, but hybrid deals often do. When quoting products and services in one deal takes a second quote, a spreadsheet, or QCP code to reconcile, the costs pile up quietly:
- Slower approvals
- Margin you can't see until after the deal closes
- Contracts that don't match what the quoting system calculated
All three paths remain open:
- Staying on Salesforce CPQ is reasonable if mixed revenue is a small part of your volume and your configuration is stable.
- Reimplementing on Revenue Cloud Advanced fits organizations that want one Salesforce revenue platform and will fund a redesign.
- Replacing only the quoting layer while keeping Salesforce CRM as the system of record fits teams whose CRM works but whose quoting engine doesn't. It keeps mixed revenue, governed pricing, and document output in one place.
Teams that get this right tend to see the same practical gains: fewer manual line items, approvals that route by rule instead of by email, and a proposal that matches the contract because one engine produced both.
Start with evidence, not vendor decks. Take your three hardest recent hybrid deals and map every revenue stream on them: one-time products, labor and professional services, project deliverables, subscriptions, usage, and renewals. For each line, note where the number came from, who can change the rule behind it, and how long the quote took to assemble. That map will show whether your constraint is configuration, pricing logic, or architecture, and which of the three paths your business case supports.
Preguntas frecuentes
What is hybrid quoting?
Hybrid quoting means pricing several revenue types on one quote, such as one-time products, labor and professional services, project deliverables, recurring subscriptions, and usage-based charges. Each type follows its own pricing math, term logic, and approval thresholds, so hybrid quoting needs one engine that can apply all of those rules together.
Can CPQ quote products, services, labor, subscriptions and usage charges together?
Yes, if the CPQ is built for mixed revenue. With Experlogix CPQ, one-time equipment, recurring subscriptions, usage-based fees, and multi-year services and support can all sit on a single quote. Each line gets its own tiers, contract terms, and regional rules, applied automatically. Test this with your hardest real deal, not a demo catalog.
Can CPQ handle one-time and recurring revenue on the same quote?
It can, but the totals for each pricing model need to stay correct on one document. Term and date logic, including start dates, co-terming, proration, and ramped multi-year pricing, also has to calculate consistently. If your team builds separate quotes for one-time and recurring items, the quoting engine is likely the constraint.
Why do mixed-revenue quotes end up in spreadsheets?
When a quoting engine handles only some revenue types well, the rest moves into spreadsheets, manual line items, or custom code. Services scoping is the most common example. With Salesforce CPQ, pricing logic that doesn't fit the native model often ends up in Quote Calculator Plugin code that only a developer can maintain.
How should margin be shown on a hybrid quote?
Margin should be visible on the whole solution and on each line, not just as a blended total. Line-level margin shows whether a discount on equipment is being offset by services or subscriptions. Bundle-level margin shows whether the deal as a whole meets policy. Experlogix CPQ shows margin across the whole bundle as well as on each line.
Put Your Hardest Hybrid Deal on One Quote
