Asher's Blog

At the end of every financial year, a company’s financial statements tell a story.

They show what the company sold, what it spent, what it owns, what it owes and how much cash it generated or consumed. But the most useful thing they reveal is not any single number. It is the pattern created by those numbers over time.

Revenue is not just cash; it is a pattern. Cash flow is also a pattern. So are payroll costs, customer acquisition expenses, gross margin, receivables and the amount spent keeping the business running. When you examine these figures across one, two or three years, they begin to show you how the company is being operated. They expose the habits of the business.

The pattern may reveal that customers are paying more, staying longer and buying more products. It may show that each new employee is helping the company create more value. It may show that growth is becoming more efficient and that the company can predictably turn investment into revenue.

But the pattern may also reveal something more dangerous: revenue is rising while cash is disappearing; sales are impressive while margins are deteriorating; headcount is growing faster than output; or the business is becoming busier without becoming stronger.

A company can report impressive sales and still remain dangerously close to failure.

Revenue, cash and profit are not the same thing

Founders often use revenue and cash interchangeably, especially when the business is still young. They are related, but they are not the same.

Under IFRS 15, the central principle is that revenue is recognised when a company transfers promised goods or services to a customer, in an amount reflecting the consideration it expects to receive. That is an accounting event. Cash may arrive before the service is delivered, at the point of delivery or many months afterwards.

This distinction matters. If a customer signs a ₦100 million contract, the company may celebrate the sale. Depending on the contract and the service delivered, some or all of that amount may eventually appear as revenue. But if the customer does not pay for six months, the contract cannot fund today’s salaries. If the cost of delivering it is ₦95 million, the size of the sale also says little about the value retained by the company. If the customer pays in advance for a service that must be delivered over twelve months, the cash has arrived, but the company has also inherited twelve months of obligations.

So a founder must learn to ask four separate questions:

• What did we sell?
• What revenue have we earned?
• What cash have we collected?
• What did it cost us to deliver the value?

Confusing these questions creates false confidence; a large sales pipeline is not revenue. Recognised revenue is not necessarily cash. Cash collected in advance is not necessarily profit. And profit on paper does not guarantee that the company can meet obligations when they fall due.

This is why businesses rarely die because the income statement looks unattractive. They die when they can no longer pay what they owe.

One month is an event; several months reveal behaviour

A strong month can happen for many reasons; a large customer may pay an overdue invoice. A seasonal campaign may work unusually well. A contract may be recognised at a particular point. A weak month can also be misleading because an expected payment arrived a few days late.

The founder’s job is not to overreact to a single month. It is to discover the pattern underneath it.

Is revenue growing consistently or jumping unpredictably? Is growth coming from new customers, higher prices, increased usage or a small number of unusually large contracts? Are customers renewing? Are discounts increasing? Is cash collection improving? Is the cost of delivering each naira of revenue rising or falling?

Patterns make the future more predictable. If a company knows the behaviour of its customers, the timing of collections and the cost required to serve them, it can plan hiring, product investment and expansion with greater confidence. If management cannot explain why revenue changed, then even growth can be a source of risk.

Predictability does not mean that every month must look identical. It means that management understands the forces producing the numbers.

Growth can conceal leakage

When a company is growing, money enters from several places and activity increases everywhere. New staff are hired, events are sponsored, offices expand, trips become more frequent and teams subscribe to more tools. Because revenue is rising, every expense appears affordable in isolation.

This is when leakage becomes difficult to see. A leakage is not always theft, fraud or an obviously wasteful payment. It is any recurring use of money, time or attention that does not create sufficient value for the company. The expense may be legitimate and properly approved. It may even have made sense when it began. It becomes a leakage when nobody continues to ask whether the value justifies the cost.

A ₦100,000 waste repeated every week becomes ₦5.2 million in a year. A poorly designed process repeated across thousands of transactions can consume more money than an extravagant one-off purchase. One unproductive role can lead to additional roles, tools and management time created to support it. Small leaks become a system.

Revenue growth can cover those leaks temporarily. It can make an undisciplined company look healthy because new cash continually arrives to replace what poor operations consume. The danger appears when growth slows. The company then discovers that what it thought was strength was simply movement.

The wrong person is an operating leakage

One of the most expensive leakages in a growing business is a round peg in a square hole: a person whose capacity, attitude or experience does not match the responsibility they have been given.

Salary is only the visible cost. The company also pays for delayed decisions, repeated mistakes, weak execution, frustrated high performers, management supervision and opportunities that were never pursued. If the person manages others, poor judgment is multiplied through the team.

This does not mean every employee must directly sell. Engineering, customer success, compliance, finance and operations create value in different ways. A security engineer may prevent a loss far larger than the revenue of a salesperson. A strong customer-success manager may preserve recurring revenue by reducing churn. A good finance employee may uncover leakages, collect receivables and prevent penalties.

