Most companies never choose an organisation structure for small business growth; they inherit one. The founder hires people one at a time, each reporting to the founder, and the structure is simply whoever the founder talks to. That works at eight people. At thirty it is the reason decisions queue up, good people leave and the same problems come back every month. This guide covers how to tell the founder-centred setup has run its course, which structures suit businesses of 10 to 100 people, and how to write roles, decision rights and reporting lines that hold up in practice.

Signs the business has outgrown a founder-centred structure

Ten or more people report directly to the founder, and most of them wait for a decision at least once a day.
Nobody can say who owns a recurring problem, such as late collections or stock-outs, other than "the founder will sort it".
Two people believe they are responsible for the same thing, and a third thing has no owner at all.
Senior hires leave within a year because their authority was never made real.
Work stops when the founder travels, falls ill or is in a long meeting.
Pay and promotion decisions are made case by case, because there is no shared picture of levels or roles.

Any two of these usually mean the structure, not the people, is the constraint. Hiring harder-working people into the same structure produces the same result with a larger payroll.

Simple, functional or hybrid: choosing a structure for 10 to 100 people

Small businesses do not need complex models. Three options cover almost every case:

Simple structure: the owner leads, with two or three trusted leads who each run a group of people. It suits businesses up to about 20 people with one location and one main line of work. Its weakness is that the leads are often senior doers rather than managers.
Functional structure: people are grouped by function, such as sales, operations or delivery, finance and administration, and people or HR, each with one head. It suits most businesses from about 20 to 100 people, because it creates clear owners and lets specialists grow. Its weakness is that functions can start working for themselves rather than for the customer.
Hybrid by location or business line: a functional core (finance, HR, purchasing) shared across several outlets, branches or product lines, each with its own manager accountable for results. It suits retail, food and beverage, clinics and service businesses opening a second or third site.

Pick the structure that fits the next two years, not the next ten. A structure designed for 200 people imposed on 35 adds layers nobody can afford and slows the business down.

How to design it, step by step

1. List the work, not the people. Write down every recurring outcome the business needs: winning customers, delivering the service, buying, collecting cash, paying people, hiring, staying compliant.
2. Group the work into functions so that each outcome sits in exactly one group.
3. Give each function a single head. One person can head two small functions; two people cannot share one.
4. Draw the reporting lines. Aim for five to eight direct reports per manager as a working range, and keep the founder's direct reports to the function heads.
5. Only now map people to boxes. Where a box has no suitable person, mark it as a future hire rather than bending the box around someone.
6. Write the role, the KRAs and the decision rights for each box before announcing anything.

Writing roles and KRAs people can actually use

A role description that lists twenty duties tells nobody what matters. A usable one fits on a page and answers five questions: why the role exists, what it owns, who it reports to and who reports to it, what it can decide alone, and how success is measured.

Key result areas (KRAs) are the three to five outcomes the role is accountable for, each with a measure the person can influence. "Manage collections" is a duty. "Receivables over 60 days kept below an agreed level, reviewed monthly" is a KRA. Good KRAs:

Describe outcomes rather than activity.
Have a number or a clear yes or no test, and a review date.
Are within the person's control, or at least their influence.
Add up across roles to the business plan, with no outcome left unowned.

Decision rights and approval limits

A chart shows who reports to whom. It does not show who decides, and that is where most small-business structures fail. Write a short decision rights table covering the decisions that come up every week: discounts, purchases, hiring, refunds, credit terms, vendor selection and exceptions to policy. For each decision, state who decides, who must be consulted and who is informed afterwards.

Approval limits turn this into numbers. A store manager may approve refunds up to an amount you choose, a purchase head may approve orders within the monthly budget, and anything above goes to the founder. Set the limits from your own figures and risk appetite, start a little lower than you think, and raise them after a quarter of good decisions. Limits written down once remove a large share of the daily questions that reach the founder.

Reporting lines and the meeting rhythm

Each person has one manager. Dotted lines for project work are fine, but the person must know whose priorities win.
Function heads meet the founder together, weekly, on a fixed agenda of numbers, issues and decisions.
Each head meets their own team on a similar rhythm, so information moves down without the founder repeating it.
Escalation is defined: what goes up, to whom and how quickly. Anything not on the list is decided at the level where it arises.

How SOPs connect to the structure

Structure says who owns an outcome; SOPs say how the work behind it gets done. Each core process should name an owning role, not a person, so that when someone leaves the process stays with the role. Where a process crosses functions, such as order to cash, the SOP should mark the hand-over points, because that is where work is dropped. Writing the structure first and the SOPs second avoids documenting a process around a reporting line you are about to change.

Rolling it out without chaos

1. Talk to the future function heads one to one before anything is announced, and agree their role, KRAs and limits with them.
2. Announce the structure to the whole team in one meeting, with the chart, the reasons and what changes for each person.
3. Publish the decision rights table where everyone can see it.
4. Run a transition period of four to eight weeks, during which the founder redirects questions to the new owner instead of answering them.
5. Review after a quarter: which limits were too tight, which roles are overloaded, and which boxes now need a hire.

The hardest part is the founder's own behaviour. If staff learn that going around the new head still gets a faster answer, the new structure exists only on paper.

For example

This is an illustrative example, not a client case. A Bengaluru food business has grown to two outlets, a central kitchen and about 45 staff. All three managers, the purchase executive, the accountant and the marketing freelancer report to the owner, who also approves every purchase. The redesign creates a hybrid structure: an operations head over both outlet managers and the kitchen, a finance and purchase function with a monthly purchase budget, and HR and administration handled by one person. Each head gets three or four KRAs and written approval limits. Purchase requests stop reaching the owner unless they exceed the budget, and the weekly heads' meeting replaces a stream of calls. The owner's time moves to menu, new sites and the numbers.

Frequently asked questions

What is the best organisation structure for a small business?

There is no single best one. A simple structure suits most businesses under about 20 people; a functional structure suits most from 20 to 100; a hybrid suits businesses with several locations or lines. Choose by the work and the next two years of growth.

When should a small business create a management layer?

When the founder has more direct reports than they can coach and review properly, often around ten, or when decisions wait on the founder every day. The first layer is usually function heads, not a general manager.

How is a KRA different from a job description?

A job description lists what a person does. KRAs state the few results they are accountable for and how those results are measured. A role needs both, but KRAs are what you review.

Beyond Basics helps owner-run businesses in Bengaluru design structures that fit their size: we look at how decisions actually move today, map the work into functions, write roles, KRAs and decision rights with the people involved, and stay through the rollout. Where processes need writing down as well, we build the SOPs around the new roles.

Start with a business diagnostic →

SOP writing and process consulting →

How to make your business run without you →

Partners in the business? What to include in a partnership deed →

This article is general information, not legal, tax or financial advice. Rules change; check the current position for your situation before acting.