Connect
I open up the systems you already use, so the web application works with current data.
Web application development
A web application is software that runs in the browser and ties your existing systems together. I build these for small and midsize businesses that have already worked out their process and want the software to fit it, not the other way around. At Inge de Bruijn Zwembad, I connected 12+ systems into one platform that sends a daily briefing every morning at 07:00 and runs 6,000+ checks every 24 hours. You discuss your requirements with the same person who builds them, not with a middleman who passes them along.
I open up the systems you already use, so the web application works with current data.
I write the application around the process you have, not around a template.
After go-live, I check that integrations and checks keep running.
At an agency, you explain your requirements to a project manager, who passes them on to a developer you never talk to. Every change goes back through that same detour. With me, you talk to the person who writes the code, from the first process review to the last check after go-live. That saves time, and not because I type faster. It's because there's nothing to translate. What I built for Inge de Bruijn Zwembad, from 12+ connected systems to the 1.7 million receipts and bookings I opened up, came together exactly like that. Directly, with no middle layers.
Every web application I build starts with a clearly scoped first version, not an open-ended project.
The process review is free and shows which part of your process lends itself to a web application. After that, I build a clearly scoped first version from €3,500, with a scope we set together. If you'd rather test a single integration or automation first, I often start smaller, from €750 for the first integration.
I map out which process you want to digitize and which systems are involved. You get concrete advice, even if the conclusion is that you don't need a web application.
I build a clearly scoped first version with a fixed scope, so you know what you'll get and when. You test along while I build, not only after delivery.
After go-live, I monitor whether integrations and checks keep working. I fix problems before they affect your process.
A clearly scoped first version starts from €3,500. If you'd rather test a single integration or automation first, you start from €750. The process review where I determine the scope is free, with no obligation.
That depends on the scope we set in the process review. A clearly scoped first version is usually ready sooner than a fully connected system with 12 or more integrations, like the one at Inge de Bruijn Zwembad. I only give a timeline after I've seen the process.
Yes. The source code and documentation belong to you, even if you later choose another party for maintenance. I don't use lock-in arrangements.
You call or email me directly, the same person who built the application. There's no project manager in between who first has to figure out what you mean. I often handle small changes as part of maintenance. Larger ones I bill separately.
Often that isn't necessary, and it isn't the goal. I connect your web application to the systems you already use, such as your point of sale, booking system or CRM, so you don't end up entering data twice. That's how I opened up 1.7 million receipts and bookings from 12+ connected systems at Inge de Bruijn Zwembad.
Start with a free process review, and within one conversation you'll know whether a web application is the right answer. After that, I build and maintain it, without you having to deal with anyone else.