For consultants
Fluidwave for consultants: a task manager for engagements, deliverables and client email
Engagements overlap, deliverables have dependencies and the client relationship lives in email. Fluidwave links the thread, the task, the calendar session and the contact, then blocks the hours to get the work done, in a free app that works on the plane.
Jobs to be done
See which deliverable is on the critical path
- Today
- Three engagements with staggered deadlines, each with a sequence of deliverables that depend on each other. Which one is actually on the critical path this week?
- With Fluidwave
- Each engagement is a project. Tasks carry due dates, duration estimates and dependencies, and the Gantt view shows the chain by day, week or month with circular-dependency detection. Auto-prioritization orders across projects by blocked, overdue, due date and importance, so the top of the list is right regardless of client.
Protect hours for the deliverable, not just the calls
- Today
- Client calls fill the calendar and the actual analysis, writing and modeling gets pushed into evenings. Billable hours you did not plan for.
- With Fluidwave
- Drag deliverables onto the calendar as work sessions, or let AI scheduling pack them into free time inside working hours with breaks around client calls. A two-day analysis splits into sessions with the remaining minutes shown. Sync the sessions you choose so the shared calendar shows you as booked.
Turn client threads into tracked work
- Today
- Scope changes, data requests and approvals arrive as email replies in long threads. Half of them turn into work, and that work is easy to miss.
- With Fluidwave
- AI triage summarizes and scores every thread. One key turns a client request into a task with the email linked and the client contact attached. Reply from inside the app and, if the reply creates a follow-up, set the task to Waiting with the kind of reply expected.
Keep stakeholder context next to the work
- Today
- At the end of an engagement you need to remember who agreed to what, and the answer is scattered across notes, email and memory.
- With Fluidwave
- Link every stakeholder as a contact synced two-way with Google Contacts. The contact page shows organization, title, notes and the count of linked tasks. @-mention contacts in task comments so the context of a decision stays with the task instead of in a separate document.
A day with Fluidwave
- 1
Morning: triage client mail into engagements
Open Triage across all connected Gmail accounts. Each client thread comes with a summary, a priority score and a suggested action; an automation has already starred anything from the engagement sponsor and archived vendor pitches. Press Task on a data request and it becomes a task on that engagement’s project with the thread linked. Press Reply on the approval you have been waiting for, answer from inside the app, and mark the waiting task done. The flow ends at inbox zero and the day’s new work is already sorted by client.
- 2
Let AI block the week around client calls
Open the calendar. Client calls are already there from Google Calendar; Fluidwave reads them only to find free time. Run AI scheduling and the unscheduled deliverables land in the gaps, inside your working hours, with breaks before and after calls. Long tasks split into sessions across the week. Drag a session to Thursday if the data is not arriving until Wednesday. Confirm the sessions you want and sync them, so anyone looking at your calendar sees the analysis block as booked time rather than an open slot.
- 3
Check the critical path across engagements
Switch to Gantt view and zoom to the week. Each engagement shows its deliverables with dependency arrows. Auto-prioritization already ranks blocked tasks last and overdue first, so the Active list matches the chart. If a client delays a review, drag the dependent tasks out and the chain moves with them. Fluidwave detects circular dependencies when you add them, which is the usual way a plan quietly becomes impossible.
- 4
Track approvals and subcontracted work
Every request that goes out to a client, such as data, sign-off or interview scheduling, moves to Waiting with the kind of reply expected. It leaves the Active list and collects in the Waiting view. Once a day, scan that view by due date and nudge on the linked thread. When you subcontract a piece of work, assign the task to a collaborator in your workspace and discuss it in threaded comments, or set it to Delegate and send it to a human assistant through the marketplace with a fixed budget and deadline.
- 5
Work offline, then run the weekly review
On a flight or in a client site with no guest Wi-Fi, keep working. Fluidwave is offline-first: tasks, sessions and the emails you have opened are cached locally, and everything syncs when you reconnect. On Friday, run a weekly review: close the Waiting items that came back, reschedule the sessions that slipped, and look at next week in Gantt for any dependency that has crept onto the critical path. Recurring tasks handle the monthly status report and invoice, with a single instance skippable when an engagement pauses.
Features that matter for this
Time blocking
Drag tasks onto the calendar as work sessions, resize them and split a task across several sessions.
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.
Email to task
Turn an email into a task with one action and keep the thread linked to it.
AI email triage
Every incoming thread gets a summary, a priority score and a suggested action you confirm with one key.
Task dependencies
Block one task on another and see the chain in a Gantt view with circular-dependency detection.
Gantt chart
Timeline view with day, week and month zoom and dependency arrows.
Waiting-on tracking
A dedicated status for tasks waiting on a reply, call or message so they stop cluttering your active list.
Google Contacts sync
Two-way sync with your address book so contacts can be linked to tasks and mentioned in notes.
Offline-first
Works without a connection and syncs changes when you are back online.
Why consultants fall between to-do apps and project suites
Consulting work sits between two kinds of tools. A personal to-do app is too flat: it has no sense of dependencies, no timeline and no idea that a deliverable due Friday cannot start until the client sends data. A full project management suite is too heavy: it assumes a team, a portfolio and a process, when you mostly need one person’s view across three engagements.
The second gap is that the client relationship happens in email, and most task apps live in a different window. Every scope change, data request or approval has to be re-read and retyped before it becomes trackable.
Fluidwave sits in the middle deliberately. Each engagement is a project with tasks that carry dependencies, and the Gantt view shows the chain with circular-dependency detection. The Gmail client is built in, so a thread becomes a task in one key with the email and the client contact attached. Time blocking is a drag onto the calendar, and AI scheduling packs deliverables into free time around client calls. The Waiting status keeps approvals off the Active list until they come back. It is a single-person system that scales to a small team, and it is free forever.
Automations consultants set up first
The visual automation builder connects a trigger to conditions and actions across email and tasks, with a live preview of what each rule matches. Consultants usually start with these:
- When an email arrives from one of the contacts you pick for an active engagement, star it and set the triage bucket to Reply, so client mail never queues behind vendor outreach.
- When an email arrives whose subject contains “data” or has an attachment from a client domain, convert to a task on that engagement’s project and set the due date for tomorrow.
- When a task changes to Waiting, add the Follow-up category so a saved view collects every open approval.
- When an email arrives that is a newsletter, archive it; then bulk-unsubscribe from the Newsletters view with one-click unsubscribe.
- When an email arrives requesting a meeting, draft an AI reply with instructions like “Thank them and offer a call next week, and say I will confirm a time within a day.” The draft waits for you to send.
Fluidwave warns when two rules would conflict on the same items or when an action is redundant, and each rule can be applied to the existing backlog. If writing rules is not your style, move an email into a bucket during triage and add a note like “Everything from Acme is a task on the Acme project”; Fluidwave drafts the rule from it.
What Fluidwave leaves to other tools
Fluidwave does not track time for billing, generate invoices or produce client-facing reports. Calendar sessions do show how many hours went into a deliverable, which is a useful sanity check against the estimate, but the invoice still comes from your billing tool.
Email is Gmail and Google Workspace only. If a client requires you to work from their Outlook tenant, that inbox stays outside Fluidwave, though the tasks it generates can still live inside. The desktop app is macOS today, with Windows and Linux coming; the web app installs as a PWA anywhere, and there are iPhone and Android apps.
If you manage a consulting team with resource planning and client-facing dashboards, a project suite such as Asana or ClickUp is the right layer for the firm, and Fluidwave can be each consultant’s personal command center next to it. Fluidwave also exposes a Claude MCP connector, so you can create and update engagement tasks from a Claude chat while drafting a deliverable.
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.