13/13 Gate✓ IQ Certified10/10?

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution ?

📖 3,031 words🗓️ Published Jul 26, 2026

Direct Answer

Model expansion rate for PLG-to-sales handoff in Pipedrive without another point solution by repurposing custom deal fields, pipeline stages, and native automation to track incremental revenue from self-serve users who receive sales engagement, then reporting the ratio via Pipedrive's built-in dashboards.

The outcome you should expect

When you model expansion rate natively in Pipedrive, you gain visibility into which PLG-to-sales handoffs actually drive incremental revenue beyond what self-serve users would have spent on their own. The primary outcome is a reliable, repeatable metric that your RevOps team can report to leadership weekly without relying on shadow spreadsheets or third-party tools. Specifically, you should expect to calculate expansion rate as the percentage of handoff-touched users who generate additional revenue within 30-90 days, alongside the average dollar amount per expansion event. For example, if 200 PLG users enter the handoff pipeline in a month and 40 close expansion deals worth an average of $300 each, your expansion rate is 20% and expansion revenue totals $12,000. This data lives entirely inside Pipedrive's reports, accessible with a few clicks. The outcome also includes cleaner sales behavior because reps know their expansion performance is tracked, and a single RevOps owner can maintain the model with roughly two hours of monthly upkeep once the initial setup is complete. Without this model, teams typically guess at expansion impact or pay for an expensive analytics platform just to answer one question.

What drives that outcome

The expansion rate model succeeds because of three interconnected drivers: data integrity at the point of entry, pipeline stage discipline, and automated validation loops. Each driver directly affects the accuracy and usefulness of your expansion metric.

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 1

Data integrity starts with custom fields that force sales reps to categorize every handoff deal. Create a required dropdown field on the deal object called "Expansion Category" with values like "Plan Upgrade," "Seat Expansion," "Cross-sell," and "No Expansion." Make this field mandatory before a deal can move to "Closed Won." This single field eliminates the ambiguity of whether a deal counts as expansion or new business. You also need a "Pre-Handoff MRR" field on the contact or organization level, populated from your billing system via a monthly CSV import or a lightweight Zapier connection. This baseline number is the anchor for calculating the delta. Without it, you cannot prove that revenue is truly incremental rather than something the user would have spent anyway.

Pipeline stage discipline means designing a dedicated expansion pipeline with five stages that mirror the customer journey from qualification to verified revenue. The stages are: "PLG Lead Qualified" (user shows buying intent), "Sales Engaged" (rep initiates contact), "Proposal Sent" (expansion offer delivered), "Closed Won Expansion" (deal signed), and "Expansion Verified" (revenue confirmed after 30 days). Each stage has clear entry criteria and automation rules. For example, a deal automatically moves from "Proposal Sent" to "Closed Won Expansion" when the rep marks the deal as won and the "Expansion Category" field is populated. This structure prevents deals from skipping stages and ensures every expansion event has a documented path.

Automated validation loops catch false positives before they pollute your metrics. Thirty days after a deal enters "Closed Won Expansion," Pipedrive's activity automation creates a task for the assigned rep to verify the user actually upgraded. The rep must either confirm the expansion amount in a custom "Verified Expansion Amount" field or move the deal to a "Failed Expansion" stage. Deals that remain unverified after 45 days automatically flag for RevOps review. This loop typically catches 10-15% of deals that looked like expansion but were actually plan downgrades or cancellations, keeping your expansion rate honest.

Benchmarks and realistic ranges

Expansion rates for PLG-to-sales handoffs vary significantly by product maturity, pricing model, and sales motion maturity. Based on patterns observed across B2B SaaS companies with similar CRM setups, here are realistic ranges to benchmark against:

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 2

For early-stage products (under $5M ARR): Expect an expansion rate of 8-15% in the first 90 days after handoff. The average expansion amount typically ranges from $200 to $800 per deal, depending on whether you're selling seat expansions (lower per-unit but higher volume) or plan upgrades (higher per-unit but fewer events). At this stage, the primary challenge is low data quality—many deals lack the "Pre-Handoff MRR" field, skewing results. If your rate is below 5%, the issue is usually that sales reps aren't logging handoff deals in the expansion pipeline at all, or they're marking standard renewals as expansion.

