Intelligence made collaborativesharpersharedhands-on

You decide. Fluid does the rest.

EMTHWIFOPA

Be among the first to join the beta.

plusfluid.app

Fluid

Sarah M.11:02

The mobile journey is still the main blocker, we really need to simplify it.

Loïc B.11:03

Agreed, plus personalized goals per household to keep people motivated.

FluidAI11:03

Two angles noted, simplification and personalization. Shall I look for the most frequent anomalies?

Amine K.11:04

Above all detect anomalies in real time, not just at the end of the month.

Chloé R.11:05

And compare with similar households, anonymously, it gives a benchmark.

FluidAI11:06

I grouped your ideas into 4 angles and wrote the workshop summary.

Scenario workshop summaryCreated 2 minutes agoFour angles stand out for the next iteration, ranked by impact and effort…

Sources

What would you like to do?

Scenario workshop summaryCreated 2 minutes ago 3 tracks · 1 adoptedDocsBoardCodeSMLBAK

Scenario workshop summary

Summary SM

The workshop brought together four participants around the energy scoping. Four angles stand out for the next iteration, ranked by estimated impact and effort.

What would you like to change?BIAa

The mobile journey remains the priority. Real-time anomaly detection comes right after, pending validation by the data team by the end of the month.

Decisions LB

Selected priorities

The committee approved two workstreams for the next sprint and postponed two topics needing further scoping before launch.

Open points

Mobile journey. Simplification approved, design to scope with the product team.
Real-time anomalies. To test with the data team before the end of the month.
Household comparison. GDPR framework to confirm with legal.

Next steps

A follow-up is planned next week to approve the mockups and settle the two postponed topics.

Week 1. Mobile journey scoping and first mockups.
Week 2. Anomaly detection test on a sample.

TFieldDataMachine stops never explainedReadings still on paperMaintenance swamped on MondaysFailure history in the ERPNo sensors on the motorsLine 4 · sensor layoutScoping note v1Written by FluidSelected prioritiesgrouped by FluidVibration sensors on the motorsReal-time maintenance alertSarahLoïc82%

export_anomalies.pyREADME.md

"""Weekly anomaly export for the committee."""import pandas as pd CRITICAL_AGE_H = 48 # hours without resolution def export_anomalies(): df = pd.read_csv("exports/anomalies_ligne4.csv") open_items = df[df["status"] != "resolved"] critical = open_items[open_items["age_h"] > CRITICAL_AGE_H] report = critical.groupby("team").agg( total=("id", "count"), avg_age=("age_h", "mean"), ) report.to_excel("anomalies_semaine.xlsx") return len(critical) print(f"{export_anomalies()} anomalies")

Python 3.12 · tested · ready to schedule

Fluid works for you.
And with you.

Fluid takes an active part in every phase of your project, from brainstorming to delivery. You describe it, it sets the context and breaks it down into gantt, tasks, milestones, sprints and budget. The coordination work then moves forward without you having to carry it. Follow-ups, briefs, tracking, the day's priorities, Fluid keeps them current at all times. You keep the decisions, Fluid keeps the pace.

Tracking · ERP rollout

You're rolling out a new ERP. Committee on Thursday, three workstreams to move.

Fluid

Overnight I followed up with the three leads and reranked your priorities.

Most urgent this morning, get the payroll batch signed off.

You

And Thursday's committee, do we have enough to hold it?

Fluid

Yes. The summary is ready and I've anticipated the two points that will block.

Lead follow-upssent
Priorities for the dayupdated
Thursday's committeeprepared

Workshop · Minutes

You're out of a two-hour product workshop. Plenty of decisions, few notes.

Fluid

The workshop minutes are written. Decisions, who does what, risks.

Ready to send as soon as you approve.

You

Perfect, send it to the participants.

Fluid

Sent to the participants and the sponsor. I created the actions and scheduled a check-in Friday.

Workshop minutessent
Actions and ownerscreated
Friday check-inscheduled

Workshop · Client portal

