Designing your project pipeline

tl;dr - add your own phases under the proposed/won/active states to customise your project pipeline.
What is a project pipeline?
How do you talk about winning a project at your firm? Each firm is different, and tiny+ lets you design your project pipeline to match how your firm already thinks about proposed projects. 
Why configure your project pipeline? Well, it's the fundamental structure for your project-based business development activity in your firm. Once you get it right, you can generate powerful reports for each pipeline stage, and give your whole firm a shared language around the process of winning a project. 
Understanding project states and phases
In tiny+ there are six umbrella states that a project will always exist in:
Proposed - We have not yet been awarded the project.
Won - We have been awarded this project. Work has not yet commenced.
Active - The project is currently being delivered.
Completed - The project is complete.
Lost - We were not awarded the project.
Cancelled - The project was cancelled or did not proceed.
These six states remain constant and cannot be changed, with the exception of the 'Won' state, which can be disabled in Account Settings -> App Settings.
Underneath these six states you can define any number of phases to suit your business development process and reporting requirements. Together, these states and phases define your Project Pipeline.
An example Project Pipeline configuration.
How to configure your Project Pipeline
You must be an Account Admin to configure the Project Pipeline.
To get started, navigate to Account Settings -> Project Phases.
From this page, you can create, edit, re-order and remove phases.
Some example Project Pipeline configurations
Looking for inspiration? Here are some common project pipeline configurations which you may like to steal! 
Example #1 - Very simple
Phase
Description
Proposed - Lead
A potential project starting at least three months from now.
Proposed - Submission
A potential project which will start in the next three months.
Won
(no phases reqd)
Active
(no phases reqd)
Example #2 - More complex
Phase
Description
Proposed - Long Term
A potential project starting at least three months from now.
Proposed - Short Term
A potential project which will start in the next three months.
Proposed - Bidding
We are currently preparing a Proposal for this project.
Proposed - Submitted
We have submitted our Proposal and are awaiting feedback.
Won
(no phases reqd)
Active - Delivering
Currently delivering the project.
Active - On Hold
On hold at client request.
​

Using tiny+ - Previous

Getting started

Designing your client relationship pipeline

Last modified 2yr ago

Copy link

Outline

What is a project pipeline?

Understanding project states and phases

How to configure your Project Pipeline

Some example Project Pipeline configurations