For growth-stage products ($5M-$20M ARR): Expansion rates should climb to 15-25% as your sales team becomes more skilled at identifying upsell opportunities during the handoff. Average expansion amounts often increase to $500-$2,000 because you're targeting larger accounts with multi-seat or multi-product deals. The key benchmark here is expansion revenue per handoff-touched user—a healthy number is $100-$300 per user per quarter. If you're below $50, your handoff process is likely converting users but failing to capture their full willingness to pay.

For mature products (over $20M ARR): Top-quartile expansion rates reach 25-35%, with average expansion amounts exceeding $3,000. At this stage, the model should segment expansion by source (upgrade vs. cross-sell vs. seat expansion) because each behaves differently. Upgrade-driven expansion typically has a 30% rate, while cross-sell expansion drops to 12-18%. Seat expansion sits in the middle at 20-25%. These segments help you decide where to invest sales resources—for example, if upgrades drive 80% of expansion revenue but only 20% of handoff volume, you might shift reps toward more upgrade conversations.

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 3

Warning signs that your expansion rate is unreliable: If your rate exceeds 40%, you're likely double-counting revenue or including deals that aren't truly expansion (e.g., a new customer who happened to start on a free plan). If your rate is below 3% and you have active PLG users, your handoff pipeline is probably broken—users aren't reaching sales, or sales isn't logging deals. The most common error is confusing "account growth" (any revenue increase) with "expansion from handoff" (revenue increase directly attributable to sales intervention). Your model must exclude organic upgrades that happen without any sales touchpoint.

Risks, edge cases, and failure modes

Modeling expansion rate natively in Pipedrive without a point solution introduces several risks that can undermine the metric's reliability. Addressing these upfront prevents the model from becoming a source of misalignment between RevOps, sales, and leadership.

Risk 1: Sales reps bypass the expansion pipeline. When reps are in a hurry, they may close expansion deals in the standard "Closed Won" stage instead of the expansion pipeline, making those deals invisible to your expansion rate calculation. Mitigate this by making the expansion pipeline the default for any deal where the contact has an existing Pipedrive organization with a "Pre-Handoff MRR" value. Use Pipedrive's workflow automation to check: if a deal is created for a contact with a non-zero "Pre-Handoff MRR" and the deal value exceeds that MRR, automatically move the deal to the expansion pipeline and alert the rep. This catches roughly 70% of misrouted deals. For the remaining 30%, run a weekly audit comparing deals closed in the standard pipeline against contacts with recent handoff activity.

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 4

Risk 2: The "Pre-Handoff MRR" baseline becomes stale. If you import this field monthly but a user upgrades their self-serve plan between imports, your baseline understates their starting point, inflating your expansion rate. For example, a user who was paying $100/month before handoff but upgraded themselves to $200/month before sales engagement would show a $100 expansion even though the sales rep contributed nothing. Fix this by adding a "Baseline Date" field and flagging any deal where the handoff date is more than 45 days after the baseline date. Those deals require manual review or exclusion from the expansion rate calculation. Alternatively, import baseline data weekly during your pilot phase.

Risk 3: The 30-day verification window misses delayed churn. Some users accept an upgrade proposal but cancel within 60 days, meaning your 30-day check shows a false positive. Your expansion rate will look artificially high until those cancellations surface. Address this by adding a 90-day "Expansion Retention" field that flags deals where the user downgrades or cancels within three months. Create a Pipedrive report that shows expansion rate both with and without the retention filter—leadership should see the retained number as the true measure. Typically, 10-20% of verified expansions fail retention, so your net expansion rate is 80-90% of your gross rate.

