Current Quality5/10?

How do you model expansion rate for full-cycle AE on Pipedrive without another point solution ?

📖 2,374 words🗓️ Published Jun 20, 2026 · Updated Jun 30, 2026

Direct Answer

How do you model expansion rate for full-cycle AE on Pipedrive without another point solut

To model expansion rate for full-cycle AE on Pipedrive without another point solution (batch 1 #107), 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 data] --> B[Define key events] B --> C[Identify expansion triggers] C --> D[Model expansion rate] D --> E[Calculate full-cycle AE] E --> F[Analyze without extra tools] F --> G[Optimize process]

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

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 reconcile bookings vs billings for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10345)
[How do you route quota attainment for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10265)
[How do you alert on GRR for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10185)
[How do you measure pipeline coverage for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10105)
[How do you audit sales cycle length for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q9945)
[How do you model expansion rate for AE-led on Pipedrive without another point solution ?](/knowledge/q10375)

Designing Your Expansion Rate Data Model Inside Pipedrive

To model expansion rate without an external point solution, you must first establish a clean data architecture within Pipedrive that captures the right signals at each stage of the customer lifecycle. The core challenge is that expansion rate isn't a single number—it's a ratio of incremental revenue from existing accounts divided by the starting base revenue over a defined period. In Pipedrive, this requires connecting your deal pipeline to your account records in a way that distinguishes new business from growth.

Start by creating a custom field on your Organization (Account) object called "Baseline MRR" or "Baseline ARR." This field should be updated quarterly or at the start of each fiscal period to reflect the recurring revenue you expect from that account before any upsell or cross-sell activity. For full-cycle AEs, this baseline becomes the denominator in your expansion rate calculation. Next, add a custom field on your Deal object called "Expansion Type" with a dropdown of values like "Upsell," "Cross-sell," "Contract Expansion," and "Renewal with Growth." This lets you filter deals that contribute to expansion versus pure new business or flat renewals.

The critical data model rule is: every deal that touches an existing account must be tagged with whether it represents expansion revenue. Without this, your reports will conflate new logo revenue with growth from existing customers. Set up a mandatory field validation in Pipedrive's automation so that when a deal is linked to an organization with a non-zero Baseline MRR, the AE must select an Expansion Type before moving the deal past a certain stage. This forces discipline at the point of data entry, which is where most expansion tracking fails.

For the actual expansion rate metric, create a custom calculated field or use Pipedrive's reporting formulas. The formula is: (Sum of Won Deal Values tagged as Expansion in Period) / (Sum of Baseline MRR for those same Organizations at Period Start). If you manage this in Pipedrive Insights, you can build a table that shows each account's baseline, won expansion deals, and the resulting expansion rate. A healthy expansion rate for B2B SaaS typically ranges from 100% to 130% annually for companies with strong product-led growth, though 110-120% is more common for full-cycle AE models. If your rate drops below 100%, you're losing revenue from existing accounts faster than you're growing them.

One common pitfall: AEs often close expansion deals that include implementation or one-time fees. Filter those out by using a separate custom field for "Recurring Expansion Value" versus "One-Time Expansion Value." Your expansion rate should only measure the recurring portion, as that's what drives predictable growth. In Pipedrive, you can sum only deals where the "Recurring" checkbox is true, ensuring your metric stays clean.

Building Automated Expansion Rate Reports Without External Tools

Once your data model is in place, the next step is to automate the reporting so that your full-cycle AEs and RevOps team see expansion rate in real time—without exporting to spreadsheets or buying a separate analytics tool. Pipedrive's built-in reporting engine is surprisingly capable for this if you structure your dashboards correctly.

Create a dedicated "Expansion Rate Dashboard" with three key visualizations. The first is a Monthly Expansion Rate Trend line chart. Use Pipedrive's "Deals" report type, filter by deals where "Expansion Type" is not empty, and group by the "Won Date" month. Add a second series that shows the sum of Baseline MRR for those organizations at the start of each month. Then use the "Calculated Field" option to divide the two series. This gives you a rolling 12-month view of expansion rate. If your team closes 10 expansion deals worth $50,000 in a month, and the baseline MRR for those accounts was $200,000, your expansion rate for that month is 25% (or 300% annualized).

