FlowPilot: define a project once, plan it many times.
FlowPilot is planning software for organizations that run the same kind of project many times: opening a branch, launching a store, onboarding a client, organizing a yearly event. You define the project once as a template. For each run you pick a key date, and FlowPilot computes every other date.
Not available yet. A free beta is planned.
It started as Project Engine
Between 2007 and 2011 we built Project Engine for BNP Paribas Fortis in Brussels, first to manage branch mergers. A planner defined a project template with stakeholder roles and tasks timed relative to a pivot date, such as the day of the merger. The system calculated the deadlines, assigned the tasks to real people and notified them.
It went on to coordinate more than 60,000 projects, including nearly 500 branch mergers, and it is still in use more than 15 years later.
FlowPilot is that engine rebuilt as a multi-tenant service. What ran for years inside a large bank becomes a product any team can use.
→Read the Project Engine case studyHow it works
Define the template once
The planner lists the activities of the project: tasks, milestones and events. Each one is placed relative to a key date, for example "sign the lease 120 days before opening day".
Pick a date for each run
Each run of the project is an iteration. The planner picks its reference date and assigns the people, and FlowPilot computes every date. Moving the reference date moves the whole plan.
Everyone is kept informed
The people involved hear about it automatically: when they are assigned, when their dates change and before their activities start.
What stakeholders get, without an account
Stakeholders are the colleagues, contractors and suppliers who do the work. They never create an account.
Short email notices
When they are assigned, when their dates change and before their activities start. The emails carry no project content, only a notice and a link.
A personal read-only page
Each stakeholder has a page of their own with the details. It is read-only, and there is nothing to log into.
A calendar subscription
Their activities appear in the calendar they already use: Outlook, Google Calendar or Apple Calendar.
Who it fits
Organizations that run the same kind of project many times, where the steps stay the same and the dates change.
- Opening a branch
- Launching a store
- Onboarding a client
- Organizing a yearly event
The free beta plan
A free beta is planned. Until it opens, FlowPilot is in private development and the waiting list is open.
How it is built
We build FlowPilot ourselves, on the stack we use for client work.
Join the waiting list
FlowPilot is in private development. The waiting list is open on flowpilot.net.
Questions
Can I use FlowPilot today?
Not yet. FlowPilot is in private development. A waiting list is open at flowpilot.net, and a free beta is planned.
What kind of project is FlowPilot for?
The kind an organization runs many times: opening a branch, launching a store, onboarding a client, organizing a yearly event. The project is defined once as a template, and each run is planned from a single reference date.
Do stakeholders need an account?
No. Stakeholders never create an account. They get short email notices, a personal read-only page with the details and a calendar subscription for Outlook, Google Calendar or Apple Calendar.
What is in the emails FlowPilot sends?
A notice and a link. The emails carry no project content; the details are on the stakeholder's personal page.
What will the free beta include?
The free beta plan is 1 user per organization, 1 project template, 10 iterations, 100 stakeholders and 200 activity definitions.
How is FlowPilot related to Project Engine?
Project Engine is the planning tool we built for BNP Paribas Fortis between 2007 and 2011; the case study is on this site. FlowPilot is the same engine rebuilt as a multi-tenant service.
Who makes FlowPilot, and where is it hosted?
Imhauser Technologies LLC, in McLean, Virginia. FlowPilot runs on Microsoft Azure in the United States.