Author

Dmitrii Kaplev is a finance business partner in the technology and gaming sector based in Cyprus

Before scaling, a profitable project should be assessed to ensure it does not deplete the organisational capability necessary to sustain its results. Such an assessment can reveal not only that revenue is growing but that technical debt is too, with key competencies concentrated in one employee, and teams increasingly reliant on urgent interventions.

Such conditions are rarely reflected in investment appraisal analytics. But it is exactly these conditions that may define whether current financial results can be reproduced at a larger scale. To approve investment in future growth, a finance business partner needs to answer an important question: what needs to be true for these economics to be repeated?

A scaling decision depends on the health of the productive systems involved

Misleading profitability

Let’s have a look at a notional case of a game development company considering increasing its quarterly budget by US$250k to broaden a live-ops calendar from 10 to 14 events; live-ops is continuous post-launch game management through the addition of events, new content (heroes, locations, etc), offers and community interaction.

A recent quarter has brought in US$1.8m in attributable revenue. After taking into account the cannibalisation effect, platform commissions, variable costs and team costs, the live-ops contribution is US$200k. The finance team has estimated that four additional events, based on the most successful event formats, would generate an additional US$400k. Deduct the planned investment of US$250k, and that’s another US$150k in profit. This prognosis depends on the reuse of formats that already generate the main portion of profits but also pressure players’ paying behaviour and the capacity of the engineering team.

Capability reconciliation rolls forward what underpins profitability

Operational data casts doubts over the decision to expand the events calendar. Three established event formats are generating 75% of quarterly contribution. A single specialist remains the only holder of undocumented assumptions. Several events have required urgent engineering support, which have inflated technical debt and the development backlog. Aggressive monetisation events have also caused negative player sentiment.

The team improved the documentation and have also begun internal training on event economics. Analytics report that forecast accuracy improved and reusable development components reduced events’ lead time.

While live-ops is currently profitable, a scaling decision depends on the health of the productive systems that enable this output.

Capability reconciliation

Organisational capability is the ability to reproduce relevant financial results in realistic operational conditions by combining people, processes, knowledge, technology and relationships. Capability reconciliation is an extension to management accounting that shows the roll-forward of the capability that created the financial results. It looks like an accounting roll-forward, which is done on a narrative basis without assessing any monetary or quantitative values.

Extra analysis is useful only when it may affect the decision

The finance team analyses three elements during the period:

  • Additions strengthen the productive system. They include reusable instruments, documented procedures, forecasting process and knowledge continuity.
  • Depletions weaken the system. They include rise of technical debt, loss of expertise, shrinkage in capacity, and reduction of planned maintenance.
  • Remaining exposures are there in the beginning and end of the period. It can be key-employee dependency, supplier concentration and many others.

The goal is to determine if these elements affect the initial investment decision. The method follows a simple rule: extra analysis is useful only when it is capable of affecting the decision.

Analysis can alter decisions

In a live-ops case, improved tooling and forecasting add to capability. Accumulating technical debt and engineering capacity are depletions. Knowledge concentration and dependence on successful formats are the remaining exposures.

The initial decision was to approve immediate calendar expansion from 10 to 14 events and an additional budget of US$250k. After capability reconciliation the decision was made to approve a budget of US$80k to improve the live-ops capability: documentation, tooling, knowledge transfer and testing of two new event formats. The remaining US$170k of initial budget was not allocated and was made subject to subsequent review.

Capability reconciliation can transform a binary investment decision into a staged capital allocation, where financing is released on the condition of operational readiness. This change is the decision delta, achieved by application of this method.

A new method

Balanced scorecard connects perspectives such as client relations, internal business processes, learning and growth with finances via a unified strategy and overarching vision. Capability reconciliation solves a narrower problem: it starts with one pending decision (eg resource allocation) and reconciles how one important capability was created, improved or depleted during the period.

Finance should coordinate economic logic and decision documentation

Intellectual capital frameworks, integrated thinking and research into ordinary and dynamic capabilities have developed related perspectives on resources that are foundational for future value creation. Capability reconciliation maps similar data directly to the specific decision and shows how it transformed the initial choice.

Traditional investment appraisal techniques such as net present value, internal rate of return or payback period have proven their value to decision-making. But even these classical methods work better in combination. And capability analysis is yet another angle that helps improve the quality of investment decisions and make them more balanced, forward-looking and robust.

Ideally placed

Finance is at the intersection of operations, forecasting, risk and capital allocation. Finance managers and business partners can define the decision, verify underlying assumptions, identify missing evidence, critically evaluate the conclusions of non-finance teams, and track how new data affects the resource allocation decision. Finance should coordinate economic logic and decision documentation, without taking ownership of the capability.

Here is a practical starting point. Spend 10 minutes and answer these three questions:

  • What capability makes this financial result repeatable?
  • What capability elements were created or depleted during the recent period?
  • What evidence might change, reinforce or condition the initial decision?

Day-to-day management assigns deadlines and owners to immediate problems. Depletion of organisational capability is happening slowly and is thus less visible to manage. The main problem here is that profitability may hide the depletion of organisational capability. Finance’s role is to make it visible before management approves the next investment.

Not just for gaming

The lessons from the live-ops example in the article can be applied to other sectors:

  • professional services: a firm may increase revenue by taking on more clients, but as a result senior staff become overstretched, mentoring declines and service quality deteriorates
  • manufacturing: a business may boost margins by deferring equipment maintenance, but in doing so increases the risk of breakdowns and future capital expenditure
  • retail: a company expands its store network but may be relying on an increasingly stretched logistics operation, undermining customer service and delivery performance.
Advertisement