Edge case: Users who pay annually vs. monthly. If a self-serve user pays $1,200 annually ($100/month effective) and upgrades to a $2,400 annual plan, the expansion is $1,200 on the deal but only $100/month in recurring terms. Your model must normalize to monthly recurring revenue (MRR) for accurate comparisons. Add a "Payment Frequency" field and use Pipedrive's formula field to calculate "Expansion MRR" as (deal value / months in billing cycle) minus (baseline MRR). For annual plans, divide by 12; for monthly, use 1. Without this normalization, your expansion rate will swing wildly based on deal timing.

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 5

Failure mode: The model is too complex for reps to follow. If your expansion pipeline has eight stages and five required fields, reps will rebel by logging deals elsewhere or refusing to use the custom fields. Keep the model simple: three required fields (Expansion Category, Pre-Handoff MRR, Verified Expansion Amount) and five pipeline stages. Anything beyond that should be optional or automated. During your pilot, track how long it takes a rep to log an expansion deal—if it exceeds three minutes, simplify. The goal is a model that survives contact with the sales team, not a perfect but unused system.

A practical rollout plan

Implementing this expansion rate model requires a phased approach that minimizes disruption to your sales team while ensuring data quality. The total timeline is 8-10 weeks from start to first reliable metric.

Phase 1: Audit and design (Weeks 1-2). Pull all deals from the past 90 days where a PLG user had any sales interaction. Manually classify each as expansion, new business, or no expansion. This gives you a baseline expansion rate and reveals how much data you're currently missing. Identify the top three custom fields you need: "Expansion Category" (dropdown), "Pre-Handoff MRR" (number field on contact), and "Verified Expansion Amount" (number field on deal). Design your expansion pipeline with the five stages described earlier. Document the exact automation rules and field requirements in a one-page playbook for your sales team.

Phase 2: Build and pilot (Weeks 3-4). Create the custom fields and pipeline in a sandbox Pipedrive environment first. Set up the workflow automations: deal creation triggers, stage movement rules, and 30-day verification tasks. Test with 10-15 fake deals to ensure the automation fires correctly. Then recruit one sales rep who handles PLG handoffs regularly to pilot the model. Ask them to log all expansion deals using the new pipeline for two weeks. Review the data weekly—check for missing fields, misrouted deals, and rep confusion. Adjust field requirements based on feedback. For example, if reps consistently forget the "Pre-Handoff MRR" field, make it auto-populate from a monthly import instead of requiring manual entry.

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution — figure 6

Phase 3: Roll out and train (Weeks 5-6). Once the pilot shows 90%+ field completion rates, roll out to the full sales team. Conduct a 30-minute training session covering: what counts as expansion, how to use the expansion pipeline, and why this metric matters for their compensation (if applicable). Provide a cheat sheet with screenshots of the required fields. Set up a Slack or email channel where reps can ask questions during the first week. Monitor deal creation daily for the first week—any deal that enters the standard pipeline but should be in the expansion pipeline triggers a manual review by RevOps.

Phase 4: Report and iterate (Weeks 7-10). Build three core reports in Pipedrive: expansion rate (deals in "Expansion Verified" / deals in "PLG Lead Qualified"), expansion revenue (sum of "Verified Expansion Amount"), and average expansion amount (expansion revenue / verified deal count). Create a dashboard with these metrics plus a funnel visualization of the expansion pipeline. Present the first month's data to leadership, clearly stating that this is a pilot metric subject to revision. After 30 days, run the retention check—compare your gross expansion rate to the net rate (excluding deals that churned within 90 days). Adjust your model to report the net rate going forward. Schedule a quarterly model audit where you sample 20% of expansion deals to verify data accuracy.

Ongoing maintenance: Each month, export your expansion data to a spreadsheet and run a cohort analysis by user signup month. Pipedrive's native reporting doesn't handle cohort analysis well, but a simple spreadsheet pivot table can show whether expansion rates are improving for newer cohorts. This takes about one hour per month. Also, review your "Pre-Handoff MRR" import process—if your billing system changes, update the import mapping immediately to avoid data gaps.

FAQ

