A system for your value flow.

"The least obvious part of the system, its function or purpose, is often the most crucial determinant of the system’s behavior."

Meadows, Donella H.. Thinking in Systems: International Bestseller (p. 16). (Function). Kindle Edition.

What MOBuS is

MOBuS's function is to gather, causally relate and unify data and information received, generated and distributed during normal, day-to-day operations into a single model. Its purpose is to present a system where the systemic effects of a single task, a single employee, a single project, supplier or customer at any level can be clearly seen and measured in real-time.

Instead of treating CRM, project management, time tracking, and costing as separate islands, MOBuS connects them into a single operational graph. That graph lets you trace how decisions turn into work, how work consumes resources, and how that effort turns into value for clients and profit for you.

How the system is structured

At the core of MOBuS is an operational graph: a structured representation of your business made of nodes and connections. Nodes represent things you care about — clients, engagements, tasks, people, teams, equipment, time blocks, prices. Connections represent how they relate — who is responsible, what depends on what, which resources feed which work, where costs originate.

This graph is directed and acyclic. In plain terms, relationships always move in a clear direction and never loop back on themselves, so every action has a traceable origin and impact. MOBuS enforces simple structural rules — for example, important work cannot exist without a responsible asset, and economic events cannot exist without a source — which keeps your operational picture complete instead of full of gaps and guesses.

Because the system understands these relationships natively, it can answer questions that normally require spreadsheets and manual reconstruction:

  • What are we really doing for this client right now?
  • Who and what is this engagement actually using?
  • Where is value being created, consumed, or lost along the way?

Core engines in the MOBuS system

Under the hood, MOBuS is composed of specialised engines that all operate on the same operational graph. You see them as capabilities; the system sees them as coordinated parts of one whole.

Client & Relationship Engine

Manage contacts, organisations, mandates, and complex relationship structures in one place. The system keeps a complete history of communication, documents, and decisions per client, so every new action is taken in the context of everything that came before.

Work & Workflow Engine

Turn engagements into structured work: tasks, projects, dependencies, and milestones. MOBuS represents work as linked task trees that clearly show who is doing what, what depends on what, and where bottlenecks form. Workflows can be automated where it makes sense, but always stay anchored in the operational graph rather than floating as isolated automations.

Economic Intelligence Engine

Attach real costs and prices to the work you do. Time, assets, and supplies are mapped to engagements so that you can see true cost, margin, and profitability per client, project, and service line — while work is still in progress. Scenario tools let you explore “What happens if we take this project?” or “What if we staff this differently?” in economic terms, not just capacity terms.

Integration & Data Engine

MOBuS connects to the systems you already use — CRMs, accounting tools, data sources, and files — and brings their information into the operational graph. Data transform and sync capabilities let you clean, reshape, and reconcile information as it flows in and out, so you gradually move from scattered data to a single, coherent picture.

How MOBuS fits into your stack

MOBuS is designed as a modular backbone. It does not assume you will abandon the systems that already work for you. Instead, it connects to them, synchronises the essentials, and adds structure and economic context on top. You keep specialised tools where they shine; MOBuS makes sure their data fits together and tells a consistent story.

Technically, MOBuS runs on the BEAM virtual machine (Erlang/Elixir), a runtime built for systems that must be observable and resilient while they run. For you, that means the system can handle many concurrent activities, stay responsive under load, and be inspected without stopping — foundations for reliable operational intelligence rather than a collection of fragile scripts.

Seeing your system think

Because MOBuS is built on a causal, message‑driven architecture, it can show you a live map of its own behaviour. Internal applications appear as nodes; connections represent supervision and communication; colour and size reflect activity. You are not just looking at logs or after‑the‑fact reports — you are watching the operational nervous system of your business as it runs.

This same structure supports everyday work: when a new client engagement is created, when a task is assigned, when cost is calculated, the corresponding parts of the system light up. Over time, this makes operational rhythm visible: periods of intense activity, emerging bottlenecks, and the impact of new initiatives.

If you are technically inclined and want to see how the runtime observes itself, you can read more in Inside the MOBuS Runtime.

System glossary

Value flow

How value is created, consumed, and absorbed as work moves through clients, people, assets, time, and constraints. MOBuS is designed to make this visible in economic and operational terms.

Operational graph

The connected structure of clients, engagements, tasks, resources, and prices that MOBuS maintains. It is the internal map the system uses to understand your operation.

Engine

A focused part of the system — for example, the client engine, workflow engine, economic engine, or integration engine — that operates on the shared operational graph to provide specific capabilities.

Backbone

The role MOBuS plays in your stack: a central structure that connects existing tools, aligns their data, and adds causal and economic context, rather than trying to replace everything you already use.

Directed graph / DAG

A network of relationships where each connection has a direction and there are no loops. In MOBuS, this ensures that every action and cost can be traced back along a clear path, without circular logic.