Website development · Leiden

A website built in
Leiden.

A website built in Leiden for one fixed price up front, live in two to three weeks. And if it has to become more than a website — a portal, a dashboard, a tool that calculates something — I build that too. Webframer is based in Hazerswoude-Dorp, half an hour away.

100%
Code in your own repository
2-3
Weeks for a website
4-6
Weeks for an application with logins
1
Fixed number up front, not a range
Sound familiar

What brings Leiden clients here.

01

You need more than a website

A site tells people what you do. With research, a spin-off or a service with users, something has to process data as well, and that is a different kind of work.

02

It runs on a spreadsheet now

Sign-ups, measurements, participants or stock in a sheet one person understands. Fine until that person leaves or a formula breaks.

03

An agency finds you too small

Too big for a site builder, too small to interest an agency with a team. A lot of work falls through that gap.

04

You are locked into a supplier

The code sits with someone else, so does the hosting, and every change costs a quote. Leaving is dearer than staying, and both parties know it.

05

User data without permissions

A shared folder or a tool without roles. One wrong link and the wrong person is looking. With personal data that is not an inconvenience but a reportable breach.

06

You started with an AI tool

Something put together with a builder or AI tool that works until it is genuinely used. Findability, permissions and server-side work are usually missing.

How it works

How the track looks.

01

Working out what it really is

A website, an application, or both. That difference drives build time more than the number of pages, and it is the question most often skipped.

02

Pinning down scope on bigger tracks

Five working days in which the core screens become clickable and the scope goes on paper, with a fixed price for the build. If building is not the smart move, you hear that too.

03

Design and build

Structure first, then design, then code. For an application: logins, roles and permissions down to row level in the database, not only in the front end.

04

Launch and handover

Everything in your repository, hosting on your account, and one session showing you how to carry on. No key only I hold.

What you get
  • Fixed project price, known up front
  • Website, application or both
  • Logins with roles and permissions where needed
  • Repository and hosting in your name
  • Hosting inside the EU
  • An honest word when building is not the smart step
Get a website built
from
€ 1,500fixed project price

If it becomes an application with logins and integrations, it starts higher. What it comes to in your case you hear after the first call.

For a website the price moves with the number of pages; for an application mainly with the number of integrations and the permission structure. After a half-hour call you get an indication.

In detail
01

Website or application: where the line sits

A website shows information: who you are, what you do, how someone gets in touch. An application processes information: people log in, enter something, and the system calculates, stores or sends. The rule of thumb: if someone can change something that stays changed, it is an application.

That difference drives build time more than the number of pages, and it also drives what has to sit under the bonnet. In an application, permissions are not a setting but a design decision: who may see which row, and does that still hold when someone bypasses the front end.

If your case leans towards software, that track is on custom software development and client portal development.

Website

Two to three weeks. Pages, design, CMS, findability. What is included is on the service page.

Application

Four to six weeks. Logins, roles, screens people work in, and integrations with what you already use.

Both

A public site that gets found, with a private area behind it. One codebase, one project, not two suppliers.

Just an integration

Tying two systems that do not know each other together is a job of days, not a project of weeks.

02

What it costs

For a website the price moves with the number of pages and the functionality. For an application it moves mainly with the number of systems that have to connect and the number of exceptions in your process. Four sources that must talk is a different project from one.

The shape is fixed: after a half-hour call one fixed price for the whole track. On a bigger project I take longer over the call, but there is no paid run-up in between. How that works is on pricing.

If you would rather outsource maintenance, that is available for a fixed yearly fee through maintenance and support.

03

Working area around Leiden

Webframer is based in Hazerswoude-Dorp, in the Alphen aan den Rijn municipality, half an hour from Leiden. Sitting down together in Leiden, Oegstgeest, Leiderdorp or Voorschoten is easy enough; on a longer track it usually works better to meet in person now and then than to do everything over video.

Frequently asked questions
Do you come to Leiden in person?
Yes. I am based in Hazerswoude-Dorp, half an hour's drive. On a short website track the first conversation is often over video because it is quicker; on a longer project I prefer to meet properly a few times.
What does a website in Leiden cost?
You get one fixed number before we start. For a website that depends on the number of pages and the functionality; for an application mainly on the integrations and the permission structure. After a half-hour call I know enough for an indication.
Do you build web applications and portals, not only sites?
Yes, that is a large part of the work. Logins with roles, data walled off per user, integrations with systems you already use. Reckon on four to six weeks rather than two to three.
Do you also work in Oegstgeest, Leiderdorp or Voorschoten?
Yes, and in Zoeterwoude, Katwijk, Rijnsburg and Kaag en Braassem. Everything around Leiden is within half an hour of Hazerswoude-Dorp.
Who owns the code?
You do. Everything lands in your GitHub repository and hosting runs on your account. If you want to continue with someone else later, nothing has to be prised loose. Why that matters is in owning your own code.
I built something with an AI tool. Can you carry on from that?
Usually. The data model and screens often stay usable; what is missing is the layer underneath — permissions, server-side work and an environment that runs independently of the subscription. Send the link and I will say whether carrying on or starting over is smarter.
Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

Bas Voets · Webframer
0:00 / 0:00
Website development in Leiden · fixed price, 2-3 weeks