Ask by email or in chat — "is the van free Thursday?" — and your Aivell checks the resource's calendar, books it or offers the nearest alternative, and keeps a usage log. Conflicts are settled by rule instead of by whoever shouts loudest, and every request is handled on the box, inside your network.
starts when: Someone asks for the van, the big room or the projector
Every shared thing in a company has the same failure mode. The van that two crews loaded plans around, the meeting room that was “definitely booked”, the projector that left for a client demo and never signed back in. The tracking system is usually a whiteboard, a group chat, or the memory of whoever answered — and untangling the collisions is part of the $17,000 per employee per year that admin quietly costs.
Proper booking software exists, and mostly goes unused: field crews don’t open a portal at 6am, and nobody maintains a system that is slower than shouting across the yard.
Asking stays as easy as shouting — the answer just gets reliable:
Guardrails hold the boundaries: resource calendars only, append-only logging, replies to the requester alone. The rules about how your fleet and rooms actually work stay in plain language, editable the day the rules change.
No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:
take requests by email or chat for the vans, the big room and the projector
every resource has its own calendar — check it before promising anything
free? book it with the requester's name and what it's for
taken? offer the nearest free slot and say who holds the current one
vans return by 6pm — overnight or weekend use needs a yes from Luca
two requests for the same thing within minutes — first come wins, tell the other
log each booking in the usage sheet, one row, with purpose
friday at 4, send Luca next week's van plan
Connected with single-click passkeys — no copied tokens, no OAuth hell.
Every tool can be limited to exactly what this chore needs. For this one, you might set:
The rule in the chore happens — typically first request wins, and the second requester is told immediately, by name, who has it and what is free instead. The argument that used to happen at 7am in the yard happens on Thursday, in writing, with time to solve it.
No — they write an email or type into the chat, the way they already ask a colleague. "Need the trailer Wednesday morning for the Rossi site" is a complete booking request. The calendar discipline is the Aivell's job, not theirs.
In your own calendars and your own sheet, processed by the box in your office. Who drives where, which client site, which equipment — operational details like these never pass through a cloud scheduling product.
Yes — the rules are sentences in the chore. Vans back by six, the projector never leaves the building, overnight use needs Luca's approval. Your Aivell applies them to every request; the guardrails make sure it cannot book around them.
Cc a private AI colleague on the 'let's find a time' thread: it collects availability, finds the slot, books the room and survives the reschedules.
Customers email for an appointment; a private AI colleague checks the calendar, proposes slots, books and confirms — nothing leaves your office.
Stock levels watched nightly in your own database, reorder emails drafted per supplier — and nothing is sent until you approve it with a tap on your phone.
Quote requests logged, site photos turned into reports, subcontractor certificates chased — an AI colleague that keeps your bids on site.
An on-premise AI colleague for manufacturing back offices: turns order emails into system entries, works supplier portals, watches stock, reads shop-floor photos.
An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.
You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.
onboard inference · air-gapped · fixed monthly fee