When spreadsheets, email and off-the-shelf software no longer fit the way your company works, it's time for an application built for that job. We take it from the first sketch to launch - and stay with it afterwards.
A web application opens in the browser just like a website, but it serves a different purpose. A website presents your company and brings in inquiries. An application is a tool people work in: orders are entered, bookings tracked, requests approved and messages sent. If you need a website for your company, see website development. If you only need to view and manage data alongside a system you already have, see admin panels and dashboards.
The companies that contact us most often have either outgrown Excel or pay for three programs that don't talk to each other. People end up copying the same data into three places, and mistakes are only noticed when a customer calls.
If off-the-shelf software covers almost everything you need, use it. We'll tell you that on the first call, because a custom application costs more up front and there's no point building one just because you can.
A custom application pays off when the way you work is part of your competitive advantage and you don't want to change it to fit someone else's software. It also pays off when per-user licenses over several years cost more than developing and maintaining your own application, or when you need to connect systems that off-the-shelf software doesn't support.
02
What we build most often
SaaS platforms you sell to other businesses on subscription, with separate data for every client.
We also build client and partner portals, booking systems and internal tools for record-keeping and approvals.
03
How an application is built
First we go through the work the application should cover, step by step, with the people who will use it. That's usually where half of the things nobody would have written into a specification come up.
That becomes the plan: who the users are and who can see what, the main features, which systems the application connects to and what goes into the first version. The first version contains only what people can't work without. It reaches users sooner, and we refine the rest of the plan based on how they actually use it.
Development runs in phases, and after each one you see what has been done. Testing runs alongside development, not in the week before launch. More on that on our software testing page.
04
Technology
We write the backend in PHP on Symfony and build APIs with API Platform. If your team or existing systems already use .NET or Java, we also build the backend in C# (ASP.NET Core) or Java (Spring Boot). The interface is built in React, Vue or Next.js, depending on what the application does and who will maintain it later.
Because we build the application around an API from day one, it's easy to add a mobile app or a connection to your partner's software later. That usually doesn't require rewriting the existing parts.
05
After launch
The day the application goes live isn't the end of the project. Users start asking for things they didn't know they needed, new versions of libraries and operating systems come out, and the business changes.
That's why we agree with you on what maintenance will look like: who monitors the application, how quickly we respond when something breaks and how new features are planned.
Applications are one part of our development services. When the application also needs a website or a mobile version, the same team builds them.
It depends on the number of user types, features, reports and the systems the application connects to. Once we understand what you need, you get an estimate - and we often suggest a smaller first version that can go live sooner.
The timeline depends on the scope. The first usable version is always ready before the whole application, so you don't have to wait for the end of the project to start using it.
It runs in the browser on any device. If you need an app installed from the App Store or Google Play, we build it on the same backend.
Yes. First we review the code and tell you what state it's in, then we decide together whether to continue or whether it's smarter to rewrite some parts.
In most cases, yes - through an API or file exchange. For older software without an API, we build an intermediate layer that handles it.