What is the difference between expansion rate and expansion revenue in this model? Expansion rate is the percentage of handoff-touched users who generate additional revenue, calculated as verified expansion deals divided by total PLG leads qualified. Expansion revenue is the total dollar amount of that additional revenue, summed from the "Verified Expansion Amount" field across all verified deals.

How often should I update the "Pre-Handoff MRR" field? Weekly during the pilot phase, then monthly once the model stabilizes. More frequent updates reduce the risk of stale baselines inflating your expansion rate. If your billing system supports API exports, automate this with a lightweight integration like Zapier rather than manual CSV imports.

What happens if a user upgrades before the sales rep contacts them? That upgrade is not expansion from handoff—it's organic growth. Exclude it from your expansion rate by checking the "Handoff Date" field. Only count upgrades that occur after the first sales touchpoint. If you can't determine the exact timing, exclude deals where the upgrade date is within 24 hours of the handoff trigger.

Can I use this model for annual contract value (ACV) expansion instead of MRR? Yes, but adjust your "Pre-Handoff Baseline" to ACV and normalize all expansion amounts to ACV. Be aware that ACV expansion rates tend to be lower than MRR rates because annual contracts have fewer upgrade opportunities within the contract term. Report both MRR and ACV expansion if your leadership team tracks different metrics.

How do I handle expansion from users who were previously on a free plan? Set the "Pre-Handoff MRR" baseline to $0 for free users. Their entire first payment counts as expansion revenue. This is accurate because the handoff converted them from a non-paying to a paying user. However, segment free-to-paid expansion separately from paid-to-upgraded expansion in your reports, as they have different economics.

What if my sales team doesn't use Pipedrive for all handoff deals? This is the most common failure mode. Enforce the model by making the expansion pipeline the default for any deal where the contact has a "PLG Source" field value (e.g., "Free Trial," "Freemium"). Use Pipedrive's email tracking to automatically create deals from sales emails to PLG users, ensuring every handoff is captured in the system.

Sources

flowchart TD S["How do you model expansion rate for PL"] S --> N0["The outcome you should expect"] N0 --> N1["What drives that outcome"] N1 --> N2["Benchmarks and realistic ranges"] N2 --> N3["Risks, edge cases, and failure modes"]

Related on PULSE

[How do you model expansion rate for inbound SDR on Pipedrive without another point solution ?](/knowledge/q10165)
[How do you alert on GRR for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10395)
[How do you model expansion rate for AE-led on Pipedrive without another point solution ?](/knowledge/q10375)
[How do you measure pipeline coverage for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10315)
[How do you model expansion rate for land-and-expand on Pipedrive without another point solution ?](/knowledge/q10305)
[How do you audit sales cycle length for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10155)

Download:

## Direct Answer

Model expansion rate for PLG-to-sales handoff in Pipedrive without another point solution by repurposing custom deal fields, pipeline stages, and native automation to track incremental revenue from self-serve users who receive sales engagement, then reporting the ratio via Pipedrive's built-in dashboards.

## The outcome you should expect

```mermaid
flowchart TD
  S["How do you model expansion rate for PL"]
  S --> N0["The outcome you should expect"]
  N0 --> N1["What drives that outcome"]
  N1 --> N2["Benchmarks and realistic ranges"]
  N2 --> N3["Risks, edge cases, and failure modes"]
```


When you model expansion rate natively in Pipedrive, you gain visibility into which PLG-to-sales handoffs actually drive incremental revenue beyond what self-serve users would have spent on their own. The primary outcome is a reliable, repeatable metric that your RevOps team can report to leadership weekly without relying on shadow spreadsheets or third-party tools. Specifically, you should expect to calculate expansion rate as the percentage of handoff-touched users who generate additional revenue within 30-90 days, alongside the average dollar amount per expansion event. For example, if 200 PLG users enter the handoff pipeline in a month and 40 close expansion deals worth an average of $300 each, your expansion rate is 20% and expansion revenue totals $12,000. This data lives entirely inside Pipedrive's reports, accessible with a few clicks. The outcome also includes cleaner sales behavior because reps know their expansion performance is tracked, and a single RevOps owner can maintain the model with roughly two hours of monthly upkeep once the initial setup is complete. Without this model, teams typically guess at expansion impact or pay for an expensive analytics platform just to answer one question.

