For remote teams
Fluidwave for remote teams: a shared task manager for small distributed teams
Small distributed teams need a shared list, clear owners and a way to see who is waiting on whom across time zones, without a heavy project suite. Fluidwave gives a team of a handful of people assignments, comments, a Slack board and each member’s own AI-planned day, free.
Jobs to be done
Give every task one clear owner
- Today
- Work gets agreed in a call, written in a chat thread and forgotten by the next morning in another time zone. Nobody is sure who owns it.
- With Fluidwave
- Assign every task to one team member and group the list by assignee to see each person’s queue. Threaded comments with @-mentions and reactions keep the discussion on the task, and each member sees their own Active list ordered by auto-prioritization.
See who is waiting on whom
- Today
- Handoffs cross time zones, so a task blocked on someone in Berlin waits a full day. A flat list hides the blockage until it is late.
- With Fluidwave
- Set a task to Waiting on a message, an email or a call and it leaves the assignee’s Active list until the reply arrives. The Waiting view shows every handoff in flight. Dependencies between tasks show in the Gantt view, so a chain across three people is visible before it slips.
Keep the team’s list where the team already is
- Today
- The team lives in Slack, the tasks live somewhere else, and the two drift apart within a week.
- With Fluidwave
- Sync a Fluidwave list to a Slack channel as a native Slack board. Tasks post as cards, status changes show up in the channel, and teammates add tasks from Slack with a slash command. The board and the list stay in step.
Let each person plan their own day
- Today
- Everyone plans their own day differently, and a shared tool that dictates the schedule gets ignored.
- With Fluidwave
- Each member connects their own Google Calendar and runs AI scheduling on their own tasks. Sessions land inside their working hours with breaks around meetings, and only the sessions they choose are written to their calendar. Shared work, private schedules.
A day with Fluidwave
- 1
Morning, in every time zone: the Active list
Each member starts their own day, in their own time zone, with their own Active list. It shows only what they can work on now, ordered by auto-prioritization, with anything waiting on a teammate hidden. Comments left overnight from another time zone show up on the task with the @-mention, so catching up is reading the tasks rather than scrolling a chat channel. Anyone who also uses Fluidwave for Gmail triages their inbox first and turns requests into tasks assigned to whoever owns them.
- 2
Let AI plan each person’s day
Each person opens their own calendar and runs AI scheduling on their own tasks. It reads their events only to find free time, packs the assigned tasks into gaps inside their working hours, and leaves breaks around calls. Nothing is written to Google Calendar until the person confirms and chooses to sync. The team shares the list but not the schedule, which is what makes a shared tool survive: nobody’s planning style is imposed on anyone else, and the shared board still reflects what is done.
- 3
Work from the Slack board and the Kanban view
The team’s list is synced to a Slack channel as a board, so tasks post as cards and status changes appear where everyone is already looking. Someone adds a task from Slack with the slash command, it appears in Fluidwave, and the owner assigns it. Decisions happen in threaded comments on the task with @-mentions, which keeps context with the work instead of in a channel nobody can search later. Group the list by assignee to see load across the team, or switch to Kanban and drag tasks between statuses in a standup.
- 4
Handoffs, waiting-on and dependencies
When a task is blocked on another person, set it to Waiting on a message. It leaves the assignee’s Active list and shows in the Waiting view. Add dependencies between tasks that must happen in order, and open the Gantt view to see the chain across people; Fluidwave detects circular dependencies as you add them. In a weekly sync, the Waiting view answers “what is stuck?” and the Gantt view answers “what slips if this does?” For overflow work nobody on the team should own, set a task to Delegate and send it to a human assistant through the marketplace.
- 5
The weekly review across the team
On Friday the team runs a short weekly review together: clear the Waiting items that came back, reassign anything that stalled, and check the Gantt view for next week’s chain. Recurring tasks bring up the retro and the monthly planning on their own. Individuals keep their own habits in the Today’s habits strip, such as posting a daily update, with streaks. Because everything syncs in real time and works offline, someone on a train with no signal still sees the list and their changes merge when they reconnect.
Features that matter for this
Slack integration
Sync a task list to a Slack board and add tasks with slash commands.
Kanban board
Drag tasks between status columns.
Waiting-on tracking
A dedicated status for tasks waiting on a reply, call or message so they stop cluttering your active list.
Auto-prioritization
The app orders your list for you using tunable criteria such as due dates, quick wins, importance and dependencies.
AI scheduling
AI splits tasks into work sessions and packs them into free time inside your working hours.
Google Calendar sync
Read events to find free time and write back only the sessions you choose to sync.
Task dependencies
Block one task on another and see the chain in a Gantt view with circular-dependency detection.
Offline-first
Works without a connection and syncs changes when you are back online.
Free plan
A usable free plan with no credit card required.
What Fluidwave does for a small remote team, and where it stops
Fluidwave is honest about its scale. It is built for individuals and small teams: a founding team, a small agency, a distributed team of a handful of people who share a list and need clear owners. Within that scale it does the team basics well. Tasks are assigned to one member, discussed in threaded comments with @-mentions and emoji reactions, grouped by assignee, moved through statuses on a Kanban board, and chained with dependencies visible in a Gantt view. Workspaces keep one team’s list apart from another, and tasks move or copy between them. A list syncs to a Slack channel as a native board.
What it is not is a large-scale project management suite. There are no portfolios, no workload charts, no custom fields and dashboards, no time tracking, and no integrations with Jira or Linear. If your team runs many projects with formal reporting, Asana, ClickUp or monday.com are the right tools, and their pages here say so.
Where Fluidwave is different from all of them is what each member gets for themselves: a Gmail client with AI triage, auto-prioritization, an Active filter and AI time blocking that writes only confirmed sessions to their own Google Calendar. The team shares the work; each person keeps their own way of doing it.
Slack boards and the automations remote teams set up first
Slack is where most remote teams already are, so the Slack integration is usually the first thing a team sets up. Connect the workspace, link each member’s Slack profile to their Fluidwave account, and pick a list to sync. The list appears in a Slack channel as a native Slack List with the Board layout, and tasks post as cards; you choose a card mode from compact to full. Status changes in Fluidwave update the board, and a slash command adds tasks from Slack, with subcommands for the board and its settings. Slack Lists require a paid Slack plan on Slack’s side.
After Slack, the automations that help most are on the task side. When a task changes to Waiting, add the Blocked category so a saved view shows every stalled handoff. When a new task lands on the Inbox list, set the Triage context so the person running standup can route it. When a task changes and its list is Client work, set important so client items rank high for everyone. Each rule previews its matches before saving, and Fluidwave warns when rules overlap or contradict each other.
For a wider view of team-scale tools, the Asana alternatives and Trello alternatives pages compare Fluidwave with the usual options.
Time zones, devices and offline: the practical details
A shared tool is only useful when everyone can reach it. Fluidwave runs as a web app that installs as a PWA on any desktop, as a native macOS app, and on iPhone and Android; Windows and Linux desktop apps are coming. The interface is available in 16 languages, which matters for a team spread across countries.
Everything syncs in real time across devices, and the app is offline-first: a member on a flight or a bad connection keeps working from the local cache, and changes merge when they reconnect. Undo and redo cover every action, including changes the AI makes.
Each member connects their own Google accounts. Nobody at Fluidwave reads anyone’s email, message bodies are never stored, and Google tokens are encrypted before they reach the database. Calendar sync reads events only to find free time and writes only the sessions each person chooses. The app is free forever with no per-seat fee and no credit card, which for a small team removes the usual reason a shared tool is never adopted.
Frequently asked questions
Ready to know exactly what to do next?
Tasks, email, calendar and contacts in one place, with AI that works out what to do next. Free forever, no credit card.