SR
EN
DE
SLSoftware
How many users to plan for a web application
The number of users affects the architecture, hosting and development price. How to estimate a realistic scale before development starts.
An application meant for twenty internal employees and an application meant for twenty thousand public users are not the same project, even though at a first, superficial glance they can look very similar in the features they offer — but the architecture carrying them, the hosting choice, and the total development budget differ fundamentally from the very start of planning.
What is useful to estimate in advance
A realistic, conservative number of users you expect in the first year of use, not the optimistic scenario "what if in five years we grow to half a million users" that unrealistically inflates the initial investment.
Whether all those users are active at the same moment (e.g. all employees during working hours), or access happens occasionally and spread through the day — this directly affects how many servers and of what capacity are truly needed.
Whether you expect sudden, short-lived load spikes — for example a marketing campaign, seasonal demand, or a known launch date — that the system must withstand without slowing down or crashing.
Why this estimate matters precisely in advance
An architecture designed from the very start for future growth — separating the database from the application, caching frequent queries, and regular performance monitoring — costs somewhat more effort and time at the very beginning of development.
But that same architecture prevents a much more expensive, painful redesign later, when the user count really grows and a system designed without thinking about scalability starts noticeably slowing down or failing under real load.
Nikola Cerić
Founder & CEO, Manage IT
More than 10 years of software development experience — in his own company and in major IT companies across the Balkans.