The Founder Authority Model A Governance Specification for Expert-Centric Organisations

The Founder Authority Model A Governance Specification for Expert-Centric Organisations

Stoyana Natseva
ORCID 0009-0008-1692-1935

Happy Life Institute for Direct Change Science, Sofia, Bulgaria
Version 1.0 | 2026 | Working paper: model specification
Licence: CC BY-NC-ND 4.0
Related work: Natseva, S. (2026). The Founder Authority Model: Scaling Online Education Without Losing Intellectual
Control. Horizon Books. ISBN 978-619-7850-04-8.
The Founder Authority Model — Specification v1.0 2

Abstract
Conventional scaling frameworks in management treat founder dependency as an operational defect to be engineered out. This assumption holds where organisational knowledge is transferable and leadership is functionally separable from intellectual capital. It fails in expert-centric organisations, where proprietary
methodology, quality assurance, and brand legitimacy are structurally embedded in one person and cannot be delegated without loss of the value they generate.
The Founder Authority Model reframes founder dependency as a strategic asset requiring structural formalisation rather than elimination. This paper specifies the model: its four components, the conditions under which each becomes operationally necessary, the dependency order governing their implementation, a
four-item diagnostic instrument for assessing organisational readiness, and the boundary conditions delimiting its transferability.
The specification derives from practice-based doctoral research employing an intrinsic single-case design applied to a founder-led online education institution. Sixty-eight open codes were generated from three triangulated evidence streams and consolidated into five governance dimensions. The resulting architecture
combines centralised intellectual leadership with distributed operational capacity. The model’s claim is analytical rather than statistical. It is offered as a transferable framework for organisations in which methodology constitutes the primary value proposition.

Keywords: founder authority; founder-led governance; expert-centric organisations; intellectual capital; scaling; hybrid governance; quality assurance; professional service firms; online education

1. The problem this model addresses
Management literature on organisational scaling converges on a consistent prescription: delegate operational authority, standardise delivery, build systems that function independently of any individual, and reduce the founder’s role from operator to steward. The founder is identified as a bottleneck, and the bottleneck is to be
routed around.
This prescription rests on an assumption that is rarely stated because it is usually true. The assumption is that organisational knowledge is transferable — that it can be documented, transmitted to a trained employee, and reproduced at equivalent quality. In a manufacturing firm this holds. In a software company it largely holds. In an organisation whose primary value proposition is a proprietary methodology, it does not hold at all.
Where methodology is the product, three conditions obtain simultaneously:
• Intellectual capital is not fully documentable. A substantial portion exists as judgment applied to non-standard cases, and judgment resists codification precisely in the cases where it matters most.
• Brand legitimacy is personal. Clients purchase access to a specific person’s method, and their trust does not
transfer automatically to an institutional substitute.
• Quality assurance is upstream of delivery. Defects in method are not detectable at the point of delivery; they surface as client outcomes one cycle later, when correction is expensive.
Applying conventional scaling logic under these conditions produces a characteristic failure sequence.
Delivery is delegated before the method is transmissible. Quality decays gradually and below the threshold of

The Founder Authority Model — Specification v1.0 3 detection. Client outcomes weaken. Referral volume falls. By the time the decay is measurable, the
organisation has scaled its way out of the position that made scaling possible.
The managerial problem is therefore not how to reduce founder dependency. It is the absence of a governance
framework that accounts for non-delegable intellectual capital as a permanent structural feature rather than a
transitional inefficiency.

2. Definition
The Founder Authority Model is a governance architecture in which the founder’s intellectual authority is formalised into transmissible organisational structure rather than delegated away enabling expert-centric organisations to scale operational capacity while retaining
methodological control.
Two elements distinguish it from adjacent frameworks.
Founder dependency is treated as an asset, not a constraint. Succession-planning and professionalisation literatures treat concentrated founder authority as a risk to be mitigated. This model treats it as the organisation’s principal differentiator and asks how it can be structurally supported at scale.
Authority is separated from operation. The model does not propose that the founder retains all decisions, nor that the founder withdraws. It specifies which decisions constitute intellectual authority — and must remain centralised — and which constitute operational execution and must not.
The resulting configuration is a hybrid architecture: centralised intellectual leadership with distributed operational capacity.

