> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How Operations Change at 10, 50 and 200 People
- URL: https://blog.jestor.com/operations-at-10-50-200-people/
- Published: 2026-09-17T22:35:28.000Z
- Updated: 2026-09-17T22:35:28.000Z
- Author: Bruno Bannach

Understanding **operations at different company sizes** helps you build what you need now rather than what you will need eventually — and to recognize the thresholds when they arrive.

## What changes at each stage

The failure modes are consistent across companies.

- **At 10** — shared context makes coordination free; almost nothing needs formalizing
- **At 50** — one person can no longer hold every process; informal approval breaks
- **At 200** — departments need separation, reporting needs consolidation, access needs governance

## What to build at each stage

| Size           | What matters                                                       |
| -------------- | ------------------------------------------------------------------ |
| **10 people**  | Intake and one source of truth for clients                         |
| **50 people**  | Approval routing, roles, and process ownership                     |
| **200 people** | Departmental separation, access governance, consolidated reporting |

## How to build for your stage in Jestor

1. At small scale, structure intake in **Jestor** and keep one record per client.
2. Approaching fifty, add routing by **cost center** and define roles by function.
3. Assign process ownership, with builder seats limited to those owners.
4. At larger scale, organize into folders per process and review access annually.
5. Consolidate reporting into panels scoped by permission rather than duplicated per team.

## Why choose Jestor across growth stages?

Across **operations at different company sizes**, **Jestor** is aimed at companies that have outgrown spreadsheets and generic tools, and the structure can be added process by process rather than in a single transformation.

Because permissions work by role, field, and action, the same build that serves a small team continues working at two hundred people with access scoped rather than rebuilt.

## Frequently Asked Questions

### What breaks first as a company grows?

Informal approval, usually around fifty people. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Should a small team formalize everything?

No — intake and a single client record are usually enough.

### Does the structure need rebuilding later?

No, permissions and folders scope it as you grow.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.