A few months ago an air-conditioning company from Stara Zagora got in touch. They had a website and an online request form. The trouble was what happened after the form: the request landed in an inbox, someone copied it into Excel, then phoned a technician, then the technician phoned back to ask for the address. Three people lost two hours a day to retyping.
They did not need a new website. They needed a web application: a browser-based system where a request is entered once and then moves through the dispatcher, the technician and the invoice without anyone copying it again.
This guide explains what a web application is, when it is worth building your own, how development works and what to watch out for so you do not pay for software nobody uses.
Web application vs website
A website mainly shows information: who you are, what you offer, how to reach you. Visitors read and maybe fill in a form.
A web application does work. Users log in, create, edit and track data. The system calculates, sends notifications, generates documents and talks to other systems, all inside the browser with nothing to install.
The line is not always sharp. An online store is both: product pages are content, while the cart, orders and account area are logic. The practical test is simple. If most of the value comes from what people do in the system rather than what they read, it is a web application.
Web app vs mobile app
A mobile app is installed from the App Store or Google Play, is built for iOS and Android (or with shared code like Flutter) and goes through review with every update. A web app runs on any device with a browser and updates instantly for everyone.
For most business systems, especially internal ones, a web app is faster and cheaper. A native mobile app makes sense when you need push notifications at scale, offline work or hardware access such as Bluetooth.
Typical web applications for small and mid-sized companies
- Client portal. Clients log in to see orders, documents, invoices and project status. Accountants, builders and importers use it to stop the endless "where are we" emails.
- Service and request system. Like the Stara Zagora example: request, assignment, schedule, field report with photos, invoice.
- B2B ordering. Wholesalers give partners their own prices, credit limits and quick ordering by SKU.
- Configurator or calculator. Made-to-measure furniture, windows, solar systems. The client picks parameters and gets an estimate and a drawing.
- Internal stock or production system. Inventory, batches, production stages, barcodes.
- Bookings with complex rules. When off-the-shelf tools cannot match rooms, equipment and staff at once.
What they share: one place where the data lives, replacing a mess of emails, spreadsheets and calls.
When a custom web application is worth it
This is the most important question, and often the answer is "not yet". Before ordering development, check whether a SaaS product solves 80% of the problem. CRM, invoicing, bookings and email marketing all have excellent subscription tools.
Custom software makes sense when at least one of these is true:
- Your process is specific and part of your competitive edge.
- You pay for 3-4 systems that do not talk to each other and someone moves data between them by hand.
- Per-user subscriptions are growing faster than the business.
- You need full control over data because of client contracts or regulation.
- You want to sell the software itself as a service.
| Approach | Time to start | Flexibility | Long-term cost | Fits when |
|---|---|---|---|---|
| Off-the-shelf SaaS | days | low, you follow their model | monthly fee that grows with users | the process is standard |
| No-code/low-code (Airtable, Bubble) | weeks | medium, up to a point | subscription plus upkeep time | you want a quick prototype |
| SaaS plus automations (n8n) | 1-4 weeks | medium to high | subscriptions plus maintaining the links | the tools are fine but disconnected |
| Custom web application | 2-6 months for a first version | full | development plus hosting and support | the process is specific and important |
The third row gets skipped a lot, yet for many companies it is the best value. If the real issue is that your CRM, accounting software and shop do not talk, connecting them may be enough. See our automation services.
How web application development works
Discovery
We sit down with the people who will use the system, not just the manager. We map a normal day, where time is lost and what the exceptions are. Exceptions are where projects get expensive if nobody spots them early. The output is a short document: roles, main scenarios, data, integrations and what stays out of version one.
Prototype
A clickable Figma mock-up that looks like the real thing but has no code. Users click through it and show where they get confused. Changing a prototype takes an hour; the same change in finished code can take a week.
MVP
The minimum viable product is the smallest version that does real work. For the service system that meant requests, assignment and field reports. Schedules, spare-parts stock and statistics came later. Resist building everything at once. Two months of real use always reveal things no meeting predicted.
Testing, launch and training
We test with real data and real people, then roll out gradually, often one team or office first. Training is short but mandatory. The best system fails if staff keep the old spreadsheet "just in case".
Support
A web application has no finish line. Browsers update, libraries get security patches, the business changes. Plan for support from day one.
The tech stack in plain terms
- Frontend is what users see: usually React, Vue or Svelte.
- Backend handles logic and permissions: Laravel (PHP), Node.js or Python.
- Database, usually PostgreSQL or MySQL.
- APIs connect the app to accounting, couriers, payments and CRM.
More important than the specific tool is that it is mainstream and well supported, so a new team can take over in three years if needed.
A Progressive Web App (PWA) can be "installed" on a phone with an icon, send notifications and partly work offline. For field technicians, sales reps or warehouse staff it often replaces a separate mobile app.
Security, GDPR and hosting
Our minimum: HTTPS and hashed passwords, roles and permissions, two-factor login for admins, an audit log of who changed what, automatic off-site backups with tested restores, and an EU server with a data processing agreement. Application hosting is different from brochure-site hosting, usually a monitored VPS or cloud setup. Our hosting page explains how we run it.

What drives the budget
We cannot give an honest price without seeing the process. Two "request systems" can differ tenfold in scope. The biggest factors are the number of roles and screens, integrations (each adds work and risk), rules and exceptions, reporting needs, payments or multilingual support, and the level of design. As a general market reference in Bulgaria, small internal systems start at a few thousand euros and complex platforms reach tens of thousands. We start every project with a process review and send an individual offer within 24 hours of the meeting. On a tight budget we suggest an MVP and phased development.
Apps rarely stand alone. The public site brings in clients through SEO and ads, the shop sells, the app handles everything after the sale. See our approach to web development and online stores.
Frequently asked questions
How long does it take to build a web application?
A first working version of a small to mid-sized system usually takes 2-4 months. Complex platforms with many integrations take six months or more. Discovery and prototyping account for 2-4 weeks of that, and they are worth it.
Can I start with off-the-shelf software and move to a custom app later?
Yes, and it is often the smartest path. The ready-made tool shows you what you really need. When the time comes, data can be migrated if the tool allows export, so check that when you choose it.
Who owns the code?
You should, and the contract should say so. Ask for access to the code repository (for example GitHub) and documentation. Without them you are tied to one supplier forever.
Does a web application work on phones?
Yes, if it is built responsively. For field staff we often build a PWA that sits on the home screen and behaves almost like a native app.
What does support cost after launch?
It depends on size and load. It covers hosting, security updates, backups, monitoring and small improvements. Budget for it as an ongoing cost from day one.
Next step
Write down one process that annoys you every week: where information enters, how many hands it passes through and where it gets lost. If three people are typing the same thing in three places, you have a candidate for a web application, or at least an automation.
Send us that description. We will tell you honestly whether you need custom software, an existing tool or just a link between what you already use. Contact us for an individual offer within 24 hours.



