Your sales team closes a ₹50 lakh deal. Three reps are involved—the AE owns the account, the sales engineer scoped the implementation, the channel partner brought the lead. Each one logs into the CRM, claims ownership, and adds it to their forecast. On paper, you now have ₹1.5 crore in pipeline. In reality, you have ₹50 lakh. By the time you hire two more heads based on that inflated number, you've already burned the cash cushion. Shared deals are the silent forecast killer. They feel like collaboration. They are collaboration. But without routing rules and ownership weighting, they're also the fastest way to double-count your pipeline and make hiring decisions on phantom revenue. Why shared deals inflate forecasts 15–40% The math is simple and brutal. A deal moves through your pipeline touching multiple people: The AE finds the opportunity, builds the relationship, owns the forecast line. The sales engineer runs discovery calls, scopes the build, and (in many CRMs) gets added as a stakeholder or co-owner. The account manager pre-closes to smooth implementation, logs time on the deal, and adds it to their pipeline projection. The channel partner sources the lead, stays involved, and tracks it against their quota. Without explicit routing rules, each person counts the deal at 100% weight in their forecast. The deal is worth ₹50L once. But four people forecast ₹50L each. Your pipeline report shows ₹2 crore. Your CFO budgets for headcount that assumes that revenue lands on schedule. When it doesn't—because you're actually landing ₹50L, not ₹2 crore—you've hired into a revenue cliff. This inflates forecasts by an average of 15–40% in teams with heavy cross-functional deals. For companies with ₹50 crore+ ACV deals, the distortion can swing hiring decisions and blow quarterly guidance. The routing rule fix: Primary owner counts, secondary = 0% weight The solution is brutal in its simplicity: one deal, one forecast count. But it requires three things: 1. Assign a single primary owner The primary owner is the person whose quota the deal is counted against. Typically, this is the AE who signed the contract or, in a team-selling motion, the person who closes the contract. In many CRM systems , you can lock this role or flag it as 'forecast owner' so the reporting engine knows which person's pipeline this belongs to. How to set this up: Create a 'Forecast Owner' field on every deal record (separate from 'Team Members' or 'Stakeholders'). Make this field mandatory. A deal without a forecast owner doesn't exist in your pipeline report. Lock it once the deal enters stage 3 or 'Demo' (or your equivalent). Changes after that date require sales ops approval. 2. Add stakeholders with zero forecast weight Everyone else who touched the deal gets added to the stakeholder or team member field—but with an explicit 0% forecast weight . This serves two purposes: It preserves collaboration visibility. The sales engineer, account manager, and partner are still logged on the deal for activity, notes, and task history. It removes them from forecast calculations. They show up in 'who worked on this' reports but not in 'what's in your pipeline' rolls-ups. Implementation rule: When adding a stakeholder, your CRM should prompt: 'Count this person's involvement in forecast?' Default answer is 'No'. If someone needs to be counted (rare—usually only the primary owner), they're checked and weighted 10–20% at most (for very early-stage multi-threaded deals). Everyone else is 0%. 3. Test your weighting in deal reports, not just in forecast summaries Most CRM forecast views hide weighting math. You'll see 'Total Pipeline: ₹2 crore' but not 'Deal A ₹50L (100% to Primary Owner) + Deal B ₹75L (0% to Stakeholder C)'. Create a detailed deal report that shows: Deal name Amount Primary owner (name) All stakeholders (with names and weights) Forecast contribution (Amount × Primary Owner Weight) Run this report monthly. If a ₹50L deal is showing as ₹50L × 4 stakeholders = ₹2L forecast contribution, your weighting is broken. The quarterly audit: Find and flatten the bloat Even with routing rules in place, deals drift. A sales engineer gets added mid-deal and claims 20% ownership. A deal passes from AE to AM, and both stay on it at 100%. Three months later, your forecast is inflated again. Run a quarterly shared-deal audit. It takes 4–6 hours and catches 80% of forecast bloat before it hits cash-flow decisions. Step 1: Pull all deals with 2+ owners (15 min) Filter your deal report to show only records with more than one stakeholder or team member. Most CRMs allow a formula like 'Count(Stakeholders) > 1' or 'Team Members Length > 1'. Export to a sheet. Step 2: Spot-check 30–40 deals for correct weighting (60 min) Open 30–40 deals at random (or stratified by stage). For each: Identify the primary owner: Who did the demo? Who's closing the contract? That's your forecast owner. Check secondary weights: Anyone else should be 0% unless they're a co-selling partner