Thorbis Brain · Roadmap
It could run the whole shop. You decide how much.
One copilot across dispatch, estimates, invoices, and the phones. It watches, drafts, and proposes; anything that matters waits for your approval. Included when released, and costly runs show an estimate first.
The owner
A workforce with rules. Not a chatbot with opinions.
The board stays the record. Money stays money. Brain drafts, compares, and waits for a person.
01
It proposes. You dispatch
Closest after Birch is a suggestion. The board does not move until you do.
02
Find the money that wasn’t collected
Due that should have been paid on the drive. Confirmed, likely, and not sure, kept apart.
03
Approvals sit with a person
Agents wait. Copilots draft. A named owner still sends, still closes, still collects.
04
Assistive AI is already in Core
Naming and summaries stay free. Brain is the longer work. If it is down, the shop still runs.
Two tiers
Some of it is already in Core. The rest says roadmap.
In Core · ships with the product
Assistive AI
The quiet layer: it fills the intake form while the call is still going, suggests the duplicate before you create it, cleans up job notes, summarizes the thread, and answers plain-English questions like “unpaid invoices over $5,000 from last month.” Useful when available, invisible when unnecessary, and never required for the product to be correct.
Roadmap · after the core product ships
Brain: the governed workforce
Named agents with scoped jobs: intake, estimate follow-up, invoice collection, an owner’s briefing. Durable runs you can watch step by step, pause, or take over. An approval queue where every proposal shows the action, the records it touches, the reason, and the cost before you say yes.
The dial
Autonomy is a dial. Not a switch.
Every signal climbs its own ladder, one rung at a time, at your pace. Overdue-invoice reminders can earn their way to running under a rule you wrote. A refund never climbs past a signature.
01
Observe
It watches the board, the phones, and the ledger. Nothing moves.
02
Explain
Why did booked revenue drop? Ranked causes, with the evidence attached.
03
Recommend
What to do about it, as a list you can ignore.
04
Draft
The estimate, the text, the schedule change. Written, not sent.
05
Request approval
The send button is yours. Every proposal shows its work.
06
Governed assistance
Rules you wrote run on their own. Everything else still waits.
What it will do
The work it takes off your desk.
Every tool below is planned, and every one follows the same law: it proposes with evidence, and a person commits.
Why did the money move
Booked revenue, completed work, cash collected: when a number changes, it names the causes in order and links every claim to the records behind it.
Find what leaked
Finished work never invoiced. Estimates expiring with no follow-up. Invoices aging out. Missed calls nobody owns. Labeled confirmed, likely, or not sure, and never silently counted as recovered.
A tighter day
Route and schedule proposals: less windshield time, gaps filled, overrun cascades caught early. Proposal-only, checked for feasibility, and stale the moment the board changes.
Good / Better / Best from your own book
Estimate options priced from your price book and playbooks, with assumptions and margin warnings stated. Material takeoff with stock on hand and lead times. A draft order, never an order it places itself.
Before the job closes
Photos, forms, signatures, the invoice, the payment. It says ready, blocked, or follow-up required, and hands you the recovery list. It cannot mark the job done.
The house brief
Everything that ever happened at this address, compressed to what the next call needs. Before you dial, before the knock, before the number is presented. Every line expands to its source.
Codes and permits, with sources
Likely code, permit, and inspection requirements by jurisdiction, with edition and provenance. When it is not sure, it says verification required instead of guessing.
Watch the market
Competitor price and offer changes, review activity, local demand. An analyst, not a spender: it cannot buy ads, send a word, or publish anything.
Draft the workflow
Say the rule in plain English; get a typed draft with the diff, a simulation, and a rollback plan. Publishing is a review, not a surprise.
Today: one calm screen
Needs approval. Agent work in progress. At risk. Spend and usage. The whole workforce, human and not, on one command center.
The rules
What it is never allowed to do.
These are not settings. They are how the platform is built.
It never writes to your records directly
Every tool calls the same authorized operations a person would use, with the same permissions as the person asking.
It never does your money math
Totals, taxes, balances, and payroll stay deterministic. AI explains numbers; it does not produce them.
Every run has a leash
Budgets, step limits, time limits, and a stop button. An agent cannot keep going just because a model keeps planning.
No hidden queues, no invented metrics
Signals carry their evidence and their definitions. Nothing counts until it is confirmed.
Injection is treated as an attack
What a customer writes in a text is data, never instructions. Context is assembled from authorized records, not one giant dump.
Turn it off and the shop still runs
The board, the invoice, and collect never depend on a model being up. That is a design rule, not a promise.
In practice
Same copilot. Different leash.
Summarize this customer’s history
Automatic
Draft the overdue-invoice text
Suggested
Send the appointment reminder
Runs under your rule
Reschedule a customer
Waits for approval
Issue a refund
A person signs
Change a permission
Never automatic
If it fails
The shop still runs.
Click a row. Dispatch the truck. Collect on the drive. Brain is intelligence on top of a shop that already works without it. That is the point.
Brain
Included when released.
Assistive AI is already in Core. The governed agents arrive after the core product ships, and costly runs show an estimate first.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.