A big upgrade to Pipelines
Matt FranklinWe're rolling out a big upgrade to Pipelines that brings more visibility, more control, and a much slicker experience for managing your projects.
Richer project cards
Pipeline cards now show much more at a glance:
- Project value β see the monetary value without clicking in
- Last activity β know when something last happened
- Time in stage β spot projects that have been sitting too long
- Tags β displayed directly on the card as before
- Incomplete tasks β quickly see what's outstanding
- Overdue invoices β flag projects with payment issues
- Proposal view status β see whether proposals have been viewed
We'll soon be adding configurability so you can choose exactly which fields and custom fields appear on your cards.
Stage guards
This is a big one. You can now set rules on pipeline stages that prevent projects from moving forward unless certain criteria are met.
Try to drag a project into a guarded stage and you'll see exactly why it's blocked β for example, "Proposal must have been sent" or "Proposal must have been accepted."
This gives you real compliance control. You know things are done before they progress, and nothing slips through the cracks.
There's a wide range of guard conditions available, including inverse conditions (e.g. "has NOT been declined"), and you can stack as many guards as you need on any stage.
Visual automations
All of the things that previously moved projects between stages automatically have been pulled out into visual automations. You can now see and configure exactly what's happening at every stage.
No more mystery moves β every automation is visible, and you're in control.
Automation triggers
Triggers define what causes a project to move into a stage. You can set these based on:
- Project events
- Proposal events (sent, accepted, expired, declined)
- Change proposal events
- DNO application events
- Task status changes
- And more
Core accounts can now add triggers too β previously this was limited to higher tiers.
Stage management
Managing your pipeline stages is now much more flexible:
- Add stages to the left or right of any existing stage
- Delete stages (when empty)
- Reorder stages by dragging them around
- Custom colours β pick from presets or set your own
- Rename stages inline
- Separate expired and declined β these were previously a combined system stage, and can now be fully split into individual stages wherever you want them in your pipeline
Sorting and filtering
- Sort projects by most/least recently updated or shortest/longest time in stage
- Filter by team member
- Switch between board and table views
- Collapsed stages are remembered as you navigate
No more automatic backwards moves
Projects will no longer automatically move backwards through the pipeline. They only move based on automations you've explicitly configured. We've migrated your existing automations across, so everything should carry over β but it's worth reviewing your pipeline to make sure it's set up how you want.
Let Dave handle it
If the configuration feels like a lot, Agent Dave can set up your stages, guards, and automations for you using natural language. Just hit Command-K and tell Dave what you need:
- "Add a stage between Survey Booked and Survey Complete called Check"
- "When that happens, send a communication internally"
- "Set up a new pipeline for my retrofit projects"
Dave understands which page you're on and can plan out your entire pipeline configuration.