The correct question is therefore not simply, How much revenue did this employee personally bring in? It is, What measurable value does this role enable, protect or create?

Leaders should define that value before hiring. What outcome requires another person? What changes when the person joins? Which constraint will they remove? What evidence, after three or six months, will show that the hire was correct?

Hiring because everyone feels busy is not enough. Sometimes the answer is a better process, automation, a clearer priority or the removal of work that should never have existed.

Revenue per employee is a useful question, not a complete answer

I pay attention to revenue per employee because it forces a company to connect team growth with economic output.

The calculation is simple:

Revenue per employee = Revenue for the period ÷ Average number of employees

If a company generates ₦1 billion in annual revenue with 100 employees, its revenue per employee is ₦10 million. If it later employs 150 people while revenue remains ₦1 billion, the figure falls to roughly ₦6.7 million. That does not automatically mean the new hires were mistakes; the company may be investing ahead of growth. But management should be able to explain what that investment is expected to produce and by when.

The metric is most useful when compared against the company’s own history, plan and business model. A software company, logistics business, bank and manufacturing company require very different labour structures. Comparing them casually can create foolish conclusions. Even within one company, a period of product development may reduce revenue per employee before the product produces returns.

So revenue per employee should not become an excuse to underinvest or exhaust a small team. It is an early-warning question:

Is our organisation becoming more capable as it becomes more expensive? I also like to compare what the company earns per employee with its total cost per employee, including salary, benefits, taxes, equipment, software, office space, travel and management overhead. The gap between those figures gives a more truthful picture than salary alone.

Every role should ultimately contribute to one or more of four outcomes: creating revenue, retaining revenue, protecting revenue or increasing the company’s future capacity to generate revenue. If management cannot connect a role to any of those outcomes, the design of the role deserves another look.

You do not always need to own the talent

Not every capability requires a full-time employee. A young company may need the judgment of an experienced chief financial officer but not forty hours of that person’s time every week. It may need specialist security, legal, regulatory, design or growth expertise for a defined period. Hiring permanently before the workload justifies it can add cost and complexity that the business is not ready to carry.

In those situations, the company can borrow talent. A consultant, fractional executive or experienced adviser can solve a specific problem, establish a system and train younger employees. Used properly, borrowed talent does more than deliver a report. It transfers judgment into the organisation.

This approach must still be managed carefully. Consultants without clear deliverables can become another leakage. The company should define the problem, outcome, duration, decision rights and knowledge-transfer requirement. The objective should be to obtain specialised capability without inheriting permanent cost too early.

Young talent brings energy, adaptability and a lower cost base. Experienced talent brings pattern recognition and the ability to avoid expensive mistakes. A thoughtful company combines both.

In Nigeria, infrastructure turns ordinary expenses into strategy

Some operating costs deserve particular attention in Nigeria and across many African markets because weak infrastructure forces companies to provide privately what businesses elsewhere can take for granted.

Power is an obvious example. Unreliable grid supply pushes businesses towards diesel generators, petrol, inverters, batteries and solar systems. The World Bank’s Distributed Access through Renewable Energy Scale-up programme was designed partly to extend reliable, clean electricity to hundreds of thousands of Nigerian micro, small and medium-sized enterprises—a recognition that electricity reliability is not merely a household issue but a constraint on business productivity.

Transportation has a similar effect. Poor roads, congestion, fuel costs and uncertain travel times can turn a simple delivery or meeting into a material operating expense. For a logistics company, these costs sit at the centre of the business model. For a software company, they may appear as travel, field sales, installations, customer support or office attendance.

These realities cannot be wished away, but they must be measured. A logistics company should understand cost per route, vehicle, delivery and customer. It should know fuel consumption, idle time, maintenance frequency, failed-delivery rates and the effect of road conditions on margins. A company that travels frequently should examine cost per trip and the commercial outcome produced. A business running on alternative power should track energy cost per operating hour, branch, transaction or unit of output.

Without these ratios, management only knows that expenses are increasing. With them, it can identify where the operating model needs to change.

Marketing activity is not marketing return

Events are another common source of invisible leakage. Sponsoring an event feels productive because the company is visible. Executives attend, photographs are taken, the brand appears on a backdrop and people discuss the company online. But visibility is not automatically value.

Before sponsoring an event, the company should decide what it expects to gain. Is the objective qualified leads, enterprise meetings, customer retention, recruitment, regulatory access or brand credibility within a specific audience? How will the company capture contacts? Who will follow up? How long is the expected sales cycle? What would make the expense successful?

If the objective was twenty qualified leads and five sales conversations, report that. If the purpose was strategic relationship-building, document which relationships moved forward. Not every return can be measured immediately in cash, but every significant expense should have a theory of return.