## What drives that outcome

The expansion rate model succeeds because of three interconnected drivers: data integrity at the point of entry, pipeline stage discipline, and automated validation loops. Each driver directly affects the accuracy and usefulness of your expansion metric.

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 1](/assets/qa/q10235-b1.jpg)


**Data integrity** starts with custom fields that force sales reps to categorize every handoff deal. Create a required dropdown field on the deal object called "Expansion Category" with values like "Plan Upgrade," "Seat Expansion," "Cross-sell," and "No Expansion." Make this field mandatory before a deal can move to "Closed Won." This single field eliminates the ambiguity of whether a deal counts as expansion or new business. You also need a "Pre-Handoff MRR" field on the contact or organization level, populated from your billing system via a monthly CSV import or a lightweight Zapier connection. This baseline number is the anchor for calculating the delta. Without it, you cannot prove that revenue is truly incremental rather than something the user would have spent anyway.


**Pipeline stage discipline** means designing a dedicated expansion pipeline with five stages that mirror the customer journey from qualification to verified revenue. The stages are: "PLG Lead Qualified" (user shows buying intent), "Sales Engaged" (rep initiates contact), "Proposal Sent" (expansion offer delivered), "Closed Won Expansion" (deal signed), and "Expansion Verified" (revenue confirmed after 30 days). Each stage has clear entry criteria and automation rules. For example, a deal automatically moves from "Proposal Sent" to "Closed Won Expansion" when the rep marks the deal as won and the "Expansion Category" field is populated. This structure prevents deals from skipping stages and ensures every expansion event has a documented path.

**Automated validation loops** catch false positives before they pollute your metrics. Thirty days after a deal enters "Closed Won Expansion," Pipedrive's activity automation creates a task for the assigned rep to verify the user actually upgraded. The rep must either confirm the expansion amount in a custom "Verified Expansion Amount" field or move the deal to a "Failed Expansion" stage. Deals that remain unverified after 45 days automatically flag for RevOps review. This loop typically catches 10-15% of deals that looked like expansion but were actually plan downgrades or cancellations, keeping your expansion rate honest.

## Benchmarks and realistic ranges

Expansion rates for PLG-to-sales handoffs vary significantly by product maturity, pricing model, and sales motion maturity. Based on patterns observed across B2B SaaS companies with similar CRM setups, here are realistic ranges to benchmark against:

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 2](/assets/qa/q10235-b2.jpg)



**For early-stage products (under $5M ARR):** Expect an expansion rate of 8-15% in the first 90 days after handoff. The average expansion amount typically ranges from $200 to $800 per deal, depending on whether you're selling seat expansions (lower per-unit but higher volume) or plan upgrades (higher per-unit but fewer events). At this stage, the primary challenge is low data quality—many deals lack the "Pre-Handoff MRR" field, skewing results. If your rate is below 5%, the issue is usually that sales reps aren't logging handoff deals in the expansion pipeline at all, or they're marking standard renewals as expansion.

**For growth-stage products ($5M-$20M ARR):** Expansion rates should climb to 15-25% as your sales team becomes more skilled at identifying upsell opportunities during the handoff. Average expansion amounts often increase to $500-$2,000 because you're targeting larger accounts with multi-seat or multi-product deals. The key benchmark here is expansion revenue per handoff-touched user—a healthy number is $100-$300 per user per quarter. If you're below $50, your handoff process is likely converting users but failing to capture their full willingness to pay.

**For mature products (over $20M ARR):** Top-quartile expansion rates reach 25-35%, with average expansion amounts exceeding $3,000. At this stage, the model should segment expansion by source (upgrade vs. cross-sell vs. seat expansion) because each behaves differently. Upgrade-driven expansion typically has a 30% rate, while cross-sell expansion drops to 12-18%. Seat expansion sits in the middle at 20-25%. These segments help you decide where to invest sales resources—for example, if upgrades drive 80% of expansion revenue but only 20% of handoff volume, you might shift reps toward more upgrade conversations.

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 3](/assets/qa/q10235-b3.jpg)



