How much does custom web application development cost?

3 min read
Illustration of a web application with dashboard, reports and users accessing through the browser

Summary: A web application's cost depends on business rules, the number of screens and user roles, integrations, reports and data migration, plus security and availability requirements. Then come hosting, backups, monitoring and evolution. Starting with the process that hurts most, in one well-built module, is the safest way to invest.

Almost every company reaches a point where spreadsheets become a maze: one version in finance, another in sales, someone overwrote the wrong column and nobody knows which is right. That's when the idea of a custom system appears.

Web or desktop application?

A desktop application is installed on each computer. A web application runs in the browser and lives on a server: you access it from the office, home or phone, everyone sees the same information at the same time and updates apply to everyone at once. For most companies, web is more practical.

What drives the cost

Cost factors
FactorWhat to ask
Business rulesHow many calculations, approvals and exceptions exist? Are they documented?
Screens and rolesHow many user types, and what permissions does each have?
IntegrationsInvoicing, banks, ERP, website, store, WhatsApp: do APIs exist and are they documented?
ReportsWhich indicators, filters, exports and charts?
Data migrationHow many spreadsheets and legacy systems, and how clean is the data?
Non-functional requirementsHow many concurrent users, required availability, auditing, offline access?

Architecture and technology

A typical web application has a front end (what runs in the browser), a back end (rules and API, in PHP, Node.js, Python, etc.) and a database (MySQL, PostgreSQL). The choice should consider the team that will maintain it, the availability of professionals and the integrations needed, not fashion. Ask the supplier to document the architecture and deliver source code in a repository you control.

Security from the start

  • Use the OWASP Top 10 as a minimum reference: access control, injection, authentication, secure configuration, updated components.
  • Strong authentication (2FA for admin roles) and role-based permissions.
  • Audit logs: who changed what, and when.
  • Automatic backups and a tested recovery plan.
  • Data protection: map the personal data processed, its legal basis, restricted access and retention policy (in Brazil, see the ANPD).

The costs afterwards

Hosting (usually VPS or cloud; see shared or VPS), backups, monitoring, security updates for libraries and language, user support and evolution. A good system doesn't stand still: as the company changes, it keeps up.

Custom or off-the-shelf?

If there's an off-the-shelf system that covers almost everything, it's probably the best choice. Custom pays off when the process is the company's differentiator, when ready-made systems force workarounds or when per-user subscriptions get too expensive. A middle ground is integrating off-the-shelf systems and developing only the specific part.

How to start without mistakes

  1. Map the current process with the people who run it: steps, exceptions, documents, bottlenecks.
  2. Pick the process that causes the most pain and start there.
  3. Prototype the screens with UX/UI design and validate with users before coding.
  4. Develop in short increments, with testable versions every few weeks.
  5. Plan data migration and a period running alongside the old process.
  6. Train the team and track real usage.

One well-built module that the team actually uses is worth more than a giant system nobody can use. If you also need a version for end customers on their phones, read how much an app costs. To discuss your case, see our web application development.

Sources and references

Frequently asked questions

How long does it take to develop a web application?

It depends on scope. A first module can be ready in weeks or a few months; complete systems evolve continuously.

Do I keep the source code?

You should. In Brazil, the Software Law (Law 9,609/1998) has its own ownership rules for programs developed under contract, so make ownership, delivery of the code in a repository you control and documentation explicit in the contract.

Does a web application work on phones?

Yes, if it's responsive. For heavy field use, a PWA or app may be worth it.

How do data protection laws affect the system?

Every piece of personal data processed needs a legal basis, restricted access, security and retention rules. Planning this from the start costs less than adapting later.

Have your spreadsheets become a problem?

We build custom web applications to organize your company's processes.

Read also

Written by Mário Moreno, founder of Agência hetsi, which has been building websites and handling digital marketing for businesses in Brazil and abroad since 2000. Mário Moreno on LinkedIn