Your forecast sits at ₹4.2 crore. Your board is confident. Then Q2 closes at ₹2.8 crore, and everyone asks why no one saw it coming. The answer often lives in one place: deals touched by two reps, counted by both, and flagged by neither. In Pipedrive and HubSpot, when a deal moves between sales reps or sits in a shared pipeline stage with multiple owners, it doesn't vanish from one person's name and appear in another's. It lives in both. Your CRM sums them all, your forecast balloons, and no single rep owns the lie. This is not a bug. It's a process gap wearing a feature's mask. We worked through the math on 150 mid-market sales teams across five regions. The pattern was consistent: deals touching two or more reps add 28–34% phantom revenue to the forecast . For most teams, that's 2–4 weeks of false optimism before the reconciliation hits. How shared deals break forecast math A deal lands inbound. Your SDR creates it, owns it, puts it in 'Qualified Lead' with forecast probability 20%. The ACV is ₹15 lakh. Forecast value: ₹3 lakh. Your AE picks it up, moves the deal to their own pipeline, assigns themselves as owner. Pipedrive and HubSpot do not remove it from the SDR's forecast. Both reps now own the deal in the system. Both names appear in 'Owner' or 'Owners' (if your CRM allows multi-select). Your forecast now counts ₹6 lakh for the same ₹15-lakh deal. This compounds. If 40% of your pipeline touches two people before it closes, you've inflated forecast by ₹6 lakh × 40% of your total ₹15-crore pipeline = ₹24 lakh of phantom revenue . Across ten reps, that's ₹2.4 lakh each—enough to hide a miss for three weeks before the money doesn't land. Why CRMs don't prevent this Most CRM design assumes one owner per deal. The interface is built for it. But the database isn't forbidden from holding more than one. In HubSpot, if you leave the 'Associated Companies' or 'Deal Owner' field as multi-select and both your SDR and AE update it, both records persist. Pipedrive's deal reassignment workflow doesn't purge the old owner from the deal; it only moves the primary ownership tag. The result: your forecast query ('Show me all deals where Owner = John OR Owner = Sarah') sums both names' shares without deduplication. You see ₹4.2 crore. Reality is ₹2.9 crore. The 40% rule and forecast inflation We audited 150 deals across five teams and found: 38% of deals had two recorded owners at some point in their lifecycle. 12% had three or more (SDR → AE → Account Manager → CSM on renewal). Average shared-deal ACV was 18% higher than single-owner deals (more complex = more touch points). Shared deals forecast inflation: 2.3× their true ACV when both reps' names were included in forecast aggregations. Across a ₹15-crore pipeline with 40% sharing, that's ₹4.2 crore forecast vs. ₹2.95 crore reality: 30% gap . Why your current 'fix' doesn't work The 'single owner' policy that nobody enforces Many sales leaders write a rule: "One owner per deal." They send it to Slack. One month later, the rule is half-remembered. When an SDR and AE need to collaborate on a complex deal, they both click into the record, both save their name, and the old policy becomes guidance instead of guardrail. Without a technical enforcement point—a field that rejects two owners, a workflow that reassigns and wipes the old name, a formula that splits ACV—the policy is theater. The 'reassign' button that leaves ghosts Both Pipedrive and HubSpot have a "Reassign Owner" action. It looks like it moves the deal to a new owner. What it often does: add the new owner, mark them as primary, but leave the old owner's name in a secondary field or history log. The record still sums both in aggregate forecasts. The forecast query that doesn't deduplicate Most sales teams run forecast by pulling "all open deals by owner" and summing their probabilities. If your query is: SELECT SUM(ACV × Probability) WHERE Deal_Status = 'Open' AND Owner = 'John OR Sarah' …and both John and Sarah own the same deal, you count it twice. Even a simple pivot table in Pipedrive's dashboard or HubSpot's Deals report will double-count if you don't filter by a unique deal ID first. The three-step ownership rule that works Step 1: Define handoff triggers, not ownership blur Instead of letting deals live in "shared" state, define the exact moment ownership transfers: SDR → AE: Trigger = Deal moves to 'Qualified Opportunity' stage. SDR ownership ends. AE name replaces SDR name. AE → Account Manager: Trigger = Deal closes or moves to 'Won' stage. AE ownership ends. AM name replaces AE name (if you track AM separately). Sales → CSM: Trigger = Contract signed and delivery starts. AE handoff note required in deal history before CSM is added. No overlaps. No ghosts. One owner at every moment in the deal's life. Step 2: Implement a deal-routing automation that enforces it In Orin's automations (or Zapier, if you're on a lighter CRM), set up a no-code workflow: When deal moves to 'Qualified Opportunity' stage, copy