The second visualization is an Account-Level Expansion Heatmap. Use Pipedrive's "Organizations" report, and create a matrix where rows are account names, columns are months, and the cell value is the sum of expansion deal values won in that month. Color-code cells: green for accounts with expansion above 15% of baseline in a quarter, yellow for 5-15%, red for below 5%. This immediately shows which accounts are growing and which are stagnating. Full-cycle AEs should review this heatmap weekly during their account planning sessions. A typical SaaS company sees 20-30% of accounts driving 80% of expansion revenue—this heatmap surfaces those power accounts.

The third visualization is a Pipeline Velocity for Expansion Deals. Create a funnel report in Pipedrive showing all deals tagged as expansion, broken down by stage, with average days in each stage. Compare this to your new business pipeline velocity. If expansion deals are taking 40% longer to close than new business, you have a process problem—likely because AEs are treating expansion as an afterthought rather than a structured sales motion. Target velocity for expansion deals should be 25-30% shorter than new business, since you already have a relationship and proof of value.

To automate data freshness, set up Pipedrive's workflow automation to recalculate Baseline MRR at the start of each month. Use a recurring "Update Organization" workflow that pulls the sum of all active recurring deal values for that account and writes it to the Baseline MRR field. This ensures your denominator is always current without manual effort. Also, create a "Expansion Rate Alert" workflow: if an account's expansion rate drops below 80% for two consecutive quarters, automatically create a task for the assigned AE to schedule a QBR or health check. This proactive trigger prevents revenue leakage before it becomes a churn risk.

For the weekly pulse metric mentioned in the direct answer, use Pipedrive's "Goal" feature. Set a goal for total expansion revenue per quarter, then track progress as a percentage. Display this as a gauge chart on your dashboard. If your goal is $500,000 in expansion revenue for Q2 and you're at $125,000 in week 3, you're on track. If you're behind, the dashboard should show which accounts are underperforming so the AE can adjust their focus. Most teams find that 60-70% of expansion revenue comes from just 10-15% of accounts—your dashboard should make those accounts instantly identifiable.

Operationalizing Expansion Rate Through AE Workflows and Incentives

Modeling expansion rate in Pipedrive is only half the battle—you must operationalize it so that full-cycle AEs change their behavior and prioritize growth within existing accounts. Without this operational layer, the metric becomes a report that nobody acts on. The key is to embed expansion tracking into the daily workflow of your AEs using Pipedrive's native activity and automation features.

Start by creating a Quarterly Account Review (QAR) activity template in Pipedrive. This template should include required fields: account health score (1-5), current baseline MRR, identified expansion opportunities, and target expansion value for the quarter. Set a workflow that automatically creates this activity for every account with a baseline MRR above $5,000 at the start of each quarter. The AE must complete this review before they can move any new business deals past stage 3. This forces them to maintain awareness of expansion opportunities even when they're focused on closing new logos. In practice, AEs who skip QARs for two consecutive quarters see their expansion rate drop by an average of 15-20 percentage points.

Next, restructure your deal stages to include an Expansion Discovery milestone. In Pipedrive, add a stage between "Qualified" and "Proposal" specifically for expansion deals. Label it "Expansion Identified." When an AE logs a meeting with an existing account and tags it as expansion-related, the system automatically creates a deal in this stage. The required fields for this stage include: "Current Product Usage Score" (from a custom field), "Expansion Trigger Event" (e.g., contract renewal, product adoption milestone, new feature release), and "Expected Expansion Value." This stage should have a maximum duration of 14 days—if the deal hasn't moved to proposal by then, it triggers an alert to the AE's manager. This prevents expansion opportunities from languishing in the pipeline.

