Speed
Every extra second of loading loses a share of users.
- Core Web Vitals in the green
- Server-rendered public pages
- Optimised images and scripts
SaaS products, customer portals, self-service, online shops and internal tools that load fast on every screen and hold up under real user load. We build the front end and the back end, so the whole application sits with one team.
A website shows; a web app does. A customer signs in, orders, pays, uploads, books, and expects all of it to be fast even when a thousand other people are doing the same. Behind that are the interface, the backend, the database, permissions and integrations, and a weak link anywhere is what the user feels.
We build the whole application with one team: an interface that is fast even on a slow phone, a backend that holds up under load, and the infrastructure it runs on. Public pages are rendered on the server so search engines see the content, and everything is measured: load time, accessibility and security.
The six most common types. The engineering is largely shared; the difference is who uses it and what it has to withstand.
Multi-tenant platforms where every customer sees only their own data: subscriptions and billing, user roles, administration and an API for other systems.
A place where customers see their contracts, invoices, orders and documents, and do for themselves what they would otherwise phone about. Connected to your existing systems.
Shops, booking and ordering systems with logic an off-the-shelf platform doesn’t cover: complex pricing, stock from several locations, rental, subscriptions.
Tools that replace spreadsheets and email chains: workflows, approvals, reports and overviews, with role-based access and a log of who changed what.
Fast, multilingual sites that marketing can update themselves, with structured data and technically sound SEO for search engines.
A web app that installs on the home screen, works on a weak connection and sends notifications, without going through a store. A good choice when a full mobile app is too big a step.
The whole application with one team, from interface to server.
React, Next.js and a fast, accessible interface on every screen.
APIs, the database, authentication and integrations.
User flows, prototypes and the design system.
Deployment, environments and monitoring.
Automated tests, performance and accessibility.
Mature, widely used tools you will still find developers for in five years.
A good-looking design is necessary but not enough. These four decide whether an app survives its first year.
Every extra second of loading loses a share of users.
A data breach costs more than the whole build.
An app everyone can use, meeting the EU accessibility requirements.
An app that can still be changed in year three, and by another team.
In discovery we write down who uses the app, what they need to be able to do and which systems it has to talk to. From that we build a clickable prototype you can test before a line of code is written.
Development runs in two-week cycles, and at the end of each there is a working version in a test environment you can try yourself. Automated tests and code review are part of every change, not the end of the project.
The launch is rehearsed and has no downtime, with monitoring that shows errors and slowness before a user reports them. After that we continue developing it or hand it over to your team.
Most problems arise between two suppliers. With us there is no such gap.
Core Web Vitals and load times are tested on real devices, because slowness costs customers and search rankings.
You see a working application, not a status report, and can change direction before it gets expensive.
Code, domains, cloud accounts and data are in your name from the start.
A first usable version with the core features usually takes 8-12 weeks. A larger platform with several user roles, payments and integrations takes several months. You see a working version every two weeks, so the deadline is never a surprise.
On the front end mostly React and Next.js, or Vue or Angular where that fits. On the back end Java and Spring Boot, Node.js, Python or .NET, with PostgreSQL as the database. We choose by what your team can maintain later, not by what is in fashion.
Yes. Every view is built from the start to work on a small screen, and we test on real devices. If you need an app installed from a store, push notifications or access to device features, a mobile app is the better answer, and it can share the same backend.
Public pages are rendered on the server, so a search engine sees all the content without running JavaScript, along with titles, descriptions and structured data. The part behind a login does not need to be in search and stays out of it.
You do. The code is in your repository, and the domains, cloud accounts and data are in your name from the start. If you later decide to continue with another team, you get everything needed to do so, documentation included.
Describe your situation in a couple of sentences. We reply within a day.
Prefer to reach us directly?