Deadline-driven work, planned
Recurring deadlines, planned from the due date.
Describe the month-end close, the board pack or the customer renewal once, as activities placed before and after a due date. Every run comes out as a dated plan with an owner on each step, and Flowstate does the chasing.
Month-end close
Due Fri 2 Oct 2026 · 16:00 · Europe/Oslo
- −2 wkMon · 10:00
Kick-off meeting
DoneMon 21 Sep · Anna
- −3 d09:00
Collect bank statements
Email sentTue 29 Sep · Jonas
- Same d14:00
Sign off the close
ScheduledFri 2 Oct · Mari
- Due16:00
Fri 2 Oct 2026
Every offset is measured from here.
- +1 moday 5 · 08:00
Send invoices
ScheduledThu 5 Nov · Notification
How it works
01 Describe
Say where each activity sits
Three days before. The Monday two weeks before. The 5th of the month after. The process is written once, without dates.
02 Give it a due date
Type one in, or let something supply it
Start a run by hand, or let a calendar event provide the due date.
03 Let it run
Flowstate dates, notifies and tracks
Every activity gets a real date and an owner. The owner gets one email with one link, and the whole run stays on one page.
Not a to-do list. Not a workflow engine.
A plan generator for work that follows the same shape every time.
- Offsets, not dates.
- The definition never goes stale. Each run resolves its own dates from its own due date.
- Follow-up without chasing.
- The owner gets one email with one link. It works without signing in and stays valid for 30 days.
- Due date moved? Reschedule.
- Activities that haven't happened are recalculated from the new date. What already happened keeps its history.
- 09:00 in Oslo stays 09:00 in Oslo.
- Times are planned in the workspace timezone and survive daylight-saving changes and teammates in other regions.
Start runs by hand or from Google Calendar and Outlook Calendar events (beta). Webhooks, Slack, Jira and Trello are on the roadmap. See integrations →
Start with one process.
Sign in with your email, name your workspace and publish a run in a few minutes.