A tool is a set of tables with screens on top. Your recipes live in one table. The meal planner and the shopping list both read it, so a change in one place shows up in the other.
How it works
Look under the hood.
Every OliBench tool runs on the same engine. Here's what's in it, for the people who like to check.
One place underneath
Every tool reads from the same tables.
Change anything
Fields, formulas, screens, rules.
- Add a field: a date, a checkbox, a link to another table.
- Write a formula: "days until due" works itself out.
- Rearrange a screen: what shows, and in what order.
- Add a rule: when a meal is planned, its ingredients go on the shopping list.
Who can see it
Everyone in the house gets their own login. The price stays the same.
Invite people with a link. Each person gets a role: someone who can change things, or someone who can only look. A role covers a whole workspace, not one table at a time.
Adding people never changes the price.
Bringing things in
Spreadsheets, lists, and loose notes.
Import a spreadsheet as a CSV file, and each row becomes an entry. Coming from another database tool? That imports too.
For loose notes, type a sentence like "Furnace filter, 16×25×1, due Friday" and quick-capture turns it into an entry.
Quick-capture uses an AI model, so it needs an AI provider connected with your own key. One note makes one entry.
Reminders
It tells you when something's due.
A tool can send you a notification when a date comes up or a rule fires.
Leaving
Your data leaves with you.
Export everything, any time: the raw database file, a CSV and a JSON file for every table, and a manifest that says what's what. Any spreadsheet opens the CSVs.
The export leaves out passwords and keys.
Seen enough?
Join the list Not open yet. Close.
Join the list and we'll email when it's your turn.