In the Business and Enterprise plans, pipelines and their stages are used to indicate the phases of a project. This way, the one and same project can move through different sales phases from creation to closing, and you don’t need to create separate sub-projects for different work phases. For example, you can create a project in the pipeline (the quote-stage pipeline) from a lead, for which a quote/offer is created. When the customer has approved the offer, you mark the project as won, and the project moves from the sales pipeline to the Won projects pipeline.
If the offer was not approved, you can mark the pipeline project as lost, and the project will no longer appear as active.
You can select the reason for winning or losing the project, including comments, and review or edit these later in the project details. Win and loss reasons are defined in settings.
Permissions: Projects
PSA plans: Business, Enterprise, Enterprise+
Marking a project as won
Winning a sales-stage project, i.e. moving it to the Won projects pipeline, can be done in several views:
-
In the project card basic details from the funnel field drop-down: won deal
-
From the project card Actions menu: mark as won
-
In the project list: from the three dots or from the funnel field drop-down: won deals
-
In the projects Kanban view from the three dots: mark as won.
Recording the reason for a won project
If win reasons have been defined in settings, changing the project to won opens an additional window where you can select the win reason and add a comment.
After saving, the project moves to the Won projects pipeline, and new fields are shown in the project basic details:
- Won reason
- Won comment
Closing a project as lost
Unlike winning a project, marking a sales-stage project as lost does not change the project pipeline; instead, it changes the project status to lost and the project will no longer appear as active. Losing a project can be done in several views; see below. The program may ask for additional confirmation if the project has uninvoiced material.
-
From the project card Actions menu: mark as lost
-
In the projects list view from the three dots: mark as lost
-
In the projects Kanban view from the three dots: close as lost.
Recording the reason for a lost project
If loss reasons have been defined in settings, changing the project to lost opens an additional window where you can select the loss reason and add a comment.
After saving, new fields are shown in the project basic details:
- Lost reason
- Lost comment