Have a web application built that fits how you really work
Considering having a web application built? If standard software doesn't fit, you reshape your process to fit the software. But it can work the other way too: a portal or dashboard that matches what you do.
What we build when you have a web application built
Often it starts small, with one process that takes too much time.

Starting small works better
Large custom projects get stuck because everything has to happen at once. So we split it up: first the part that takes the most time, then the rest.
- First the process that now takes the most manual work
- A working version your team actually uses, not a demo
- Expand based on what turns out to be missing in practice
- Documentation and access in your organisation's name, so you stay independent
How we do it
You know where we stand along the way and why something is built that way, even if you are not a tech expert yourself.
Look
We walk through the process with the people who do it every day, not just the client.
Proposal
One document with the approach, scope and price. We do not charge for what is not in it.
Build
In pieces you can view and use along the way, with common, well-maintained technology.
Stay
After launch, maintenance, updates and support. With most clients, we stay involved for years.
Frequently asked questions
When is having a web application built a good idea?
If standard software reshapes your process significantly, or if you pay a lot yearly for something you only use a fraction of. If an existing package fits, we'll tell you that, because it's cheaper.
How do we prevent the project getting too big?
By delivering in chunks. Each chunk is usable, so you can pause afterwards without being stuck with a half-finished product.
What happens to our data?
It stays yours, on infrastructure in your organisation's name. We also align the setup with the law if it involves sensitive data.
Can existing systems be integrated?
Usually yes, as long as the system allows an integration. But we check first because an API that only exists on paper isn't an integration.
Who maintains it afterwards?
Us, if you want. Otherwise we hand it over with documentation so another party can take over.
A process taking too much time?
Tell us in five short steps what you need. Then we know enough to call or email you with a proposal.