When should I create a new Project pipeline instead of another template?

Create a new template when the Project follows the same lifecycle but requires a different set of Tasks.

Create a new Project pipeline when the lifecycle itself changes.

Keep the same pipeline when

• The same Project stages apply.
• Tasks can be mapped cleanly to those stages.
• Stage completion means roughly the same thing across the templates.

Create another pipeline when

• The stage sequence changes.
• A template repeatedly needs Tasks that do not fit the existing stage model.
• The meaning of a milestone is materially different.
• The delivery motion has different approval, handoff or completion steps.

This keeps HubSpot pipelines meaningful and prevents creating a separate pipeline for every product, service or variation.