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

What it is and why it matters

Expansion rate is the ratio of incremental revenue generated from existing accounts to the revenue base those accounts started the period with. For a full-cycle AE — someone who both closes new logos and manages the account afterward — this number is the clearest signal of whether their book of business is actually growing or just holding steady on renewals. Most CRMs, Pipedrive included, don't ship this metric out of the box, which is why teams reach for a bolt-on analytics tool. That instinct is usually wrong: Pipedrive's Organization object, Deal custom fields, and Insights reporting engine already contain everything needed to build the calculation, provided the underlying data is tagged consistently.

The reason this matters beyond a dashboard vanity number is that expansion rate is a leading indicator of net revenue retention, which board decks and investors weight heavily. A full-cycle AE who closes new business but neglects account growth will show flat or declining expansion rate even while their new-logo numbers look healthy. RevOps teams that fail to instrument this in the CRM of record end up with two competing truths: what the CRM says and what a spreadsheet says, and the spreadsheet almost always wins politically because it's more visible, even when it's less accurate. Building the metric inside Pipedrive keeps a single source of truth and avoids the maintenance burden, license cost, and data-sync fragility of a second system. It also means the AE sees the number in the same tool they work deals in every day, rather than in a report someone emails out monthly.

The step-by-step process (mermaid)

Building this without another point solution is a five-step exercise: data model, tagging discipline, calculation, automation, and review cadence.

First, add two custom fields to the Organization object: "Baseline MRR" (a currency field, updated quarterly) and "Baseline Period Start" (a date field marking when that baseline was set). This baseline is the denominator for every expansion calculation tied to that account. Second, add an "Expansion Type" dropdown field to the Deal object with values like Upsell, Cross-sell, Contract Expansion, and Renewal with Growth, plus a boolean "Recurring" checkbox to separate one-time fees from ongoing revenue. Third, enforce tagging at the point of entry: a Pipedrive automation rule that blocks a deal from advancing past a given stage unless Expansion Type is populated whenever the linked Organization has a non-zero Baseline MRR. Fourth, build the calculation itself in Insights: a custom report summing won deal value where Expansion Type is set and Recurring is true, divided by the sum of Baseline MRR for those same organizations at period start. Fifth, wire a recurring workflow that refreshes Baseline MRR automatically at the start of each month or quarter by summing active recurring deal value per account, so the denominator never goes stale.

Once these five pieces exist, the metric updates itself every time a deal closes — no manual export, no reconciliation step, no second login for the AE or RevOps to check.

Costs, timelines, and typical ranges

Because this build uses only native Pipedrive fields, automations, and Insights, there is no incremental software cost beyond the Pipedrive plan tier that includes custom fields and Insights reporting (typically the Advanced plan or higher). The time cost is what you're really budgeting: a RevOps admin familiar with Pipedrive can stand up the field structure and one dashboard in a single working session, roughly 4-6 hours, including testing the automation rule against a handful of real deals. Getting the automated Baseline MRR refresh workflow running correctly typically adds another 2-3 hours, mostly spent validating that the summation logic only pulls active, recurring deal value and doesn't double-count renewals still open in the pipeline.

The rollout timeline for full adoption across an AE team runs longer than the technical build. Expect one to two full quarters before the expansion rate number is trustworthy, because Baseline MRR has to be backfilled for every existing account and AEs need at least one full tagging cycle to build the habit of setting Expansion Type before advancing a deal. During that ramp, expect a data-quality tax: some percentage of deals — often 15-25% in the first month — will be tagged incorrectly or left blank, requiring RevOps to spot-check and correct them manually until the stage-gate automation catches everything.

On the metric itself, typical ranges are useful for sanity-checking your build. For B2B SaaS companies running a full-cycle AE model, a healthy annual expansion rate sits between 100% and 130%; company operating in the 110-120% range are generally considered strong performers without needing product-led growth motion to carry the number. Anything below 100% means existing accounts are shrinking faster than they're growing, which should trigger an immediate review of churn risk. Expansion deal velocity — time from opportunity identification to close — should run 25-30% faster than new-business velocity, typically 30-45 days versus 60-90 days for net-new logos, because the AE already has the relationship and proof of value in hand.

Where teams get it wrong

The single most common failure is treating Baseline MRR as a set-once field instead of a maintained one. Teams populate it at rollout, get an accurate expansion rate for one quarter, then let it go stale as accounts grow or shrink without anyone updating the baseline. Six months later the expansion rate number is meaningless because the denominator no longer reflects reality. The fix is the automated monthly or quarterly refresh workflow described above — treat Baseline MRR like a calculated field that a human never edits directly, only a workflow does.

A second common mistake is lumping one-time fees, implementation charges, or professional services revenue into the expansion figure. A $30,000 upsell that includes $10,000 of onboarding services is not $30,000 of recurring expansion — it's $20,000. Without a separate Recurring checkbox or field to filter on, the resulting expansion rate is inflated and gives leadership a false sense of account health. Every dollar counted toward expansion should be revenue that will recur in the next billing cycle without additional AE effort.

