Your forecast sits in your board deck at ₹50 crore. Your CEO nods. Three months later, actual closes track ₹42 crore. You blame deal velocity, market softness, quarter-end pushout. In 80% of cases, you're wrong. The culprit is simpler and uglier: two reps are sitting on the same deal, and your CRM is counting it twice. The phantom pipeline math Start with a baseline. You have 50 sales reps. Average deal value is ₹50 lakh. Each rep carries 8 deals in their pipeline. That's ₹200 crore of forecast. Now the corruption: deal ownership is unclear. A rep pursues a lead. Wins a champion. Pulls in their manager to close. Manager hands off to a customer success rep who also records a touch. Three people, one deal, three pipeline entries. At a 20% overlap rate—conservative in most orgs—you're carrying phantom revenue: 50 reps × 8 deals × ₹50L average = ₹200Cr forecast 20% of deals touched by 2+ people = 80 deals with split ownership 80 deals × ₹50L × 1.2x multiplication factor = ₹48Cr phantom pipeline That's a 15% inflation baked into your number before you've even looked at deal stage accuracy or probability weighting. Most CRMs don't deduplicate on forecast rolls. They sum pipeline by rep, then by team, then by region. Multiply at each layer. The real risk: you believe the ₹200 crore. You forecast ₹150 crore close. You plan hiring, marketing spend, and commission pools on phantom revenue. When actual closes land at ₹127 crore, you've already committed capital you don't have. Why your CRM doubled the deal The mechanics are straightforward. Most CRMs (HubSpot, Pipedrive, and without proper configuration, even Orin) handle deal ownership like this: Primary owner : the rep who created the deal or closed it Collaborators : anyone else tagged to the record Forecast calculation : sum all deals where the rep is owner OR collaborator So when your AE owns the deal and your manager is a collaborator, both reps' pipeline views include it at 100% value. Neither system automatically halves it. And when you roll up to team forecast, you're adding both halves. HubSpot calls this deal association . Pipedrive calls it deal participants . The feature is well-intentioned—it tracks who influenced a deal. But forecast math doesn't account for it. Most teams don't either. The three-layer recovery: ownership rules, weighting, audits Layer 1: Define and enforce deal ownership Start here. A deal can have one owner and unlimited collaborators. That's non-negotiable. In your CRM: Only the owner's rep is counted in forecast. Period. Collaborators are tracked for attribution and relationship mapping, not pipeline math. Establish the rule: whoever first qualified the opportunity (not whoever created the record) owns it until close or explicit handoff. In Orin, set deal ownership in pipeline settings and lock it to the qualification-stage gate. Pipedrive allows deal participant weighting—but it's optional and teams skip it. HubSpot doesn't natively weight participants; you'd need a custom property and filter logic to fix it, which most don't. Test case: An AE qualifies a ₹50L deal. A manager joins the call in week 3. Manager should be a collaborator, not a co-owner. When the manager's forecast is rolled up, that deal doesn't appear—only the AE's does. Layer 2: Weight shared deals mathematically Some deals require real collaboration. A large deal might need multiple reps' effort. In those cases, don't lie in forecast—distribute the value proportionally. 50% deal : AE + manager both working it equally. Each gets 50% of the deal value in forecast. 70/30 deal : AE drove it; manager stepped in late. AE gets 70%, manager 30%. 100% deal : AE owns it. Manager is involved but doesn't appear in rep-level forecast. (Manager's view can show influence attribution separately.) Implement this in your CRM as a forecast weight or attribution weight custom property. When a rep collaborates on a deal, the system should prompt: What % of this deal's value counts toward your forecast? HubSpot users: create a custom property called Forecast Weight on the deal. Use a number field (0–100). Exclude any deal with weight Pipedrive users: leverage Deal custom fields the same way. Set a rule: forecast = deal value × (forecast weight / 100). Orin: deal ownership and weighting are native . Set collaborators with an explicit ownership %, and forecast rolls up correctly without custom fields. Layer 3: Audit your forecast purity quarterly Math alone won't hold. People will revert. Run a 90-minute forecast audit every quarter: Pull your current forecast by rep (don't filter by stage yet). Export as CSV. Count deal frequency . For each deal ID, count how many reps claim it. Deals appearing 2+ times are your contamination. Sample 20 contaminated deals . Pull their records. Who's the real owner? Who should be collaborator? Fix ownership in the system. Remove secondary reps as owners; add them as collaborators with 0% forecast weight if they don't deserve a slice. Recalculate forecast