FlowPilot: define a project once, plan it many times.
FlowPilot is a planning methodology for organizations that run the same project many times. We define your project once as a template, and from then on every new run is planned from a single date, with everyone involved told what is coming and when. It is a method we apply with you, not software you subscribe to.
Not a software subscription: no platform fee, no lock-in. Everything is set up in accounts you own.
The same project, planned from scratch every time
Opening a store, a clinic or a branch, onboarding a client, migrating a site, running a yearly event: when an organization does the same project over and over, the steps hardly change. Only the dates and the people do. Yet most teams still plan each run from scratch, copying last time's spreadsheet or project file, re-typing dates and chasing contractors by email.
FlowPilot is the method we built to fix that, first for a bank and now for anyone with the same problem. The method is what lasts. The tools it runs on are chosen for today, belong to you, and can change tomorrow, which in the age of AI they will.
A methodology, not a software product
What our clients need is the method, not one more application to log into. Three reasons:
The method is the hard part
Turning "how we open a store" into a clean template with the right offsets, roles and reminders is where the value is, and where most teams get stuck. That is the work we do with you, and it stays yours whatever tools you use.
The tools move faster than ever
With AI assistants, databases and dashboards changing every few months, a dedicated planning system built today is out of date before it pays for itself. A method does not age; the tools under it can be swapped.
You should own your planning
Your templates and project history are part of how your business works. They belong in accounts you control, not on a vendor's servers, and they should not disappear if a vendor does.
So we do not sell you a platform. We sell the method, apply it to your project, and set it up on tools you own, today Claude and Supabase. If they change, or a better option appears, the method and your templates come with you.
The method in eight principles
The same principles that ran more than 60,000 projects.
Define the project once
The project becomes a template: every activity your team does each time, written down once, with an owner role and a description of what "done" looks like.
One reference date
Every template hangs off one key moment, such as opening day, and each activity is placed relative to it: "sign the lease 120 days before opening".
Three kinds of activity
A task has a deadline, a milestone is a single day, an event happens on given dates. Telling them apart is what makes the dates and reminders right.
Roles, not names
The template says "architect" or "IT provider", never a person, so one template serves every location, region and contractor.
Every run is an iteration
A new store or client is one iteration: a name, a reference date and the people. The full schedule is generated in seconds, not rebuilt.
Move one date, the plan follows
When opening day slips, you move one date and every activity moves with it, except the ones a planner has deliberately fixed by hand.
One master plan
All iterations on one timeline, so you see the whole year, the busy weeks and the clashes at a glance.
People are told, not asked to log in
Contractors, suppliers and colleagues get short notices when they are assigned, when their dates change and before their work starts, plus a calendar feed.
Optional, for teams that want to follow execution as well as plan it: owners record actual start and end dates and expected dates when something will slip, and the planner is warned before a delay reaches the reference date.
Where it comes from
Between 2007 and 2011 we designed and built Project Engine for BNP Paribas Fortis in Brussels, first to manage branch mergers. A planner defined a project once, with roles and tasks timed relative to a pivot date such as the day of the merger. The system computed every deadline, assigned the work to real people and kept them informed.
Project Engine 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. The technology under it has been replaced; the method has not. That is the lesson FlowPilot is built on: the way you plan a repeated project lasts for decades, the tools last a few years.
→Read the Project Engine case studyHow your team works with it
The method needs three things from its tools: one place that computes dates exactly, a way for planners to work, and a way for everyone else to know what is coming. This is how we set it up today, all in your accounts.
Planners ask Claude
In plain English: "set up the Reston opening for 15 May with Jane as branch manager", "what changes if Tysons slips two weeks?". Claude shows what will change and asks before saving or notifying anyone.
A dashboard in Claude
For planners and managers with Claude: every iteration on one timeline, the weeks ahead, who is busy when, and buttons for the common actions.
A read-only master plan page
For managers without Claude: the same master plan in the browser, from a private link.
Stakeholders, no account
Contractors, suppliers and colleagues get short email notices, a personal read-only page and a calendar feed for Outlook, Google or Apple Calendar. No account, no login.
Underneath, a small FlowPilot connector is the only way in to your planning data. It offers just the actions the method allows (create an iteration, preview a date move, apply it, assign a person, list what is coming), and the dates themselves are computed by tested rules in the database, never by the AI. The connector uses the Model Context Protocol, an open standard that other AI assistants support as well, so Claude is today's choice, not a dependency.
How it works
-
01
A free planning review.
Thirty minutes on the project you repeat, how you plan it today and how many runs a year you have. Within two business days you get a one-page note: whether FlowPilot fits, the size of the template, which package and a fixed price.
-
02
Template workshops.
Week 1: two working sessions with your project lead and one or two people who run the project on the ground. We start from your last run, not a blank page, and you get the draft template: activities, kinds, offsets, durations and owner roles.
-
03
Blueprint.
Week 2: we check the template against two past runs and one upcoming run, then agree the notification rules. You get the Blueprint, ready to use in any tool.
-
04
Setup.
Weeks 2 to 4, with FlowPilot Setup: the planning database and connector in your Supabase project, the planner skills and master plan dashboard in your Claude account, the stakeholder pages, and your template loaded.
-
05
First live runs.
Weeks 4 to 5: your planners create their upcoming iterations with us beside them, and the first notices go out to real contractors.
-
06
Training and handover.
Weeks 5 to 6: a hands-on session for planners and a short guide, then a 30-day check where we adjust what is not working. You end with a team that runs it without us.
Two fixed-price packages, one optional plan
The Blueprint is useful on its own: a team can run the method in the workbook it receives, and its fee is credited in full if you move to FlowPilot Setup within 60 days. The tools are separate, paid by you to the vendors.
- Planning review and two template workshops
- The template: activities, kinds, offsets, durations, owner roles and reference date
- A planning workbook that computes a run's dates from its reference date
- Notification rules: who is told what, when, and the reminder schedule
- A short playbook: create a run, move it, keep the template up to date
- Usable in any tool
- Everything in the Blueprint
- Planning database in your Supabase project, every date computed by tested rules
- The FlowPilot connector and Claude skills for planners: create a run, preview and apply a date move, assign people, weekly lookahead
- Master plan dashboard in Claude, and a read-only master plan page for people without Claude
- Stakeholder notices by email, personal read-only pages and calendar feeds
- Your past and upcoming runs loaded, up to ten iterations
- Planner training, a guide and a 30-day check
- One template, up to 200 activities and 10 planners; larger setups quoted
- Template changes
- Help with new runs
- Upkeep as the tools evolve
- A monthly check of notices
- Month to month, cancel any time
Fixed fees: half when work starts, half when the first iteration goes live (Blueprint: half on delivery). FlowPilot Care: billed monthly in advance; cancel any time and it stops at the end of the paid month. Your tools: you create the Claude and Supabase accounts and pay the vendors directly; we never resell them or mark them up. Ownership: the template, workbook, playbook, database, connector, skills, dashboard, pages and any code are yours. Travel: on-site work in the Washington DC metro is included.
What the tools cost you
List prices as of October 2026, for US customers, before tax. Prices change, so we confirm them in your planning review note.
| Tool | Who needs it | Price |
|---|---|---|
| Claude, Team plan | Planners, and managers who want the dashboard inside Claude | From $20 per person a month billed annually, or $25 billed monthly. If you already have Claude, nothing new to buy |
| Supabase, Pro plan | One project for the planning database | From $25 a month. The free plan pauses a project after a week without activity, so it is not suitable for live planning |
| Notices to stakeholders | Sent from a mailbox in your Microsoft 365 or Google Workspace, or a transactional email service. Usually no extra cost | |
| Stakeholders | Contractors, suppliers, colleagues | Nothing. They never need an account |
Example: three planners on Claude Team billed annually plus one Supabase Pro project come to about $85 a month. There is no FlowPilot license and no platform fee on top.
Who it is for
- Organizations that run the same kind of project at least ten times a year, with a dozen or more activities and several outside parties each time
- Multi-unit brands and groups: restaurants, retail, franchise systems, dental, veterinary and medical groups, med spas, fitness, parking and facility operators
- Service companies that onboard a new client or site on the same plan every time, and organizers of recurring events
- Teams that plan today in spreadsheets, email and generic project tools, and lose time re-planning and chasing people
- One-off projects: the method pays off from the third or fourth run
- Projects that need a critical path with dependencies between hundreds of tasks, such as trade-level construction scheduling. FlowPilot plans by offsets from one date, deliberately; tools like Primavera P6 or Procore are built for the other case
- Buyers looking for an off-the-shelf software subscription: FlowPilot is a method we apply with you, set up in your accounts
Data and ownership
- Everything lives in your accounts. Your Supabase project, your Claude organization, your mailbox. We hold none of your planning data.
- Little personal data. Stakeholders are a name, an email address and the roles they fill. Nothing else is needed.
- Exact dates, human approval. Dates come from the database rules, never from the AI's own arithmetic. Claude shows what a change will do and asks before saving it or notifying anyone.
- One narrow door. The FlowPilot connector only offers the planning actions of the method; it cannot run arbitrary queries on your data.
- Personal links, read-only. A stakeholder's page and calendar feed are reached through a personal link that only reads, and that can be reset if it is shared by mistake.
- No lock-in. The template is a documented workbook as well as a database. If you change tools in five years, the method and your templates come with you.
What we do not do
- We do not sell you a platform, a license or a software subscription, and there is no recurring fee to us unless you choose FlowPilot Care.
- We do not resell or mark up Claude or Supabase, and we take no commission from Anthropic or Supabase.
- We do not let the AI decide dates or send notices on its own: the rules compute, a planner confirms.
- We do not replace your construction, accounting or field service systems; FlowPilot plans and informs around them.
- We do not promise a time saving we have not measured with you; the 30-day check measures it.
We are independent. Imhauser Technologies is not affiliated with, endorsed by or a reseller for Anthropic or Supabase. We use their products because they are the best fit today, and the method does not depend on them. Claude is a trademark of Anthropic, PBC. Supabase is a trademark of Supabase, Inc.
Questions people ask
Is FlowPilot software?
No. FlowPilot is a planning methodology. We apply it to your project and set it up on tools you own; today that is Claude and Supabase. There is no FlowPilot app to subscribe to and no license to renew.
What happens when Claude or Supabase change?
Your planning rules are written down in your Blueprint, your data sits in a standard Postgres database, and the connector uses an open standard. If a tool changes or a better one appears, the method and your templates move with you. FlowPilot Care covers the upkeep.
Do contractors and suppliers need Claude?
No. They get short email notices, a personal read-only page and a calendar feed. Only your planners use Claude.
We do not use Claude. Can we still use FlowPilot?
Yes. The Blueprint comes with a workbook that computes a run's dates from its reference date, and many teams start there. The setup can also be adapted to another AI assistant or to browser screens only; we quote it after the planning review.
Can AI get the dates wrong?
Not in FlowPilot. Dates are computed by rules in the database that we test; Claude only asks the database and shows you the result.
Does it handle dependencies between tasks?
FlowPilot plans every activity from one reference date, which is what kept Project Engine simple enough for 60,000 projects. If you need a full critical-path schedule, a scheduling tool is the better choice, and we will say so in the planning review.
Who owns the template and the data?
You do, along with everything we build: the template, the workbook, the playbook, the database, the connector, the skills, the dashboard and the pages. It all lives in accounts you control.
Are you an Anthropic partner?
No. We are an independent consultancy, and we set FlowPilot up with Anthropic's own documented tools, in accounts that belong to you.
Book a free planning review
In 30 minutes we look at the project you repeat and how you plan it today. Within two business days you get a one-page note: whether FlowPilot fits, the size of your template and a fixed price.