Asher's Blog

Founders often talk about scaling as if it were simply the decision to do more: hire more people, enter more markets, spend more on marketing, add infrastructure and raise more capital. Those activities may accompany scale, but they do not create the operational readiness required to survive it.

Scaling is not merely growth. A business can grow through heroic effort, founder intervention and temporary improvisation. Scaling begins when the company can handle materially more customers, transactions, employees and complexity without quality collapsing, costs becoming uncontrollable or the founder turning into the only person capable of resolving every important issue.

Let us assume the founder has already answered the earlier question. Customers love the product, the market is sufficiently large, retention is encouraging and there is a credible economic case for expansion. The problem is worth building around, and the time to scale appears to have arrived. What must the founder get right operationally before pressing the accelerator?

My first answer is financial visibility. The second is leadership quality. Around those two sit several supporting systems: clear metrics, repeatable processes, reliable technology, customer-support capacity, controls, accountability and enough cash discipline to absorb the mistakes that expansion will inevitably expose.

The central principle is simple: scale does not repair weak operations. It multiplies whatever is already present.

You must know when you are making money and when you are losing it

Before scaling, a founder needs a finance system that can tell the truth about the business. It should show where money comes from, where it goes, which products and customers create value, which activities consume cash, what obligations are approaching and how much time remains before the company faces a liquidity problem.

This sounds obvious, but many young companies operate on bank-balance accounting. If the account balance is increasing, they assume the business is healthy; if it is falling, they become worried. A bank balance is important, but it does not tell you whether the money belongs to customers, whether taxes or payroll are due, whether an annual contract has been collected upfront for services that must be delivered over twelve months, or whether a large payment temporarily hides an unprofitable model.

A company preparing to scale should be able to produce accurate financial statements on a reliable schedule. The founder should understand the income statement, balance sheet and cash-flow statement well enough to ask intelligent questions, even if a finance professional prepares them. Revenue should be recognised correctly. Customer funds must be separated from operating cash where applicable. Receivables, payables, payroll, taxes and statutory obligations should be reconciled. The company should have a budget, a forecast and a process for comparing actual performance against both.

Most importantly, the founder must understand the difference between profit and cash. A company can report revenue and still be unable to meet payroll because customers have not paid. It can collect substantial cash and still be economically unhealthy because that cash was obtained through debt, advance payments or funding rather than profitable operations. It can appear profitable while postponing critical investments or failing to recognise liabilities.

If you cannot explain why cash moved last month, you are not ready to multiply the volume of those movements.

Build a financial operating system, not a year-end accounting ritual

Some founders treat finance as the work an accountant performs after the year has ended, mainly to file taxes or produce audited statements. That is compliance, not financial management. A scaling company needs finance to function as a daily and monthly operating system.

At minimum, that system should answer several questions without a prolonged investigation. What revenue did we earn, and from which products, segments and geographies? What is our gross margin? How much cash did operations generate or consume? What are our largest cost movements? How much is owed to us, and how much do we owe? What is our current runway? Which customers are becoming less profitable to serve? Where are we experiencing leakage, fraud, duplication or unexplained variance?

The answers will vary by business model. A software company may focus on recurring revenue, gross retention, net revenue retention, customer-acquisition cost, payback period and gross margin. A marketplace will care about transaction volume, take rate, repeat behaviour, contribution margin and the balance between supply and demand. A lending business must understand defaults, recoveries, cost of capital and liquidity. A payroll or financial-technology company must also pay close attention to reconciliation, safeguarding, settlement timing, regulatory obligations and the difference between transaction volume and earned revenue.

This is why copying another startup’s dashboard can be dangerous. The metrics must reflect the economic engine and principal risks of your own company.

Verne Harnish’s Scaling Up organises execution around people, strategy, execution and cash. The inclusion of cash is not incidental. Growth creates demand for working capital before it creates comfort. New employees must be paid before their full productivity arrives, marketing is funded before customers convert, infrastructure is purchased before capacity is consumed and large customers may negotiate longer payment terms. A business can grow itself into insolvency if its cash cycle is misunderstood.

Scaling should therefore begin with a finance cadence: daily visibility where risk requires it, a disciplined monthly close, regular forecasts and clear ownership of every significant number.

The founder needs one intelligent dashboard every morning

Operational readiness does not mean overwhelming the founder with hundreds of charts. When everything is presented as critical, nothing receives proper attention. The aim is to identify a small number of measures that reveal whether the company’s engine is healthy.

