An assistant that knows the whole operation
An assistant that delivers real-time business intelligence and surfaces anything that needs attention.
A brief that rewrites itself as the day changes
The dashboard opens on a written brief: leads, active work and scheduling, each narrated in a plain paragraph rather than a wall of charts. Under each section sit short action notes that link straight to the place you can act — the inquiry that has waited longest, the job that is finished and not yet billed.
The leads section watches for inquiries nobody has answered, wins nobody has converted, and estimates that have sat out too long. Active work watches for jobs ready to bill, invoices aging, parts still open, and a technician’s raised hand — a job flagged not complete. Scheduling narrates the shape of the week.
This is not a report that goes stale by ten o’clock. When your data changes, the brief rewrites. Accept two leads and book one job, and the brief now says so. And it stays short on purpose — a few action notes per section at most, so the brief reads as a briefing, never a backlog.
What’s urgent is decided by rules, not by a model’s mood
The part worth being skeptical about is the part we made boring on purpose. Which items surface, and in what order, is decided by deterministic rules — plain, testable code, not a model’s judgment — rules that put an unanswered inquiry above pipeline housekeeping and a declined crew booking above nearly everything. The AI’s only job is to write the sentence. It cannot invent an emergency, and it cannot quietly drop one.
Ask it anything about your own operation
The same assistant sits in the header of every office page. Ask what’s still unscheduled this week, what a job was billed at, which estimates are sitting unanswered, what parts the crew has asked for — it answers from your live customers, schedule, estimates, slips and parts. And it shows its work: every lookup it runs appears as a visible step, ticked as it lands, so an answer is never a black box. Links in its answers go to the real page inside the product, where you can act on what it found.
Ask it how do I — how do I take a deposit, how do I reopen a closed job — and it answers by quoting the same help pages a person would read, rather than improvising from memory. One assistant, both kinds of question: what is going on, and how do I do this.
What does the AI assistant actually do?
Two things. It writes a brief of where the business stands — leads, active work and scheduling, each narrated in plain sentences with links to the place you can act — and it rewrites that brief as your data changes. And it answers questions about your own operation from live data: customers, schedule, estimates, slips, parts and money.
How do I know what it tells me is right?
Because the judgment isn’t left to the model. What surfaces in the brief, and in what order, is decided by deterministic rules — plain, testable code — and the AI only writes the sentences. When you ask a question, it looks the answer up in your live data and shows each lookup as a visible, ticked step, so you can see where the answer came from.
What can I ask it?
Anything you could work out yourself from your own records: what’s in the inbox, what’s still unscheduled this week, what a job was billed at, which parts requests are open. And “how do I…” questions — those it answers by quoting the same help pages a person would read, rather than improvising from memory.
Who can ask my assistant for answers?
TODO — answer pending. This chapter does not yet state who inside the business can ask the office assistant for answers.
Is this the same assistant my customers talk to?
No. The assistant in this chapter works for you, in the office — the brief and the answers. The assistant on your website talks to prospects and captures leads, and it answers from the knowledge base you wrote, not from your books — so it can’t promise something you never put in writing. They are kept separate on purpose.