Have a web application or client portal built
Do you want a web application built, or a client portal? We develop web applications that form the heart of your operation - simple at the front, the complexity solved behind the scenes.
The trade-off
When a web application or client portal is the right choice
Understand first, then build - we work alongside your people.
It usually starts small: customers email for a status update, planners work in three screens at once, and somewhere there is a spreadsheet nobody dares to change any more. The work gets done, but every step takes manual effort - and no two people have the same picture of what is going on.
A custom web application or client portal solves that challenge at the source: one place where your team and your customers work from the same up-to-date information, available from any browser and any type of device. It is one of the forms of custom applications we develop - software that adapts to your process, not the other way around.
A familiar sign: the work does not stand still, but it runs on manual effort and scattered spreadsheets instead of one up-to-date system.
The signals
- Customers email or call you themselves for a status update
- Planners or staff work in several screens at once
- There is a spreadsheet nobody dares to change any more
At that point, not having one central place costs you time every week - and often errors too. Not sure? That is what the Discovery sprint is for: in four weeks we sharpen the challenge and you get an honest go/no-go recommendation.
Start here - Discovery sprint
From challenge to a clickable prototype of your web application in four weeks.
We work alongside your people, sharpen the challenge for your web application or client portal and build a prototype your team can try out. Then you decide - with something tangible in your hands.
4 weeks
fixed timeline
1 prototype
clickable, built on your process
1 recommendation
honest go/no-go with a budget
What a custom web application delivers
For Soli Infratechnik GmbH we built one digital workflow for hundreds of engineers and subcontractors across Germany: 12 branches, 700+ staff, one application in which the work is visible from assignment to completion. For Swishfund we built a client portal on a microservices architecture, connected to three banking platforms. Two very different organisations, the same principle: the application follows the process, not the other way around.
A web application rarely stands on its own. Often the real value sits in the connection to what is already there: your accounting package, your CRM, your planning system. That is why we build API integrations that let data flow automatically instead of being retyped - with error handling and monitoring, so a connection that falters never causes silent data problems.
And because a good application grows with your business, our work does not stop at launch. The same team that builds it stays responsible for ongoing development and maintenance: monitoring, maintenance and new functionality in short, manageable steps.
- Client portals where customers arrange and track things themselves
- Planning tools and workflow applications for your team
- Secure connections to the systems you already use
- Automated tests and deployments from day one
- The same team for ongoing development after launch
Our approach
How we approach it
No months-long project with one big delivery at the end. Every phase produces something tangible you can steer on - and after every step you decide whether and how we continue.
week 1-4
Discovery sprint
We work alongside your people, sharpen the challenge and build a clickable prototype. You leave with an honest go/no-go recommendation and a budget.
from week 5
Building in short iterations
We start with the core of your process and develop in small, budget-controlled steps. Your team works on the project with us, so the application fits how the work is actually done. Automated tests and deployments make releasing routine: a new version is ready every four weeks.
ongoing
Ongoing development & maintenance
After launch the same team stays on board: monitoring, maintenance and ongoing development based on what real usage shows.
In practice
VAF Infra
One digital chain, from the office to the roadside
One digital workflow for planning and execution: materials and statuses are directly visible per branch and work in the field is processed into a correct administration without detours.
View case →
Soli Infratechnik GmbH
The digital backbone of the German fibre roll-out
Soli Infratechnik laid fibre in Germany with software that connected work in the field and the administration directly, so progress stayed visible and invoices came out of the same recorded work.
View case →
Not sure whether a web application is the answer? Rik van Dijk, partner at eenvoud, will happily think along with you - even when the answer is “not yet”. Or start with a Discovery sprint: from challenge to clickable prototype in four weeks.
Frequently asked questions
What you want to know before you start.
What does it cost to have a web application built?
That depends on the scope, and we sharpen that together first. The Discovery sprint has a fixed duration of four weeks and ends with a budget for the next stage. After that we build in small, budget-controlled steps: after each part you decide whether and how we continue. After the first conversation you know where you stand.
Custom, or an off-the-shelf package after all?
If an off-the-shelf package or a SaaS product covers your challenge well, we say so - you will be up and running faster and cheaper that way. Custom pays off when your process is what sets you apart, or when you notice you are bending your way of working to fit the software. We have that conversation honestly during the discovery.
How long does it take to build a web application?
The Discovery sprint takes four weeks and produces a clickable prototype. How long the build takes after that depends on the scope - but we always work in short iterations with a new version every four weeks, so you have something working in your hands quickly instead of waiting months for a delivery.
Who owns the code, and what about security?
The code we build for you is yours - you are not tied to us. Security is built into the foundation: encrypted connections, carefully managed access rights and automated tests that run with every release. We also build applications in domains where that weighs heavily, such as financial services.
What happens after launch?
That is when it really starts. The same team that built the application stays responsible for monitoring, maintenance and ongoing development. That is how we have worked with many clients for years - with Soli Infratechnik ten years, for example, and with Swishfund eight. An application that grows with you keeps delivering value.
Can the application connect to our existing systems?
Yes, that is often part of the work. We connect web applications to accounting packages, CRMs, planning systems and banking platforms - with proper error handling and monitoring. For Swishfund we connected three banking platforms to the client portal, for example.
Which technologies do you use for web applications?
We work with Laravel and Vue.js; that combination powers Van Amerongen’s work order portal, Taskmaster’s customer portal and Swishfund’s financing platform. It keeps your portal clear and ready to extend. We use React when it fits better with your team. TypeScript keeps larger codebases readable, Node.js helps with realtime and calculation work, and PostgreSQL stores data reliably. With Redis we build caching and queues, so screens stay fast and work runs in the background. We choose technology that will exist in ten years, because we keep developing and managing applications.