What Changes at €30k, €50k and €100k Per Month

Revenue does not scale smoothly. It moves through thresholds, and at each one something that used to work stops working. The specific failures are consistent enough across companies to be worth naming in advance, because every one of them is cheaper to prevent than to fix under load.

The euro figures are markers rather than laws — a services business and a product business hit these walls at different revenue. What is consistent is the sequence.

Below €30k: the owner is the system

Everything routes through one or two people who hold the whole operation in their heads. This works, and it works well — coordination cost is near zero because there is nothing to coordinate.

What breaks: nothing yet. The risk is different: habits form here that become liabilities later. Undocumented process is free at this stage and expensive at the next one.

Worth doing early, while it is cheap: put accounts and domains in the company's name, keep client correspondence in company systems rather than personal inboxes, and write down pricing logic as rules instead of judgment.

At €30k: the founder becomes the bottleneck

This is the first genuine wall. Volume now exceeds what one person can personally touch, but the process still assumes they will. Every decision waits for them. Quality is inconsistent because it depends on whether they got involved.

What breaks: - Response times, because everything queues behind one person - Consistency between clients handled by the owner and clients handled by others - The owner's ability to do any strategic work, since the day is consumed by operations

What has to exist to pass it: documented process for the recurring 60% of work, with decision rules for the common exceptions. Not a handbook — rules specific enough that someone else can apply them and reach the same answer.

The characteristic mistake: hiring a generalist to "help" without defining what they own. That produces a second person who also needs the owner to decide. See you can't hire your way out of a process problem.

At €50k: the seams start leaking

Now there are functions — someone sells, someone delivers, someone handles accounts. Each works. The failures move into the gaps between them.

What breaks: - Handoffs. Work crosses between functions as assumptions, and margin disappears in the gap. This is measurable: what a broken sales-to-delivery handoff costs per month - Reporting. Multiple sources of truth appear, and people start checking numbers against spreadsheets before trusting them - Onboarding. Ramp-up stretches to months because the real process is undocumented - Cash timing. Revenue is comfortable, but growth consumes working capital faster than expected

What has to exist to pass it: one system of record that both sales and delivery work from, a structured handoff rather than a conversation, and a single reporting source nobody feels the need to verify.

The characteristic mistake: buying more tools. Each function picks its own, and now the integration gap is the problem. This is where build, buy or configure starts mattering.

At €100k: management becomes the constraint

The functions have teams. The problem is no longer whether work gets done — it is whether anyone knows what is happening while it is happening.

What breaks: - Visibility. You find out about problems after they cost something - Margin per project, which drifts downward while revenue rises, because coordination overhead grows faster than output - Key-person dependency, now concentrated in two or three operators who each hold a domain in their heads. What happens when your best operator leaves stops being hypothetical - Quality variance across teams doing nominally the same work

What has to exist to pass it: leading indicators rather than lagging reports, process enforced by systems rather than by convention, and documentation good enough that a competent new manager could run a function without a three-month apprenticeship.

The characteristic mistake: adding management layers to compensate for missing systems. A manager whose job is to remember the process is an expensive substitute for writing it down.

The pattern underneath all three

Every one of these walls is the same wall in a different costume: something that was held in someone's head has to move into a system.

At €30k it is the owner's judgment becoming rules. At €50k it is the handoff becoming a record. At €100k it is oversight becoming instrumentation. The companies that pass each threshold cleanly are the ones that did the transfer before the wall, not during it.

The tell that you are approaching the next one

Not revenue. The signal is that your best people are spending an increasing share of their week holding things together rather than moving things forward — reconciling, re-explaining, chasing, checking. That ratio starts shifting well before revenue reaches the next threshold, and it is the earliest warning available.

If you want a number to watch instead of a feeling, ask everyone for one week: what did you do that a system should have done? Track that total quarterly. When it starts rising faster than revenue, the next wall is already in front of you.

Related reading: The Difference Between Growing and Scaling a Business and When Your Business Has Outgrown Off-the-Shelf Software.