3. Empirical basis
The specification derives from practice-based doctoral research in Business Administration. Design. Qualitative, exploratory, intrinsic single-case study. The case is a founder-led branded online education institution, examined longitudinally across successive phases of organisational development.
Evidence streams. Three sources were collected and triangulated:
Source Codes generated Share
Organisational documents 24 35%
Operational records 22 32%
Reflective practitioner
notes
22 33%
Total 68 100%

The near-even distribution across sources indicates that no single evidence stream dominated the analysis.
Analysis. Structured thematic coding in three stages — open coding, thematic clustering, selective integration.
Sixty-eight open codes were consolidated into five governance dimensions: founder authority embedding,
delegation dynamics, quality assurance mechanisms, legitimacy formation, and scaling constraints and
The Founder Authority Model — Specification v1.0 4
enablers. The first three accounted for over 65% of coded observations.
Researcher position. The author occupied a dual role as founder of the case organisation and researcher, within the reflective practitioner paradigm accepted in professional doctoral research. Methodological safeguards included systematic contemporaneous documentation of managerial decisions, explicit separation
of empirical observation from interpretive inference, and disclosure of the analytical steps producing the framework.
Claim. Analytical generalisation, not statistical generalisation. A single case cannot generalise to a population.
It can produce a framework whose transferability is assessable against stated boundary conditions (Section 8).

4. The four components
4.1 Founder intellectual authority — codification
The methodology exists in transmissible form: documented principles, decision criteria for non-standard cases, worked examples, and a defined standard against which delivery is judged. Codification does not mean scripting. It means that a certified practitioner can determine what the method requires in a situation the
documentation does not directly cover.
4.2 Governance architecture — decision rights
Defined allocation of decision authority. The operative distinction is not seniority but decision class: decisions affecting methodological integrity remain centralised; decisions affecting operational execution are allocated to defined roles with explicit thresholds. A decision right is specified only if the holder can exercise it without
consultation.
4.3 Quality assurance system
Continuous monitoring of adherence to the codified standard, applied during delivery rather than after it. The distinction is functional: post-hoc measurement detects methodological decay one delivery cycle after it becomes consequential. In-cycle measurement permits correction while correction is still cheap.
4.4 Operational scalability — modular design
Programme and delivery structures built as modules sharing a common methodological core. Modularity permits capacity expansion without proportional expansion of founder supervision — but only where the shared core exists and adherence to it is monitored.
5. Activation thresholds
The components do not activate simultaneously. Each becomes necessary at a distinct point in organisational development. Premature formalisation is as damaging as delayed formalisation, and the failure modes differ.
Table 1. Activation conditions for governance components
Component Activation trigger Risk if delayed Risk if premature
Codification of methodology
Method delivered by anyone other than the founder
Methodological drift;
inconsistent client outcomes
Rigidity; the method ossifies
before it has matured
The Founder Authority Model — Specification v1.0 5
Component Activation trigger Risk if delayed Risk if premature
Decision rights Founder becomes the bottleneck for routin operational decisions
Escalation queues; delivery delays; founder overload
Diffuse accountability; decisions taken without methodological grounding
Quality assurance Second cohort delivered by certified practitioners
Silent quality decay, detected only through attrition
Administrative overhead disproportionate to delivery volume
Modular design Portfolio exceeds the founder’s direct supervisory capacity
Growth ceiling; expansion halted by supervision limits
Fragmentation; modules developed without shared core
The triggers are observable events, not stages of maturity or revenue thresholds. This is deliberate: revenue
and headcount correlate weakly with the governance transitions the model describes, whereas the listed events
mark the precise point at which the corresponding structure becomes load-bearing.

6. Implementation sequence
The components are ordered by dependency, not by importance.
Codification precedes all others. Decision rights cannot be delegated meaningfully until the standard against which decisions are judged exists in transmissible form. Delegation without codification is not delegation; it is the transfer of responsibility without the transfer of criteria.
Decision rights precede quality assurance. A monitoring system requires a specification of who is accountable for what. Monitoring without allocated accountability produces measurement without correction.
Quality assurance precedes modular design. Modules are coherent only if they share a codified core and a mechanism verifying adherence to it. Absent verification, modules diverge silently.
Reversing the sequence — constructing modular structures before codifying methodology — produces the fragmentation pattern observed in the delegation-dynamics coding cluster: operational units develop locally optimal practices that diverge from the institutional standard. Each unit performs adequately in isolation.
Collectively they cease to constitute a single methodology.
Codification → Decision rights → Quality assurance → Modular design

