How do you score ARR waterfall for BDR-to-AE split on Pipedrive without another point solution ?

Direct Answer

To score ARR waterfall for BDR-to-AE split on Pipedrive without another point solution (batch 1 #412), 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[Start with Pipedrive Deal] --> B[Set BDR and AE fields] B --> C[Track Stage Changes] C --> D[Calculate ARR at each stage] D --> E[Assign ARR split by stage] E --> F[Use custom fields for attribution] F --> G[Generate ARR waterfall report]

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.

<!--pillar-weave-->

Related on PULSE

• [How do you score ARR waterfall for multi-product bundles on Pipedrive without another point solution ?](/knowledge/q10400)
• [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)

Building the ARR Waterfall Logic Layer in Pipedrive Custom Fields

The core challenge of scoring ARR waterfall for BDR-to-AE splits without a point solution is that Pipedrive lacks native multi-stage revenue attribution. You must build a logic layer using custom fields, formula fields (available in Pipedrive Advanced or Enterprise), and deal-stage probability mappings. Start by creating three custom field types that will serve as your waterfall engine:

Field 1: BDR Contribution Type (single-select dropdown in the Deal Details section):

• Sourced – BDR generated the initial meeting or opportunity
• Assisted – BDR touched the deal but didn't generate the initial entry
• Unassisted – No BDR touch (AE-sourced or inbound with no SDR involvement)
• Co-Sourced – Two or more BDRs contributed (requires a secondary field for split percentage)

Field 2: BDR ARR Credit % (numeric field, 0-100, decimal allowed): This field should be auto-populated via workflow automation based on rules you define. For example:

• If BDR Contribution Type = "Sourced" → set BDR ARR Credit % = 50% (or your org's standard split)
• If "Assisted" → 25%
• If "Co-Sourced" → 40% (with a secondary field for the second BDR's share)
• If "Unassigned" → 0%

Field 3: BDR ARR Credit Amount (formula field, currency): [Deal Value] * [BDR ARR Credit %] / 100

This formula field automatically calculates the dollar amount attributable to the BDR for each deal. The AE's portion is simply [Deal Value] - [BDR ARR Credit Amount]. For ARR waterfall reporting, you'll then create a custom dashboard that sums these fields across stages (won, committed, pipeline) by month.

Implementation note: If your Pipedrive plan doesn't support formula fields (requires Advanced or Enterprise), use a webhook-based automation via Zapier or Make.com to calculate and write the value back to the deal. This adds a dependency but avoids a full point solution. Expect 2-4 hours of setup time for the initial field structure and automation rules.

Mapping Deal Stages to Waterfall Probability Weights

A true ARR waterfall requires weighting pipeline deals by their probability to close, then attributing that weighted value to BDRs and AEs separately. Pipedrive's default stage probabilities are often too simplistic (e.g., 10%, 50%, 90%). For BDR-to-AE split reporting, you need stage-specific probability tiers that account for the handoff point.

Create a probability mapping table in a Google Sheet or Notion doc that your team agrees on, then apply it to Pipedrive stages via custom field automation. Here's a realistic example for a typical SaaS sales cycle:

The key insight: BDR-attributed probability decreases after handoff because the AE's actions (or inaction) now drive outcomes. To implement this in Pipedrive without a point solution:

1. Create a custom field BDR-Weighted Probability (numeric, 0-100)
2. Set up workflow automation rules that update this field when a deal moves stages:

• When stage changes to "AE Demo Scheduled" → set BDR-Weighted Probability = 20
• When stage changes to "Demo Completed" → set to 25
• Continue through all stages

1. Create a formula field BDR Weighted ARR = [Deal Value] * [BDR-Weighted Probability] / 100 * [BDR ARR Credit %] / 100

This gives you a true waterfall view: total ARR in pipeline, weighted by probability, further split by BDR contribution. The AE's weighted ARR is the inverse. You can then build a dashboard with two line charts:

• BDR Waterfall: Sum of BDR Weighted ARR by month and stage
• AE Waterfall: Sum of AE Weighted ARR (calculated as [Deal Value] * [Stage Probability] / 100 * (100 - [BDR ARR Credit %]) / 100)

Caveat: This approach requires consistent stage progression and manual probability calibration every quarter. Expect to spend 2-3 hours per quarter updating probability weights based on historical close rates. Without this calibration, your waterfall will be misleading.

Automating BDR-to-AE Split Reporting with Pipedrive Dashboards and Email Reports

Once your custom fields and probability logic are in place, the final step is building automated reporting that delivers the ARR waterfall to stakeholders without requiring manual exports or additional tools. Pipedrive's native dashboarding and reporting capabilities (available on Advanced and Enterprise plans) can handle this if structured correctly.

Step 1: Create three key dashboard widgets

Widget 1: BDR ARR Waterfall by Stage (stacked bar chart)

• X-axis: Deal stage (grouped)
• Y-axis: Sum of BDR ARR Credit Amount
• Filter: BDR Contribution Type ≠ "Unassisted"
• Color by: Month (so you see progression over time)

Widget 2: AE ARR Waterfall by Stage (stacked bar chart)

• X-axis: Deal stage
• Y-axis: Sum of AE ARR Credit Amount (calculated field: [Deal Value] - [BDR ARR Credit Amount])
• Filter: All deals (since AE touches everything)

Widget 3: Split Comparison Table (table widget)

• Columns: Deal name, Deal value, BDR name, AE name, BDR ARR Credit %, BDR ARR Credit Amount, AE ARR Credit Amount, Stage, Close date
• Sort by: Close date descending
• Filter: Stage = "Closed Won" and close date within current quarter

Step 2: Set up automated email reports

Pipedrive allows you to schedule dashboard snapshots via email. Configure:

• Weekly BDR Waterfall Report: Send every Monday at 9 AM to BDR team lead and RevOps. Include Widgets 1 and 3.
• Monthly AE Waterfall Report: Send on the 1st of each month to sales leadership. Include all three widgets plus a summary of total ARR attributed to BDRs vs. AEs for the prior month.

To calculate the summary metric without a point solution, create a custom report in Pipedrive's Reports section:

1. Go to Reports → New Report → Deals
2. Metric: Sum of BDR ARR Credit Amount and Sum of AE ARR Credit Amount
3. Group by: Close month
4. Filter: Stage = "Closed Won"
5. Save as "ARR Split by Month"
6. Add this report as a fourth widget to your dashboard

Step 3: Handle the handoff timing edge case

A common issue in BDR-to-AE split reporting is timing: a deal may be sourced by a BDR in January but close in March. Your waterfall should credit the BDR in the close month, not the source month. To handle this:

• Add a custom date field BDR Source Date (populated automatically when BDR Contribution Type is first set to "Sourced")
• In your dashboard filters, always use Close Date for ARR waterfall reporting, not BDR Source Date
• Create a separate "BDR Pipeline Velocity" report using BDR Source Date to show how quickly sourced deals move through stages

Limitations to acknowledge:

• Pipedrive's dashboard widgets cannot currently show running totals or cumulative waterfall lines (like a funnel chart). You'll need to export to Sheets for that visualization.
• Email reports are static snapshots; real-time waterfall views require users to open the dashboard directly.
• If you have more than 5 BDRs or 10 AEs, the table widget becomes unwieldy. Consider using Pipedrive's List View with grouping instead.

Total setup time for this reporting layer: 3-5 hours, including field creation, workflow automation, dashboard building, and email report scheduling. Maintenance is roughly 1 hour per month to verify data accuracy and adjust probability weights. This approach works well for teams with 2-15 BDRs and up to 50 AEs; beyond that, you'll likely need to graduate to a dedicated revenue attribution tool.

Sources

• Pipedrive Knowledge Base — official documentation on deal stages, custom fields, and reporting features.
• ARR (Annual Recurring Revenue) definition from SaaS Capital or OpenView — standard metrics for recurring revenue.
• HubSpot Sales Blog — best practices for BDR-to-AE handoff processes and sales compensation.
• Revenue Operations (RevOps) resources from Gartner or Forrester — frameworks for aligning sales roles and revenue attribution.
• Pipedrive Community Forum — user discussions on workarounds for waterfall reporting and split calculations.
• Sales Hacker or Revenue.io blog — guides on building ARR waterfalls and tracking conversion metrics without extra tools.

FAQ

What’s the minimum viable data I need to start scoring ARR waterfall in Pipedrive? You need at least three custom fields on the Deal object: “BDR Source” (picklist), “First Touch Date” (date), and “AE Handoff Date” (date). Without these, you can’t attribute pipeline stages to BDR or AE activity. Start with these before building any waterfall logic.

How do I split credit between BDR and AE without a point solution? Use Pipedrive’s built-in “Stages” and “Won Amount” reports, then manually calculate the waterfall by filtering deals by “BDR Source” and date ranges. For example, compare deals created by BDRs in Stage 1 vs. deals moved to Stage 2 by AEs. It’s manual but works for teams under 10 reps; beyond that, you’ll need automation.

Can I automate the waterfall scoring using Pipedrive’s native tools? Yes, with Pipedrive’s “Automations” and “Workflows” features. Set triggers like “Deal moved to Stage 2” to update a custom field “AE Touch” to “Yes,” then use the “Revenue Forecasting” report to sum won amounts by BDR vs. AE fields. This avoids third-party tools but requires careful field mapping and testing.

What’s the biggest mistake teams make when trying this without a point solution? They skip defining clear handoff criteria between BDR and AE. Without a shared definition of “qualified lead” (e.g., meeting booked, demo completed), the waterfall becomes subjective. Document your SLA in Pipedrive’s “Notes” field on each deal to ensure consistency.

How often should I audit the waterfall data in Pipedrive? Weekly for the first month after setup, then monthly. Check for missing “BDR Source” values, deals stuck in stages longer than 7 days, and inconsistent “AE Handoff Date” entries. A 15-minute audit prevents garbage-in-garbage-out in your reports.

What if my team has multiple BDRs and AEs—can I still score per rep? Yes, but you’ll need a custom field “BDR Owner” and “AE Owner” on each deal. Pipedrive’s “User” fields allow filtering by rep. The waterfall then becomes a per-rep comparison of won amounts by stage, which you can export to a spreadsheet for manual scoring.

Bottom line

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