I believe a founder should be able to open one intelligent dashboard every morning and understand what requires attention. It should not attempt to replace detailed departmental reports. It should function like the instrument panel of an aircraft: enough information to reveal direction, performance and danger, with the ability to investigate further when something is outside the expected range.

The dashboard might include cash available, runway, revenue movement, collections, new customers, activation, retention, transaction success, major incidents, unresolved customer issues and a measure of team capacity. A regulated or transaction-heavy company may need daily reconciliation exceptions, settlement exposure, fraud indicators and customer-fund positions. An enterprise business may need pipeline movement, implementation status and concentration risk.

Every metric should have four properties. It should be clearly defined, consistently calculated, owned by a named person and connected to a decision. If a number changes and nobody knows what action follows, it may be interesting information rather than an operating metric.

The founder should also resist dashboard theatre. Beautiful visualisations do not compensate for unreliable data. If revenue is calculated differently by finance and sales, if customer counts include inactive accounts, or if incidents disappear because teams classify them inconsistently, the dashboard creates false confidence. Before scale, the company needs a common language for its numbers and a dependable data trail behind them.

Peter Drucker is often associated with the idea that what gets measured gets managed, although the popular wording is frequently oversimplified. Measurement alone does not produce management. People can optimise the wrong metric, manipulate targets or ignore qualities that are difficult to quantify. The founder’s task is to choose measures that illuminate reality without allowing the measure to become a substitute for judgment.

Know your unit economics before adding volume

A business is not operationally ready to scale if it does not understand what happens economically when one more customer, order, employee or transaction is added.

The question is not simply whether revenue increases. What is the incremental cost of serving that growth? Does customer support expand in a roughly linear way, or does the product reduce service effort over time? Are transaction fees higher than the fees charged to customers? Does each sale carry hidden implementation work? How long does it take to recover customer-acquisition spending? How many customers remain long enough for the relationship to become profitable?

Founders sometimes assume that losses will disappear at scale because fixed costs will be spread across more revenue. That can happen, but only if the fundamental transaction is healthy or has a credible path to health. If each additional customer creates an avoidable loss, growth multiplies the problem. If the business is subsidising behaviour that will disappear when the subsidy ends, volume may be evidence of purchased activity rather than durable demand.

Unit economics must also include the costs founders prefer not to see: payment processing, refunds, fraud, cloud infrastructure, onboarding, customer success, discounts, commissions, compliance, failed transactions and the founder’s own manual intervention. A margin calculated before the real cost of delivery is not a margin you can scale.

The company does not need every number to be perfect. It does need to know which assumptions are proven, which are improving with volume and which remain dangerous.

Hire leaders who have crossed the terrain before

The second major requirement is leadership. Once a company begins to scale, the founder cannot personally carry every function. The organisation needs people who can translate the founder’s vision into plans, systems, decisions and outcomes without waiting for constant intervention.

This is when I advise founders to look for the best of the best. An average leader may be able to maintain an existing department, but a scaling company needs leaders who can build. They must recruit stronger people, create operating rhythms, manage resources, confront underperformance, make trade-offs and preserve standards while the environment changes rapidly.

Experience matters, particularly experience with the next stage you are entering. Someone who successfully led a team of ten may not yet know how to lead one hundred, while an executive from a company of ten thousand may struggle to work without the infrastructure, brand and resources that supported them there. The ideal leader is not simply the person with the most prestigious employer on the CV. It is the person whose judgment, energy and experience match the problems the company will encounter next.

Look for evidence. What did this person build? What was broken when they arrived? Which metrics changed? Whom did they hire and develop? How did they perform when capital was constrained? Can they explain a failure without blaming everybody else? Do former colleagues trust them? Can they move between strategy and detail without becoming trapped in either?

Andy Grove’s High Output Management offers a useful way to think about managerial leverage: a manager’s output is connected to the output of the teams and neighbouring groups influenced by that manager. The implication for a founder is significant. A brilliant individual contributor may create excellent personal work, while a strong leader creates the conditions in which many people produce excellent work. At scale, leverage matters.

Do not hire executives merely to remove work from the founder

Founders sometimes hire senior people because they are tired. They want somebody to “take sales,” “handle operations” or “own product” so the problem will disappear. That motivation can produce a very expensive mistake.

