Case 04 · Ops Suite
Operations keep running.
Control stays with you.
One control layer connects field teams, communication and accounting. Routine runs in the background; important decisions and exceptions go to a person.
Running in productionRules firstEmergency stops
54implemented automation workflows
31workflows active in production
Humandecides at the final boundary
PyPython
n8nn8n
TGTelegram
NNocoDB
LLexoffice
AAmoCRM
GGoogle Workspace
WAWhatsApp
DDocker
THURSDAY · 23 JULYGood morning. Operations are on schedule.
31 workflows activeOOps Monitor
GESAMTSTATUSEverything is running normally
18/18StatusProcessesIncidents
Automations31 live workflows
StableData sourcesNocoDB · CRM · Drive
CurrentApprovals2 actions waiting
ReviewLAST CHECK10:42 · no incidentNext check in 3 minutes
The starting point
The information was there.
The shared view was missing.
The owner had to assemble jobs, hours, messages and accounting events from several sources into one daily picture.
Scattered signals
Each specialist application showed its own slice, but none explained the full operating day.
Communication without a dossier
Email, WhatsApp and CRM had to be searched separately for every customer question.
Automation without boundaries
A process is trustworthy only when it is clear what it may do and where it must stop.
A day as a system
Prepare. Observe.
Review. Close.
The core is not one bot, but a reliable daily cycle with clear states.
The plan reaches the team automatically.
At 17:50, the system builds tomorrow's plan from the job calendar using fixed rules.
Signals arrive in the cockpit.
Jobs, communication and accounting status become one operational view.
Exceptions are routed to a person for approval.
The report clearly marks missing responses, retrospective changes and assumptions.
Telegram · Tomorrow’s plan
THURSDAY · 24 JULY4 teams · 12 jobsDry · 24 °C 08:00 08:30
PTomorrow’s plan
Team North · 3 jobsMitte → Pankow → WeißenseeMaterials complete · 1 photo brief
Team South · 4 jobsNeukölln → TempelhofVehicle 03 · Route checked
Dashboard · One operational view
Field work9 / 123 active Communication62 open Accounting82 to review Systems18 / 18stable CaseField teamContactFinanceStatus
OPERATING VIEW12 jobs · 4 teams
No incident#184 · Care, MitteReport readyCustomer informedreadyDone
#185 · Installation, Pankowon siteno questionopenLive
#186 · South servicewaitingQuestion—Review
Rules first · Human approval point
! ↻ €
20:00 · CREATED AUTOMATICALLYOnly exceptions need attention
Rules firstJOB #186Team response missingPlanned time never replaces actual working time.
DetailsJOB #179Time changed afterwards7.5 h → 8.0 h · change logged
ReviewBUCHHALTUNG2 booking drafts preparedNothing is submitted before your approval.
OpenSystem views
Operations from four
decisive perspectives.
All views are anonymised and show real process logic without business or personal data.
System landscape
Many specialist systems.
One controlled daily cycle.
Each assistant handles one clearly bounded task. No single bot is allowed to do everything.
SchedulingTeams & jobs
CommunicationEmail & WhatsApp
AccountingReceipts & status
Operating rulesApproved data
CockpitOne operational view
MonitoringErrors & kill switch
AI governance in daily operations
The model suggests.
The approved operating rules decide.
Draft, approval and execution are deliberately separate stages.
No invoice is sent without final human approval.
Irreversible or reputation-sensitive actions stop at a clear boundary and show exactly what is being approved.
Emergency stop and audit log are part of the product.
Active workflows can be stopped deliberately. Status, errors and completed steps remain traceable.