Aigerim Nargelova
Growth is usually a sign that a business is moving in the right direction. More customers, more transactions, a larger team and expanding operations all point to progress. Yet growth can also expose weaknesses that were almost invisible when the company was smaller. A reconciliation that once took an hour begins taking several days. Reporting becomes increasingly dependent on spreadsheets and manual corrections. Responsibilities that were obvious to a small team become less clear as more people enter the process. In some companies, essential financial routines continue to depend on the knowledge of one employee simply because those routines were never formally documented.
For financial reporting and internal control specialist Aigerim Nargelova, these are not isolated accounting problems. They are signs that the financial infrastructure of a business has not developed at the same pace as the organization itself. Nargelova has spent more than 15 years working in accounting, financial reporting and financial-process management, including roles as an economist-accountant and chief accountant. Her experience has covered financial and tax reporting, budget control, audits, analytical reporting and the organization of accounting processes. Over time, her attention shifted from correcting individual errors to examining why the same types of weaknesses continue to appear as businesses become more complex.
That work became the basis for the Nargelova SCALE Framework™, an approach to financial reporting and internal control designed for small and mid-sized businesses. Its underlying premise is straightforward: before a company introduces another approval, checklist or software solution, it should first understand why the existing process is failing. The point is not to create the maximum number of controls. It is to identify the underlying risk, choose a proportionate response and then determine whether that response actually improves the process.
When more control does not mean better control
Finance teams often respond to problems in practical and understandable ways. If reporting is late, management may introduce a stricter deadline. If an incorrect payment occurs, another approval is added. If employees perform the same task differently, a checklist is created. Each response can make sense on its own, but over time a company may accumulate procedures without developing a coherent view of the risks those procedures are meant to address.
A delayed month-end close illustrates the problem. On the surface, it may appear that the accounting team simply needs to work faster. In reality, the delay could be caused by incomplete reconciliations, unclear ownership of particular accounts, information arriving late from operating departments or excessive reliance on manual consolidation. Tightening the deadline may increase pressure on employees without changing any of those underlying conditions. The same logic applies elsewhere: another approval does not automatically improve payment control, more documentation does not necessarily create accountability, and a longer checklist does not guarantee that the most important risk has been addressed.
SCALE approaches the issue in a different order. The framework is organized around five stages — Scan, Classify, Apply, Learn and Expand — but the sequence matters more than the terminology. The organization first examines how a financial process actually works and identifies recurring errors, delays, undocumented activities, manual interventions, unclear responsibilities and areas where the process depends heavily on individual knowledge. Those weaknesses are then considered in terms of their financial, operational, reporting or compliance impact before a control is selected.
This is particularly important in smaller organizations, where financial responsibilities are rarely divided across large specialist teams. A major corporation may have separate functions for financial reporting, treasury, internal audit, compliance and financial systems. A small or mid-sized business may have only a few people covering several of those responsibilities at once. A control structure that is entirely reasonable in a large corporate environment can therefore become unnecessarily burdensome when copied into a smaller company. Multiple approval levels may slow routine transactions, while detailed reporting requirements can consume more employee time than the risk they are intended to manage justifies.
Nargelova’s approach is based on proportionality. A minor procedural weakness may require clearer documentation or better assignment of responsibility. A recurring problem affecting cash, financial reporting or compliance may justify stronger review and regular measurement. Two businesses may display the same visible symptom but require different solutions because the underlying risks are different. The objective is therefore not to standardize every control, but to standardize the reasoning used to decide which control is appropriate.
From professional experience to a structured approach
Nargelova does not present SCALE as a new accounting standard or as a replacement for established principles of internal control. Reconciliation, segregation of duties, documentation, management review and risk assessment are well-established professional practices. The distinction lies in how those elements are organized into a process intended for growing businesses that may not have the resources or specialist functions of larger organizations.
The framework combines financial-process diagnosis, risk classification, control selection, implementation and measurement. It includes diagnostic tools, a proposed model for assessing financial-process risk, control modules and instruments for evaluating whether a control is producing the intended result. One of those instruments is the proposed Nargelova Control Effectiveness Score, which considers factors such as errors, processing time, compliance, recurrence, cost and employee effort. It is not positioned as an external accounting or auditing standard, but as a management tool whose value ultimately depends on practical application and evidence.
That distinction matters because the existence of a control is not the same as evidence of effectiveness. A reconciliation checklist can be completed every month while unresolved differences continue to accumulate. A new approval requirement can reduce one category of error while creating unnecessary delays elsewhere. Even apparently positive metrics can be misleading when viewed in isolation. A process may become faster because important review steps were removed, while an increase in detected errors after a stronger review is introduced may simply mean that the organization has become better at finding problems that previously remained hidden.
For that reason, measurement in SCALE is tied to the problem the organization originally set out to solve. The company first establishes how the process is performing, introduces a response and then examines what changed. Depending on the issue, this could involve recurring errors, processing time, unresolved exceptions, timeliness of reporting or consistency in performing the control. The aim is not to produce more metrics for their own sake, but to establish whether the intervention addressed the risk and whether the improvement can be sustained.
Nargelova’s professional experience with small-business financial processes helped shape this approach. During her more recent work with a New York accounting practice, she dealt with areas including QuickBooks Online reconciliations, transaction reviews, payroll and tax reporting, while also developing checklists and templates intended to make reporting more consistent. The experience reinforced an important distinction in her work: a checklist may help standardize a process, but standardization is only useful once the company understands what should be standardized and why. Otherwise, an inefficient process can simply become an inefficient process that is performed more consistently.
Evidence matters as much as structure
This focus on measurement also influences the way Nargelova presents SCALE itself. The framework includes case studies showing how the approach could be applied in different small-business environments, but those examples are identified as teaching scenarios rather than evidence that particular companies have already achieved specific results through the methodology. Where verified implementation data does not exist, the framework does not assign improvement percentages merely to make the outcome appear more convincing.
That distinction is significant because business methodologies are often judged first by how persuasive their claims sound and only later by the evidence supporting them. A framework can be coherent, detailed and professionally developed while still requiring real-world implementation before its effectiveness can be assessed. In the case of SCALE, the architecture is already defined; the next stage is to build a larger body of documented implementations showing what a process looked like before an intervention, what was changed and what happened afterwards.
For Nargelova, this is not separate from the logic of the framework. A methodology based on evidence-driven financial control should itself be evaluated through evidence. If a company cannot establish what changed after a new control was introduced, it should be cautious about attributing an improvement to that control. The same principle applies when evaluating the methodology across different organizations.
That also places limits on how SCALE should currently be described. It can be presented as a developed framework with a defined diagnostic, risk, control and measurement structure, but broader claims about effectiveness depend on documented implementation. This distinction makes the approach less dramatic than business frameworks built around promises of rapid transformation, but it also makes the question of validation much clearer.
From one business to a repeatable model
The longer-term challenge is whether the approach can be applied beyond the work of its original developer. Small and mid-sized businesses may encounter similar categories of problems — delayed reconciliations, inconsistent documentation, manual workflows, unclear responsibilities and dependence on individual employees — but that does not mean they need identical controls. A retailer struggling with cash reconciliation may need a different response from a professional-services firm facing a slow month-end close or a distributor experiencing weaknesses in accounts payable.
What can be repeated is the method used to reach the solution. The process begins by identifying where the weakness actually sits, evaluating the risk it creates, selecting a response that fits the organization and then measuring the outcome. This distinction between standardization and uniformity is central to SCALE. A methodology becomes more transferable when other qualified professionals can reproduce its decision-making logic without being required to impose the same solution on every business.
This is one reason the framework considers accounting and advisory firms as a possible route for wider implementation. Such firms already work across multiple small-business clients and often see different versions of the same financial-process problems. Under Nargelova’s model, the role of the accounting professional would not be simply to distribute a standard package of templates. Instead, firms could use a common diagnostic and risk-assessment process while adapting the actual controls to the circumstances of each client. Training, professional workshops and implementation guidance are intended to support that transfer of the methodology rather than merely increase distribution of its documents.
The scale of the small-business sector makes that question relevant. The U.S. Small Business Administration’s Office of Advocacy reports more than 36 million small businesses in the United States, employing more than 60 million people. The size of the sector does not automatically make any particular financial-control initiative significant, but it does highlight the practical value of approaches that can address recurring process weaknesses without assuming that every company should operate like a large corporation.
Whether SCALE can ultimately achieve that level of transferability will depend on evidence from real implementation. Wider use alone would not establish effectiveness. The more meaningful questions are whether the correct problems are identified, whether the selected controls address the underlying risks, whether improvements are measurable and sustainable, and whether other qualified professionals can reproduce the process across different business environments.
For growing companies, the broader lesson is more immediate. Financial systems cannot remain static while the organizations around them become more complex. Sometimes the appropriate response will be new technology. In other cases, it may be stronger documentation, clearer ownership or a different control. But when the same financial problem continues to return, adding another procedure should not automatically be the first response.
The better starting point is to understand why the process is failing in the first place.
