Services

Web application development

Internal systems that replace spreadsheet chaos: orders, document workflows, registers and self-service portals.

A web application is software that runs in the browser and does a specific job for a company: it takes orders, manages documents, tracks processes or serves customers. It differs from a website in that a website informs, while an application does work: it has user roles, data logic and actions that change the state of the business.

When a custom application pays off

An off-the-shelf tool is a cheaper start and in many cases the right choice. A custom system starts to pay off once at least one of these signs appears:

The process is your competitive advantage, and ready-made software forces you to simplify it.
The same data is entered into several systems because they do not talk to each other.
Licence costs grow with headcount, even though you use a fraction of the features.
You need integrations the platform does not allow or charges extra for.
Data has to stay on your own infrastructure because of regulations or contracts.

What we typically build

Order and job management: from enquiry to invoice in one place.
Document workflows: drafting, approval and electronic signing.
Self-service portals: for customers or partners, with separate permissions.
Internal registers and logs: attendance, resources, schedules.
Management reporting: real-time metrics instead of month-end summaries.

Technology

On the server side we use Laravel (PHP), for the interface Vue or Livewire, and for data MySQL or PostgreSQL. It is a mature, widely used stack: finding another maintainer will not be a problem, and security updates are released regularly.

We choose the architecture to fit the project, not the other way round. If a monolith is enough, we build a monolith; if the system has to serve several interfaces, we separate out an API.

Process and maintenance

We start with a paid discovery phase that ends with a defined scope, an architecture decision and an estimate. Then come a clickable prototype, development in two-week sprints, testing, and launch with user training. After launch the system is covered by SLA maintenance with an agreed response time. More about our process.

If the system needs to talk to the software you already run, see integrations and automation.

Off-the-shelf software vs a custom system

A comparison worth going through before you decide.

Criterion	Off-the-shelf software	Custom system
Time to deploy	Days or weeks	Months, depending on scope
Initial investment	Low, charged per user	Higher, one-off
Long-term cost	Grows with the number of users	Maintenance, independent of user count
Process fit	Processes adapt to the software	Software adapts to the processes
Integrations	Only those the vendor provides	Any system with an API
Data control	Vendor infrastructure	A server of your choice
Dependency	On vendor pricing and roadmap	On a maintainer you can replace

FAQ

Frequently asked questions

When is a custom web application better value than off-the-shelf software?

When the process is one of your strengths and ready-made software forces you to bend it, when licence costs grow in line with headcount, or when data is scattered across several systems and has to be re-entered by hand. If the process is standard and an existing tool covers it, you do not need a custom system.

How long does it take to develop a web application?

The discovery phase takes 2-4 weeks and ends with a defined scope and estimate. The first working version is usually delivered within 2-4 months of the start of development, after which the system grows in two-week sprints.

What happens if requirements change mid-project?

We work in sprints, so priorities can be changed every two weeks. Changes that fit within the agreed scope are taken in order of priority; larger ones are assessed separately before work begins.

Who owns the source code?

The client. We hand over the code, documentation and access credentials. The system can be moved to another maintainer without any technical obstacles.

How do you keep a web application secure?

Role-based access rights, password and session protection, an audit log, backups and an update policy. Security testing is carried out before launch, and public sector projects also get an accessibility review against WCAG 2.1 AA.

Can the system connect to our accounting software or other applications?

Yes, integrations are one of our core areas. We connect accounting systems, online stores, courier services, email and any other platform with an API.

What happens after launch?

SLA-based maintenance with an agreed response time, monitoring, updates and further development. We never leave a system without someone looking after it.