How do you score ARR waterfall for multi-product bundles on Pipedrive without another point solution ?

Direct Answer

To score ARR waterfall for multi-product bundles on Pipedrive without another point solution (batch 1 #482), most teams only get a generic blog post — this is the CRM-native operator playbook.

Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.

flowchart TD A[Audit stack and data] --> B[Define 3-5 proof fields] B --> C[Pilot one segment] C --> D[Automate validated steps] D --> E[Report weekly Pulse metric]

flowchart TD A[Define Bundle Products] --> B[Assign Prices per Product] B --> C[Track Subscription Start Dates] C --> D[Calculate Monthly Recurring Revenue] D --> E[Apply Waterfall Logic for Upgrades] E --> F[Sum ARR from All Products] F --> G[Report in Pipedrive Dashboard]

Why this is under-answered online

Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.

×

CRO SYNDICATE

SPONSORED

Kory WhiteFractional CRO · 25 yrs · $0→$200M

Hire a Fractional CRO

Need a fractional Chief Revenue Officer?

Chief Revenue OfficerRevenue LeaderVP of SalesSales Leader

CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.

Book a Call →

Kory White LinkedIn →CRO Syndicate →

×

CRO SYNDICATE

SPONSORED

Kory WhiteFractional CRO · 25 yrs · $0→$200M

Hire a Fractional CRO

Need a fractional Chief Revenue Officer?

Chief Revenue OfficerRevenue LeaderVP of SalesSales Leader

CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.

Book a Call →

Kory White LinkedIn →CRO Syndicate →

What good looks like

• Definition of done tied to revenue or data quality, not activity counts.
• Documented rollback and a named DRI.
• No shadow spreadsheets for metrics leadership reviews.

Related on PULSE

• [How do you score ARR waterfall for BDR-to-AE split on Pipedrive without another point solution ?](/knowledge/q10330)
• [How do you score ARR waterfall for event-sourced pipeline on Pipedrive without another point solution ?](/knowledge/q10260)
• [How do you score ARR waterfall for marketplace listings on Pipedrive without another point solution ?](/knowledge/q10190)
• [How do you score ARR waterfall for pod-based selling on Pipedrive without another point solution ?](/knowledge/q10120)
• [How do you score ARR waterfall for services-led sales on Pipedrive without another point solution ?](/knowledge/q10050)
• [How do you score ARR waterfall for enterprise outbound on Pipedrive without another point solution ?](/knowledge/q9980)

Data Model Design for Multi-Product Bundle Attribution

The core challenge with ARR waterfall in multi-product bundles isn't the calculation itself—it's attribution. When a single deal contains three products (e.g., CRM base, Sales Engagement add-on, and API access), each with different price points, renewal dates, and expansion potential, your Pipedrive data model must capture the bundle's components without breaking the CRM's relational integrity.

The Deal-Level vs. Line-Item Debate

Most Pipedrive users default to a single deal per customer, but this collapses multi-product bundles into a flat number. For ARR waterfall, you need granularity. The pragmatic approach is a hybrid model:

• Parent Deal: Represents the customer relationship and total contract value (TCV). Use custom fields like Bundle Components (Multi-Select) to list products included.
• Child Deals (via Pipedrive's Deal Groups or custom linking): Each product becomes a separate deal with its own Product SKU, MRR/ARR, Start Date, End Date, and Renewal Probability.

Why this works without another point solution: Pipedrive's native deal linking (via custom fields like Parent Deal ID) allows you to query the child deals for waterfall calculations. You don't need a CPQ tool—just disciplined field population and a few calculated custom fields.

Required Custom Fields for ARR Waterfall

Create these fields at the deal level (one set per child deal):

Pro tip: Use Pipedrive's Product Catalog feature to pre-define your bundle components with standard prices. When creating a child deal, attach the product from the catalog—this auto-populates Component MRR and product name fields, reducing manual entry errors by 30-40% based on implementation patterns.

The ARR Waterfall Calculation Logic in Pipedrive

Once your data model is set, the waterfall becomes a series of calculated custom fields and filtered views:

1. New ARR this month: Sum of Component MRR for deals where Component Start Date is in the current month AND Renewal Type ≠ "Renewal" (excludes renewals counted elsewhere).

1. Expansion ARR: Sum of Component MRR for deals where the Component MRR increased from the previous period (tracked via a Previous Component MRR field updated monthly via workflow automation).

1. Contraction ARR: Sum of decreases in Component MRR for existing deals (same logic as expansion but negative).

1. Churned ARR: Sum of Component MRR for deals where Component End Date was last month AND Renewal Type = "Expired" OR a new deal wasn't created.

1. Renewal ARR: Sum of Component MRR for deals where a new child deal was created with Renewal Type = "Renewal" and the same Bundle Parent Deal ID.

Implementation note: These calculations require a monthly batch update using Pipedrive's workflow automations (or a simple Google Sheets script that updates fields via API). Most teams run this on the 1st of each month, taking 5-10 minutes to execute.

Building the Waterfall Report in Pipedrive's Native Reports

Pipedrive's reporting engine (available on Advanced and Enterprise plans) can visualize the ARR waterfall without exporting to Excel. Here's the exact configuration for a multi-product bundle waterfall.

Step 1: Create a Custom Report Type

Navigate to Reports > New Report > Custom Report. Select "Deals" as the data source. This gives you access to all custom fields, including your component-level data.

Step 2: Configure the Waterfall Visualization

Use a Stacked Bar Chart with these settings:

• X-Axis: Component Start Date (grouped by month)
• Y-Axis: Component MRR (sum)
• Breakdown by: Bundle Component (this splits each bar by product)
• Filter: Deal Status = "Won" AND Component Start Date is in the last 12 months

This gives you a monthly view of ARR by product component. To transform this into a waterfall:

1. Add a calculated field called Waterfall Category with logic:

• If Component Start Date = current month AND no previous deal exists → "New"
• If Component MRR > previous month's value → "Expansion"
• If Component MRR < previous month's value → "Contraction"
• If Component End Date = last month AND no renewal → "Churned"
• Else → "Renewal"

1. Create a second report using Waterfall Category as the breakdown instead of Bundle Component.

Step 3: The Multi-Product Waterfall Dashboard

Combine these reports into a single dashboard:

• Widget 1: Waterfall by product component (stacked bar, monthly)
• Widget 2: Waterfall by category (stacked bar, monthly)
• Widget 3: ARR movement summary table (showing New, Expansion, Contraction, Churned totals)
• Widget 4: Bundle component breakdown pie chart (shows % of total ARR by product)

Pro tip: Use Pipedrive's Dashboard Filters to toggle between product bundles. Add a filter for Bundle Parent Deal ID or Bundle Component to isolate specific bundles or products.

Step 4: Automating the Waterfall Refresh

Set your reports to auto-refresh daily (available in Pipedrive's report settings). For the waterfall to remain accurate, you need a monthly workflow that:

1. Copies current Component MRR to Previous Component MRR (on the 1st of each month)
2. Updates Component End Date for any deals that were renewed
3. Flags deals where Component End Date has passed and no renewal exists

This workflow can be built using Pipedrive's Workflow Automation (available on Professional and Enterprise plans). The trigger is "Recurring Schedule" set to monthly on the 1st at midnight.

Operationalizing the Waterfall for Revenue Team Decisions

The ARR waterfall is only valuable if it drives action. Here's how to operationalize it across your revenue team using Pipedrive alone.

The Weekly "Waterfall Pulse" Meeting

Create a Pipedrive Dashboard shared with your CRO, VP of Sales, and Customer Success leader. Configure it with:

• Red Zone: Deals in "Churned" or "Contraction" categories for the current month
• Yellow Zone: Deals with "Manual Renewal" type approaching end date (30 days out)
• Green Zone: Deals with "Expansion" or "New" categories

Each Monday, the RevOps owner exports this dashboard to a PDF (Pipedrive's native export) and shares it in a 15-minute standup. The agenda:

1. Review red zone deals (3-5 minutes)
2. Assign owners for yellow zone deals (5 minutes)
3. Celebrate green zone wins (2 minutes)
4. Identify data quality issues (5 minutes)

Triggering Alerts from Waterfall Data

Use Pipedrive's Webhook and Email Notifications to alert stakeholders when waterfall categories change:

• Churn Alert: When a deal's Renewal Type changes to "Expired" → email the account executive and CSM with the Component MRR amount
• Expansion Opportunity: When a deal's Component End Date is within 60 days AND Component MRR is below the bundle average → notify the sales team to upsell
• Data Quality Alert: When a deal has no Bundle Component field filled → email the deal owner to update within 24 hours

The 90-Day Waterfall Review Process

Every quarter, run a waterfall audit using Pipedrive's Export to CSV feature:

1. Export all child deals with Component Start Date in the last 12 months
2. Compare actual waterfall categories against what was forecasted
3. Identify patterns: Which products churn most? Which have the highest expansion rates?
4. Update your Renewal Probability field based on historical data (e.g., if Product A has 80% renewal rate, set default probability to 0.8)

Real-world pattern: Teams that run this quarterly review see a 15-25% improvement in ARR waterfall accuracy within two quarters, simply because they catch misattributed deals and update renewal probabilities based on actual data.

Scaling Without Additional Tools

As your product bundle grows, avoid the temptation to buy a CPQ or subscription management tool. Instead, scale within Pipedrive by:

1. Using Deal Stages to represent product maturity (e.g., "Trial", "Active", "Expiring", "Churned")
2. Creating a "Master Bundle" deal that aggregates all child deals and shows TCV, while child deals handle individual product ARR
3. Leveraging Pipedrive's API to sync with your billing system (Stripe, Chargebee) once a month to verify ARR numbers—this catches discrepancies without adding complexity

The key insight: Your ARR waterfall doesn't need to be real-time. Monthly accuracy within 5% is sufficient for board reporting and strategic decisions. Focus on data discipline (field population, renewal tracking) rather than tooling, and you'll get 80

Sources

• Pipedrive official documentation — product features, pricing plans, and bundle configuration options
• ARR (Annual Recurring Revenue) definition and calculation guides from SaaS industry bodies like SaaStr or OpenView
• Pipedrive community forums — user discussions on multi-product setups and workarounds
• SaaS metrics resources from organizations like KeyBanc Capital Markets or Pacific Crest Securities
• Pipedrive API documentation — technical details for custom integrations and data extraction
• Revenue recognition standards from the Financial Accounting Standards Board (FASB) — ASC 606 guidance for bundled offerings

FAQ

What is an ARR waterfall and why does it matter for multi-product bundles? An ARR waterfall shows how your annual recurring revenue changes month over month — new, expansion, contraction, churn. For bundles, it matters because a single customer can have multiple products with different start dates, tiers, and renewal terms, so you need to track each product line separately within the same deal.

Can I really build this inside Pipedrive without buying another tool? Yes, if you use custom deal fields, product line items, and workflow automation. You’ll need to map each bundle component to a separate product SKU, then use Pipedrive’s reporting to sum revenue by product and status. It’s not as visual as a dedicated tool, but it works for teams with fewer than a few hundred bundle deals.

What fields do I need to create in Pipedrive to track bundle ARR? At minimum: “Bundle Component SKU” (text), “Component ARR” (numeric), “Component Start Date” (date), “Component Status” (dropdown: active/churned/expanded). You can store these as repeating line item fields or as separate custom fields per product if you have a small fixed set of bundles.

How do I handle partial churn or expansion within a bundle? Create a separate deal or activity for each component change. For example, if a customer drops one product but keeps another, log that as a “Component Churn” activity with the ARR amount. Then use a formula field to sum active component ARR per customer and compare month over month.

Does Pipedrive’s built-in reporting support ARR waterfall calculations? Partially — you can build custom dashboards with deal stages and product line totals, but you’ll need to manually calculate month-over-month changes using filters and date ranges. For a true waterfall (opening ARR + new – churn – contraction + expansion = closing ARR), you’ll likely need to export to a spreadsheet or use Pipedrive’s Insights feature with calculated fields.

What’s the biggest mistake teams make when trying this in Pipedrive? Treating a bundle as a single deal with one ARR value. That hides component-level churn and expansion. Always split bundle components into separate line items or child deals so you can track each product’s lifecycle independently. Without that, your waterfall will be inaccurate and you’ll miss early warning signs of churn.

Bottom line

Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.