**Warning signs that your expansion rate is unreliable:** If your rate exceeds 40%, you're likely double-counting revenue or including deals that aren't truly expansion (e.g., a new customer who happened to start on a free plan). If your rate is below 3% and you have active PLG users, your handoff pipeline is probably broken—users aren't reaching sales, or sales isn't logging deals. The most common error is confusing "account growth" (any revenue increase) with "expansion from handoff" (revenue increase directly attributable to sales intervention). Your model must exclude organic upgrades that happen without any sales touchpoint.

## Risks, edge cases, and failure modes

Modeling expansion rate natively in Pipedrive without a point solution introduces several risks that can undermine the metric's reliability. Addressing these upfront prevents the model from becoming a source of misalignment between RevOps, sales, and leadership.

**Risk 1: Sales reps bypass the expansion pipeline.** When reps are in a hurry, they may close expansion deals in the standard "Closed Won" stage instead of the expansion pipeline, making those deals invisible to your expansion rate calculation. Mitigate this by making the expansion pipeline the default for any deal where the contact has an existing Pipedrive organization with a "Pre-Handoff MRR" value. Use Pipedrive's workflow automation to check: if a deal is created for a contact with a non-zero "Pre-Handoff MRR" and the deal value exceeds that MRR, automatically move the deal to the expansion pipeline and alert the rep. This catches roughly 70% of misrouted deals. For the remaining 30%, run a weekly audit comparing deals closed in the standard pipeline against contacts with recent handoff activity.

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 4](/assets/qa/q10235-b4.jpg)


**Risk 2: The "Pre-Handoff MRR" baseline becomes stale.** If you import this field monthly but a user upgrades their self-serve plan between imports, your baseline understates their starting point, inflating your expansion rate. For example, a user who was paying $100/month before handoff but upgraded themselves to $200/month before sales engagement would show a $100 expansion even though the sales rep contributed nothing. Fix this by adding a "Baseline Date" field and flagging any deal where the handoff date is more than 45 days after the baseline date. Those deals require manual review or exclusion from the expansion rate calculation. Alternatively, import baseline data weekly during your pilot phase.


**Risk 3: The 30-day verification window misses delayed churn.** Some users accept an upgrade proposal but cancel within 60 days, meaning your 30-day check shows a false positive. Your expansion rate will look artificially high until those cancellations surface. Address this by adding a 90-day "Expansion Retention" field that flags deals where the user downgrades or cancels within three months. Create a Pipedrive report that shows expansion rate both with and without the retention filter—leadership should see the retained number as the true measure. Typically, 10-20% of verified expansions fail retention, so your net expansion rate is 80-90% of your gross rate.

**Edge case: Users who pay annually vs. monthly.** If a self-serve user pays $1,200 annually ($100/month effective) and upgrades to a $2,400 annual plan, the expansion is $1,200 on the deal but only $100/month in recurring terms. Your model must normalize to monthly recurring revenue (MRR) for accurate comparisons. Add a "Payment Frequency" field and use Pipedrive's formula field to calculate "Expansion MRR" as (deal value / months in billing cycle) minus (baseline MRR). For annual plans, divide by 12; for monthly, use 1. Without this normalization, your expansion rate will swing wildly based on deal timing.

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 5](/assets/qa/q10235-b5.jpg)


**Failure mode: The model is too complex for reps to follow.** If your expansion pipeline has eight stages and five required fields, reps will rebel by logging deals elsewhere or refusing to use the custom fields. Keep the model simple: three required fields (Expansion Category, Pre-Handoff MRR, Verified Expansion Amount) and five pipeline stages. Anything beyond that should be optional or automated. During your pilot, track how long it takes a rep to log an expansion deal—if it exceeds three minutes, simplify. The goal is a model that survives contact with the sales team, not a perfect but unused system.


