Skip to main content

Featured

Shareholder Primacy vs. Stakeholder Theory: A Critical Analysis of Corporate Legal Obligations

The debate between shareholder primacy and stakeholder theory concerns the legal obligations of corporate directors. Introduction A corporation is never just a machine for making money. It is a legal institution, a social system, and a vehicle for allocating power, risk, and responsibility. That is why one of the most important debates in corporate governance continues to divide scholars, executives, regulators, and investors: should corporations exist primarily to maximize shareholder value, or should they balance the interests of all the people and institutions affected by their actions? This debate is commonly framed as shareholder primacy vs. stakeholder theory. Shareholder primacy says the corporation's central obligation is to its owners, the shareholders. Stakeholder theory says the corporation owes duties to a wider circle of affected parties, including employees, customers, suppliers, creditors, communities, and sometimes society at large. This is not a purely academ...

Financial Planning and Projections

Financial planning and projections are the process of translating a venture’s operating assumptions into a set of numbers that show whether the business can pay for itself and how much capital it will need. Most founders treat the projections as a formality for investors, and that reading is a mistake. The projections are the place where the founder discovers whether the venture actually works, and the founders who do the modelling honestly find problems that the pitch deck would have hidden.

By Kateule Sydney — Researcher and Writer | Last Verified: 2026-09-28 | Published by Kat-Syd Resources Hub
Founders reviewing financial projections and cash-flow forecast on a spreadsheet
Financial planning: translating assumptions into numbers that reveal whether the venture works

Drivers come before numbers, and the numbers are worthless without them

Financial projections are estimates of future financial performance, expressed as a set of statements that cover revenue, costs, cash, and balance-sheet position. But the projections are only as good as the operating drivers behind them, and the drivers are the assumptions about how the business actually works.

A driver is a variable that produces a financial outcome. For a subscription venture, the drivers are customer acquisition rate, churn rate, and average revenue per user. For a retail venture, they are store traffic, conversion rate, and average transaction value. The financial projection is nothing more than the mathematical consequence of the drivers.

The founders who build projections from the drivers get a model they can update when reality diverges from the plan. The founders who build projections from a target revenue figure and work backwards produce a model that is wrong the moment the target turns out to be wrong, which is almost immediately.

The four most common operating drivers in early-stage projections are:

  • Customer acquisition — how many new customers arrive per period and at what cost
  • Customer retention — how many customers stay and for how long
  • Revenue per customer — how much each customer pays over the relationship
  • Unit cost — the direct cost of serving each customer or producing each unit

The interpretive insight is that the founder who cannot name the drivers cannot defend the numbers. The numbers are a symptom, and the drivers are the cause, and the cause is what the founder manages.

The three statements answer three different questions, and all three are needed

The standard projection set contains three statements: the income statement, the balance sheet, and the cash-flow statement. Each answers a different question, and the founder who produces only one of the three misses something the other two would have revealed.

The income statement shows whether the venture is profitable over a period. The balance sheet shows what the venture owns and owes at a point in time. The cash-flow statement shows whether the venture has enough cash to keep operating.

Key point: a venture can be profitable on the income statement and still run out of cash, because profit and cash are not the same thing.

The cash-flow statement is the one most founders underinvest in, and it is the one that kills the most ventures. A business that sells on credit, holds inventory, or pays for growth ahead of revenue can show a healthy profit while running out of cash. The founders who model all three statements see the cash problem before it happens, and the founders who model only the income statement discover it when the bank account is empty.

The three statements serve three distinct purposes:

  • Income statement — measures profitability over a defined period
  • Balance sheet — measures financial position at a point in time
  • Cash-flow statement — measures liquidity and survivability

The interpretive insight is that the three statements are a system, not a set of alternatives. The founder who produces only one is not projecting a business, but a fragment of one, and the fragment is where the venture will eventually fail.

Scenario planning is how the founder stops projecting a single future

Scenario planning is the practice of producing multiple versions of the projection under different assumptions, rather than committing to a single forecast. Peter Schwartz, in The Art of the Long View (1991), developed the scenario method for corporate strategy, and the same logic applies to early-stage ventures.

The three scenarios most founders should build are the base case, the upside case, and the downside case. Each assumes a different set of driver values, and each produces a different capital requirement. The downside case is the one that matters most, because it tells the founder how much capital to raise to survive if the plan does not work.

A venture that raises only enough capital for the base case is under-capitalised against the probability that the base case will not materialise. A venture that raises for the downside case has enough capital to keep iterating through the failure of the first plan, and the ability to iterate is what produces the eventual success.

The three scenarios that anchor a projection are:

  • Base case — the most likely outcome, based on current evidence
  • Upside case — the outcome if the drivers perform better than expected
  • Downside case — the outcome if the drivers perform worse, which determines the capital requirement

