Why Small Businesses Should Build Systems From Day One

Small businesses that say ‘we’ll get organised once we grow’ usually never do. That might sound like a provocation, but after watching dozens of small enterprises across Turkey’s provincial and urban markets, I keep arriving at the same conclusion: the most frequent reason for failure is not bad luck, poor demand, or a difficult sector. It is deferred structure. I once spoke over lunch with a food producer in Eskisehir who had moved from wholesale distribution of flour and sugar into his own branded biscuit line. For the first six months, everything lived inside his head: which customer owed how much, which supplier batch was paid, whose cheque was due when. By month seven, his mental load was full, errors started appearing, and he began losing clients. ‘I don’t have time to keep records,’ he said. What he actually meant was: there is no system for keeping records. The missing resource was not time. It was infrastructure.There is no threshold at which building a system is considered ‘too early.’ The moment you need one is the moment to build it. This view conflicts directly with the logic many small business owners have internalised: find the work first, get organised later. That logic rests on an assumption — that systems emerge naturally as volume grows, that once turnover increases, orderly bookkeeping becomes inevitable. This is partly true, but it misses the critical point. A system is not the product of growth; it is the condition for it. A business that keeps no records does not grow. And if it does manage to grow, it cannot sustain that growth, because every decision depends on the owner’s recall. When the owner is ill, exhausted, or distracted, the business stalls. That is not a management problem. It is a structural one.Cash flow is where this failure is most visible. In Turkey’s small commercial market, deferred payment terms remain dominant. Post-dated cheques and promissory notes still serve as primary settlement instruments, and most small operators track receivables through a physical folder system or memory alone. Without a system, the answer to ‘do we have cash?’ is an estimate, not a fact. Consider a small paint and building materials merchant in Ankara with 48 credit customers whose payment dates he memorises. One day, a cheque date passes unnoticed, collection is delayed. That month, rent and social insurance contributions fall due at the same time, and a cash gap opens. The owner’s mental sharpness has become the sole variable determining the business’s continuity. That is not a sustainable operating model under any interpretation.Defining ‘system’ narrowly as accounting software is another common mistake. Here, system means: every transaction is recorded, receivables and payables are tracked, weekly cash position is visible, and the operation continues functioning when the owner is absent. Building this does not require an expensive software suite. In 2010, lean accounting and basic front-end bookkeeping solutions from Turkish software providers were already available at accessible price points for small-scale operators. The obstacle was not technology. It was commitment. The transition required the owner to have already decided: this must be done. That decision, in most cases, was made during a crisis, too late to prevent the damage it was meant to address. A caveat belongs here: installing a programme is not the same as building a system. Entering data consistently, reading the ageing receivables report every Monday, running a forward cash projection — these are habits, not features. Software creates value only to the extent that it supports those habits.The second dimension of system-building in small teams is leadership and responsibility distribution. In a one- or two-person operation, the word ‘system’ may carry an unnecessarily corporate resonance. But the question is simple: when the owner is not present, how are decisions made? Is there any written framework for which customers can receive goods on credit, which orders are prepared first, which payments can be deferred? The owner of a small furniture accessories workshop in Bursa once described to me a production loss that occurred when an apprentice made 312 components to the wrong specification. ‘The measurements were not written down; I always told them verbally,’ he said. That day, the person who would have given those measurements was not on the floor. A written production instruction would have prevented the loss, or caught it far earlier. A system is a safety net. In a small team, without that net, every operation is bounded by the cognitive capacity of one person.So when should a system be built? The answer is direct: when the first customer is acquired, or when the first sale is made. If there is more than one customer, more than one product, or more than one payment term in play, a system is not optional. Three steps that can be put into practice on Monday morning follow. First, for one full week, record every incoming and outgoing amount — without linking it to anything else — in a notebook or a simple bookkeeping programme; at the end of the week, calculate your open position. Second, list every receivable alongside its due date in a single document and update it every Monday morning. Third, build a 30- and 60-day cash projection: what comes in this month, what goes out, and where is the gap? These three steps are the starting point for building a system. They are not perfect, but they are categorically better than the current state in most small businesses operating without one. System-building starts with commitment, not scale. The cost of not starting is always higher than the cost of starting.

This article was originally published in Turkish by Gökhan MERCANOĞLU on April 29, 2010. The English edition has been reviewed and edited by the author.


strategic finance creates lasting value only when user behavior, executive ownership, and data quality are handled together. Technology does not create transformation by itself; it only makes the need for transformation more visible. Success is less about the system working and more about the organization learning to work with it.


Gökhan Mercanoğlu
Finans Yönetimi