The founder is often the business's greatest asset. They understand the customers, remember the promises made during difficult negotiations and have a feel for the decisions that matter. In an early-stage company, that concentration of knowledge and authority can be a substantial advantage.
At some point, however, being central to everything becomes a constraint. The organisation may have recruited capable managers, but decisions still wait for one individual. Growth has increased the number of questions without changing the way answers are provided. The ScaleUp Institute’s 2025 annual review identifies leadership and talent among the challenges reported by its surveyed scaleups. [1]
The bottleneck is not necessarily a person problem
It is easy to characterise a hands-on founder as unwilling to let go. That description may occasionally be fair, but it overlooks how the operating model rewards direct involvement. Customers may insist on speaking to the founder; managers may be unsure whether they can make a commercial concession; and the founder may be the only person with the context needed to judge an exception.
The obvious question is therefore not simply why decisions are retained. It is what would be necessary for another competent person to make those decisions well.
For a small organisation, I would start with three types of decision: routine, consequential and exceptional. Routine decisions should usually be made close to the work. Consequential decisions need defined limits, a named owner and usable evidence. Exceptional decisions merit escalation because they exceed agreed boundaries, carry material risk or create commitments the company has not previously considered.
Find the queues that never appear in reports
Decision delays are rarely recorded in the same way as unfinished customer work. A project manager may wait for a pricing exception while the sales forecast continues to look healthy. A supplier may be ready to start but lack approval for a small change. Two managers may ask the same question separately because neither knows the other has already received an answer.
A short decision log can make the pattern visible. Record what was requested, why it required escalation, who could decide and how long the request remained unresolved. After a fortnight, categories begin to emerge. Some will deserve the founder's involvement; others may reveal unclear authority or missing information.
An illustrative software business might discover that every renewal discount above a nominal threshold is referred to the founder. The problem may not be the discount itself but the absence of an agreed margin floor and exception criteria. Once these are understood, a commercial manager can handle most renewals, with unusual commitments still escalated.
Delegation requires a usable boundary
A job description is rarely enough to define decision authority. It may describe general responsibilities without identifying which commercial, operational or people decisions can be taken independently.
A practical decision-rights table can be quite short. For each common decision, identify the accountable role, limits of authority, information required and triggers for escalation. An individual should not need to interpret an organisational chart every time an exception occurs.
The same logic applies to approvals. If a manager can commit to a purchase up to an agreed limit, the business also needs to decide whether the limit is per transaction, per supplier or for a defined period. Otherwise the apparent delegation may conceal a new ambiguity.
Release information as well as responsibility
The founder may have context that is not accessible anywhere else: customer profitability, historical commitments, supplier reliability or reasons for rejecting a previous proposal. Asking somebody else to decide without that knowledge is not a meaningful transfer of responsibility.
The solution does not require recording every conversation. It means identifying which information is necessary for sound judgement and arranging for it to be available at the point of decision. A concise customer account summary, agreed commercial thresholds or clear service priorities can be more valuable than a large management report.
It is also important to distinguish control from checking. The founder can retain oversight through exception reporting and periodic review without personally approving every routine action. Good delegation should make mistakes visible early, not pretend they are impossible.
Accept that some decisions will be different
Delegation inevitably introduces judgement that is not identical to the founder's. A manager may choose an option that the founder would not have selected. That does not automatically make it the wrong decision.
A useful test is whether the decision remained within agreed boundaries, used reasonable evidence and considered the relevant consequences. If so, differences in preference may be a healthy sign of a developing management team. Reversing every decision for reasons of personal style quickly teaches colleagues that authority has not really moved.
Where an error occurs, the response should separate a weakness in the decision framework from poor execution. Was the information incomplete? Was the boundary unclear? Did the decision-maker lack the skills required? The corrective action will differ.
Reducing dependency without losing founder influence
The intention is not to remove founders from their own businesses. It is to concentrate their time where it adds the greatest value: important relationships, future direction, major investment and decisions outside established policy. Smaller companies still benefit from the founder's distinctiveness; the challenge is making it sustainable. The British Business Bank’s 2026 finance markets report provides wider context on financing conditions facing smaller firms. [2]
I would measure progress by the decisions no longer requiring unnecessary escalation, the time saved, the quality of exceptions and whether customer commitments remain dependable. An arbitrary target to reduce founder involvement could remove useful oversight as easily as it removes delay.
Customers need continuity, not merely a different contact
Founder dependency can be reinforced by external relationships. A key customer may trust the founder because of the personal history behind the contract, particularly where there have been difficult decisions or exceptional commitments. Moving that relationship abruptly to a manager can create unnecessary concern.
A staged approach is usually more practical. Introduce the operational decision-maker, explain their authority and make sure both parties understand which matters will still reach the founder. Record the relevant commitments and context so that the relationship no longer depends solely on personal recollection. This is not a suggestion to make every relationship impersonal; it is an attempt to preserve service continuity as the business expands.
Look for the effect on the wider team
The time returned to the founder is only one measure of progress. I would also want to know whether managers make decisions with more confidence, whether customers receive answers promptly and whether unexpected risks reach the appropriate person. A decrease in escalations is not automatically positive if material exceptions are being ignored.
Delegation may reveal a capability gap. That is valuable information. The answer could involve coaching, clearer information or recruitment, depending on the nature of the decision. A new authority matrix cannot substitute for expertise where specialist competence is required.
Sources and further reading
[1] ScaleUp Institute, Annual Review 2025 Read online
[2] British Business Bank, Small Business Finance Markets Report 2026 Read online
Sources accessed 6 November 2026. All examples explicitly described as illustrative are hypothetical.