A leader needs a clear mandate, decision rights, resources, measurable outcomes and a founder who is willing to let the person lead. If the founder keeps overriding every decision, the executive becomes a highly paid coordinator. If the mandate is vague, the leader may build an organisation around a different interpretation of success. If incentives reward growth without regard to margin, risk or retention, the leader may reach the visible target while damaging the company underneath.

Before making a scaling hire, define what success should look like after twelve to eighteen months. Clarify what the leader owns, which decisions require consultation and which boundaries cannot be crossed. Give access to the information needed to do the job. Establish a regular review rhythm, then evaluate outcomes and behaviour rather than relying on charisma.

The best leaders also improve the quality of disagreement. They should be able to tell the founder that an assumption is wrong, support their view with evidence and remain committed after a decision has been made. A company in which every senior person agrees immediately with the founder is not necessarily aligned; it may simply be afraid.

Turn founder knowledge into organisational knowledge

Early companies often run on information stored inside the founder’s head. The founder knows why a special price was offered, which customer requires a manual step, which engineer understands an old system and which promise was made during a sales conversation. That may work with a small team, but it becomes a serious operational risk when volume grows.

Before scaling, the company should identify its critical processes and make them understandable, repeatable and owned. This does not mean producing a hundred-page manual for every task. It means that important work should not depend entirely on memory, personality or the presence of one employee.

Start with processes whose failure could damage customers, cash, compliance or reputation: receiving and safeguarding money, approving payments, onboarding customers, releasing software, responding to incidents, managing access, reconciling accounts, handling complaints, calculating payroll, meeting statutory deadlines and recovering from system failure.

For each critical process, someone should be able to answer: Who owns it? What triggers it? What does good completion look like? Which controls prevent error or fraud? What is the escalation path? What happens if the owner is unavailable? Which evidence proves the process occurred?

Process should not become bureaucracy. The purpose is not to slow intelligent people down, but to stop the organisation from solving the same preventable problem repeatedly. A good process absorbs learning and makes the next execution more reliable.

Reliability must precede demand you cannot safely serve

Scaling exposes product and infrastructure weaknesses because greater volume creates more opportunities for every rare failure to occur. An error that affects one transaction in ten thousand may feel insignificant at low volume; at millions of transactions, it becomes a regular customer event.

Before accelerating demand, founders should know the limits of their systems. Can the product handle a sudden increase in concurrent users? Are backups tested rather than merely configured? Can the company restore service after a failure? Are monitoring and alerts connected to people who can respond? Are permissions controlled when employees join, change roles or leave? Is sensitive customer data encrypted and auditable? Are software releases reversible?

For businesses handling money, payroll, identity or regulated information, reliability is not an engineering preference. It is part of the product promise. A customer does not care that the interface is beautiful if salaries fail, funds cannot be traced or private data is exposed.

Operational readiness also includes the human side of reliability. Who communicates during an incident? Who decides whether to stop transactions? How quickly will customers be informed? What will the company learn afterward? A mature incident review does not exist to find somebody to punish. It identifies the conditions that allowed failure and ensures the same failure becomes less likely.

Customer support must scale with the promise

A company is not ready for rapid growth if every new customer increases confusion faster than value. Before scaling acquisition, founders should examine onboarding, education, support and customer success.

Where do customers become stuck? How long before they receive the promised value? Which questions are repeated every day? What percentage of issues require engineering intervention? How long do enterprise implementations take, and who owns the handoff from sales? Are salespeople promising features or timelines operations cannot deliver?

Support tickets are not merely a cost to reduce. They are a form of product research. Repeated questions may reveal poor design, unclear language, missing automation or a gap between the product being sold and the product customers actually experience.

The goal is not to remove human support from every situation. Some customers and high-stakes processes require excellent human judgment. The goal is to decide deliberately where human intervention creates value and where better product design should make intervention unnecessary.

If the company acquires customers faster than it can onboard and support them, marketing success will create reputational failure.

Controls are not the enemy of speed

Founders sometimes resist controls because they associate them with large-company bureaucracy. Yet a company that is moving faster and handling more money needs stronger protection against error, fraud and concentration of authority.

No single person should be able to create a vendor, approve a payment and conceal the transaction without review. Bank and payment accounts should be reconciled. Material contracts should have appropriate approval. Customer funds and company funds should not become casually mixed. Access to systems should follow roles, and sensitive actions should leave logs. Regulatory filings, taxes and employee obligations should have owners and calendars rather than depending on memory.