The interpretive insight is that the downside case is the most important of the three, because it is the one that determines whether the venture survives long enough to reach the upside. The founders who raise for the base case often do not reach it, and the founders who raise for the downside case often do.

Runway is the metric that determines whether the venture survives to test its plan

Runway is the number of months a venture can operate before its cash runs out, given the current burn rate. It is calculated as cash on hand divided by net monthly cash burn. Runway is the single most important financial metric for an early-stage venture, because a venture that runs out of cash does not get to test its next iteration.

The standard target for most ventures is eighteen to twenty-four months of runway after each funding round. The reason is that eighteen months allows the venture to hire, iterate, and produce enough evidence to raise the next round. A venture with six months of runway is always fundraising, and a founder who is always fundraising is not running the business.

Key point: the founder’s job is to raise for the downside case, hire for the base case, and monitor the runway weekly.

The interpretive insight is that runway is not a fundraising metric. It is a decision metric, because it determines what the founder can afford to try next. The founder who knows the runway can make deliberate choices about which experiments to run and which to defer, and the founder who does not know it makes those choices by accident.

The projections are a management tool, not a fundraising document

Founders often build the projections once, use them in the pitch deck, and then file them away. That is a mistake. The projections are the model through which the founder runs the business, and the model is useful every month, not only during fundraising.

The monthly routine that makes the projections useful is the variance review. The founder compares the actual results against the projection, identifies which drivers differed, and updates the projection for the next period. The variance is not a judgement on the founder. It is information that tells the founder which assumption was wrong and what to test next.

The four variance categories that matter most are:

  • Acquisition variance — the venture acquired more or fewer customers than projected
  • Retention variance — the customers stayed longer or shorter than projected
  • Revenue variance — the revenue per customer was higher or lower than projected
  • Cost variance — the direct costs were higher or lower than projected

The interpretive insight is that the projections are a mirror of the founder’s understanding of the business, and the variance review is what keeps that understanding current. The founders who review the variance monthly learn faster than the founders who review it annually, and the speed of learning is what determines whether the venture finds a working model before the runway runs out.

Judgement

The case evidence from Airbnb in the United States and Safaricom’s M-PESA in Kenya establishes a proposition that is more useful than either case alone: the quality of financial planning is what determines whether the venture survives long enough to find a working model, and the founders who treat the projections as a management tool outperform the founders who treat them as a fundraising document.

Airbnb’s founding team sold collectible cereal boxes in 2008 to fund the venture when the traditional funding routes were closed to them. That is a cash-flow decision, not a revenue decision, and it reflects the founders’ understanding that runway, not revenue, was what mattered at that stage. As the venture grew, the founders built projections that modelled acquisition cost, retention, and average booking value as drivers, and the model allowed the venture to raise capital at valuations that matched its actual performance rather than its aspirational forecasts.

M-PESA’s financial planning inside Safaricom was shaped by a different constraint. The service required heavy investment in agent networks and mobile infrastructure before it produced revenue, and the financial plan had to justify that investment to the parent company’s board. The plan modelled agent rollout, transaction volume, and revenue per transaction as drivers, and the venture’s survival through the early period of low usage depended on the plan being coherent enough to defend internally.

Both ventures treated financial planning as a management discipline, not a fundraising obligation. Both produced multiple scenarios. Both monitored the actual results against the drivers and adjusted the plan as the evidence arrived. And both survived long enough to reach the scale they now enjoy, in part because the financial discipline gave them the runway to iterate.

The analytical foundations I rely on here are the standard accounting framework for the three statements, the scenario planning method developed by Schwartz (1991), and the venture capital practice on runway and burn rate that has become the standard reference in the startup literature. The standard treatment of financial planning for entrepreneurs undersells three things.

First, it undersells the role of drivers in the projections. Most templates start from a revenue target and work backwards, which produces a projection that is wrong the moment the target is wrong. The founders who start from the drivers build a model that adapts as the drivers turn out differently.

Second, it undersells the downside scenario. The base case is what the founder hopes will happen, and the downside case is what the founder must be prepared for. A venture that raises only enough for the base case is under-capitalised against the probability that the base case will not materialise.

Third, it undersells the variance review. The projections are not a document produced once for investors. They are a management tool that is useful every month, and the monthly variance review is what keeps the founder’s understanding of the business current.

My recommendations follow from that conclusion:

  • Build from the drivers — start the projection from acquisition, retention, revenue per customer, and unit cost, not from a target revenue figure
  • Produce all three statements — the income statement, the balance sheet, and the cash-flow statement answer different questions, and the cash-flow statement is the one that determines survival
  • Build the downside scenario first — the capital requirement is set by the downside, not the base case, and the founder who raises for the base case often does not reach it
  • Target eighteen to twenty-four months of runway — the runway is what gives the venture the time to iterate, and a founder who is always fundraising is not running the business
  • Review the variance monthly — the projections are a management tool, and the monthly variance review is what keeps them useful

