Software that runs in the browser and is built around your process. Not an off-the-shelf package you have to bend your work into, and not an app everyone has to install first.
Web app Development.
in short
A web application is software that runs in the browser, with no installation, on any device. I build them around your own workflow, with integrations into the systems you already use. You own the code: no lock-in and no subscription trap.
What you get
A web application is software you open in a browser, with no installation, on laptop, tablet and phone. I build them for businesses stuck on spreadsheets, on separate systems that do not talk to each other, or on a package that almost does the job. From first sketch to running application, by one senior engineer.
An application built around your workflow rather than the other way round: planning, registration, quotes, records, stock, whatever it is.
Role-based access so office, field staff and clients each see only what they should.
Integrations with the systems you already run, from accounting to stock or transport.
Works on any screen: no separate app builds, no App Store, one address that is always the latest version.
Next.js and React for the interface
Supabase or Postgres for database, permissions and auth
API integrations into your existing systems
Hosted on Vercel, with backups and monitoring
how I work
- 1
Call and scope
I look first at how the work runs today and where it breaks. Sometimes the conclusion is that you do not need a web application. I will say so.
- 2
Design and first version
I build the core that removes the most manual work first, so you get something genuinely usable instead of waiting months.
- 3
Integrate and extend
Then come the integrations with your existing systems and the functions that turn out to be missing in daily use.
- 4
Handover and maintenance
You get the code, the access and the keys. I maintain it if you want, but you are not tied to me.
Why itMatters
Most businesses outgrow their spreadsheets without noticing. First it is one tab, then five, then a shared folder where nobody knows which version is right. Errors creep in the moment the same data is maintained in three places, and the real time cost sits in the re-typing. A web application takes that work out of loose files and puts it in one system everyone uses at the same time, with per-role permissions and a history of who changed what. At Avam Bouw that saved around seven hours of admin a week, because data only has to be entered once.
My web applications run in production at real companies. Avam Bouw replaced scattered spreadsheets with one app. BMD Logistics got a WMS to TMS integration, so nothing is re-keyed between systems. Mozaiek got an app built around the contractor's workflows.
Common questions
What exactly is a web application?
A web application is software that runs in the browser instead of being installed on your computer. You open an address, log in and work. A website mostly shows information; a web application lets you actually work in it: enter, plan, approve, report.
What is the difference between a web app and an App Store app?
A web app works straight in the browser on any device, with no install and no approval from Apple or Google. A native app sits in the stores and can reach deeper into the hardware, such as camera or push notifications. For internal business software a web app is usually faster, cheaper and easier to update. If yours is the exception, I will say so in the first call.
What does a web application cost?
It depends on scope: how many screens, how many user roles, and above all how many integrations with existing systems are needed. A contained internal tool is a very different project from a platform with a client portal and invoicing. I do not work with fixed packages. After a call where I pin down the scope, you get a quote so you know where you stand up front.
How long before I can use something?
I build in short rounds so you follow along instead of waiting months for a surprise. A first working version with the core function usually comes first, then we extend based on what actually proves useful in practice.
Can it integrate with the software I already use?
Yes, and usually that is the whole point. Through API integrations the application talks to your accounting, stock, planning or transport system. For BMD Logistics I connected the WMS and the TMS so data is no longer re-keyed by hand between two systems.
What technology do you use?
Next.js and React for the interface, Supabase or Postgres for the database with permissions and authentication, and API integrations into what you already have. Hosted on Vercel, with backups and monitoring. No exotic choices nobody can maintain in three years.
How is security and data backup handled?
Access runs through login with roles and permissions, so not everyone sees everything. The database is backed up automatically and the connection is encrypted. The data stays yours, on infrastructure you can take over yourself.
Do I own the code?
Yes. You get the code, the access and the keys. Want me to keep maintaining it? Fine. Want to move it in-house or to another party later? Also fine. No lock-in.
I already have an outdated application. Can you replace or extend it?
Both happen. Sometimes extending is enough, sometimes maintenance costs more than starting over. I look at what is there first and tell you honestly which of the two works out cheaper, even if that means you do not need anything built for now.
Do you only work regionally or nationwide?
I am based in Tiel and work with businesses across the Netherlands and internationally. Meeting in person is easy if you are nearby, and everything else works fine remotely over video calls and WhatsApp.
Who is a web application actually for?
Mostly for businesses where several people work on the same thing and the admin currently lives in spreadsheets, email and shared folders. Think planning that gets re-typed every time, quotes built from a template, or stock that is only correct after the fact. If you are one person handling ten rows a week, a web application is overkill and I will say so.
Can the web application be extended later?
Yes, and usually that is the plan. I deliver the core that removes the most manual work first, then extend based on what actually turns out to be missing. Because you own the code, that can be done by me, by your own team, or by another party.
Related services
Often combined with:
Ready to put yourProcess into software?
Tell me where your process breaks down today and I will tell you honestly whether a web application is the right answer or whether something smaller gets you there.
