Your forecast shows ₹1.5L closing this quarter. Three reps own a ₹50L deal together. Do the math: if each weights it fully, you've just added ₹100L of phantom value to your pipeline. That's not optimism. That's arithmetic. Shared deals are the silent killer of forecast accuracy. A deal that should count as ₹50L shows up as ₹150L because three reps each see themselves as the owner. Your board nods at your numbers. Your ops team scrambles to explain why actuals miss forecast by 40%. Your reps never learn to own outcomes because responsibility is split three ways. The fix is not a conversation. It's structural. Single ownership, mechanical deal routing, and forecast math that corrects for the splits you can't eliminate. Why Shared Deals Bloat Forecast: The Arithmetic When a deal lands in your CRM, it has one value: ₹50L. But if three reps are assigned, most platforms count it three times at 100% weight. Here's what happens: Rep A sees ₹50L closing in Q3. That's their number. Rep B also sees ₹50L closing in Q3. Their number too. Rep C looks at the same deal, same value, same close date. Your forecast rolls up to ₹150L from one deal. Reality closes ₹50L. Forecast was off by 200%. This compounds across 50 deals. Some shared by two reps, some by three. Your total forecast is now 30–40% bloated. You've turned a measurement problem into a planning crisis. Shared deals aren't a forecast problem; they're a routing problem. Fix the routing, and forecast follows. The Root Cause: Fuzzy Ownership Rules Most teams don't set explicit routing discipline because they believe deals are naturally collaborative. Account execs collaborate with sales development. Sales engineers own technical validation. Executives sponsor close. All three touch the deal. All three want credit. That's real. But your CRM should enforce a rule: only one rep owns the deal in forecast math . Everyone else is a participant, not an owner. Without that rule, you get: Deal assigned to the SDR who opened it Deal re-assigned to the AE who qualified it Deal still showing on the SDR's board because no one removed them Deal also assigned to a sales engineer for demo support Forecast counting it four ways Most CRMs (Pipedrive, HubSpot, Orin included) allow multiple assignees. That's useful for task routing. It's poison for forecast math. Single-Owner Routing: The Mechanical Fix Your routing rule should be: one primary owner per deal, always . Here's how to enforce it: Define handoff triggers. SDR owns until qualification call is completed. AE owns from qualification to legal. Sales engineer is a participant, not an owner. Assign them to a task, not to the deal itself. Set explicit assignment rules in your CRM. When a deal moves from 'qualified' to 'in negotiation', automatically remove the SDR as owner and assign to the AE. Don't ask reps to do this manually—they won't. Create deal participant roles. In Orin, you can tag participants without making them owners. Pipedrive and HubSpot have similar structures. Use them. A sales engineer is a 'participant'; the AE is the 'owner'. Only the owner counts in forecast. Lock ownership at close. Once a deal closes, only one rep gets commission credit, only one rep's territory is credited for the win. Make that the owner. Everyone else was support. This is not about fairness—it's about causality. One person's actions drove this deal to close. Everyone else enabled it. Forecast should measure the driver. Deal Split Rules: For the Deals You Can't Route Cleanly Some deals genuinely need to be split. A co-selling arrangement where two AEs own one territory together. A partnership deal where your rep and a channel partner both close it. A customer that moves between reps mid-cycle. For these, don't leave it ambiguous. Use explicit deal-split math: 50/50 split: Rep A owns 50%, Rep B owns 50%. Each counts ₹25L in forecast for a ₹50L deal. Weighted split: Rep A closed 70% of the deal, Rep B closed 30%. Rep A counts ₹35L, Rep B counts ₹15L. Time-based split: Rep A owns it until month-end, Rep B owns it from month-end forward. Their forecast weights based on expected close date and ownership duration. The key: write it down. In your CRM's deal record , create a field: 'Forecast Split %'. When you upload deals or assign them, populate this field. Your forecast report then pulls this value, not a simple owner count. If your CRM doesn't support this natively, a formula field or a custom sync layer will do it. Orin's custom fields let you log the split percentage; your forecast automation then divides the deal value by that percentage for each rep. Correcting Forecast Math: The Calculation Layer Even with perfect routing, legacy deals and edge cases will exist. Your forecast calculation needs to correct for them. Here's the formula that works: Rep's Forecast Value = (Deal Value ÷ Number of Owners) × Forecast Split % × Stage Probability For a ₹50L deal with three owners, no explicit split, and 75% stage probability: Each rep gets: (50L ÷