Custom web applications for your business.

I build dashboards, client portals and internal tools for businesses in the Netherlands and Aruba. We define the users, tasks and integrations first. The work includes the interface, backend, launch and documentation for whoever maintains it next.

Start a project

You have outgrown the spreadsheet.

You may be managing work in spreadsheets, entering the same data into several tools, or relying on a process only one colleague understands.

A custom application can help when those workarounds cause repeated errors or take too much time.

We first check whether existing software could solve the problem. Then we scope the parts that need a custom build.

What gets built.

The interface, database, integrations, testing and deployment for an agreed set of features.

Interfaces people use daily

Dashboards, portals and admin screens designed around the tasks people use them for.

Data modelling

A data model that reflects your business, with relationships and validation agreed before importing existing data.

Authentication, roles and permissions

Sign-in and permissions for each user role. We decide who can view or change information before building the screens.

Payments, and what happens when they fail

Checkout, subscriptions and refunds where needed, including handling failed payments and payment notifications.

Integrations with what you already run

Connections to your accounting software, CRM, email or calendars. We check the available APIs before committing to an integration.

Tests, deployment and the ability to change it

Tests for important user journeys, automated checks and a documented deployment process.

What it costs.

This range covers a small web app with one main workflow, limited user roles and at most one straightforward integration. Complex payments, data migration or additional workflows may need a larger quote or separate phases.

€4,000 – €10,000

for a small, defined web app

Excl. VAT. Quoted for an agreed scope.

The quote covers an agreed scope. If that scope changes, we agree the added cost and timing before continuing.

What determines the price

How many distinct user roles the system has
Whether it integrates with software you already run
Payments, and what has to happen when one fails
How much existing data has to be migrated, and how clean it is

How it runs.

Scope, integrations and my availability determine the timeline. You review working software throughout. Larger projects can be split into releases.

First

Scope, and what it is not

We agree the first release, exclusions, technical risks, timeline and price.

Early

The first working version

I build the database, sign-in and main user journey so you can try the application early.

Ongoing

Regular working reviews

You review a working build each week. We use your feedback to plan the next changes.

Launch

Ship, then hand over

I check the agreed features, performance and accessibility, then hand over the code, documentation and deployment details.

What is and is not in it.

Included

Front end and back end, by the same person
Database design and migrations
Authentication, roles and permissions
Third-party integrations and APIs
Automated tests on the paths that matter
CI/CD, hosting setup and monitoring
Written handover documentation
A walkthrough with whoever maintains it next

Not included

Round-the-clock support
Native iOS and Android apps, unless we scoped them in
Content and copy, unless you ask for it
Ongoing feature work after launch, unless we agree a retainer
Rebuilding something that is working fine

A project example.

I built the tools I use to run Ayo: a template library, editor, client demo links and a CRM with website audit tools.

These tools bring the studio's project and prospect information into one place. They are internal work, rather than a client project.

See selected work

Before we start.

Can you work with the system we already have?

Yes. I review the existing system first, then recommend what to keep, improve or replace.

What happens if you are unavailable halfway through?

Your code is kept in your repository and documented during the build. Using common technologies makes it easier for another developer to take over.

Who owns the code?

You own the code, repository and hosting accounts.

Can we work together remotely?

Yes. I work from the Netherlands, with weekly reviews and written decisions so we can work remotely.

What do you need from us during the build?

Plan for a weekly review with someone who can make project decisions. The time needed depends on the scope and stage of the build.

Tell me about your project.

Tell me what you're working on. I'll tell you how I'd build it, what it would take, and whether I'm the right person for it. No obligation.