Use Cases
What a local database looks like
Schema walkthroughs for common use cases. Each page explains the table structure, shows how an agent works with it, and notes where the approach falls short.
How the examples work
Each example starts from the tables. It names each table and its fields, and shows how the tables relate: a contact has many interactions, and an item has many stock movements. Then it shows the forms and lists you work in day to day, and what an agent can do in the same tables when you let it.
Each example also says where a local database falls short, for example when several people must edit at once from different places. To see a finished project before you build your own, open the Recipes sample database. To build one, start with the customer database or the inventory database and the user guide.
Guides
- Customer & Client DatabaseTwo tables: clients, and the interactions logged against each client, each with a next follow-up date. For freelancers and small shops that pay a monthly CRM fee for a list of names and notes.
- Inventory & Equipment DatabaseThree tables: items, locations and stock movements. For tracking stock, serial numbers and equipment without an ERP subscription.
- Sample database: RecipesA worked example you can download and open: four linked tables with records, photos, layouts and a print layout.