You're starting a client portal for the new term. Several teams to coordinate.

You

I'm starting a client portal for the new term. Design, dev and support involved.

Fluid

Got it. Is the date firm, and who signs off on design and on support?

You

Date is firm, September. Karim on design, Léa on support.

Fluid

I structure it into phases and milestones, create the tasks and alert you at every step.

Phases, milestones and roadmapcreated
Tasks and progress trackingenabled
Team and approversaligned

Workshop · Feasibility study

You need to scope a feasibility study, then send it to secure a budget.

You

I want to scope a feasibility study before asking for a budget.

Fluid

Got it. On what scope, and for what decision deadline?

You

Replacing our billing tool. Decision expected end of July.

Fluid

I structure the study, the risk analysis and the recommendation. In parallel I prepare the budget case.

Study plan and scopestructured
Risk analysis and recommendationready
Budget caseprepared

For you · follow-ups & tracking

The right deliverable.
For every audience.

Every document is written and tailored to whoever will read it. The same topic isn't told the same way to the field, to the technical team or to leadership. Fluid prepares the right version for each audience, in your brand style. You review, you approve, you send.

MinutesSteering committee

Decisions

Actions

Risks

Progress reportData project

82 %Progress

14 / 16Milestones met

3Open risks

PresentationLeadership

Project progress

SpecificationsERP rollout

Requirements

Technical constraints

Expected deliverables

Migration planERP

Work packages & dependencies

Milestones

Projected workload

Workload planMigration

Scoping

Data migration

Testing

Cutover

Action planQuality

Corrective actions

OPS

Compliance

Email per audience2 versions

To the field

Logistics package schedule

The start moves to the 15th. Prepare the site access and the equipment list for Monday.

To leadership

Logistics update

A controlled 5-day shift, with no impact on the budget. A decision is expected Thursday.

These deliverables can carry your signatures and brand guidelines.

The project lives on.
You keep the thread.

When the team changes, the context stays. Decisions, reasoning, trade-offs, meetings and key milestones stay connected to the project, in one place. After a pause, a restart or a change of people, you pick up the thread again in minutes. No one starts from scratch.

Parcours adopté Pistes en cours À explorer

One space. For everything.

Workspace

The single space where the whole project lives. Notes, tasks, documents and decisions in one place, with no juggling between ten tools.

"I didn't need another project management tool. I needed to stop spending my days keeping the project alive instead of moving it forward."

I ran Data, AI and industrial projects for years. A project today means ten different disciplines. Each one has its own tools, its own language, its own urgencies.

Someone has to tie it all together. No one has the time. Fluid does.

It understands the project. It prepares the deliverables. It keeps the context. Not one more tool. What every other one was missing.

Patrick NgungaFounder & CEO

Frequently asked questions.

What exactly is +Fluid?

Your single workspace for your projects, powered by an AI teammate that runs the project for you. It files, recontextualizes, follows up, orchestrates, alerts and produces your deliverables. You decide, Fluid executes.

What's the difference between "+Fluid" and "Fluid"?

+Fluid is the environment, your workspace. Fluid is the engine, the brain that understands the project, suggests, acts and talks to you. The "+" is everything this space brings to life around the engine.

Where does the project memory come from?

Fluid draws on your workshops, notes, meetings, documents and decisions to maintain a usable project memory.

What can I do from day one of the beta?

Launch a project in an interactive workshop (Fluid asks the questions and structures the project), let Fluid orchestrate the day to day (follow-ups, tracking, priorities), automatically organize the context, and generate ready-to-send deliverables, tailored to each audience.

Who is +Fluid for?

Built for cross-functional projects where too much information moves between meetings, emails, decisions and business teams.

Is my data secure?

Security is a design principle, not an option. Isolation of your data, GDPR compliance, and content (documents, emails, transcripts) always treated as data that belongs to you, never reused without your knowledge.

How much does it cost?

The beta is free. Early members shape +Fluid and move to the front of the line at launch. Pricing will be announced with a lasting benefit for beta testers.