Growth Is Not Enough How to Build a Management System in a Fast-Growing Company
Growth Is Not Enough: How to Build a Management System in a Fast-Growing Company
In June 2024, I assumed the General Manager role at a project-based real estate development company. On the surface, sales were not the primary proble
The company had strong demand-generation capability and substantial growth potential. New projects were coming in, the team was expanding, and business volume was rising. Yet in the same management meeting, different answers could emerge about a project's progress, financial outcome, collection schedule, and delivery risk.
Sales were growing. Sales, operations, finance, legal, and project management were not maturing at the same pace.
"Was the company truly scaling, or was business volume growing faster than management capacity?"
When I took the role, monthly revenue was approximately TRY 20 million, the company employed 17 people, and the active portfolio consisted of 7 projects. After a transformation lasting more than eighteen months, monthly revenue reached TRY 140 million, headcount rose to 87, and the active portfolio expanded to 33 projects.
This case, however, is not about the numbers. It is about how we built the management capacity required to carry them.
The Starting Point
In project-based companies, every new assignment creates more than revenue. It also creates working-capital demand, delivery commitments, legal obligations, operational load, and coordination requirements.
At the outset, some critical information lived in people's memories, separate files, or disconnected tracking methods. Projects were moving, but financial performance, operational progress, customer commitments, and management decisions did not come together in one view.
The problem was not a lack of effort. The problem was that intense effort had not yet become a shared management system.
First Observation — See
My first observation was simple:
"The first sign of growth appears in the sales figures. The first sign of losing control appears when the same question receives different answers."
Loss of control rarely begins with a major crisis. Delivery dates start moving. Sales and operations interpret the same commitment differently. Finance sees the collection schedule but not the project's physical progress. Management meetings become information-gathering sessions instead of decision-making forums.
The General Manager then starts closing information gaps between departments instead of managing the system.
When the symptoms were read together, the real issue was clear: business volume had grown, but the management architecture had not grown with it.
The Real Diagnosis — Read
At first glance, the answer might have appeared to be more people, new software, or more frequent meetings. The underlying issue was the gap between business volume and management capacity.
Gap
Diagnosis
Organizational gap
Finance, Operations, Sales, Legal, Digital Media, and Project Management were not at the same level of maturity.
Visibility gap
A project's commercial, financial, operational, and legal status could not be monitored in one management view.
Accountability gap
The person performing an activity and the person accountable for the outcome were not always defined with equal clarity.
Management cadence gap
There was no standard for what information would become a decision, by whom, how often, and in which meeting.
The diagnosis was clear: the company did not lack work. It lacked a management system capable of carrying its growth.
The Measurement System — Measure and Manage
Monthly revenue and project count were outcome indicators. Management needed earlier visibility into the mechanisms creating — or threatening — those outcomes.
For every active project, we brought the following fields into a single management view:
- Contract value and revenue potential
- Collected and outstanding amounts
- Physical progress
- Planned and actual cost
- Delivery date and critical risk
- Pending decision and next action
- Project owner and escalation requirement
Project tracking therefore moved beyond "Is the work progressing?" to "How are value, cash, risk, and decisions progressing?"
Let's Pull a Rabbit Out of the Hat
I call the practical framework derived from this case the Growth Capacity Matrix.
Capacity
Management question
Commercial capacity
Can the company generate new customers and projects?
Operational capacity
Can it deliver what it sells on time, at the required quality and cost?
Financial capacity
Can it carry the working-capital, collection, and cash requirements created by growth?
Management capacity
Can its decisions, accountabilities, data, and escalation mechanisms manage the increased business volume?
True scaling requires all four capacities to grow together. If commercial capacity grows faster than the others, the company can sell but cannot deliver. If operational capacity expands while financial capacity falls behind, the company can stay busy without generating cash. If headcount increases without stronger management capacity, the organization becomes larger but coordination becomes weaker.
"A company's safe growth limit is determined not by its strongest capacity, but by its weakest management capacity."
The Growth Capacity Matrix is an application layer of the Management Integrity Model. It brings strategy, organization, authority, accountability, decision systems, performance, and governance together around one question: can the company carry its growth?
The Transformation Plan — Transform and Scale
The first step was not to buy new software. It was to make the company's actual way of working visible. We brought active projects, revenues, collections, owners, delivery dates, and open decisions into one management perspective.
We then strengthened the organizational backbone. Finance, Operations, and Sales were developed. A Legal function was established to manage the growing volume of contracts and obligations, while a Digital Media function was created to support market visibility.
We moved project tracking out of individual memory and separate files into a shared business platform. The objective was not simply to use software. It was to make projects, owners, open items, and decisions visible.
We then established a management cadence: weekly project and operations reviews, cash and collection tracking, sales-to-operations capacity alignment, escalation for critical issues, and outcome reviews with functional managers.
Every meeting had to answer four questions:
- What happened?
- Why did it happen?
- What decision is required?
- Who will act, and by when?
We treated delegation not as assigning tasks, but as defining the decision boundary, expected outcome, tracking indicator, and escalation condition together.
Results
Indicator
Starting point
Result
Monthly revenue
TRY 20 million
TRY 140 million
Headcount
17
87
Active project portfolio
7
33
Finance, Operations, and Sales were strengthened. Legal and Digital Media functions were established. A management infrastructure supporting project visibility, follow-up, and accountability was put in place.
These outcomes were also shaped by the owners' entrepreneurial capacity, employees' effort, customer demand, market conditions, and team performance. A General Manager's role is not to claim the corporate result personally, but to build the system that aligns different contributions around the same objective.
A sevenfold increase in monthly revenue was significant. The more important management achievement was moving a fast-growing company toward a more visible, measurable, and accountable operating model.
What Would I Do Differently Today?
1. I would standardize project, revenue, cost, collection, and delivery definitions in a single data dictionary from the outset.
2. I would clarify the decision rights and performance accountabilities of second-line managers earlier.
3. I would connect sales targets to operational and financial capacity through a more formal model. Every new project consumes not only resources, but also cash, time, and management attention.
"Management experience is not the claim that everything was done perfectly in the past. It is the ability to build the same system earlier, more simply, and more resiliently today."
The First 90 Days
Days 0–30 | See the Reality
Bring every active project into one inventory. Connect revenue, collections, cost, progress, delivery, risk, and accountability. Identify conflicting data definitions and processes that depend on specific individuals.
Days 31–60 | Build the Management System
Create the project view, decision ownership, escalation rules, and meeting cadence. Put Finance, Sales, and Operations on the same project data. Define decision boundaries and outcome accountability.
Days 61–90 | Run and Calibrate the System
Test the system on live projects. Measure delayed decisions, cost variances, collection risks, and delivery issues. Remove reports that do not support decisions, add missing indicators, and turn the system from personal follow-up into the organization's normal way of working.
Implications for General Managers
Growth and scaling are not the same. Higher sales create growth; stronger organization, cash discipline, delivery capacity, and decision systems create scale.
A General Manager's job is not to personally track every project. It is to build a system in which the right people manage projects with the right data and the right operating rhythm.
Creating new departments is not, by itself, professionalization. If a function's purpose, authority, and expected outcome are undefined, the organization chart grows while management capacity does not.
A digital tool cannot replace a management system. Software creates value only when shared data, accountability, decision cadence, and follow-through discipline already exist.
In rapid growth, the greatest risk is not losing a sale. It is losing management integrity.
Conclusion
Increasing a company's monthly revenue matters. The real test of senior management is building the system that can operate behind that growth.
Sales initiate growth. Organization, decision systems, financial discipline, operational capacity, and accountability produce scale.
"Sustainable success is not about placing more work on the shoulders of a few strong people. It is about producing a larger result through a stronger management system."
Editorial and Intellectual Property Note
This Management Case is an editorial management analysis based on Orkun Akçasarı's direct executive experience. Company and personal names, as well as commercially sensitive information, have been protected. The company has been anonymized, and certain processes have been generalized to preserve corporate confidentiality.
This article does not constitute an audit, valuation, legal opinion, investment recommendation, financial, technical, or management consulting service, or a definitive performance assessment of any specific company, person, or institution. The outcomes are not attributed to one individual alone; the contributions of owners, executives, employees, customers, suppliers, and market conditions are acknowledged.
The original narrative, classification, application structure, the Growth Capacity Matrix name, and its positioning within the Management Integrity Model belong to Orkun Akçasarı. No monopoly is claimed over abstract concepts such as growth, scaling, project management, or governance where the law does not recognize one. The protection claim relates to the original expression, arrangement, naming, classification, and integrated presentation.
This text may not be reproduced, adapted, republished under another name, or used in commercial training, consulting, software, reports, or presentations without permission. Short quotations must identify the author, article title, publication date, and active access address. Specialist legal advice should be obtained for any specific dispute, registration, or licensing requirement.
© 2026 Orkun Akçasarı. All rights reserved.
References
Orkun Akçasarı, Turkish Resume and Career Documents, 2026, private working archive, accessed August 6, 2026.
Orkun Akçasarı, Interview Preparation and Management Transformation Notes, 2026, private working archive, accessed August 6, 2026.
International Organization for Standardization, "ISO 21502:2020 — Project, Programme and Portfolio Management — Guidance on Project Management," 2020, accessed August 6, 2026. https://www.iso.org/standard/74947.html
International Organization for Standardization, "ISO 21505:2017 — Project, Programme and Portfolio Management — Guidance on Governance," 2017, accessed August 6, 2026. https://www.iso.org/standard/63578.html
Project Management Institute, "Governance of Portfolios, Programs, and Projects: A Practice Guide," accessed August 6, 2026. https://www.pmi.org/standards/governance
Committee of Sponsoring Organizations of the Treadway Commission, "Internal Control Guidance," accessed August 6, 2026. https://www.coso.org/guidance-on-ic