A third mistake is skipping the stage-gate enforcement and relying on AEs to remember to tag deals voluntarily. Voluntary tagging discipline decays within a few weeks of rollout; without a hard block in the pipeline, expansion tagging rates typically fall below 50% by the second month, which corrupts the entire calculation. The automation that prevents a deal from advancing without an Expansion Type selected is not optional — it's the mechanism that makes the rest of the build meaningful.

A fourth mistake, more subtle, is conflating renewal-without-growth with expansion. A flat renewal at the same contract value is not expansion; it should be excluded from both numerator and denominator changes. Teams that count every renewal touch as an "expansion opportunity" dilute the AE's attention away from accounts that actually have growth potential and toward busywork that inflates activity metrics without moving revenue.

Decision framework: when to choose what (mermaid)

Not every team should build this natively in Pipedrive, and the decision hinges on scale, complexity, and how the number will be used downstream. If your account base is under roughly 200 organizations and finance doesn't require audit-trail-grade revenue recognition, the native approach described here is almost always the right call — it's fast, free beyond the existing Pipedrive license, and keeps the AE workflow in one tool. If your account count is larger, or if you need cohort-based retention analysis, multi-currency normalization, or integration with a billing system for automatic MRR sync, a dedicated revenue analytics tool starts to earn its cost, because Pipedrive's Insights engine will start to strain under the report complexity required.

The other deciding factor is who consumes the number. If expansion rate is primarily an operational metric for AEs and their managers to act on weekly, native Pipedrive is sufficient and arguably better, since it lives where the AE already works. If expansion rate needs to feed a board deck with GAAP-adjacent revenue recognition rules, tie into a finance system of record, or reconcile against actual invoiced billing rather than deal value, that's a strong signal you need a system built for financial reporting rather than a CRM's reporting layer stretched past its intended use.

Most full-cycle AE teams operating on Pipedrive fall into the left branch of this framework, which is why the native build is the default recommendation rather than the exception.

Related questions

What's the difference between expansion rate and net revenue retention?

Expansion rate measures growth from existing accounts against a baseline period; net revenue retention (NRR) additionally nets out churn and contraction from the same base. Expansion rate is a component of NRR, not a replacement for it — track both if churn is material.

Can Pipedrive automations calculate expansion rate directly, or only report on it?

Automations in Pipedrive handle tagging, field updates, and alerts, but the actual ratio calculation happens in Insights reports using calculated fields, not in the automation engine itself.

How do I backfill Baseline MRR for accounts that already exist?

Export active recurring deal value per organization as of a chosen start date, then bulk-import it into the Baseline MRR field using Pipedrive's import tool, tagging that date as the baseline period start.

Should expansion deals go through the same pipeline as new business?

No — use a separate deal pipeline or at minimum a distinct "Expansion Identified" stage, since expansion deals have different required fields, shorter expected velocity, and different manager review triggers than new-logo deals.

FAQ

Does this require a Pipedrive plan upgrade? Custom fields and multiple pipelines are available on most paid Pipedrive tiers, but full Insights reporting with calculated fields typically requires the Advanced plan or higher — check current plan feature breakdowns before committing to the build.

What happens if an AE forgets to update Baseline MRR manually? That's exactly why the refresh should be automated through a recurring workflow rather than left to manual entry; manual baseline maintenance is the most common point of data decay in this model.

Can I track expansion rate per AE instead of per account? Yes — since deals and organizations are both owned by an AE in Pipedrive, filter your Insights report by deal owner to roll the same calculation up to individual AE performance rather than only account-level views.

Is 100% expansion rate good or bad? 100% means existing accounts neither grew nor shrank in aggregate — flat, not bad, but not the 110-130% range that indicates a healthy growth motion for most B2B SaaS full-cycle AE teams.

How do I avoid double-counting a deal as both new business and expansion? Gate it at the data model level: a deal can only be tagged with an Expansion Type if it's linked to an organization with an existing non-zero Baseline MRR, which structurally prevents a net-new logo from being miscounted as expansion.

Do one-time services fees ever belong in the expansion number? No — keep them in a separate "One-Time Expansion Value" field for visibility, but exclude them from the recurring expansion rate calculation since they don't represent repeating revenue growth.

Sources

• https://www.pipedrive.com/en/blog
• https://developers.pipedrive.com/docs/api/v1
• https://hbr.org/topic/subject/sales
• https://www.gartner.com/en/sales
• https://www.forrester.com/blogs/category/customer-lifecycle-management/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.saastr.com/net-revenue-retention/

Related on PULSE

• How do you reconcile bookings vs billings for full-cycle AE on Pipedrive without another point solution ?
• How do you route quota attainment for full-cycle AE on Pipedrive without another point solution ?
• How do you alert on GRR for full-cycle AE on Pipedrive without another point solution ?
• How do you measure pipeline coverage for full-cycle AE on Pipedrive without another point solution ?
• How do you audit sales cycle length for full-cycle AE on Pipedrive without another point solution ?
• How do you model expansion rate for AE-led on Pipedrive without another point solution ?