The exact control environment should fit the company’s size and risk; imposing public-company procedures on a ten-person startup can be wasteful. Still, basic segregation of duties, reconciliations, approvals and audit trails should emerge before volume makes their absence catastrophic.

Good controls actually support speed because people know the boundaries within which they can act. Without them, every decision rises to the founder, or the company discovers too late that trust was being used as a substitute for verification.

The operating cadence should convert information into decisions

Metrics, reports and leaders become valuable only when the company has a rhythm for using them. A scaling organisation needs an operating cadence that allows information to move, decisions to be made and commitments to be reviewed.

Daily check-ins may be appropriate for revenue, incidents, cash movements or time-sensitive operations. Weekly leadership meetings should focus on major outcomes, constraints and decisions rather than departmental narration. Monthly reviews should examine financial performance, customer health, product reliability, people and progress against the operating plan. Quarterly sessions can address strategy, capital allocation and whether assumptions about the market remain valid.

Every meeting should have a purpose. Information that can be read should usually be circulated in advance. The meeting should concentrate on understanding variance, resolving conflict, assigning ownership and deciding what happens next. Actions need named owners and dates, while unresolved risks should remain visible until they are genuinely closed.

This cadence is how a founder stops carrying the whole company mentally. The organisation begins to observe itself, correct itself and learn at a speed that does not depend on one person’s memory.

Test scale before committing the whole company

Operational readiness should be tested, not assumed. Before a national launch, a large marketing campaign or a major enterprise rollout, conduct controlled exercises that expose weakness while the consequences remain manageable.

Increase transaction volume in stages. Onboard a demanding customer. Simulate the failure of a critical vendor. Test whether backups restore correctly. Run a cash-flow stress scenario in which collections are delayed and costs rise. Ask what happens if a key leader leaves, an account is compromised or customer support volume triples.

The purpose of stress testing is not pessimism. It is to discover whether the organisation’s confidence comes from evidence or from the fact that it has not yet faced sufficient pressure.

This is especially important in Africa, where businesses may have to plan around currency volatility, unreliable infrastructure, policy changes, payments disruption and limited access to emergency capital. Resilience cannot be imported at the moment of crisis. It has to be designed into cash reserves, vendor choices, technical architecture and decision-making authority.

A practical operational-readiness test

Before scaling seriously, I would expect the founder and leadership team to answer these questions clearly:

• Can we close our accounts accurately and explain revenue, costs, cash movement and obligations?
• Do we know our unit economics, including hidden delivery and support costs?
• Can the founder see a small set of reliable operating metrics every morning?
• Does every critical metric have one definition, one source and one owner?
• Do we have leaders who can build the next stage rather than merely maintain the present one?
• Are decision rights clear enough that the organisation can move without waiting for the founder?
• Are our most important processes documented, controlled and able to continue when one person is absent?
• Can our product and infrastructure handle materially more volume without unacceptable failure?
• Can customer onboarding and support absorb growth without destroying trust?
• Do we have controls around cash, customer funds, access, approvals, contracts and compliance?
• Is there a regular cadence for reviewing performance, making decisions and following through?
• Have we tested adverse scenarios, and do we have enough runway to survive execution mistakes?

If the answers are vague, the company may still choose to grow, but the leadership should recognise that it is scaling unresolved risk.

Scaling should make the company stronger, not merely larger

The operational work that precedes scale can feel less exciting than launching in a new country or announcing a large funding round. Finance systems, reconciliations, dashboards, leadership mandates, access controls and process ownership rarely attract public applause. Yet these are the foundations that allow ambition to become durable.

The founder does not need a perfect company before scaling. Perfection is impossible, and waiting for it can become another form of fear. What the founder needs is visibility into the most important truths, leaders capable of carrying responsibility, processes that protect customers and cash, and an organisation able to detect and correct failure before it becomes existential.

Set up finance so you know when you are making money, when you are losing it and why. Build one trustworthy dashboard that tells you what requires attention every morning. Recruit exceptional leaders who have evidence of building through the next stage. Give them clear ownership and the authority to produce outcomes. Turn knowledge into repeatable systems, prepare your product and support functions for greater volume, and put controls around the areas where one mistake could destroy trust.

Then scale.

Because the objective is not simply to become a bigger company. It is to become a company that can carry greater responsibility, serve more people and deploy more capital without losing control of the qualities that made growth possible in the first place.