Accept the mandate
A founder's staying power comes from a purpose received or chosen that is larger than personal ambition.
In practice: The founder writes down the mandate in one sentence and tests every major commitment against it.
The 27 models
WCRC-GLC-23 — The Modern Sages
Srila Prabhupada
The WCRC Jaladuta Founder Model
Accept the mandate, make the voyage, then build to last.
THE MODEL
The WCRC Jaladuta Founder Model
A founder model in five stages: accept a mandate larger than oneself, make the risky first move into an unknown market, plant one small working seed, codify the knowledge so it can travel, and then scale through people. Age, resources and comfort are treated as conditions to work with, never as reasons to wait.
Anchor teaching: The voyage of the Jaladuta (his guru's request to share Sri Chaitanya's message in English)
This is a selection of teachers linked with the Hindu tradition, not a ranking. The models offer management reflection, not religious instruction.
WCRC is not affiliated with or endorsed by any teacher or organisation discussed.
MODEL STRUCTURE
How it works
Make the voyage
The first move into an unknown market carries real personal risk and cannot be delegated or endlessly prepared for.
In practice: The founder sets a date to enter the new market personally and keeps it.
Plant the seed
Scale starts with one small, visible thing that works: one park, one chant, one storefront.
In practice: The founder proves the idea in a single location with real users before seeking wider growth.
Codify the knowledge
Writing the core down, as he did in over sixty volumes, lets the idea travel without the founder in the room.
In practice: The founder commits time every week to documenting the method, principles and standards.
Scale through people
Growth comes from training others who can carry the work, in place of the founder doing everything.
In practice: The founder measures success by how many capable leaders can run the work without them.
TEACHING AND CONTEXT
The thinking behind it
On 13 August 1965, aged 69, Srila Prabhupada sailed from Calcutta on the cargo ship Jaladuta as its only passenger. Devotees recount that he survived two heart attacks on the 35-day voyage and landed at Boston on 17 September with a few dollars' worth of rupees and a crate of his books. Within about a year he had registered ISKCON in New York (July 1966) and, on 9 October 1966, led the Hare Krishna chant under an elm in Tompkins Square Park.
At their first meeting in Calcutta in 1922, devotees recount, Bhaktisiddhanta Sarasvati asked the young Abhay why he did not preach Sri Chaitanya's message throughout the world, in English.
Encyclopedia.com; krishna.com"I have tried to present Bhagavad-gita as it is, without any adulteration."
Bhagavad-gītā As It Is, Preface, © The Bhaktivedanta Book Trust International, Inc."Everyone should know that a living entity is eternally a servant." One serves either Krishna or illusion.
Bhagavad-gītā As It Is, Preface, © The Bhaktivedanta Book Trust International, Inc.Sharing knowledge: following his guru's order, he gave his life to putting the bhakti texts into English and distributing them.
krishna.com; Encyclopedia.comOPERATING MODEL
From principle to practice
Inputs
- A mandate larger than the founder
- Willingness to take personal risk
- Core knowledge worth spreading
- Minimal starting capital
Practices
- Enter the new market in person
- Prove one small working seed
- Document the method relentlessly
- Train people to lead locally
Outputs
- First working site in new market
- Codified body of knowledge
- Trained local leaders
- Repeatable model for new sites
Outcomes
- Global reach from a small start
- Mission that survives the founder
- Late-career founding shown possible
- Durable, recognisable identity worldwide
BENEFIT MODEL
Who it is for
leader
The founder gains a clear sequence that turns a large mission into concrete next steps, at any age.
employees
Early team members join a mission with a written core and a path to lead their own part of it.
customers
Customers in new markets receive the real thing, consistent with its source, through people trained in it.
investors
Investors see a model that proves itself small before asking for scale, with knowledge captured as an asset.
society
Knowledge from one culture becomes available to people far beyond it, in their own language.
WCRC MODEL PARAMETERS
Model emphasis
The scores describe this model's emphasis on each parameter. They are not scores for a person or organisation.
Vision Quotient4 / 5
Impact Index4 / 5
Innovation Score3 / 5
People Leadership3 / 5
Stakeholder Trust2 / 5
Resilience Factor5 / 5
Global Mindset5 / 5
THE AI AGE
Why it matters now
Age is no barrier to founding, and AI tools now let a small team, even a single founder, reach the world as he did with a crate of books. The WEF expects two-fifths (39%) of existing skill sets to be transformed or become outdated over 2025-2030 [2], so leaders at every stage of a career will need a growth mindset [3]. Codifying experience matters more as tools multiply: once some experience exists, deliberately articulating and codifying it beats simply gathering more [1]. Prabhupada's books did the work of a team he did not yet have.
EXECUTION
Put the model to work
Write your mandate in one sentence and set a date on which you will personally enter the new market you have been planning.
Founder and CEO
- Accept the mandate in writing: In the first week, write down the mandate in one sentence and test your current commitments against it, dropping any that do not serve it. Share it with your co-founders or top team so they can hold you to it.
- Set the voyage date: Fix a date to enter the new market in person and keep it, without waiting for perfect preparation. In a large company, the CEO still goes personally for the first stretch rather than sending a delegation.
- Plant one seed: Stay close to a single location until it works with real users and meets proof criteria you set in advance. Resist opening a second site before the first one has proved itself.
- Write the method weekly: Set aside fixed time every week to document the method, principles and standards in usable form. Treat codification as founder work, since nobody else knows the core as well as you.
- Step back on purpose: Once local leaders are trained, deliberately stay out of units for set periods and see whether they meet their targets without you. Measure your success by how many can run the work without you, while keeping your own health and team in view.
Company
- Diagnose founder dependence (CEO office): List which decisions, sites and processes still need the founder, and how much of the core method is written down in usable form. This sets the baseline for codification coverage and leaders who can run without the founder.
- Pilot one seed site (Founder with a local lead): Open a single location in the new market with defined proof criteria agreed before launch. Log every expansion request against those criteria in a shared expansion log.
- Embed mandate in approvals (Board and finance head): Require every major commitment's approval paper to say how it serves the written mandate, and make documenting one's method part of every leader's role. Promote leaders who can run units without founder intervention.
- Train local leaders (CHRO with founder): Build a training path from the codified method so local leaders can open and run sites on their own. The founder teaches parts of it personally at first, then hands them on.
- Track seed and codification KPIs (CEO office): Report the seed-to-scale ratio, codification coverage, leaders who can run without the founder and mandate alignment every quarter. Flag any new site opened before its predecessor met proof criteria.
- Scale and keep the core alive (Board): Expand through trained leaders once seeds meet their criteria, and review the codified core each year so it adapts to new contexts and does not harden into dogma. Review founder workload and health in the same session.
Readiness check
Before starting
- Can our founder state the mandate in one sentence that is larger than personal ambition?
- Are we willing to prove one site fully before opening a second?
- Is enough of our method written down that a trained leader could run a unit without the founder?
Phase 1 · Diagnose and commit
Fix the mandate in writing, set the voyage date and see how far the work still depends on the founder.
- Write the Accept the mandate sentence and test every current commitment against it.
- Set and announce a date to enter the new market in person for the Make the voyage step.
- List the decisions, sites and processes that still need the founder.
- Measure how much of the core method is written down in usable form.
Deliverable: A one-sentence mandate, a fixed voyage date and a founder dependence map with codification coverage.
Gate: The mandate is written and shared, the voyage date is fixed in the diary, and baselines for codification coverage and founder dependence are recorded.
Phase 2 · Pilot and prove
Plant one seed in the new market and prove it with real users before anything else opens.
- Agree the proof criteria for the first site before launch and record them in the expansion log.
- Have the founder stay close to the single Plant the seed location until it works.
- Start weekly founder time on the Codify the knowledge step, writing up what the seed teaches.
- Name the first local lead to work beside the founder.
Deliverable: A working first site with its proof criteria, expansion log entries and the first codified method documents.
Gate: The first site has met every proof criterion set before launch, and no second site has been opened.
Phase 3 · Embed and scale
Turn the seed into a repeatable model that trained people can open and run.
- Build a training path for local leaders from the codified method.
- Require every major commitment's approval paper to state how it serves the mandate.
- Open further sites only through trained leaders and only after the previous site met its criteria.
- Have the founder stay out of trained units for set periods to test whether they run alone.
Deliverable: A leader training path, a mandate line in approval papers and a growing list of units run by trained leaders.
Gate: Each new site in the log opened after its predecessor met proof criteria, and at least one unit has met its targets without founder intervention.
Phase 4 · Sustain and renew
Make the mission outlast the founder without the written core hardening into dogma.
- Review the codified core every year and adapt it for new contexts.
- Measure how many units run without the founder and plan the founder's next step back.
- Check founder workload and health in the same board session as expansion.
- Retire commitments that no longer serve the mandate.
Deliverable: An annual review of the codified core, a founder succession plan and the four KPIs for the board.
Gate: The board has reviewed codified content for relevance within the year and the count of leaders who run without the founder is rising.
Governance
sponsor: The founder, because the mandate, the voyage and the first seed cannot be delegated in this model.
lead: A chief of staff or head of expansion who keeps the expansion log, the codification library and the leader training path.
forum: The founder and lead review the seed and codification monthly, and the board reviews the four KPIs every quarter.
decision_rights: The lead can schedule training, update documents and assess proof criteria; opening a new site or changing the mandate goes to the founder and board.
Cadence
Weekly: Fixed founder time to write the method, principles and standards in usable form.
Monthly: Review of the seed site against its proof criteria and of every expansion request in the log.
Quarterly: Report on seed-to-scale ratio, codification coverage, leaders who run without the founder and mandate alignment.
Annually: Board review of the codified core for relevance, plus the founder's workload, health and succession.
By company stage
startup
The founder personally makes the first market entry and writes the method in a simple shared notebook each week. One site is proved before any second hire is made for a new location.
scaleup
A small expansion team keeps the log and proof criteria, and trained leaders open new sites from the codified method. The founder steps back from units deliberately and measures what still needs them.
enterprise
The board requires a mandate line in every major approval paper and tracks leaders who run units without the founder. New ventures inside the group follow the seed rule and the founder or CEO goes in person for the first stretch.
Success looks like
- New sites are opened and run by trained leaders using the written method, with the founder absent.
- Major commitments can be traced back to the written mandate in their approval papers.
- The codified method has been revised by people other than the founder and still reflects the core.
MEASUREMENT AND LIMITS
What to watch
Seed-to-scale ratio
Number of new sites or markets opened only after a first site met its defined proof criteria, from the expansion log.
Codification coverage
Share of core processes and principles documented in current, usable form, reviewed each quarter.
Leaders who can run without the founder
Count of sites or units led by trained leaders that met targets without founder intervention over the year.
Mandate alignment
Share of major commitments whose approval paper states how they serve the written mandate.
Failure modes
- Founder dependence: the voyage is heroic, but nothing is codified and the work stalls when the founder steps back.
- Codification hardens into dogma, and the written core stops adapting to new contexts.
- The heroic solo story is glamorised, and founders ignore health and team-building in its name.
Execution risks
- Founder dependence persists because the founder keeps doing the work instead of writing it down.: Weekly codification time is cancelled and units call the founder for routine decisions. Mitigation: Protect codification time in the diary and track founder interventions per unit each quarter.
- Expansion pressure from investors or the board opens sites before the seed is proved.: Expansion requests appear in the log without proof criteria or before the first site meets them. Mitigation: Make proof criteria a hard condition in board approvals and report any exception openly.
- The codified method hardens into dogma and stops fitting new markets.: Local leaders work around the written method instead of proposing changes to it. Mitigation: Invite local leaders to propose amendments and review the codified core every year.
- The heroic solo story is glamorised, and the founder neglects health and team-building.: The founder is the only person who has visited new markets, and health or workload concerns are dismissed. Mitigation: Put founder health and team depth on the board agenda alongside expansion.
RESEARCH SOURCES
Sources and notes
- Di Stefano, G., Gino, F., Pisano, G. P., & Staats, B. R. (2016). Making experience count: The role of reflection in individual learning. Harvard Business School Working Paper No. 14-093 (SSRN 2414478).
- World Economic Forum. (2025, January). The Future of Jobs Report 2025. Geneva: WEF.
- Dweck, C. S. (2006). Mindset: The New Psychology of Success. New York: Random House (Ballantine paperback 2007).
The WCRC Guru Management Codex and its 27 models are proprietary WCRC models. © WCRC. All rights reserved.