How do i handle multiple opportunities representing the same salesprocess?

(0) Share

Report

Posted on by CU17110857-0

I have a customer that uses Dynamics 365 sales for selling construction equipment for big building projects.
When my customer becomes aware of a pending building project, they reach out to potential contractors (the contractors bidding on the project) and offer them a deal on the products the contractors need for the construction of the building. In this scenarios the same product is offered to multiple potential customers (contractors), creating multiple opportunities where only one can win in the end.

Here is three view:
- Building project
- Product offered
- Opportunity
- Opportunity
- Opportunity
- Building project
- Product offered
- Opportunity
- Opportunity

How do i handle this?
Do i create a custom tabel representing the "product offering"? or do i use a parent-child opportunity relationsship?
My biggest concern is the effect that my choice will have on my pibeline and forecasting.

Categories:

Dynamics 365 Sales

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Tom_Gioielli 2,778 Super User 2025 Season 2 on at

Like (2)

Report
I might recommend looking at a Parent/Child Opportunity relationship to essentially group up the opportunities that are mutually exclusive to each other.

Parent Opportunity: Represents the overall potential sale, and should be the record used in Pipeline reporting. The potential value should be tracked here, along with estimated close.

Child Opportunities: One for each of the companies you are offering the product to. These records should have the Forecast Category set to "Omitted" so that they aren't counted in the sales reporting. Individual activities and tracking with each customer can be tracked here.

Automation: When one of the child Opportunities is marked as won, then the parent Opportunity should be updated as well. Then, you can auto-close the other child Opportunities. This should all be very doable in Power Automate flows.

The only downsides to this approach I can think of would be:

Training users or defining a process by which the parent Opportunity is created, and making sure child opportunities are being properly associated to it

Sales where there is only one potential customer don't need this structure, but as soon as you have 2 it will be necessary. Making it as easy as possible to create and maintain these records is where you will sink or swim

That's my opinion at least, and what I would recommend for a customer. Let me know if you have further questions or clarifications, or you can mark approved if it all makes sense. Thanks!

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

#ManoVerse 455 on at

Like (2)

Report
My understanding of your scenario is:
You have a single building project with multiple contractors bidding for it. Your customer supplies construction equipment, so each contractor becomes a potential customer. The products offered represent potential business opportunities with these contractors. In the end, only one contractor will win the building project and place an order for the equipment. Essentially, this is a bidding process involving multiple contractors, where only one will convert into an actual sale and give your customer a business.

I appreciate Tom’s solution and find it very insightful. I would also like to share my suggestion for your consideration, and you can decide which approach works best for your needs.

My solution would be like below :

Building Project as Anchor

Create a custom table for Building Project (assuming this already exists).

This will act as the main record linking all related opportunities.

Use Standard Opportunities

Each contractor’s bid is represented as a separate Opportunity.

Add a lookup field on Opportunity to link it to the Building Project.

Handle Products Efficiently

Add products manually to the first opportunity for the project.

Add a custom column on Opportunity called “Use as Project Template”.

When this column is marked, a Power Automate flow will:

Copy all products from the template opportunity to any new opportunity created for the same Building Project

This avoids manual product entry for every contractor.

Extend the same Power Automate flow (or create new ) so that:
When one opportunity is marked as Won, all other opportunities linked to the same Building Project are automatically updated to Canceled.
This keeps your pipeline clean and accurate.

In my opinion, this will help simplify
Forecasting and pipeline reporting remain standard because everything is based on Opportunities.
Maintainable customization with minimal effort , just one lookup field and one Power Automate flow (or two flows if you choose to separate product copying and opportunity cancellation).
Easy to maintain and scales for future needs and Reflects real-world bidding logic in Dynamics 365.

1 people found this reply helpful.

Was this reply helpful? Yes No

Join the conversation

Community site session details

How do i handle multiple opportunities representing the same salesprocess?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

How do i handle multiple opportunities representing the same salesprocess?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates