How do you route quota attainment for land-and-expand on Pipedrive without another point solution ?
To route quota attainment for land-and-expand on Pipedrive without another point solution (batch 1 #67), 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 route quota attainment for inbound SDR on Pipedrive without another point solution ?](/knowledge/q10405)
- [How do you route quota attainment for usage-based pricing on Pipedrive without another point solution ?](/knowledge/q10335)
- [How do you route quota attainment for full-cycle AE on Pipedrive without another point solution ?](/knowledge/q10265)
- [How do you route quota attainment for partner-sourced pipeline on Pipedrive without another point solution ?](/knowledge/q10195)
- [How do you route quota attainment for channel co-sell on Pipedrive without another point solution ?](/knowledge/q10125)
- [How do you route quota attainment for AE-led on Pipedrive without another point solution ?](/knowledge/q10055)
Mapping the Land-and-Expand Quota to Pipedrive’s Native Deal Stages and Pipeline Logic
Most sales teams treat land-and-expand as a single-stage pipeline, which creates a blind spot for quota routing. In Pipedrive, you can solve this without a point solution by restructuring your deal stages to reflect the two distinct revenue events: the initial “land” (first purchase) and the subsequent “expand” (upsell/cross-sell within the same account). The key is to use Pipedrive’s custom deal stages and probability fields to route attainment calculations automatically.
Start by creating a dedicated “Land-and-Expand” pipeline (or a separate pipeline per segment if you have multiple product lines). Define stages that explicitly separate the land and expand phases. For example:
- Stage 1: Prospecting (land target identified)
- Stage 2: Land Negotiation (first deal in progress)
- Stage 3: Land Won (first deal closed)
- Stage 4: Expand Discovery (post-land account health check)
- Stage 5: Expand Proposal (upsell/cross-sell in motion)
- Stage 6: Expand Won (expansion deal closed)
Now, for quota routing, you need to assign attainment credit based on the stage the deal is in. In Pipedrive, you can use the “Deal Value” field combined with a custom “Revenue Type” field (dropdown: “Land” or “Expand”). Then, create a calculated field or use Pipedrive’s built-in “Weighted Revenue” feature to split the deal value into two virtual buckets. For instance, if a deal is in Stage 3 (Land Won), the full value counts toward land quota. If it moves to Stage 4 or beyond, the incremental value (expand portion) counts toward expand quota.
To automate this routing without a point solution, set up Pipedrive workflows (automations) that trigger when a deal moves from Stage 3 to Stage 4. The workflow can:
- Duplicate the original deal (to preserve the land record) or create a linked deal.
- Assign the new deal to the expand owner (could be the same rep or a different team).
- Set the “Revenue Type” field to “Expand” automatically.
- Apply a custom probability (e.g., 50% for expand discovery vs. 80% for land won) so that weighted pipeline reflects realistic attainment.
For quota attainment reporting, use Pipedrive’s “Reports” dashboard. Create two separate reports:
- Land Quota Attainment: Sum of deal values where “Revenue Type” = “Land” and stage is “Land Won” or later.
- Expand Quota Attainment: Sum of deal values where “Revenue Type” = “Expand” and stage is “Expand Won” or later.
You can also layer in a “Quota Period” custom field (monthly, quarterly) to slice by time. This approach keeps everything in Pipedrive, avoids spreadsheets, and gives you a single source of truth for both land and expand attainment — no third-party tool needed.
Designing a Custom “Account Health Score” Field to Trigger Expand Quota Routing
A common failure point in land-and-expand quota routing is timing: when does a “land” deal become eligible for “expand” credit? Without a point solution, you can build a simple account health score directly in Pipedrive using custom fields and automation. This score acts as the gatekeeper for routing expand quota to reps.
Create a custom field group on the Organization (account) level called “Account Health.” Add these fields:
- Time Since Last Land: Number field (days). Update automatically via workflow when a land deal closes.
- Product Adoption Score: Single-select dropdown (Low, Medium, High). Manually set by CS or sales ops based on usage data (even if you pull from a CSV quarterly).
- Contract Renewal Date: Date field. If renewal is within 90 days, score drops.
- Support Ticket Count: Number field (updated monthly via CSV import or manual entry).
- Expansion Eligibility: Formula field that calculates “Eligible” if Time Since Last Land > 30 days AND Product Adoption = High AND Support Tickets < 3. Otherwise, “Not Eligible.”
Now, route quota attainment based on this health score. Set up a Pipedrive workflow that checks the “Expansion Eligibility” field whenever a deal is moved into the “Expand Discovery” stage. If the field says “Not Eligible,” the workflow can:
- Prevent the deal from moving forward (use a required field validation).
- Send an internal notification to the RevOps team to review.
- Automatically reassign the deal back to the land owner for nurturing.
For quota routing itself, use the health score to determine which rep gets credit. For example, if the account health is “High,” the expand deal automatically routes to an enterprise expansion rep. If “Medium,” it goes to a mid-market rep. If “Low,” it stays with the original land rep (who may need to re-engage). You can implement this with Pipedrive’s “Automation” feature: when a deal enters the “Expand Discovery” stage, check the “Expansion Eligibility” field and then use a “Conditional Action” to change the “Owner” field to the appropriate rep based on the score.
To avoid manual data entry, schedule a monthly CSV import (Pipedrive’s native import tool) that updates the “Support Ticket Count” and “Product Adoption Score” fields. Or, if you have a basic integration with a support tool like Zendesk (via Zapier or Pipedrive’s built-in connector), you can pull ticket counts automatically. The goal is to keep the health score dynamic enough to trigger the right routing without adding a point solution.
Finally, create a dashboard widget that shows “Accounts Eligible for Expansion” vs. “Accounts Not Eligible.” This gives your sales team a clear view of where to focus expand efforts — and ensures quota attainment is only routed for truly ready accounts, preventing false credit and pipeline inflation.
Building a Quota Attainment Roll-Up with Pipedrive’s Custom Reporting and Goal Tracking
The final piece of routing quota attainment without a point solution is the roll-up: how do you consolidate land and expand attainment into a single, accurate view for each rep or team? Pipedrive’s native “Goals” feature, combined with custom reporting, can do this — but only if you structure your data correctly.
Start by creating two separate “Goal” types in Pipedrive under “Settings” > “Goals”:
- Goal 1: Land Quota — Based on “Deal Value” where “Revenue Type” = “Land” and stage = “Land Won” (or later). Set the goal period (monthly/quarterly) and target amount.
- Goal 2: Expand Quota — Based on “Deal Value” where “Revenue Type” = “Expand” and stage = “Expand Won” (or later). Set the same period and target.
Now, assign these goals to the appropriate users. If a rep handles both land and expand, they get both goals. If the roles are split (e.g., land reps vs. expand reps), assign only the relevant goal. Pipedrive will automatically calculate attainment as a percentage of the goal based on closed deals.
For a more granular roll-up, use Pipedrive’s “Custom Reports” builder. Create a report with the following dimensions and metrics:
- Dimensions: User (Owner), Revenue Type (Land vs. Expand), Month/Quarter.
- Metrics: Sum of Deal Value (for closed won deals), Count of Deals, Average Deal Size.
- Filters: Stage = “Land Won” OR “Expand Won”; Date range = current period.
This report gives you a side-by-side view of land and expand attainment per rep. To route the quota attainment to leadership, schedule this report to be emailed weekly (Pipedrive’s native scheduling feature) to the CRO or sales ops team.
The trick to making this work without a point solution is consistency in data entry. Train your team to always set the “Revenue Type” field when a deal is created. Use Pipedrive’s “Required Fields” setting on the deal creation form to enforce this. Also, use “Pipeline” level permissions to prevent reps from accidentally moving deals between land and expand stages without proper routing.
For advanced use cases (e.g., quota credit splits between multiple reps on the same deal), use Pipedrive’s “Participants” feature. Add both the land rep and the expand rep as participants on the deal, then use a custom “Credit Split %” field (number, 0-100) to allocate attainment. In your report, you can then multiply the deal value by the credit split percentage to get each rep’s attainment. This avoids double-counting and keeps the math accurate.
Finally, create a “Quota Attainment Dashboard” with three widgets:
- Land Attainment by Rep (bar chart, filtered by “Revenue Type” = “Land”).
- Expand Attainment by Rep (bar chart, filtered by “Revenue Type” = “Expand”).
- Combined Attainment vs. Target (table showing each rep’s land + expand total, goal, and % attainment).
This dashboard becomes your single source of truth for quota routing — no spreadsheets, no point solutions, just Pipedrive’s native capabilities. With the fields, workflows, and reports described here, you can route land-and-expand quota attainment accurately and efficiently, even as your team scales.
Sources
- Pipedrive Official Documentation — product features, settings, and native quota management capabilities.
- Gartner — market analysis and best practices for sales quota design and territory management.
- Harvard Business Review — research articles on sales compensation, land-and-expand strategies, and CRM effectiveness.
- Salesforce Blog — insights on quota routing and expansion tactics within CRM ecosystems.
- Forrester Research — reports on sales performance management and CRM platform limitations.
- LinkedIn Sales Solutions — thought leadership on land-and-expand models and quota attainment without third-party tools.
FAQ
What does "land-and-expand" mean in a quota routing context? Land-and-expand refers to selling a smaller initial deal (the "land") and then growing the account over time (the "expand"). For quota routing, you need to assign credit for both the initial sale and any subsequent growth, often splitting attainment between the original rep and the account manager or expansion team.
How do I track land-and-expand quota in Pipedrive without buying extra software? You can use Pipedrive's custom deal fields and pipelines to tag deals as "land" or "expand," then create weighted revenue reports that sum attainment per rep per period. The key is setting up a single "Deal Source" field and a "Primary Owner" field, then using Pipedrive's built-in dashboards to filter and calculate splits manually or via formulas.
Can I split quota credit between two reps in Pipedrive natively? Pipedrive doesn't have native split-credit functionality, but you can approximate it with a custom "Credit Split" field (e.g., 50/50 or 70/30) and a separate "Attribution" table in Google Sheets synced via Zapier or Pipedrive's export. For most teams, a manual monthly reconciliation is workable until you hit dozens of splits.
What fields should I add to Pipedrive for land-and-expand routing? Add at least three custom fields: "Deal Type" (Land/Expand), "Original Rep" (for land deals), and "Expansion Rep" (for expand deals). Optionally include "Attribution %" and "Expansion Source" to track which land deal triggered the growth. These fields let you filter and report without extra tools.
How do I prevent double-counting revenue when a rep lands and expands the same account? Set a rule that the "Original Rep" field locks once the land deal closes, and the "Expansion Rep" field is only editable for new deals on the same account. In reports, sum land revenue by Original Rep and expand revenue by Expansion Rep, then combine totals per rep. This avoids double-counting because each deal has a single owner for its type.
What's the simplest weekly report to monitor land-and-expand attainment? Create a Pipedrive dashboard with two widgets: one showing "Land Revenue by Rep" (filtered to deals with Deal Type = Land) and another showing "Expand Revenue by Rep" (filtered to Deal Type = Expand). Add a third widget for total attainment per rep (sum of both). Refresh weekly and compare against quota targets set in a separate spreadsheet or CRM note.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.