7. Diagnostic instrument
Four questions establish which component constitutes the binding constraint in a given organisation. They are ordered to match the implementation sequence: the first question that returns a negative answer identifies the constraint, and subsequent components should not be addressed before it is resolved.
Q1. Can the core methodology be delivered at recognised quality by a certified practitioner other than
the founder?
If no, codification is the binding constraint. All subsequent structural work is premature. This is the most
frequently misdiagnosed constraint, because the symptom presents as a delegation problem — the founder
appears unwilling to release control — when the underlying condition is that there is nothing transmissible to
release.
The Founder Authority Model — Specification v1.0 6
Q2. What proportion of routine operational decisions escalates to the founder?
Sustained escalation above approximately one third of routine decisions indicates that decision rights are
undefined rather than merely unused. Where rights are defined but unused, escalation declines when the
founder becomes unavailable. Where rights are undefined, escalation converts to inaction. The distinction is
diagnostic and easily tested.
Q3. Is quality measured during delivery or after it?
Post-delivery measurement — satisfaction surveys, completion rates, outcome reviews — detects decay one
cycle after it becomes consequential. In-cycle measurement includes observed delivery, methodological
adherence review, and calibration sessions.
Q4. Do new programmes draw on a shared methodological core, or are they constructed independently?
Independent construction signals absent modular design. It typically becomes visible twelve to eighteen
months before it is recognised as structural, initially appearing as harmless local variation.

8. Boundary conditions
The model presupposes three conditions present in the case organisation. Each is falsifiable, and the model’s
transferability should be assessed against them before application.
C1. Proprietary methodology constitutes the primary value proposition. Where the organisation’s value
derives principally from distribution, price, network effects, or accreditation, founder authority is not the asset
the model is designed to protect.
C2. The founder’s personal standing carries material market weight. Where clients select the institution
rather than the individual, centralised intellectual authority provides less strategic return than conventional
professionalisation.
C3. Delivery formats permit certified intermediaries. The model requires an intermediate layer between
founder and client. Where delivery is irreducibly personal, capacity is bounded by the founder’s time and no
governance architecture removes that bound.
Where any condition is absent — for instance in content-licensing models with no certified delivery layer, or
in institutions whose legitimacy rests on external accreditation rather than founder authority — conventional
governance frameworks are likely to serve better.

9. Limitations
Single case. The empirical base is one organisation. The model is an analytically generalised description, not a
universal prescription, and its transferability remains to be tested across cases.
Researcher position. The author was simultaneously founder of the case organisation and developer of the
framework. Methodological safeguards constrain but do not eliminate interpretive influence.
Absence of external stakeholder data. The analysis draws on the founder-practitioner perspective supported
by documentary and operational records. Students, instructors, and operational staff were not sampled as
independent sources. Extension to a multi-stakeholder design would strengthen the empirical grounding of the
governance claims.
The Founder Authority Model — Specification v1.0 7
Temporal bounding. The framework describes governance dynamics as they obtained during the observation
window. Governance practice in founder-led organisations evolves continuously.
Sector specificity. The case is an online education institution. Applicability to other expert-centric sectors —
professional services, clinical practice, specialist consulting — is proposed on the basis of shared structural
conditions (Section 8) and has not been empirically tested.

10. Priorities for further research
Four extensions would materially strengthen the model:
1. Multi-case replication across expert-centric sectors, testing whether the activation thresholds in Table 1
recur.
2. Multi-stakeholder designs incorporating instructor and client perspectives on the same governance
events.
3. Operationalisation of the escalation threshold in Q2, currently an observed approximation rather than a
validated parameter.
4. Longitudinal testing of the implementation sequence, particularly whether reversal reliably produces
the predicted fragmentation pattern.
How to cite
Natseva, S. (2026). The Founder Authority Model: A Governance Specification for Expert-Centric
Organisations (Version 1.0) [Working paper]. Zenodo.
The extended empirical treatment is published as:
Natseva, S. (2026). The Founder Authority Model: Scaling Online Education Without Losing
Intellectual Control. Horizon Books. ISBN 978-619-7850-04-8.
Terminology note
This model is designated the Founder Authority Model in all publications by the author. The designation
Founder-Led Education Governance Model, which appears in earlier drafts of the extended monograph, refers
to the same framework and is deprecated.