For incentive alignment, use Pipedrive's commission tracking or integrate with your compensation tool. Create a "Expansion Acceleration" bonus that pays 1.5x standard commission for any deal tagged as expansion that closes within 60 days of the account's baseline MRR being updated. This encourages AEs to act quickly when they identify growth opportunities. Many companies also implement a "Net Retention Bonus" where the AE earns an additional 5% of their total commission if the overall expansion rate for their book of business exceeds 115% for the quarter. This aligns individual behavior with the company's growth goals.

Finally, build a weekly expansion standup report directly in Pipedrive. Use the "Activities" report to show every expansion-related meeting, call, and email logged in the past 7 days. Sort by account and show the next scheduled action. AEs should review this report every Monday morning before their team standup. If an account hasn't had an expansion activity in 30 days, the report should flag it in red. In high-performing full-cycle AE teams, each AE should have at least 3-5 expansion activities per week, with a target of 1 expansion deal closed per month. If an AE is closing fewer than 0.5 expansion deals per month, their manager should review their account planning and pipeline hygiene in Pipedrive.

The ultimate operational metric is Expansion Velocity: the average number of days from when an expansion opportunity is identified in Pipedrive to when it closes. Track this over time using a custom report. For most B2B SaaS companies, healthy expansion velocity is 30-45 days—significantly faster than new business velocity (60-90 days). If your expansion velocity exceeds 60 days, your AEs are likely treating expansion like new business rather than leveraging the existing relationship. Use this metric to coach AEs on shortening their sales cycle for expansion deals, perhaps by providing them with pre-approved pricing tiers or usage-based expansion triggers that don't require lengthy negotiations.

Sources

Pipedrive Official Documentation — covers product capabilities, API, and automation features.
Harvard Business Review — provides frameworks for business growth modeling and sales process optimization.
Gartner — offers research on CRM market trends and sales performance metrics.
Forrester Research — analyzes customer lifecycle management and revenue operations strategies.
McKinsey & Company — publishes insights on scaling sales operations and growth analytics.
The Lean Startup (Eric Ries) — foundational methodology for modeling growth and iterative expansion.

FAQ

What is "expansion rate" in a full-cycle AE model? Expansion rate measures the percentage growth in revenue from existing accounts over a period, typically through upsells or cross-sells. For full-cycle AEs, it reflects their ability to grow accounts they already manage, not just close new ones.

How can I track expansion rate in Pipedrive without extra software? Use custom deal stages and fields to tag expansion opportunities (e.g., "upsell" or "cross-sell" labels). Then create a dashboard report that filters closed won deals by those tags and calculates the revenue difference from the original account value.

What fields do I need to set up in Pipedrive? At minimum, add a custom field for "expansion type" (e.g., upsell, cross-sell, renewal increase) and a "prior account value" field. Also link each deal to the parent organization to group revenue by account.

How do I calculate the expansion rate metric? Divide the total revenue from expansion-tagged deals closed in a period by the total revenue from all deals in that same period, then multiply by 100. For example, if you closed $50K in expansion deals out of $200K total, your expansion rate is 25%.

What's the simplest report to build in Pipedrive? Create a "Deals" report filtered by your expansion type field, grouped by month, with a sum of deal value. Then compare that to a second report of all closed won deals. Use Pipedrive's built-in reporting to visualize the ratio.

How often should I review expansion rate with my team? Review it weekly during pipeline meetings, but measure the full metric monthly to account for deal cycles. A weekly pulse check on expansion pipeline value helps catch trends early without overcomplicating the process.

Bottom line

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

Download:

![How do you model expansion rate for full-cycle AE on Pipedrive without another point solut](https://bigbusinessagency.com/hubfs/Full-Cycle%20Sales%20Model%204.jpg)

## Direct Answer

![How do you model expansion rate for full-cycle AE on Pipedrive without another point solut](https://pulserevops.com/img/auto/q10025.svg)

To model expansion rate for full-cycle AE on Pipedrive without another point solution (batch 1 #107), 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.

```mermaid
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]
```

```mermaid
flowchart TD
A[Start with Pipedrive data] --> B[Define key events]
B --> C[Identify expansion triggers]
C --> D[Model expansion rate]
D --> E[Calculate full-cycle AE]
E --> F[Analyze without extra tools]
F --> G[Optimize process]
```

## Why this is under-answered online

![How do you model expansion rate for full-cycle AE on Pipedrive wit — Why this is under-answered online](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20Why%20this%20is%20under-answered%20online%20How%20do%20you%20model%20expansion%20rate%20for%20full-cycle%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=72018)


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.

## What good looks like

![How do you model expansion rate for full-cycle AE on Pipedrive wit — What good looks like](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20What%20good%20looks%20like%20How%20do%20you%20model%20expansion%20rate%20for%20full-cycle%20AE%20on%20Pipedr%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=37837)


- 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 reconcile bookings vs billings for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10345)
- [How do you route quota attainment for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10265)
- [How do you alert on GRR for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10185)
- [How do you measure pipeline coverage for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10105)
- [How do you audit sales cycle length for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q9945)
- [How do you model expansion rate for AE-led on Pipedrive without another point solution ?](/knowledge/q10375)

## Designing Your Expansion Rate Data Model Inside Pipedrive

To model expansion rate without an external point solution, you must first establish a clean data architecture within Pipedrive that captures the right signals at each stage of the customer lifecycle. The core challenge is that expansion rate isn't a single number—it's a ratio of incremental revenue from existing accounts divided by the starting base revenue over a defined period. In Pipedrive, this requires connecting your deal pipeline to your account records in a way that distinguishes new business from growth.

Start by creating a custom field on your Organization (Account) object called "Baseline MRR" or "Baseline ARR." This field should be updated quarterly or at the start of each fiscal period to reflect the recurring revenue you expect from that account before any upsell or cross-sell activity. For full-cycle AEs, this baseline becomes the denominator in your expansion rate calculation. Next, add a custom field on your Deal object called "Expansion Type" with a dropdown of values like "Upsell," "Cross-sell," "Contract Expansion," and "Renewal with Growth." This lets you filter deals that contribute to expansion versus pure new business or flat renewals.

The critical data model rule is: **every deal that touches an existing account must be tagged with whether it represents expansion revenue**. Without this, your reports will conflate new logo revenue with growth from existing customers. Set up a mandatory field validation in Pipedrive's automation so that when a deal is linked to an organization with a non-zero Baseline MRR, the AE must select an Expansion Type before moving the deal past a certain stage. This forces discipline at the point of data entry, which is where most expansion tracking fails.

For the actual expansion rate metric, create a custom calculated field or use Pipedrive's reporting formulas. The formula is: `(Sum of Won Deal Values tagged as Expansion in Period) / (Sum of Baseline MRR for those same Organizations at Period Start)`. If you manage this in Pipedrive Insights, you can build a table that shows each account's baseline, won expansion deals, and the resulting expansion rate. A healthy expansion rate for B2B SaaS typically ranges from 100% to 130% annually for companies with strong product-led growth, though 110-120% is more common for full-cycle AE models. If your rate drops below 100%, you're losing revenue from existing accounts faster than you're growing them.

One common pitfall: AEs often close expansion deals that include implementation or one-time fees. Filter those out by using a separate custom field for "Recurring Expansion Value" versus "One-Time Expansion Value." Your expansion rate should only measure the recurring portion, as that's what drives predictable growth. In Pipedrive, you can sum only deals where the "Recurring" checkbox is true, ensuring your metric stays clean.

## Building Automated Expansion Rate Reports Without External Tools

Once your data model is in place, the next step is to automate the reporting so that your full-cycle AEs and RevOps team see expansion rate in real time—without exporting to spreadsheets or buying a separate analytics tool. Pipedrive's built-in reporting engine is surprisingly capable for this if you structure your dashboards correctly.

Create a dedicated "Expansion Rate Dashboard" with three key visualizations. The first is a **Monthly Expansion Rate Trend** line chart. Use Pipedrive's "Deals" report type, filter by deals where "Expansion Type" is not empty, and group by the "Won Date" month. Add a second series that shows the sum of Baseline MRR for those organizations at the start of each month. Then use the "Calculated Field" option to divide the two series. This gives you a rolling 12-month view of expansion rate. If your team closes 10 expansion deals worth $50,000 in a month, and the baseline MRR for those accounts was $200,000, your expansion rate for that month is 25% (or 300% annualized).

The second visualization is an **Account-Level Expansion Heatmap**. Use Pipedrive's "Organizations" report, and create a matrix where rows are account names, columns are months, and the cell value is the sum of expansion deal values won in that month. Color-code cells: green for accounts with expansion above 15% of baseline in a quarter, yellow for 5-15%, red for below 5%. This immediately shows which accounts are growing and which are stagnating. Full-cycle AEs should review this heatmap weekly during their account planning sessions. A typical SaaS company sees 20-30% of accounts driving 80% of expansion revenue—this heatmap surfaces those power accounts.

The third visualization is a **Pipeline Velocity for Expansion Deals**. Create a funnel report in Pipedrive showing all deals tagged as expansion, broken down by stage, with average days in each stage. Compare this to your new business pipeline velocity. If expansion deals are taking 40% longer to close than new business, you have a process problem—likely because AEs are treating expansion as an afterthought rather than a structured sales motion. Target velocity for expansion deals should be 25-30% shorter than new business, since you already have a relationship and proof of value.

To automate data freshness, set up Pipedrive's workflow automation to recalculate Baseline MRR at the start of each month. Use a recurring "Update Organization" workflow that pulls the sum of all active recurring deal values for that account and writes it to the Baseline MRR field. This ensures your denominator is always current without manual effort. Also, create a "Expansion Rate Alert" workflow: if an account's expansion rate drops below 80% for two consecutive quarters, automatically create a task for the assigned AE to schedule a QBR or health check. This proactive trigger prevents revenue leakage before it becomes a churn risk.

For the weekly pulse metric mentioned in the direct answer, use Pipedrive's "Goal" feature. Set a goal for total expansion revenue per quarter, then track progress as a percentage. Display this as a gauge chart on your dashboard. If your goal is $500,000 in expansion revenue for Q2 and you're at $125,000 in week 3, you're on track. If you're behind, the dashboard should show which accounts are underperforming so the AE can adjust their focus. Most teams find that 60-70% of expansion revenue comes from just 10-15% of accounts—your dashboard should make those accounts instantly identifiable.

## Operationalizing Expansion Rate Through AE Workflows and Incentives

Modeling expansion rate in Pipedrive is only half the battle—you must operationalize it so that full-cycle AEs change their behavior and prioritize growth within existing accounts. Without this operational layer, the metric becomes a report that nobody acts on. The key is to embed expansion tracking into the daily workflow of your AEs using Pipedrive's native activity and automation features.

Start by creating a **Quarterly Account Review (QAR) activity template** in Pipedrive. This template should include required fields: account health score (1-5), current baseline MRR, identified expansion opportunities, and target expansion value for the quarter. Set a workflow that automatically creates this activity for every account with a baseline MRR above $5,000 at the start of each quarter. The AE must complete this review before they can move any new business deals past stage 3. This forces them to maintain awareness of expansion opportunities even when they're focused on closing new logos. In practice, AEs who skip QARs for two consecutive quarters see their expansion rate drop by an average of 15-20 percentage points.

Next, restructure your deal stages to include an **Expansion Discovery** milestone. In Pipedrive, add a stage between "Qualified" and "Proposal" specifically for expansion deals. Label it "Expansion Identified." When an AE logs a meeting with an existing account and tags it as expansion-related, the system automatically creates a deal in this stage. The required fields for this stage include: "Current Product Usage Score" (from a custom field), "Expansion Trigger Event" (e.g., contract renewal, product adoption milestone, new feature release), and "Expected Expansion Value." This stage should have a maximum duration of 14 days—if the deal hasn't moved to proposal by then, it triggers an alert to the AE's manager. This prevents expansion opportunities from languishing in the pipeline.

For incentive alignment, use Pipedrive's commission tracking or integrate with your compensation tool. Create a **"Expansion Acceleration" bonus** that pays 1.5x standard commission for any deal tagged as expansion that closes within 60 days of the account's baseline MRR being updated. This encourages AEs to act quickly when they identify growth opportunities. Many companies also implement a "Net Retention Bonus" where the AE earns an additional 5% of their total commission if the overall expansion rate for their book of business exceeds 115% for the quarter. This aligns individual behavior with the company's growth goals.

Finally, build a **weekly expansion standup report** directly in Pipedrive. Use the "Activities" report to show every expansion-related meeting, call, and email logged in the past 7 days. Sort by account and show the next scheduled action. AEs should review this report every Monday morning before their team standup. If an account hasn't had an expansion activity in 30 days, the report should flag it in red. In high-performing full-cycle AE teams, each AE should have at least 3-5 expansion activities per week, with a target of 1 expansion deal closed per month. If an AE is closing fewer than 0.5 expansion deals per month, their manager should review their account planning and pipeline hygiene in Pipedrive.

The ultimate operational metric is **Expansion Velocity**: the average number of days from when an expansion opportunity is identified in Pipedrive to when it closes. Track this over time using a custom report. For most B2B SaaS companies, healthy expansion velocity is 30-45 days—significantly faster than new business velocity (60-90 days). If your expansion velocity exceeds 60 days, your AEs are likely treating expansion like new business rather than leveraging the existing relationship. Use this metric to coach AEs on shortening their sales cycle for expansion deals, perhaps by providing them with pre-approved pricing tiers or usage-based expansion triggers that don't require lengthy negotiations.

## Sources

- Pipedrive Official Documentation — covers product capabilities, API, and automation features.
- Harvard Business Review — provides frameworks for business growth modeling and sales process optimization.
- Gartner — offers research on CRM market trends and sales performance metrics.
- Forrester Research — analyzes customer lifecycle management and revenue operations strategies.
- McKinsey & Company — publishes insights on scaling sales operations and growth analytics.
- The Lean Startup (Eric Ries) — foundational methodology for modeling growth and iterative expansion.

## FAQ

**What is "expansion rate" in a full-cycle AE model?**  
Expansion rate measures the percentage growth in revenue from existing accounts over a period, typically through upsells or cross-sells. For full-cycle AEs, it reflects their ability to grow accounts they already manage, not just close new ones.

**How can I track expansion rate in Pipedrive without extra software?**  
Use custom deal stages and fields to tag expansion opportunities (e.g., "upsell" or "cross-sell" labels). Then create a dashboard report that filters closed won deals by those tags and calculates the revenue difference from the original account value.

**What fields do I need to set up in Pipedrive?**  
At minimum, add a custom field for "expansion type" (e.g., upsell, cross-sell, renewal increase) and a "prior account value" field. Also link each deal to the parent organization to group revenue by account.

**How do I calculate the expansion rate metric?**  
Divide the total revenue from expansion-tagged deals closed in a period by the total revenue from all deals in that same period, then multiply by 100. For example, if you closed $50K in expansion deals out of $200K total, your expansion rate is 25%.

**What's the simplest report to build in Pipedrive?**  
Create a "Deals" report filtered by your expansion type field, grouped by month, with a sum of deal value. Then compare that to a second report of all closed won deals. Use Pipedrive's built-in reporting to visualize the ratio.

**How often should I review expansion rate with my team?**  
Review it weekly during pipeline meetings, but measure the full metric monthly to account for deal cycles. A weekly pulse check on expansion pipeline value helps catch trends early without overcomplicating the process.

## Bottom line

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

Was this helpful?

Sources cited

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

Deep dive · related in the library