Today we're launching one of our most requested features: custom workflows. You can now design your own pipeline stages, set rules for task transitions, and create templates to reuse across projects.
Why custom workflows matter
Every team works differently. A design team's process (Brief → Exploration → Refinement → Handoff) looks nothing like an engineering team's (Backlog → In Progress → Review → QA → Done). Forcing everyone into the same "To Do / In Progress / Done" pipeline was limiting.
With custom workflows, your board reflects how your team actually works — not how a software vendor thinks you should work.
How it works
Head to any project's settings and you'll see a new "Workflow" tab. From there you can add, remove, rename, and reorder stages. Each stage gets a color, and you can optionally set rules like "tasks must have an assignee before entering Review."
We've also created six starter templates for common use cases: Software Development, Content Pipeline, Design Process, Bug Tracking, Hiring Pipeline, and a simple Kanban. Pick one as a starting point and customize from there.
What we learned building this
The biggest challenge was keeping it simple. Workflow engines in enterprise tools are notoriously complex — some have visual drag-and-drop editors with conditions, branches, and automation rules that require a dedicated admin to manage.
We went the other direction. Workflows in TaskFlow are a flat list of stages with optional rules. No branches, no conditional logic, no automation. Just clear stages that map to how your work actually flows.
Is it less powerful than enterprise alternatives? Absolutely. Is it usable by anyone on the team without reading documentation? Also absolutely. That's the trade-off we're comfortable with.
Try it now
Custom workflows are available on all Pro and Team plans starting today. Free plan users get one custom workflow per project. We can't wait to see what you build with it.