The owner can see every ticket. Verbal access barely holds. The risk is treating a patch as culture.
Headcount rising is not “make the group bigger and add columns to the spreadsheet.” What actually changes: the people who know the rules become the bottleneck, exceptions become the habit, and the owner turns from decision-maker into the end of every unread. Systematizing is not for looking formal. It is so departments can keep moving when the owner is not in the group.
Systematized means rules leave one person’s head
At twenty, admin remembers who can borrow the seal; finance remembers who can see payroll. At eighty, if those two people take leave, the company stops for half a week. Leave, expenses and seals have to become tickets. Roles have to live on jobs. Policy has to live in a searchable library. Verbal rules break on this step—see Why verbal permission rules eventually fail. WeChat approvals become unchaseable—see What happens when every approval lives in WeChat.
Which few flows to ship first matters more than buying a full suite
Growing companies swing between two extremes: do nothing, or buy a full ERP on day one. The first bleeds on contracts and access. The second drags the floor into training and empty fields. The right step: three to five high-frequency approvals in phase one, permissions that follow the role, to-dos that can be seen. Scenario breakdown: Growing companies: which approvals to ship first. You do not always need a full ERP—see Do you need a full ERP?.
Eighty people also means people start moving. If handover is a USB drive and “ask them,” the next manager reinvents verbal rules. How to-dos survive: How to-dos and permissions survive when a manager leaves. DaXi stages by your headcount and the flow that hurts most—not a software module list. Spell out the messy points on the ladder on the Management systems service page. The case for building: Why companies need a management system.
Headcount is not the only signal. Department walls are
Some firms at thirty already have three business units and two sites. Verbal rules fail earlier than at an eighty-person single department. Some eighty-person firms still orbit the founder; systematizing arrives later—but contracts and seals will not wait. Judge the step on three things: whether cross-department tickets stop matching; whether new hires cannot find the current policy; whether the owner is the end of every unread. If two of those are true, pull high-frequency approvals into a back office. Visible efficiency shows up first on chasing and checking status—see Visible efficiency a management system can deliver. You do not have to ship a full ERP in parallel—see Do you need a full ERP?. Change “wait until headcount” to “build when the wall appears,” or the step is missed in firefighting.