How do you automate CAC payback for BDR-to-AE split on Pipedrive without another point solution ?
To automate CAC payback for BDR-to-AE split on Pipedrive without another point solution (batch 1 #172), 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.
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.
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallKory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallWhat 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 automate CAC payback for services-led sales on Pipedrive without another point solution ?](/knowledge/q10370)
- [How do you automate CAC payback for enterprise outbound on Pipedrive without another point solution ?](/knowledge/q10300)
- [How do you automate CAC payback for outbound SDR on Pipedrive without another point solution ?](/knowledge/q10230)
- [How do you automate CAC payback for multi-product bundles on Pipedrive without another point solution ?](/knowledge/q10160)
- [How do you automate CAC payback for event-sourced pipeline on Pipedrive without another point solution ?](/knowledge/q10020)
- [How do you automate CAC payback for marketplace listings on Pipedrive without another point solution ?](/knowledge/q9950)
Data Architecture: The Three-Layer Field Stack for CAC Attribution
Most teams fail at CAC payback automation because they treat it as a single calculation rather than a layered data architecture. In Pipedrive, you need three distinct field layers that feed into each other without external tools. Layer 1 is cost attribution — how much did each deal cost to generate? Layer 2 is time-to-revenue — when did the BDR touch happen versus AE close? Layer 3 is payback calculation — the automated formula that combines both.
For Layer 1, create a custom deal field called BDR Sourcing Cost (numeric, currency format). This isn't a manual entry field — it's populated by a Pipedrive workflow that triggers when a deal moves from BDR stage to AE stage. The workflow pulls from a separate custom field on the person or organization record called BDR Cost per Lead (also numeric, currency). You set this cost per lead quarterly based on your actual BDR team expenses divided by qualified leads generated. For example, if your BDR team costs $50,000 per quarter and generates 250 qualified leads, your cost per lead is $200. The workflow multiplies this by the number of BDR touches on that deal (tracked via a BDR Touch Count field that increments each time the BDR logs an activity on the deal).
Layer 2 requires a BDR First Touch Date field (date format) and the existing Won Date field. The workflow auto-populates BDR First Touch Date when a deal enters the first BDR stage. The Days from BDR to Won field (numeric, integer) is a formula field that calculates Won Date minus BDR First Touch Date. This gives you the exact revenue cycle length attributable to that specific BDR-AE pair.
Layer 3 is the CAC Payback Days field (numeric, integer). The formula is: (BDR Sourcing Cost + AE Commission Portion) / (Deal Value / Days from BDR to Won). The AE commission portion is another custom field (AE Commission on Deal, currency) that you can auto-calculate as a percentage of deal value based on your comp plan. Pipedrive's formula fields support basic arithmetic, so you can build this directly in the deal view. The result tells you: "For this specific deal, how many days of revenue does it take to pay back the combined BDR and AE cost?"
The critical operational rule is that every field must have a single source of truth. No manual overrides except by the RevOps admin. You enforce this through Pipedrive's permission sets — make these fields read-only for sales users, editable only by users with the "RevOps Admin" role. This prevents the data corruption that kills most CAC automation attempts.
Workflow Automation: The BDR-to-AE Handoff Trigger Sequence
Pipedrive's built-in workflow automation (available on Professional and Enterprise plans) can handle the entire BDR-to-AE CAC split without any external tooling. The key is designing a trigger sequence that fires at the exact moment the deal transitions from BDR ownership to AE ownership, not at deal close.
Create a workflow named "CAC Payback Attribution" with the trigger: "When deal stage changes to [AE Qualification Stage]" — this is the stage where the BDR hands off to the AE. The workflow has three sequential actions. Action 1: "Copy field value" — copy the BDR Cost per Lead from the person/org record to the deal's BDR Sourcing Cost field. Action 2: "Set field value" — set BDR First Touch Date to the current date if it's empty (this prevents overwriting if the deal re-enters this stage). Action 3: "Calculate and set" — set BDR Touch Count to the number of activities logged on the deal by users with the "BDR" role in the last 30 days. Pipedrive's workflow engine can filter activities by user role, so this is natively supported.
The second workflow triggers when the deal stage changes to "Won." Name it "CAC Payback Finalize." Actions: 1) Set Days from BDR to Won to [Won Date] - [BDR First Touch Date]. 2) Set AE Commission on Deal to [Deal Value] * 0.10 (replace 0.10 with your actual AE commission rate — common ranges are 5-15% for enterprise, 8-12% for SMB). 3) Set CAC Payback Days to ([BDR Sourcing Cost] + [AE Commission on Deal]) / ([Deal Value] / [Days from BDR to Won]).
You need a third workflow for the rare but important edge case: deals that skip BDR stages entirely (e.g., inbound direct to AE). Trigger: "When deal created" with condition "Stage is not [BDR Stage]." Action: Set BDR Sourcing Cost to 0, BDR First Touch Date to current date, and BDR Touch Count to 0. This ensures your CAC payback calculations don't break when BDRs aren't involved — those deals simply show $0 BDR cost and a payback period based solely on AE cost.
Test this with a sandbox or test pipeline first. Create a test deal, move it through BDR stages, then to AE stage, then to won. Verify that every field populates correctly. The most common failure point is the activity count — if your BDRs log activities inconsistently (e.g., using different activity types), the BDR Touch Count will be inaccurate. Standardize activity types to a single "BDR Touch" type before deploying this automation.
Reporting and Governance: The Weekly Pulse Dashboard
Without a dashboard, your CAC payback automation is just data rot. Build a Pipedrive dashboard with four key reports that give you actionable insight, not just vanity metrics. Use the "Deals" reporting object, filtered to deals won in the current quarter.
Report 1: CAC Payback Distribution — a histogram chart with CAC Payback Days on the X-axis (bucketed into 0-30, 31-60, 61-90, 90+ days) and deal count on the Y-axis. Color-code by BDR-AE pair (use the Owner field combined with a custom BDR Owner field). This immediately shows you which pairs are efficient (0-30 days) and which are dragging (90+ days). The target for most B2B SaaS companies is under 60 days for SMB, under 90 for enterprise.
Report 2: BDR Cost Efficiency by Source — a bar chart showing average BDR Sourcing Cost per deal, grouped by the lead source (e.g., LinkedIn, Outbound Email, Events). Overlay a line for average Deal Value. This reveals which sources produce deals with lower acquisition cost relative to value. If LinkedIn-sourced deals cost $300 in BDR effort but close at $10,000, while event-sourced deals cost $800 and close at $5,000, you know where to shift BDR time.
Report 3: AE Commission ROI — a scatter plot with AE Commission on Deal on the X-axis and Deal Value on the Y-axis. Each point is a deal, colored by AE name. Add a trendline. This visualizes whether higher commission payouts correlate with higher deal values. If you see a cluster of low-value deals with high commissions, your comp plan may be misaligned.
Report 4: CAC Payback Trend — a line chart showing average CAC Payback Days per week over the last 12 weeks. Add a target line at your desired payback period (e.g., 60 days). This is your pulse metric — if the line trends upward, your BDR-to-AE handoff is deteriorating. Investigate immediately by drilling into the BDR-AE pairs that are driving the increase.
Governance is the unsung hero. Assign a single RevOps owner to review this dashboard every Monday morning. Their job is not just to look at numbers but to take three actions: 1) Flag any deal where CAC Payback Days exceeds 120 days — these deals are destroying unit economics. 2) Identify BDR-AE pairs where the gap between BDR First Touch Date and the date the deal entered AE stage is over 14 days — this indicates a slow handoff that inflates CAC. 3) Update the BDR Cost per Lead field monthly based on actual BDR team costs (salaries, tools, overhead divided by qualified leads). If you don't update this, your CAC payback numbers become stale within 60 days.
The governance cadence also includes a quarterly audit of the workflow triggers. Pipedrive's workflow engine can occasionally misfire due to stage name changes or field deletions. Set a calendar reminder to test the three workflows on a dummy deal every 90 days. This prevents the silent data corruption that makes your dashboard look good while your actual CAC payback is worsening.
Sources
- Pipedrive Knowledge Base — official documentation on Pipedrive’s automation features, workflows, and API capabilities.
- HubSpot Blog — articles on sales metrics, CAC payback, and BDR/AE compensation structures.
- Salesforce Ben — insights on sales operations automation and revenue attribution models.
- Gartner — research reports on sales performance metrics and CRM automation best practices.
- RevOps (Revenue Operations) community forums (e.g., RevGenius, Pavilion) — practitioner discussions on custom CAC payback calculations and Pipedrive workarounds.
- Pipedrive Community Forum — user-shared solutions and scripts for automating split calculations without third-party tools.
FAQ
What exactly is CAC payback for a BDR-to-AE split? It’s the time it takes for revenue generated by a BDR-sourced deal to cover the combined cost of the BDR and AE involved. You calculate it by dividing the fully loaded cost of both roles by the gross margin contribution from closed-won deals they jointly influenced.
How can I track BDR and AE costs separately in Pipedrive without extra software? Use custom person and deal fields to tag each deal with the BDR and AE names, then create a formula field that sums their salary, commission, and overhead percentages. Pull that into a custom report that divides total cost by deal revenue to show payback months per rep pair.
What fields do I need to set up in Pipedrive to automate this? You’ll need at least three custom deal fields: “BDR Owner,” “AE Owner,” and “Deal Cost Basis” (a formula that references your rep cost table). Optionally add “Deal Gross Margin” and “Payback Period” (calculated as cost ÷ margin). These let you build a pipeline report without external tools.
How do I handle deals where the BDR and AE split changes over time? Create a “Split %” field on the deal that you update when the handoff occurs—common ranges are 50/50, 60/40, or 70/30. Then adjust your cost formula to multiply each rep’s cost by their split percentage before summing. This keeps the calculation accurate without adding a new system.
Can I use Pipedrive’s built-in reporting to visualize payback trends? Yes, use the “Deals” report type with filters by BDR and AE owner, then add a calculated column for payback months. Group by month or quarter to see trends. The limitation is that Pipedrive’s native reports don’t auto-update formulas dynamically, so you’ll need to refresh data weekly.
What’s the biggest mistake teams make when automating this in Pipedrive? They skip auditing their existing data quality first—missing or inconsistent rep tags, no cost basis field, or deals not linked to the right owners. Without clean data, any automated calculation will produce misleading payback numbers. Fix field hygiene before building reports.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.