Structuring a Small Sales Team as It Grows

The generalist stage

Up to three or four people, generalists are usually right. Everyone does everything, coordination happens by conversation, and the overhead of specialisation is not worth paying. The thing to watch is not efficiency but neglect: with generalists, one activity always quietly loses. It is almost always new business development, because servicing an existing customer is more urgent and more comfortable than making a cold approach.

The first split

When you do split, split on the activity being neglected rather than on seniority. If new business is not happening, create a role that does only that, and protect it from being pulled into service work. Write down what happens at the handover point, meaning when a new customer transfers to whoever will look after them, because that handover is where the customer experience of your structure is decided.

The first manager

The role exists to do three things: run the pipeline review, coach individuals, and own the process. Notice that none of those is selling. A player-manager arrangement is a reasonable transitional step and a poor permanent one, because when the month is tight the manager reverts to selling and the coaching stops precisely when it is most needed.

Whatever the structure, enquiries need an owner within minutes. The three workable models are round robin, which optimises for speed and fairness; territory or segment, which optimises for knowledge and relationship; and skill-based, where enquiries route by product or language. Small businesses often need a hybrid, and that is fine as long as the rules are written down and the fallback is automatic.

The rule that matters more than the model is this: every enquiry must be assigned to a named person automatically at capture, and must escalate to someone else if untouched after a short interval. Shared ownership is the slowest routing model in existence, and it is what happens by default whenever the rules are unwritten.

Every specialisation you add creates a handover, and every handover is a moment where a customer may have to repeat themselves. Design each one explicitly: what information transfers, who makes the introduction, and what the receiving person must read before the first contact. A handover where the new person opens the conversation by demonstrating that they already know the history is a genuine improvement in service. One where they open by asking the customer to explain again is a downgrade dressed up as an organisation chart.

A structure change usually implies a compensation change, and forgetting that is how good structures fail. If you create a new business role, its incentive should reward new accounts rather than total revenue. If you create an account management role, its incentive should reward retention and expansion rather than new logos. When both roles are paid on the same undifferentiated revenue number, they will both drift towards whichever activity is easiest, which is exactly the neglect problem the split was meant to solve.

Change it when something specific breaks, and name the thing. Enquiries are being missed. New business is not happening. Nobody is coaching. Customers are repeating themselves. Each of those has a structural fix and each is visible before it becomes expensive. What does not work is reorganising in anticipation of growth, because the cost of a reorganisation is immediate and disruptive while the benefit is speculative.

One practical caution: do not change structure and systems in the same month. If you are moving people between roles, keep the process and the tooling constant so you can tell which change caused what. Teams that reorganise and migrate simultaneously spend the following quarter unable to explain their own numbers.

Related reading: CRM for small business, lead management software, what a CRM is, features, use cases, and book a walkthrough.