AAA AI Business OS Home

Service company

What the platform covers in a service business and what it lacks

A field engineer shows a customer something on a tablet

What this actually is

The «Service company» template exists in the product register and is listed as planned: it needs a field work module — a work order, an engineer, a visit — and that has not been built. An internal operations request is not a substitute: it lives inside the company, while a work order goes outside it.

Until that module exists, a service company runs on general modules. That covers intake, the queue, deadlines, approval and the trace of the decision — and does not cover planning a visit.

Which modules are switched on

The set switched on for a service company today:

Which AI employees work here

The lines of work that have something to do in a service business:

What is not in this build

What is missing, and what does not substitute for it:

What is the same in every industry

Company isolation enforced by the database, a closed register of permissions, an immutable journal, and a second person signing off where the action calls for it. That is how the platform is built, and it does not depend on which modules are switched on.

In every industry an AI employee produces a draft. Sending a message, paying, signing and deciding about a person are things the platform does not do — in no mode and under no role.

Basis: packages/contracts/src/project.ts, docs/MODULE_TRUTH_TABLE.md §5, §5a. This page describes what exists in this build, not what is planned.