## A practical rollout plan

Implementing this expansion rate model requires a phased approach that minimizes disruption to your sales team while ensuring data quality. The total timeline is 8-10 weeks from start to first reliable metric.

**Phase 1: Audit and design (Weeks 1-2).** Pull all deals from the past 90 days where a PLG user had any sales interaction. Manually classify each as expansion, new business, or no expansion. This gives you a baseline expansion rate and reveals how much data you're currently missing. Identify the top three custom fields you need: "Expansion Category" (dropdown), "Pre-Handoff MRR" (number field on contact), and "Verified Expansion Amount" (number field on deal). Design your expansion pipeline with the five stages described earlier. Document the exact automation rules and field requirements in a one-page playbook for your sales team.

**Phase 2: Build and pilot (Weeks 3-4).** Create the custom fields and pipeline in a sandbox Pipedrive environment first. Set up the workflow automations: deal creation triggers, stage movement rules, and 30-day verification tasks. Test with 10-15 fake deals to ensure the automation fires correctly. Then recruit one sales rep who handles PLG handoffs regularly to pilot the model. Ask them to log all expansion deals using the new pipeline for two weeks. Review the data weekly—check for missing fields, misrouted deals, and rep confusion. Adjust field requirements based on feedback. For example, if reps consistently forget the "Pre-Handoff MRR" field, make it auto-populate from a monthly import instead of requiring manual entry.

![How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution  — figure 6](/assets/qa/q10235-b6.jpg)



**Phase 3: Roll out and train (Weeks 5-6).** Once the pilot shows 90%+ field completion rates, roll out to the full sales team. Conduct a 30-minute training session covering: what counts as expansion, how to use the expansion pipeline, and why this metric matters for their compensation (if applicable). Provide a cheat sheet with screenshots of the required fields. Set up a Slack or email channel where reps can ask questions during the first week. Monitor deal creation daily for the first week—any deal that enters the standard pipeline but should be in the expansion pipeline triggers a manual review by RevOps.

**Phase 4: Report and iterate (Weeks 7-10).** Build three core reports in Pipedrive: expansion rate (deals in "Expansion Verified" / deals in "PLG Lead Qualified"), expansion revenue (sum of "Verified Expansion Amount"), and average expansion amount (expansion revenue / verified deal count). Create a dashboard with these metrics plus a funnel visualization of the expansion pipeline. Present the first month's data to leadership, clearly stating that this is a pilot metric subject to revision. After 30 days, run the retention check—compare your gross expansion rate to the net rate (excluding deals that churned within 90 days). Adjust your model to report the net rate going forward. Schedule a quarterly model audit where you sample 20% of expansion deals to verify data accuracy.

**Ongoing maintenance:** Each month, export your expansion data to a spreadsheet and run a cohort analysis by user signup month. Pipedrive's native reporting doesn't handle cohort analysis well, but a simple spreadsheet pivot table can show whether expansion rates are improving for newer cohorts. This takes about one hour per month. Also, review your "Pre-Handoff MRR" import process—if your billing system changes, update the import mapping immediately to avoid data gaps.

## Related questions

### How do you prevent sales reps from logging expansion deals in the wrong pipeline stage?

Create a Pipedrive workflow automation that checks the "Pre-Handoff MRR" field on the contact. If a deal is created for a contact with a non-zero value and the deal value exceeds that MRR, automatically move the deal to the expansion pipeline and alert the rep via email.

### What is the minimum Pipedrive plan needed for this expansion model?

You need at least the Advanced plan for workflow automations and custom reports. The Essential plan lacks these features. Growth or Enterprise plans provide additional automation limits and advanced reporting capabilities that simplify the model.

### How do you handle expansion from users who upgrade multiple times in one quarter?

Count only the net expansion from the first upgrade to the current state. Create a "Current MRR" field on the contact and update it with each upgrade. The expansion amount is the difference between the current MRR and the pre-handoff baseline, not the sum of individual upgrades.

### Can you track expansion rate by sales rep using this model?

