Your pipeline shows ₹50 million. But when you run the numbers, actual close probability doesn't match. You dig into the data and find the same ₹3 million deal appears twice: once in your AE's forecast, once in the support rep's. Neither knows it's counted twice. Both think they're responsible. Nobody knows who to follow up with. The forecast is inflated by 15%. This isn't a data hygiene problem. It's a routing architecture problem. When you don't define primary and secondary ownership explicitly, shared deals become forecast parasites. They bloat your pipeline while stalling actual close velocity. Why shared deals break forecasts A deal isn't "shared" by accident. Usually, it lands there because: Account-based selling: The AE owns the relationship, but a CSM also touches the deal because they're managing implementation risk. Sales development handoff: An SDR qualifies the lead, hands to AE, but both track it as "theirs" in the CRM. Cross-functional close: A presales engineer is critical to the technical sale, so they also mark themselves on the deal. Territory overlap: Two reps both have incentive to claim the customer because they share the account. Without explicit routing rules, forecast inflation becomes systematic. Each rep adds their own probability, their own close date, their own win likelihood. A ₹2M deal touched by three people becomes ₹6M in forecast math. Most teams solve this by asking reps to "just be honest" about shared deals. That fails 100% of the time. Incentive structures are too strong. You need a system, not a norm. The routing rule: Primary + secondary, forecast credit only to primary The fix is simple in concept, strict in execution: Primary rep: Owns the deal, owns the forecast line, owns the commission or quota credit. Secondary rep(s): Logged as collaborators, visible on the deal record, but not counted in forecast calculations. Forecast rollup: Aggregates only primary rep deals. Secondary reps see their collaboration history but don't inflate pipeline. This rule does three things at once: Prevents double-counting. One deal, one forecast line. Preserves visibility. You still know everyone who touched the deal, so you can audit close patterns and see which roles actually move deals forward. Aligns incentive. Primary rep has the motive to move it. Secondary reps help without creating conflicting ownership. The enforcement point is critical: forecast rollup must explicitly filter on primary ownership, not just raw deal count. Implementation: Pipedrive, HubSpot, and Orin Pipedrive Pipedrive doesn't have a native "primary + secondary" framework, but you can build it: Use the Deal Owner field as primary. This field always rolls up into forecast. Create a custom field called Collaborators (multi-select or text). Link the secondary reps here. In your dashboard, forecast widget, filter by Deal Owner only . Do not sum across collaborators. Use Pipedrive's custom activities to log secondary rep touchpoints, so they appear on the deal timeline but don't affect ownership. Gotcha: Pipedrive's API and automation rules can't yet filter forecast on "primary only," so you'll need to rebuild your dashboard filters and export your own forecast reports. If your deals move fast, this manual step becomes a tax. HubSpot HubSpot has deal associations and deal stages, but ownership is singular by default: Keep the Deal Owner field as your primary rep. Use Associations to link secondary reps to the deal (create a "Collaborator" association type). HubSpot will show them on the deal record. In Forecasting settings, ensure your forecast view filters on Deal Owner only. HubSpot's native forecast already does this, so you're protected. Use Custom properties to log secondary rep role (SDR, CSM, presales) so you can audit contribution without inflating forecast. Advantage: HubSpot's forecasting module is explicit about ownership, so this is relatively clean. The catch: your team will still manually move the Deal Owner field if they disagree on primary, so you'll need a governance policy ("AE = primary unless they explicitly reassign"). Orin Orin's CRM lets you define deal routing rules before the deal is even created. When a deal is added or transferred, automation rules can assign primary ownership and tag secondary collaborators in one step: Routing rule: "If deal source = inbound lead AND AE assigned, then AE = primary owner. If CSM is involved, add CSM as collaborator via workflow." Forecast calculation: Orin's reporting natively separates primary ownership from collaboration tags. Your forecast only sums primary deals. Audit trail: Every time a secondary rep is added or removed, Orin logs it. You can see which collaborators stick around and which deals they actually close. Integration: If you're using Orin's team chat or unified messaging , secondary reps get pinged on deal activity without needing to own it themselves. The operational edge: Orin routes once. You don't have to manually move Deal Owner fields