The same principle applies to flights, conferences, advertising, partnerships, discounts and promotional campaigns. Activity should not be mistaken for progress.

Working capital is where profitable companies become anxious

A company can grow revenue and become more cash-constrained at the same time.

Imagine that customers take ninety days to pay, while employees, suppliers, fuel providers and landlords must be paid immediately. Every new contract then requires the company to finance three months of delivery before receiving the related cash. The faster the company grows, the larger the funding gap becomes.

This is a working-capital problem. It explains why profitable businesses can feel continually short of money.

Founders should track days sales outstanding, invoice ageing, payment terms, supplier terms, inventory days where relevant and the cash-conversion cycle. They should know which customers pay reliably, which contracts produce disputes and which revenue is growing only because the company has become a free lender to its customers.

Good collections are not an administrative afterthought. They are part of product design and customer selection. Clear contracts, correct invoices, automated reminders, deposits, milestone payments and incentives for early payment can alter the cash pattern of a business without adding a single new customer. Revenue quality is partly determined by how reliably revenue becomes cash.

Discounts can create a misleading pattern

Revenue may grow because the company is creating more value, but it may also grow because the company is purchasing sales through discounts.

Discounting is not inherently wrong. It can help a company enter a market, encourage annual payment, reward volume or win a strategically important customer. The danger is allowing discounts to become the default response to weak demand.

Management should track gross revenue, discounts, net revenue and gross margin separately. It should know whether discounted customers renew at the normal price and whether their lifetime value justifies the acquisition cost. A company that celebrates gross sales while hiding concessions is learning the wrong lesson from its numbers.

The pattern to seek is not revenue at any cost. It is repeatable revenue with improving economics.

Look for leakage before cutting blindly

Cost discipline does not mean cancelling everything or assuming that the cheapest decision is the best one.

Some expenditure is an investment. Strong security, excellent people, reliable infrastructure, customer service and product quality may look expensive before their returns become visible. Cutting them carelessly can protect this month’s cash while damaging next year’s revenue.

The purpose of studying leakage is to distinguish productive cost from unproductive cost.

Ask of every meaningful expense:

1. What outcome was this cost intended to produce?
2. Is that outcome still important?
3. What evidence shows that the expense is working?
4. Can the same outcome be achieved more simply?
5. Is this cost variable when it should be fixed, or fixed when it should be variable?
6. What secondary costs does it create elsewhere in the company?
7. What happens if we stop, reduce or redesign it?

This method protects the company from indiscriminate austerity. The goal is not to build a small company merely for the sake of being small. It is to build a company in which resources consistently move towards value.

Build a management rhythm around the pattern

Financial statements should not be documents founders encounter only at year-end. By then, the story has already happened.

Management should build a regular rhythm for reading the business. The exact frequency depends on the company, but a useful structure could include:

• Daily: cash position, major receipts and payments, payment reconciliation, failed transactions and unusual movements.
• Weekly: sales pipeline, collections, revenue movement, customer churn, service failures and large discretionary spending.
• Monthly: income statement, balance sheet, cash-flow statement, budget variance, gross margin, runway, receivables ageing and revenue per employee.
• Quarterly: pricing, customer profitability, organisational design, supplier and partner performance, capital allocation and the assumptions behind the annual plan.

Do not merely receive the reports. Interrogate the movements. Why did this line rise? Why did that one fall? Is the change temporary or structural? Which management decision caused it? What happens if the pattern continues for another twelve months?

The purpose is not to predict the future perfectly. It is to see the future early enough to influence it.

The numbers are the consequences of decisions

Every line in a financial statement began as a decision. Revenue reflects decisions about the customer, product, price, distribution and sales process. Payroll reflects decisions about whom to hire, what work to perform internally and how the organisation should be structured. Marketing expenditure reflects decisions about attention and growth. Receivables reflect decisions about credit and collections. Cash flow is the combined consequence of these choices and their timing.

That is why the pattern matters more than the isolated figure. A number tells you what happened. A pattern helps you understand how the company behaves.

When revenue rises, ask what produced it and whether it can happen again. When cash falls, ask where it went and whether the expense created lasting value. When headcount grows, ask whether capability and output are growing with it. When the business looks successful, look for the leakage that success may be hiding.

Revenue is not merely money entering an account. It is evidence of how customers respond to the value you create. Cash flow is not merely a bank balance. It is evidence of how well the company converts that value into endurance.

Read the pattern early, and you can change the story before the year-end financial statements write the ending for you. —

References and further reading

• IFRS Foundation, IFRS 15: Revenue from Contracts with Customers.
• World Bank, “Going Green: Scaling up access to clean electricity for over 17.5 million Nigerians”.
• World Bank, Business Costs of Unreliable Infrastructure.
• Richard Rumelt, Good Strategy/Bad Strategy.
• Ram Charan, Profitable Growth Is Everyone’s Business.