Currently, Opportunities are tightly linked to the Primary Contact and Company, causing automatic updates and dependencies that don't fit all sales processes.

We would like the ability to independently manage:

Opportunity Name

Primary Contact

Company/Account

without forcing one field to control or update the others.

Desired Functionality:

Allow Opportunity Names to remain static even when the Primary Contact changes.

Allow users to change the Primary Contact without automatically renaming the Opportunity.

Provide a setting to disable auto-population of Opportunity Name from Contact or Company.

Allow multiple opportunities under the same company without requiring contact-based naming conventions.

Give admins the option to choose naming behavior at the pipeline level.

Use Case:

In complex B2B sales environments, opportunities often represent projects, products, manufacturing requests, commercialization initiatives, or RFQs rather than individual contacts. Users need the flexibility to name opportunities based on the project or business opportunity itself while still associating contacts and companies for communication purposes.

Benefits:

More accurate forecasting and pipeline management

Better support for enterprise and multi-contact sales processes

Reduced accidental renaming of opportunities

Improved flexibility for custom sales workflows and CRM implementations