Routines
Recurring work that runs by itself, and stops where it should.
Set recurring work to run on a schedule.
Quotation follow-up
Every Monday, 08:00
Where general tools stop
Vibe coding
A vibe-coded script runs until it silently stops. Nobody is told, and there is no history to look back at.
ChatGPT or Claude
ChatGPT or Claude can schedule a prompt for one person. A company routine needs shared ownership, stops for approval and a history that others can check.
The problem
Follow-ups, weekly checks and month-end steps depend on someone remembering them. They slip as soon as it gets busy, and classic workflow tools need an expert for every change.
The solution
Describe the routine, choose when it runs and where it has to stop for a person. Every run is recorded: what it did, where it waited, and who answered.
Try it yourself
See it on screen.
Interactive example with sample data
Routines
What is happening
What you get
- Runs on a schedule, or when something happens in a connected system.
- You choose the stops: where it asks first.
- A history of every run, with failures on top of the list.
Per project we specify which parts already exist, which are configured, which are integrated and which are newly built.
Use cases
See what this looks like in practice.
Food manufacturing
Truck tours planned from the day's orders
Large public events
One platform for every volunteer and crew member
Events and sponsorship
From raw survey data to a verified report
Building technology
A sales workspace from first call to order
Construction and fire protection
From building model to a reviewed quote list
Insurance
Product benchmarks that stay up to date
Insurance
Every new lead answered with a first analysis
Insurance
Claims-history certificates without the spreadsheet