System + team
The right view for each person.
Staff work on orders, managers organise the team and customers check their own requests. We plan roles, permissions and a history of relevant changes.
Web application and custom software development
Web applications and systems. Built around everyday work.
We build management panels, customer portals and SaaS applications. We organise processes, connect data and design tools around how your business works.
From a single process to a complete product.
-
Business systems and panels
Orders, bookings, customers and tasks in one place. We design views and working rules around your team, instead of turning every spreadsheet into a separate app.
-
Customer and partner portals
Access to offers, documents, statuses and history. Customers can check progress or provide information while your team sees what they need in the panel.
-
SaaS applications and MVPs
We help define a first version and the features needed to test it. Accounts, roles and billing are planned, with further stages informed by real use.
Less passing things on. More getting things done.
Connect people, data and tools. Each person sees what they need to carry out their part of the work.
Application + integrations
Data reaches the places it is needed.
Your website, payments, bookings and business tools can share one process. We review provider APIs and define what happens automatically, including when a connection fails.
Example layouts. Features and integrations are agreed together.
Custom software for businesses
A good system starts with clear decisions.
Web application development also needs to account for situations outside the main flow. What happens after an order changes, when access is denied or when an external system stops responding?
-
Processes and rules
We describe statuses, exceptions and responsibilities, then use them to design forms, notifications and automation.
-
Access and data
We define roles, permission checks and the history to retain. We also plan data backups, error handling and necessary alerts.
-
SEO for public content
Public catalogues, profiles and offers can be prepared for indexing. Signed-in panels are protected with access controls. Product marketing pages can support the application’s visibility and sales.
-
Performance and future development
We consider data volumes, search behaviour and the workload of key views. Testing, monitoring and further stages are agreed as part of the scope.
Working together
Built in stages. Checked in practice.
-
Understand the process
We walk through real working examples and agree on users, rules and integrations.
-
Show the screens
We design screens and user journeys, reviewing them with the people who will use the system.
-
Build and test
We develop the application, API and connections, checking permissions, main flows and failure cases.
-
Launch and improve
We plan data migration and the team’s start, then agree on further features based on needs and use.
Technology chosen for your project
- Next.js
- NestJS
- TypeScript
- API
We choose the interface, backend and data storage for the project. A web application runs in the browser, with screens also designed for phones.
Accessibility and performance
Looks good.
Feels easy to use.
Clear content, simple controls and a quick response. We look after the details that help customers explore your services, buy and get in touch.
-
Digital accessibility
More people. The same care.
We design with WCAG 2.2 AA in mind, considering contrast, keyboard navigation, clear structure and screen reader support.
-
Core Web Vitals
Less time waiting.
We optimise images and code, checking loading, response to clicks and layout stability, including on slower connections.
-
On every screen
Made for your thumb.
We adapt menus, buttons and forms for phones. We also check enlarged text and reduced motion preferences.
The scope of conformance with WCAG and the European EN 301 549 standard, along with verification, is agreed for each project.
Accessibility and European requirements
WCAG addresses web content accessibility. EN 301 549 covers digital technology more broadly. We select relevant criteria, plan improvements and manual tests, including keyboard and screen reader use.
The European Accessibility Act (EAA) applies to selected products and services, including e-commerce. Requirements and exemptions depend on the business. Conformance is assessed against the agreed scope, content and integrations. An automated test alone cannot establish it.
Performance you can measure
Core Web Vitals are Google metrics for the experience of using a website. Optimisation aims for these recommended values:
- LCP Main content loading
- ≤ 2.5 s
- INP Response to interaction
- ≤ 200 ms
- CLS Layout stability
- ≤ 0.1
These are optimisation targets, not this website’s results or a guarantee for every device. Assessment uses the 75th percentile of real visits. We run lab tests before launch and can analyse user data after publication, once enough is available. Hosting, connection speed and third-party tools also affect the results.
Questions about systems and applications.
How is a web application different from a website?
A website usually presents an offer and helps people get in touch. An application handles data, accounts, roles and processes such as bookings or orders. Both can work together and share the same backend.
How much does a custom system or application cost?
The estimate depends on processes, roles, integrations and data migration. We start with the first version’s scope and agree on features, stages, maintenance costs and third-party fees before development.
Can we start with a smaller MVP?
Yes. We select the features needed to handle the main process or test the idea. Other features are recorded as later stages, so the initial scope can be assessed against concrete scenarios.
Can you connect the application to our existing tools?
We review documentation, APIs, export options and provider restrictions, then agree on the direction and frequency of data exchange. If a direct connection is unavailable, we discuss other workable options.
Will the application work on a phone?
We design responsive applications accessed through a browser. Forms, lists and key actions are adapted for small screens. Offline use and installation as a PWA need to be agreed separately.
Do you maintain and develop applications after launch?
We can agree on ongoing work covering updates, monitoring, errors and new features. Access to code, documentation and infrastructure is defined in the contract.
What takes up most of your team’s time?
Describe the process you want to improve and the tools you use. We will suggest a first version to start with.
Let’s talk about your project