Yes. Add a "Handoff Rep" field to the expansion pipeline stage and group your reports by that field. Pipedrive's reporting allows you to filter and segment by any custom field, so you can compare expansion rates across reps and identify coaching opportunities.

## FAQ

**What is the difference between expansion rate and expansion revenue in this model?**  
Expansion rate is the percentage of handoff-touched users who generate additional revenue, calculated as verified expansion deals divided by total PLG leads qualified. Expansion revenue is the total dollar amount of that additional revenue, summed from the "Verified Expansion Amount" field across all verified deals.

**How often should I update the "Pre-Handoff MRR" field?**  
Weekly during the pilot phase, then monthly once the model stabilizes. More frequent updates reduce the risk of stale baselines inflating your expansion rate. If your billing system supports API exports, automate this with a lightweight integration like Zapier rather than manual CSV imports.

**What happens if a user upgrades before the sales rep contacts them?**  
That upgrade is not expansion from handoff—it's organic growth. Exclude it from your expansion rate by checking the "Handoff Date" field. Only count upgrades that occur after the first sales touchpoint. If you can't determine the exact timing, exclude deals where the upgrade date is within 24 hours of the handoff trigger.

**Can I use this model for annual contract value (ACV) expansion instead of MRR?**  
Yes, but adjust your "Pre-Handoff Baseline" to ACV and normalize all expansion amounts to ACV. Be aware that ACV expansion rates tend to be lower than MRR rates because annual contracts have fewer upgrade opportunities within the contract term. Report both MRR and ACV expansion if your leadership team tracks different metrics.

**How do I handle expansion from users who were previously on a free plan?**  
Set the "Pre-Handoff MRR" baseline to $0 for free users. Their entire first payment counts as expansion revenue. This is accurate because the handoff converted them from a non-paying to a paying user. However, segment free-to-paid expansion separately from paid-to-upgraded expansion in your reports, as they have different economics.

**What if my sales team doesn't use Pipedrive for all handoff deals?**  
This is the most common failure mode. Enforce the model by making the expansion pipeline the default for any deal where the contact has a "PLG Source" field value (e.g., "Free Trial," "Freemium"). Use Pipedrive's email tracking to automatically create deals from sales emails to PLG users, ensuring every handoff is captured in the system.

## Sources

- https://support.pipedrive.com/en/article/custom-fields
- https://support.pipedrive.com/en/article/workflow-automation
- https://support.pipedrive.com/en/article/reports-and-dashboards
- https://www.productled.org/blog/product-led-growth-metrics
- https://openviewpartners.com/blog/expansion-revenue-benchmarks
- https://www.gartner.com/en/sales/insights/revenue-operations
- https://hbr.org/2023/01/a-better-way-to-measure-sales-performance
- https://www.pipedrive.com/en/plans

## Related on PULSE

- [How do you model expansion rate for inbound SDR on Pipedrive without another point solution ?](/knowledge/q10165)
- [How do you alert on GRR for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10395)
- [How do you model expansion rate for AE-led on Pipedrive without another point solution ?](/knowledge/q10375)
- [How do you measure pipeline coverage for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10315)
- [How do you model expansion rate for land-and-expand on Pipedrive without another point solution ?](/knowledge/q10305)
- [How do you audit sales cycle length for PLG-to-sales handoff on Pipedrive without another point solution ?](/knowledge/q10155)

Was this helpful?

Sources cited

Pulse RevOps — long-tail RevOps gapsPulse RevOps — long-tail RevOps gaps

Kory White

How do you model expansion rate for PLG-to-sales handoff on Pipedrive without another point solution ?

The outcome you should expect

What drives that outcome

Benchmarks and realistic ranges

Risks, edge cases, and failure modes

A practical rollout plan

Related questions

How do you prevent sales reps from logging expansion deals in the wrong pipeline stage?

What is the minimum Pipedrive plan needed for this expansion model?

How do you handle expansion from users who upgrade multiple times in one quarter?

Can you track expansion rate by sales rep using this model?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