Updated

Plan & Organize

Custom Workflows

A kanban board answers 'what's in progress.' A workflow answers 'what stage is this project at.' Every workspace ships with a real default lifecycle — and you can build your own.

Product Preview
Screenshot of custom workflows in the app
/images/features/custom-workflows.jpg

How It Works

01

Start from the default lifecycle

Idea → Planning → In Progress → Review/Testing → Launch → Maintenance → Completed — seeded into every new workspace, built for how software actually ships.

02

Or define your own stages

Name your stages, set their order, and mark which one counts as 'done' — a workflow can be as simple or as detailed as your process needs.

03

Move projects through it

Every project sits in exactly one stage at a time, visible on the project list and rolled up in reports.

Why It Matters

Distinguishes project-level stage (planning vs. shipped) from task-level status (to do vs. done)
Gives leadership a one-glance view of what's early-stage vs. what's about to launch
Doesn't force a Scrum-sprint model on teams that don't run sprints
One workflow, reused across every new project — set it up once

Frequently Asked Questions

Is this the same as the Kanban board columns?

No — board columns track task status inside a project; a workflow tracks the project's own stage. They're separate, complementary layers.

Can different projects use different workflows?

Yes — a workspace can define more than one workflow and each project picks the one that fits.

What happens to a project when it reaches the final stage?

It's simply marked at that stage — you can also separately mark a project Completed or Archived regardless of workflow stage.