The final argument of this article is that financial planning is not what you show investors. It is what you use to run the business. The numbers describe the venture, and the discipline of the monthly review is what turns the numbers into decisions.

Read Also on Kat-Syd Resources Hub

Entrepreneurship and Innovation Part I — Ideation and Opportunity Recognition — The entrepreneurial mindset, source of innovation, and opportunity assessment.

Developing the Business Plan Entrepreneurship and Innovation — Part II — Business plan anatomy, marketing strategy, financial planning, and risk management.

Revenue Growth Playbook Series — Analytical series on the strategies and operating levers that drive sustainable revenue expansion.

Written by Kateule Sydney — Researcher and Writer

© 2026 Kat-Syd Resources Hub. All rights reserved.

Kat-Syd Resources Hub — Educational case studies and analytical reference

You might also want to read

Porter's Five Forces: Deep Dive, Origins & Limits

Porter’s Five Forces is examined here as an industry-analysis framework for understanding competitive pressure and the distribution of economic value. This post traces the framework’s 1979 origins, tests its claims against case applications to East African Breweries and Shopee Indonesia, and evaluates recent conceptual extensions proposed for digital, algorithmic, and platform competition. The central argument is that Five Forces remains valuable within its proper scope, but is neither obsolete nor complete. By Kateule Sydney — Researcher and Writer | Research Audit: 2026-10 | Published by Kat-Syd Resources Hub Porter’s Five Forces is neither obsolete nor complete. It remains a strong framework for analysing industry structure and competitive pressure, but its conclusions should be supplemented when firm-level, ecosystem, technological, regulatory, and dynamic factors materially affect competition. Table of Contents Origins and Purpose What the Five Forces Actually Analyse ...

SWOT Analysis in Marketing: The Complete Framework for Strategic Market Assessment

Strengths, Weaknesses, Opportunities, and Threats — Mapped to Real Marketing Strategy, Case Studies, and Campaign Execution Last Verified: 2026-09-11 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub Source: Kat-Syd Resources Hub / Unsplash Summary: SWOT Analysis remains the most widely used strategic framework in marketing because it forces disciplined thinking about internal capabilities and external forces. This comprehensive guide walks through every stage — the internal marketing audit, external market analysis, the SWOT/TOWS matrix, real-world case studies from Netflix, Apple, LEGO, Starbucks, and DTC brands, plus templates, workshop facilitation tips, and integration with PESTLE, Porter's Five Forces, and VRIO. Table of Contents Introduction — Why Every Marketing Strategy Starts with SWOT Chapter 1 — What Is SWOT Analysis in Marketing? Chapter 2 — Conducting...

Agile Productivity: Why Organizations Accumulate Activity Without Output

A playbook on the productivity paradox, institutional concentration, and the discipline of agile execution Last Verified: 2026-09-12 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub The productivity paradox: organizations generate more activity than output Summary: Despite 43% of executives ranking productivity growth as their top priority, organizations continue to accumulate activity without commensurate output. This playbook examines the structural roots of organizational busyness, introduces institutional concentration as a counterweight, and demonstrates how integrating agility with disciplined focus creates a sustainable productivity model. Table of Contents Introduction — The Productivity Reckoning Chapter 1 — The Productivity Imperative: A Defining Challenge Chapter 2 — The Roots of Organizational Busyness Chapter 3 — Institutional Concentration as a Co...

Formal Planning Systems and Their Limits

This post is a deep dive into Mintzberg's distinction between strategic planning and strategic thinking, and the case for adaptive planning under uncertainty. The analysis is tested against two different adaptations of formal planning under changing conditions, including General Electric's planning evolution and Safaricom's layered planning model. By Kateule Sydney — Researcher and Writer | Last Verified: 2026-10-01 | Published by Kat-Syd Resources Hub Strategic planning versus strategic thinking: analytical discipline versus synthesis Table of Contents The Claim The Witnesses The Practice The Cross-Examination The Defense The Verdict References I Put the Planning-Adaptation Binary on Trial, and the Real Question Is Not Whether to Plan but How The framework I am examining is the distinction between strategic planning and strategic thinking, most clearly drawn by Henry Mintzberg in his 1994 Harvard Business Review article "The Fall and R...

Integrating Management Functions

Bringing together planning, organizing, staffing, directing, and controlling into an integrated framework for management practice. Last Verified: 2026-09-13 | Author: Kateule Sydney | Published by Kat-Syd Resources Hub Integrating the five management functions: planning, organizing, staffing, directing, and controlling. Summary: The integration of management functions represents the culmination of managerial practice, where planning, organizing, staffing, directing, and controlling operate as an interdependent system. This playbook examines how these functions interact dynamically, how managers can diagnose organizational challenges using established diagnostic frameworks, and how management capabilities develop through deliberate practice. Table of Contents Introduction — The Imperative of Integration Chapter 1 — The Interdependence of Management Functions Chapter 2 — Diagnosing ...