
Have your software developed and maintained
Software is never finished. We develop and maintain custom applications for organisations that have to be able to rely on their software - even when it was built by another party.
The trade-off
Developing software further without rebuilding everything

Understand first, then develop further - we work alongside your people.
Sound familiar? The application runs and the work goes on, but the party that developed it has dropped out of sight or is slow to respond.
We solve that challenge with continuous maintenance and ongoing development in small steps. The same team that builds custom applications keeps the software healthy: monitoring, maintenance and a new version in production on a regular basis.
Meanwhile your organisation keeps growing - and the software does not grow with it.
The signals
- Updates are left undone
- A small change takes months
- Nobody dares to touch the code any more
Start here - Discovery call
Find out in a discovery call whether further development is possible
We look at the application technically to see whether further development is possible. If there are changes or future wishes, we work out a proposal.
What ongoing development and maintenance deliver
To us, ongoing development means making your existing software better step by step, while the work simply carries on. No big rebuild with a big-bang delivery, but short cycles with a new version every few weeks. Every release is small enough to oversee and big enough to make a difference - and you decide what happens first.
Maintenance is not a side issue. Maintaining custom software - updating dependencies, applying security updates, watching performance - determines whether an application is still adaptable in five years or grinds to a halt under a backlog of overdue work. That is why we automate tests and deployments, so even a small change goes live safely and predictably.
This applies to everything we maintain, from client portals to planning tools - the same kind of systems you can read more about under web applications and portals. Because most of the value of software is created not at launch, but in the years after, when it carries the work every day.
Taking over software from another agency
Stuck with your current supplier, or has it stopped operating? We regularly take over software built by another party. That always starts with a code review: we look at the code, the infrastructure and the documentation and give an honest picture of the state it is in - even when that picture turns out better than feared and your current setup is better than you thought.
After that we put the foundation in order: access and environments, monitoring, automated tests and a reliable way to push changes live. From that moment on you can move forward again - without depending on knowledge that lives in a single head.
- A stable team and a single point of contact, years after launch too
- Monitoring and alerts: we see problems before your users do
- Security updates and maintenance of dependencies
- Ongoing development in small, budget-controlled releases
- Documentation and transferable code - you are never locked in with us
Our approach
How we approach ongoing development and maintenance
Whether we built your software ourselves or are taking it over: the first weeks are about understanding and foundations, after that it is about rhythm.
call 1 & week 1-2
Introduction & code review
We discuss your application, your challenge and what you expect from a technical partner. Then you know whether it clicks. We assess the code, the infrastructure and the documentation and share an honest picture of the state it is in, with a concrete proposal for the first steps.
month 1
Foundation in order
Monitoring, automated tests and a reliable deployment process. From here on, changes go live safely and predictably.
ongoing
Developing further in small steps
A new version every few weeks, prioritised by what your organisation needs right now - with a stable team that knows your process inside out.
Long-term collaboration is the core of our work, not a footnote. With Soli Infratechnik we worked together for ten years, with Metics five; Van Amerongen and Swishfund have been working with us for eight years, Schadefonds Geweldsmisdrijven for seven. Software that lasts that long is no accident - it is the result of continuous maintenance and ongoing development in small steps.

Doubts about the state of your software? Rik van Dijk, partner at eenvoud, will happily take a look with you - even if your application was built by another agency. Or start with a four-week Discovery sprint.
Frequently asked questions
What you want to know before you start.
Can you take over software from another agency?
Yes, we do that regularly. For that we need access to the source code and to the environments the application runs on, plus whatever documentation exists. Nothing more: missing documentation is normal, and we reconstruct that knowledge from the code itself. Cooperation from the previous party helps, but it is not necessary.
What do maintenance agreements at eenvoud look like?
We make agreements to fit, matched to how critical the application is for your operation: about availability, monitoring, the rhythm of updates and the pace of ongoing development. We set those out clearly, without small print. And they grow with you: if your application becomes more important, the agreements scale with it.
How does our software stay secure and up to date?
By making maintenance a fixed rhythm instead of an emergency measure. We update dependencies and frameworks regularly, apply security updates quickly and watch the application with monitoring and alerts. Automated tests catch errors before it goes live, so even a small update is safe.
What do ongoing development and maintenance cost?
That depends on the size of the application and the pace at which you want to develop it further. We work in small, budget-controlled steps: you decide how much happens per period and can always adjust. After a first conversation - and in the case of a takeover, a code review - you get a concrete estimate, with no hidden costs.
When is rebuilding better than developing further?
Less often than you think. A full rebuild usually only makes sense when the underlying technology is genuinely at the end of its life. More often we replace risky parts step by step, while the rest simply keeps running. The code review gives an honest answer to that - even when the answer is that your current software can carry on just fine.
Which technology do you use for ongoing work?
We also take over existing PHP applications built by others; taking over and improving them is the point of this service. New work uses Laravel for a maintainable technical foundation and Vue.js for fast, clear interfaces. With GitLab CI/CD, every change is tested and deployed to production automatically, which keeps releases predictable. We host on Ubuntu Linux at DigitalOcean or Azure for stable, manageable environments, and use Kubernetes when scale calls for it. Soli Infratechnik has been with us for ten years, Swishfund eight, Taskmaster seven.

