How a broken product data model — stretched across 100+ countries, multiple plans, subscription types and complex pricing tiers — was rebuilt from the ground up into a clean, scalable CPQ system

Background

A telecommunications company needed a best practice, scalable CPQ (Configure, Price, Quote) implementation for their Sales Operations. The company sold products with a pricing model that varied across multiple dimensions: plan, structure, subscription, region, country, data allowance tier, and a dual-price structure combining a base fee with a usage-based overage charge. The company presented complex business requirements that had grown into an architectural crisis.

To handle this complexity, the previous approach had been to create a separate Salesforce product record for every combination of these variables. A single product sold across different regions, countries, plans, structures, subscriptions and data tiers multiplied into thousands of individual product records. The product master would have been painful to maintain when updating pricing or adding new markets without creating a cascade of manual work and data integrity issues.

This was not a configuration problem. It was a fundamental data model problem that required a complete architectural redesign — not a patch. The engagement also included building an approval workflow, implementing multiple region, country, plan and subscription-level product rules, and integrating DocuSign to automate contract generation and signature tracking end-to-end.

The Challenges

Challenge 1: An Unscalable Product Data Model Built on Duplication

• The existing product architecture used one Salesforce product record per pricing combination — meaning a single real-world product existed as hundreds of variations in the system.
• With products sold across 100+ countries and multiple plan, structure, subscription, and data tier combinations, the product master had grown to thousands of records.
• Adding a new country, plan type, or data tier required manually creating and configuring dozens of new product records — a process that was error-prone, time-consuming, and completely unscalable.
• Updating pricing across the catalog required finding and editing hundreds of individual records, with no efficient way to manage changes globally.
• The bloated product master was not just a maintenance problem — it was an opportunity to rethink the entire architecture and introduce a far more streamlined, maintainable process.

Challenge 2: Complex, Multi-Dimensional Pricing Logic

• Pricing was not simply a matter of product and quantity. Every quote line item needed to account for plan type, structure, subscription, region, country, and data allowance tier simultaneously.
• The dual-price model — a base (basic) fee combined with a usage-based overage charge — meant each quote line effectively required two related pricing entries.
• Certain plan and subscription combinations were only valid for specific regions or countries, requiring configurable rules to prevent invalid combinations from being quoted.
• Add-on products required separate pricing logic with controlled editability — some fields editable by Sales, others auto-populated by the system.

Challenge 3: No Scalable Approval Framework for Discount Control

• Sales reps had flexibility to adjust pricing on quote lines, but there was no systematic framework to determine when those adjustments required escalated approval.
• The approval chain needed to be dynamic — escalating automatically from Sales Rep level to Manager, Director, or CEO depending on how far the proposed price deviated from the defined pricing threshold at each level.
• Without this framework, discounting was inconsistent and margin protection was entirely dependent on manual oversight.

Challenge 4: No End-to-End Contract Automation

• Once a quote was approved, the contract generation and signature process was handled outside of Salesforce, breaking the end-to-end visibility of the deal.
• There was no automated link between quote approval, contract generation, DocuSign envelope sending, and signature status tracking back in Salesforce.
• Sales had no real-time visibility into whether a contract had been sent, viewed, or signed without following up manually.

The Solutions

Solution 1: Complete Product Data Model Redesign Using a Core Product Bundle Model & Custom Object for Variations

• Rather than patching the existing structure, the product master was completely rebuilt from the ground up.
• Product Master: Each base product was defined by its core attributes only — Plan, Structure, and Subscription — the elements that remain constant regardless of where or how the product is sold. One product record per core base selection, no duplicates, no variation bloat.
• Custom tables: Each variant product was defined by the core attributes + its variant attributes (country / data tier / base vs overage fee) and stored as individual records in a custom object. This object stored every combination of plan, structure, subscription, region, country, data allowance tier, base fee, and overage charge as its own record — linked back to the core parent product.
• This architectural separation meant the product master went from thousands of records to a few dozen. All the complexity lived in the custom object where it belonged.
• Adding a new country, plan, or data tier meant adding records to the custom object instead of duplicating product records. Pricing updates could be managed centrally without touching the product catalog.
• The result was a product master that was clean, maintainable, and infinitely more scalable than what existed before.

Solution 2: Dynamic Pricing Rules with Region, Country, Structure and Subscription Dependencies

• CPQ price rules were configured to dynamically apply the correct pricing from the custom pricing object based on the combination of plan type, structure, subscription, region, country, data allowance, and fee type selected on each quote line.
• The dual-price model (base fee + overage) was implemented using a Basic & Overage pair logic — when a quote line was created, a second paired line was automatically created to capture the overage fee, eliminating the need for manual entry.
• Region and country auto-population rules were applied: products with region-specific designations auto-populated their allowable region and country fields on save. For other products, the available country selections were pre-filtered based on the region, structure, and subscription chosen.
• Product rules were configured to enforce valid combinations — preventing sales reps from quoting plans or subscriptions that were not available in the selected region or country.
• Some product quantities were editable by Sales, while others were auto-populated based on rules — enforcing minimum order requirements without relying on manual entry.

Solution 3: Dynamic Tiered Approval Workflow Based on Pricing Thresholds

• A multi-tier approval framework was built into CPQ that automatically determined the required approval level based on how the quoted price compared to defined pricing thresholds.
• If the quoted price fell below the Sales Rep price threshold, Manager approval was automatically triggered. If it fell below the Manager threshold, Director approval was required. If it fell below the Director threshold, CEO approval was escalated to.
• The approval tier was calculated and displayed directly on the quote line, giving Sales full visibility into which approvals would be needed before submitting.
• Approvers received email notifications and Salesforce task assignments when a quote required their review. Tasks were auto-completed once the approval step was actioned, keeping the workflow clean and auditable.
• A CPQ dashboard was built for Managers and Directors showing all pending approvals across the team, with filtering by approval level and quote status.

Solution 4: DocuSign Integration for End-to-End Contract Automation

• DocuSign was integrated directly into the CPQ quote process. Once a quote reached Approved status and all required DocuSign mandatory fields were populated, the ‘Create Contract’ button became available on the quote record.
• Clicking ‘Create Contract’ generated the contract document and initiated the DocuSign envelope, sending it to the designated Signing Authority Contact for e-signature.
• Quote status in Salesforce updated automatically at each stage of the DocuSign process: the status moved to ‘Sent’ when the envelope was dispatched, and to ‘Signed’ when the contract was executed — giving Sales and leadership real-time visibility without leaving Salesforce.
• Key DocuSign fields — including Plan, Subscription, and Data Type — were auto-populated by automation based on the products selected on the quote, reducing manual data entry and the risk of contract errors.
• A no-approval version of the quote process was also implemented for Sales to send a branded pricing PDF directly to contacts from the Account record — a lightweight alternative to the full contract process for early-stage opportunities.

Outcomes

Zola Consulting LLC • HubSpot Partner & Consultant • Salesforce Partner & Consultant • Upwork Expert-Vetted Top 1%