Web applications built to grow.

Who I build them for

A web application suits organisations running into the limits of off-the-shelf software. You often know exactly what you need, but no ready-made package covers it, or you pay monthly for ten features while using two.

• You work with loose spreadsheets and tools that do not talk to each other.
• You have an idea for a product or service and want to get it live.
• Your current software does not grow with your organisation.
• You want clients or staff to log in somewhere and handle things themselves.

From idea to working application

You talk to the same person from start to finish: the developer who builds your application. Here is how that works.

1. 1

   We get it sharply in focus

   We start with a conversation about what you need and why. A vague idea or a worked-out plan are both a fine starting point.

2. 2

   I build a working core

   In short steps I build the core, so you quickly have something real in hand instead of a document full of promises.

3. 3

   We refine based on real use

   You use it, give feedback and I adjust. That is how the application grows into what it really needs to be.

4. 4

   I stay on after delivery

   Software is never finished. I stay available for maintenance, extensions and the next step.

What that looks like in practice

Layoutr is a web application I built myself: you upload your floor plan, set the scale and place furniture at true size, entirely in the browser. It runs live in production and has grown step by step since launch, following what users actually needed.

layoutr.app

Frequently asked questions

What does a web application cost?

That depends on what you need. A focused tool is very different from a complete platform. I work per project and map out the cost clearly up front, so there are no surprises.

What technology do you build with?

Usually .NET for the core and Next.js for the front end, hosted on Microsoft Azure. I pick the technology that fits your project, not the other way around.

How long does it take?

A first working version is often ready within a few weeks. I prefer to ship something usable quickly and build from there, rather than working in silence for months.

Can the application grow later?

Yes. I build with growth in mind: readable, maintainable code you can extend without starting over.