Adding a department without rebuilding the company

Most software has a cliff. It works at one size and breaks at the next; a system built for ten people needs rewriting for a thousand. The cliff is there because assumptions about size get baked into the structure: fixed schemas, hard-wired routing, one big configuration. Adding a department means re-engineering the whole thing.

Vepartment was built to avoid that from the first day. The department is not a metaphor. It is the one building block, the same at every size.

One block, any size

A sole founder uses one department. A growing company uses five. A group uses every department in every business unit. The block is the same each time: a job, the company's facts, the people who say yes, the work it drafts. Nothing changes in the structure when you add one; there are no new abstractions to learn and no new layer of coordination.

Knowledge that stays in its place

Each department keeps its own knowledge of the company; there is no single pile that grows with every addition. When a department is added, it starts with its own facts, and references between departments are explicit links, not shared state. The people doing the work do not read the whole pile either: they get a small, precise slice — the facts, rules and earlier decisions that matter to this task — so the cost of a task stays the same whether the company has a hundred facts on file or ten thousand.

Templates, not projects

A new department is not built from scratch. It starts from a template that names its jobs, its tools, its default level on the Human Agency Scale and the facts it needs first. Adding marketing to a company is a set-up step of a few minutes, not a development project.

Departments do not talk to each other directly

In a company, adding departments adds meetings and handovers. In a naive system of many agents, it adds message traffic and races. Here, departments pass each other events, requests and finished documents through one structured channel, with Ori, the company's assistant, keeping the overview. The cost of coordination stays flat however many departments there are.

The four-step test

• Pick a template, or describe the department in your own words.
• Choose how much it may do alone.
• Give it the facts it needs, or let it read what the company already has.
• Switch it on.

No deployment, no migration, no downtime. The running company takes the new department the way it takes a new colleague: a desk, an introduction, and the first drafts by the end of the week. That is the mechanism: the right building block, applied the same way at every size.