Services - Custom applications
Software that does what your process needs.
Spreadsheets bursting at the seams, time-consuming manual entry and off-the-shelf software that only solves part of your problem. We develop custom applications that do fit your processes and do exactly what your organisation needs.
Not a big, risky undertaking. We start small, develop in short steps and you are part of the team - so at any moment you know what’s there and what it costs.
- Scalable architecture with well-documented APIs
- Interfaces your team likes to work with
- Automated tests and deployments from day one
- The same team for ongoing development after launch
From code to interface
Line by line into a working interface.
The same building blocks in two guises: what starts out as code ends up as the screen your team works in every day.
Our tech stack
Laravel Vue.js React Node.js TypeScript PostgreSQL
Start here - Discovery sprint
From challenge to clickable prototype in four weeks.
We work alongside your people, sharpen the challenge and build a prototype your team can try out. Then you decide - with something tangible in hand.
4 weeks
fixed timeline
1 prototype
clickable, built on your process
1 recommendation
honest go/no-go with a budget
The trade-off
When custom software is the right choice
Understand first, then develop.
Not every challenge calls for custom software. If an off-the-shelf package or SaaS solution covers your process well, you’ll get there faster and cheaper - and we’ll tell you so. Custom applications pay off when your process is what sets you apart: the way you plan, produce or serve customers differs from the norm, and that is exactly what you don’t want to flatten into whatever a package happens to support.
The signal is usually easy to recognise: your team bends its way of working to fit the software, instead of the other way around.
The signals
- Shadow administrations appear in spreadsheets alongside the official system
- Exports and macros hold everything together just barely
- Nobody knows which version is correct anymore
At that point the lack of fitting software costs time every week - and often errors too. In doubt? That is what the Discovery sprint is for: in four weeks we sharpen the challenge and you get an honest go/no-go recommendation - even if that recommendation is that you are better off staying with your current package.
What we do
Three services, one coherent whole.
Not a loose collection of projects, but one continuous service. The same team that develops stays responsible after launch - with tests, monitoring and further development.
Web applications & portals
Client portals, planning tools and web applications that form the core of your operations - secure and scalable.
Internal tools & process automation
From error-prone manual work to one flowing process: tools that fit exactly how your team works.
Ongoing development & maintenance
After launch the same team stays on: monitoring, maintenance and a new version every four weeks.
Rather get straight to it? Rik van Dijk, partner at eenvoud, will happily think along with you about what custom software could mean for your process.
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 →From challenge to production
In phases towards software that carries the work.
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. That keeps the risk small and the direction yours.
week 1-4
Discovery sprint
We work alongside your people, sharpen the challenge and build a clickable prototype. You receive an honest go/no-go recommendation and a budget.
from week 5
Developing in short iterations
We start at the core of your process and develop in small, budget-controlled steps - with a new version every four weeks for your team to try out.
ongoing
Launch & further development
What works goes live in a controlled way. We stay on board for monitoring, maintenance and further development where needed.
Frequently asked questions
What you want to know before you start.
What does a custom application cost?
That depends on the scope, and we sharpen that together first - a budget without a sharp challenge is guesswork. The Discovery sprint has a fixed timeline of four weeks and ends with an honest budget for what comes next. After that we develop in small, budget-controlled steps: after every step you decide whether and how we continue, so the costs never run ahead of you.
Custom or an off-the-shelf package: how do you choose?
In broad terms: choose an off-the-shelf package if your process is common and the package covers it well - then you are done faster and more cheaply. Choose custom if your process is what sets you apart, or if your team keeps bending the way it works to fit the software. In the discovery sprint we give you honest advice on that, also when that advice is “no custom software”.
How soon do we have something working in our hands?
After four weeks. The Discovery sprint ends with a clickable prototype your team can try out. If we then decide to build, there is a new version every four weeks - so you never wait months for one big delivery, but adjust course on the basis of what is actually there.
Who owns the software - are we tied to you?
The code we develop for you is yours. We document, use common technology and keep the code transferable, so another team can in principle take it over. That we do stay on board for years at many clients is because the collaboration works well - not because it has to.
How do you keep the risk of a custom project small?
By never building for long without showing something. Every phase delivers something tangible: first a prototype, then a working version every four weeks. Steps are small and budget-controlled, automated tests catch errors before go-live and after every step you can adjust course or stop. That way a custom project stays a series of manageable decisions.
Let’s talk
Four weeks, one prototype. Then you decide.
Tell us where your process is getting stuck. We’re happy to think it through with you.