How to design your organisation by function as you grow.

In the earliest days the co-founders do everything. That stops scaling surprisingly early: sales slows when the person selling is also fixing bugs, invoices go out late, and nobody owns customer onboarding. Organisation design is the deliberate choice of who owns what. It is not about job titles or a large org chart; it is about making sure every essential activity has a named owner and that the next hire fixes the biggest gap.

Start with functions, not people

Techcelerate looks at every company through nine functional units: Opportunity and Strategy, Product and Engineering, Marketing, Sales Engine, Operations, Customer Success, Finance, HR and Legal. Each maps to a playbook in this knowledge base. Drawing your organisation around these units, rather than around the people you happen to have, shows what is missing.

Step by step

1. List the functions and, under each, the activities that must happen every week or month. For Finance: invoicing, payroll, the monthly close, the cash forecast. For Customer Success: onboarding, support, renewals.
2. Assign one owner per function. At first, one person may own several. Ownership means accountable for the outcome, not doing every task.
3. Score each function on a simple scale: not covered, covered badly, covered well. Be honest.
4. Identify the constraint. Which weak function most limits revenue or creates most risk right now? That is your next hire, contractor, outsourced service or volunteer role.
5. Write short role descriptions for each function: purpose, responsibilities, key measures, who they work with.
6. Set a decision map. For the decisions that matter (pricing, hiring, spend above a limit, product priorities), write who decides, who is consulted and who is informed.
7. Review quarterly. Redraw the chart as revenue and headcount change.

The how-to designing the organisation with SkilledUp Life shows how to fill functional gaps with skilled volunteer teams alongside your paid team.

A rule of thumb for the decision map: if a decision is easy to reverse, push it to the function owner; if it is hard to reverse or commits significant cash, keep it with the founding team.

How structure changes with stage

• Validation: co-founders own everything, with help on specific tasks. Focus on customer discovery and a working product.
• First revenue: separate ownership of product and sales. Add basic finance and customer success processes.
• Growth: functional leads emerge. Each function gets measures, a budget and, often, its first specialist hire.
• Scale: leaders build teams beneath them; the chief executive manages the leaders rather than the work.

Worked example

Coralfold is a fictional Edinburgh tech startup selling booking software to independent gyms. With six people it felt busy but was stalling at £18,000 MRR. Mapping the nine functions showed Product and Engineering well covered by three developers, Sales owned by one co-founder, and Customer Success, Marketing and Finance owned by nobody in particular. Onboarding was ad hoc, so new gyms took weeks to go live and many churned in the first quarter.

Instead of hiring a fourth developer, Coralfold gave customer success ownership to its most customer-facing developer for a quarter, documented an onboarding process and then made a customer success manager its next hire. Time to go live halved and early churn fell, and the next growth hire after that was in marketing.

Common mistakes

• Hiring more of the skills you already have because they are familiar.
• Copying the structure of a much larger company.
• Shared ownership, which usually means no ownership.
• Job titles inflated early that are hard to change later.
• Never revisiting the structure as the company changes.

What to measure

• Functions with a named owner, and functions scored “covered well”.
• Revenue per full-time employee, as a rough efficiency check.
• Time from identifying a gap to filling it.
• Whether each new hire or role removed the constraint it was meant to.