Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Multiple Opportunity Pipelines Based on Opportunity Type #10454

Open
oddieis opened this issue Feb 24, 2025 · 0 comments
Open

Support for Multiple Opportunity Pipelines Based on Opportunity Type #10454

oddieis opened this issue Feb 24, 2025 · 0 comments

Comments

@oddieis
Copy link

oddieis commented Feb 24, 2025

Scope & Context

We would like to request improving opportunity management in Twenty CRM.
The ticket is about enabling different opportunity pipelines, allowing users to define distinct sets of stages based on the opportunity type.

Current behavior

Currently, all opportunities follow a single, fixed set of stages.
Many CRMs allow users to define multiple pipelines with different stage progressions that align with different types of opportunities.
Since users cannot currently define separate pipelines in Twenty CRM, they are forced to find workarounds.

Additionally, users cannot hide the standard Opportunity object, meaning they must work within its constraints rather than defining custom pipeline types.

Expected behavior

Users should be able to create multiple opportunity pipelines, each with its own set of stages.
When creating an opportunity, users should be able to select a pipeline that determines the opportunity's progression.

For example:

  • A new customer opportunity follows an onboarding flow with specific stages.
  • A prospective customer for Product A follows a different sales process with unique stages.
  • A new partner follows an entirely separate partnership approval process.

Each of these scenarios should be supported by separate pipelines with their own custom-defined stages.

Technical inputs

  • Modify the opportunity model to allow multiple pipelines with distinct stage configurations.
  • Create an interface for defining and managing pipelines.
  • Update the opportunity creation flow to allow users to select a pipeline.
  • Ensure that opportunities follow the correct pipeline with appropriate stage progression.
  • If possible, allow users to hide the standard Opportunity object if they prefer to use custom pipelines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant