Introducing Flow: project management that knows who the client is

Today we are launching Flow, the project and task manager built into the MPP Portal. It is the third thing we have replaced with our own software this year, and the one people asked for loudest.

The specific complaint

We were long-time ClickUp users. Before that, Asana. We have run projects in Monday and Jira and, during one memorable quarter, a spreadsheet with conditional formatting that a colleague still describes as "the incident".

Every one of those tools does task management well. The problem was never the task management. It was that a task in a general-purpose tool is an island. It has a title, an assignee, a date, and no idea that it belongs to a client who pays us $6,000 a month, whose website is mid-migration, whose main contact has been slow to approve things for three weeks.

So we did what everyone does: we recreated that context by hand. Client names became list prefixes. Account value became a custom field somebody updated monthly, or did not. Someone built a "health" tag and maintained it heroically for two months.

Every workaround in a project tool is a piece of context that should have been a relationship in a database.

What Flow is

Flow is a full work manager, with the features you would expect, because a tool missing them is not a replacement:

• Projects with custom statuses, so a content project and a website build do not have to pretend they move through the same stages.
• Four views: List grouped by whatever you like, a Kanban board, a Calendar, and a Timeline for dependencies, plus a My Tasks home that answers "what am I meant to be doing today" without a saved filter.
• Priorities, multiple assignees, dates, tags, subtasks, dependencies, and time tracking for the people who want it.
• Comments and a full activity trail on every task, so the decision and its reasoning live with the work instead of in a chat scroll.
• Importers from ClickUp and from our own legacy task list, because a migration nobody can do is a product nobody adopts.

That is table stakes. Here is the part that made it worth building.

Tasks that know things

Because Flow lives in the Portal, a task is connected to the rest of the company by default rather than by convention.

A task belongs to a project; a project belongs to a client; a client has a value, a status, a website, a plan, a contact, and a communication history. None of that has to be copied into the task, tagged onto it, or maintained by a person. It is simply reachable.

What that changes in practice:

• Open an account and see everything in flight for it, without a filter someone had to build.
• Prioritize by what the work is worth, not just by what is loudest, because the value is right there.
• Turn an imported project plan into live tasks in one action: the plan we send a client and the work we do for them stop being two documents that drift apart.
• Get a standup that is actually about accounts rather than tickets.

Flow AI

There is an AI feature and we want to describe it honestly, because "AI-powered" is doing a lot of unearned work in this industry.

Flow's AI does four things, all of which are chores:

1. Generates subtasks from a task that is too big: the "break this down" step people skip.
2. Drafts descriptions so a two-word task title becomes something a colleague can act on.
3. Writes your standup from what actually changed, rather than from what you remember changing.
4. Prioritizes your day by looking at dates, dependencies, blockers, and account value together.

It does not assign work, decide what matters, or move things without being asked. The judgment stays with the person who owns the number. What it removes is the administrative tax that makes people stop maintaining the system, and a project tool that people stop maintaining is worse than no project tool, because it is confidently wrong.

What we learned building it

The hard part of project software is not tasks. It is views. The same fifty tasks need to look like a board to one person, a calendar to another, and a timeline to whoever is worrying about the critical path. We spent more time on the four views than on everything else combined.

Statuses are a modeling problem, not a settings screen. "Not started" is not "in progress", "ongoing" is not "blocked", and a tool that flattens those distinctions produces reports nobody trusts.

Adoption is decided by the import. Every team we have watched abandon a new tool abandoned it during migration. The ClickUp importer was not a nice-to-have; it was the feature that determined whether any of this shipped at all.

Available now

Flow is live in the Portal for the whole team, including viewers, because collaboration tools with per-seat gates end up with half the company outside the system, which defeats the purpose.

Next in this series: our own workspace, our own chat, and the website grader we have been quietly running against client sites for months.

If you want a partner whose operating system is this specific about accountability, apply for partnership.