In short
Before scaling, verify five conditions: no critical process depends on one person, every core workflow is documented and owned, each data type has one system of record, you can measure cycle time and rework, and you know your cash conversion cycle. Growth does not create operational problems; it removes the slack that was hiding them. The practical test is whether adding 50% more volume would require adding more than 50% more effort — if so, fix the leverage before adding the volume.
Key takeaways
- Growth is a stress test, not a cause. It reveals problems that already existed.
- The diagnostic question: would 50% more volume require more than 50% more effort?
- Informal coordination is the first thing to fail, usually somewhere between fifteen and thirty people.
- Onboarding time is the single best summary measure of operational readiness.
- Cash conversion breaks growing businesses more often than demand does.
What growth actually does to a business
Growth is not a force that damages operations. It is a stress test that removes the conditions under which weak operations were survivable.
Specifically, it removes four kinds of slack:
- Time slack. Undocumented processes work while there is time to explain them. At higher volume, explaining becomes the bottleneck.
- Relationship slack. Informal coordination works while everyone knows everyone. Somewhere between fifteen and thirty people, no single person holds the whole map any more.
- Attention slack. A founder who catches problems by noticing them cannot notice everything past a certain scale, and the catching mechanism silently stops working.
- Cash slack. Growth consumes working capital before it produces profit. A business that was comfortable at one volume can be genuinely short at 1.5x.
Nothing new goes wrong when you grow. The things that were already wrong stop being invisible.
The leverage question
The most useful single diagnostic: if volume increased by half, would the effort required increase by more or less than half?
If more, you have negative leverage — each additional unit of work costs more than the last, usually because coordination overhead grows faster than the work does. Adding volume in this state converts growth into strain rather than into margin. The fix is not to grow more carefully. It is to fix the leverage first, then grow.
Readiness check 1: knowledge is in the business, not in people
The first thing to break, and the hardest to fix retrospectively.
Test it: list every process the business would notice stopping within two weeks. For each, count how many people could run it to standard without asking anyone. Any count of one, on anything touching revenue or compliance, is a blocking issue.
| Signal | Ready | Not ready |
|---|---|---|
| Bus factor on critical processes | Two or more, demonstrated | One, or two on paper only |
| Holiday for a senior operator | A scheduling matter | Requires planning by several people |
| New hire to useful output | Measured, and shortening | Unknown, or “depends who trains them” |
| Access to critical systems | Role-based, at least two holders | Personal accounts, one holder |
The methods are covered in detail in documenting processes from scratch and key person risk. The relevant point here is sequencing: this work takes a quarter and cannot be compressed, so it has to begin before the growth does, not in response to it.
Onboarding time as the summary measure
If you track one readiness number, track how long a new hire takes to reach useful independent output. It aggregates documentation quality, systems clarity, ownership clarity and training capacity into one figure. A business where this is 3 weeks can absorb growth. A business where it is 4 months cannot, and hiring ahead of the curve will make things worse before they get better.
Readiness check 2: ownership and systems hold their shape
Two structural conditions that determine whether adding people adds capacity.
Ownership
Every core outcome has one named owner with the authority and access to deliver it, and every decision point has a deadline and a stated default. Without this, each new person adds coordination load rather than capacity, because there are now more people who might be responsible and more places for work to wait. The mechanics are in who owns what.
Test it: pick three recent items that took longer than they should have. For each, identify who owned the delay. If the answer is unclear or contested in any of the three, ownership is not real yet.
Systems
Each core data type has a declared system of record, and the number of human bridges between systems is known and shrinking. Tool sprawl scales badly in a specific way: every new hire must learn every system, and every manual bridge must be performed more often.
Test it: ask two people in different functions how many active clients the business has. If they consult different systems and get different answers, you are not ready to add either clients or people. The audit method is in your tools don't talk to each other.
The rough headcount at which informal coordination stops working entirely. Businesses that have not built explicit ownership and handoffs by this point typically spend the next year in meetings trying to recreate by discussion what structure would have provided by design.
Readiness check 3: you can see and you can absorb
Measurement
You need to be able to detect degradation before a customer does. At minimum: cycle time with its distribution, throughput, work in progress, and some measure of rework. Growth without measurement means you discover problems through complaints, and complaints arrive weeks after the cause. See operations metrics that matter.
Test it: what is your 90th percentile delivery time this month against last quarter? If nobody can answer within a day, you are flying on impression.
Capacity and the constraint
Know where your constraint is before you add volume, because volume finds it immediately and without mercy. Businesses that scale into an unidentified constraint experience it as a sudden collapse in delivery quality, typically two months after the new work arrives.
Test it: if 30% more work arrived next month, name the step that would break first. If your team cannot agree on the answer, run the queue walk before committing to the growth.
Quality under load
Rework rate under pressure is the most honest quality signal there is. Many businesses maintain quality at normal volume through informal checking — someone senior glances at things. That mechanism is the first casualty of volume, and its failure is invisible until the rework arrives. If your quality control is a person's attention rather than a step in the process, it will not survive growth.
Readiness check 4: the cash side of growth
Operations writing usually stops at process. It should not, because the most common way growing businesses actually fail is not operational collapse but running out of cash while succeeding.
- Cash conversion cycle
- The time between paying for the resources needed to deliver work and receiving payment for that work. The longer it is, the more cash each additional unit of growth consumes before it returns anything.
Growth extends this cycle at exactly the moment it increases the volume passing through it. You hire before the revenue arrives, buy before you invoice, and deliver before you are paid.
Test it: for a typical engagement, count the days between your first cost and the payment clearing. Multiply by the volume increase you are planning. That is roughly the additional working capital required — and it is frequently larger than expected, because the calculation is rarely done at all.
Operational levers that shorten the cycle, in order of ease:
- Invoice on time. A depressing number of businesses lose more days to slow invoicing than to slow payment. This is a process problem, not a finance problem.
- Invoice at milestones rather than completion. Changes the shape of the cycle without changing terms.
- Take a deposit. The single largest structural improvement available to most services businesses.
- Chase systematically rather than personally. A defined, owned dunning process outperforms a person remembering, and it removes the relationship discomfort that causes delay.
The sequence, and what to do if you are already scaling
If you are ahead of the growth, the order that works:
- Access and bus factor — weeks, cheap, removes catastrophic risk
- Document the top processes — a quarter, and everything else depends on it
- Ownership map with decision clocks — an afternoon to draft, a month to bed in
- System of record declarations — free, immediate, prevents future mess
- Four metrics with thresholds — a month to establish a baseline
- Then automate what has proven stable
If you are already scaling and things are breaking — which is the more common situation — the sequence changes. You cannot do a quarter of preparation retrospectively. Triage instead:
- Stop the bleeding first. Fix access dependencies this week. It is the cheapest intervention and it removes the failure mode you cannot recover from quickly.
- Document only what is currently failing. Not the whole business. The three processes generating the most rework or the most questions.
- Consider slowing intake deliberately. Unpopular and frequently correct. Taking on work you cannot deliver well converts a capacity problem into a reputation problem, and the second is much harder to fix.
- Resist hiring as the first response. Adding people to an unstructured operation adds coordination cost immediately and capacity slowly. Sometimes it is right, but it should be a considered choice rather than a reflex.
The businesses that come through growth well are rarely the ones that predicted everything. They are the ones that knew which parts were fragile, fixed the cheapest ones early, and were honest about the rest — which is exactly what the Mayim Ops assessment is built to produce: a scored, evidenced picture of where you actually are, and a ranked view of what to fix first.
Frequently asked questions
How do I know if my business is ready to scale?
Check five conditions: no critical process depends on one person, every core workflow is documented and owned, each data type has one system of record, you can measure cycle time and rework, and you know your cash conversion cycle. The summary test is whether 50% more volume would require more than 50% more effort. If it would, fix the leverage before adding the volume.
What breaks first when a business grows?
Informal coordination, usually somewhere between fifteen and thirty people. Below that, everyone knows everyone and work moves through relationships. Above it, no single person holds the whole map, and businesses that have not built explicit ownership and structured handoffs by then tend to try to recreate through meetings what structure would have provided by design.
What is the best single measure of operational readiness?
How long a new hire takes to reach useful independent output. It aggregates documentation quality, systems clarity, ownership clarity and training capacity into one number. Around three weeks suggests a business that can absorb growth; four months suggests hiring ahead of the curve will make things worse before better.
Should I hire before or after fixing operations?
Usually fix first, at least the cheap items. Adding people to an unstructured operation adds coordination cost immediately and capacity slowly, and the new hire spends their first months absorbing undocumented context from the people who are already overloaded. Access fixes and documentation of the top three failing processes can be done in weeks and change what a hire is worth.
Why do growing businesses run out of cash?
Because growth extends the cash conversion cycle at the same time as it increases the volume flowing through it. You hire before the revenue arrives, buy before you invoice, and deliver before you are paid. Multiply your typical days from first cost to cleared payment by the planned volume increase to estimate the additional working capital required.