V2 - Multiple Opportunities for each Project
Under Opportunity Management V2, a single Project can — and usually does — have more than one Opportunity, one per participating Account that qualifies under the auto-create rules (Processor, Dealer, and any other role configured as auto-create). This is a deliberate difference from the older V1 model of a single Opportunity per Project, and it’s the piece that trips people up most when moving from generic Salesforce Opportunity thinking to Baucore’s project-driven model.
Why one Opportunity per Account
A construction Project realistically involves several companies who each represent separate revenue, separate close probability, and separate forecast entries — a Processor bidding the work, a Dealer supplying materials, sometimes more than one of each competing for the same Project. Rolling all of that into one Opportunity record would hide exactly the information a forecast needs: which specific company relationship is actually going to close, and when.
It also means Baucore can forecast on indirect customers who never buy directly — a Specifier or Building Owner who influences the outcome without being the one who places the order — by giving each of them their own Opportunity too, rather than leaving that influence invisible to standard Salesforce forecasting.
So V2 creates one Opportunity per Account with an auto-create Role, linked back to the same Project:
- Each Opportunity carries its own Stage, Amount, Close Date, and Probability.
- Each is kept in sync with the Project’s own fields (Close Date, Amount, Probability) via the field-synchronization rules described in Key Concepts of Opportunity Management V2 — with per-Opportunity overrides available (
donotoverride, Respect Record Access). - Each moves through Stage independently, driven by that Account’s own Participant Status (Won / Won for Competitor / Lost) rather than a single shared status for the whole Project.
What this means in practice
- Pipeline reports roll up correctly to Account and to Project — a Project with three competing Dealers shows as three pipeline entries, not one.
- Closing one Opportunity doesn’t close the others. A Processor being marked Won doesn’t touch the Dealer’s Opportunity on the same Project — each reflects that Account’s own outcome.
- “Our Company” is always excluded — you don’t get a self-referential Opportunity for your own organization’s participation on a Project.
- No duplicates: if an Opportunity already exists for a given Account on a given Project, a new matching Participant updates its Roles instead of creating a second Opportunity for the same Account.