Custom Web Application Development

Software built around your business — not the other way around

When off-the-shelf tools stop fitting, you need custom software: a marketplace, a booking system, an internal dashboard, a customer portal. I design and build these end to end — and I've done it for my own production systems, not just clients'.

From €8,000, billed as fixed-price milestones rather than hours; scope at this tier typically runs €8,000 to €25,000, depending on how many workflows the system has. Fixed quote within 48 hours — see what is included.

What I build

Built securely, by default

Security isn't a feature tier. Every application ships with proper authentication (JWT, session security with remote sign-out), role-based access control enforced on the server, input validation, and encrypted transport. I've implemented KYC identity verification and multi-device session security in production — the same patterns used in e-commerce and digital banking.

The stack

Frontend: React 18, TypeScript, Vite. Backend: Node.js/Express or Java 17/Spring Boot — chosen for the job, not for fashion. Data: MySQL, Prisma/Hibernate. Infrastructure: Docker, nginx, automated deploys with HTTPS. You get clean, documented code that any future developer can pick up.

How we keep the project on track

  1. Scoping: we define the smallest version that delivers value — you get a milestone plan with a fixed price per milestone.
  2. Design first: clickable mockups before code, so expensive changes happen when they're still cheap.
  3. Weekly staging builds: you click through real progress every week, not read reports about it.
  4. Launch with ownership: your repository, your servers, your data. Documentation included.

Frequently asked questions

How do you price a web application when the full scope isn't clear yet?
Nothing gets a price until it has a definition, so the fixed quote you receive within 48 hours covers only what we have actually specified. The unclear parts are named as open questions and priced in a later milestone, once using the first version has answered them. An unknown never turns into an open-ended bill, and you never approve a number for work neither of us can describe yet.
How long before I have a version I can actually use?
Before the app is finished — the first milestone is deliberately a working slice, not a demo. Milestone dates are agreed during scoping, before any code is written, and you get a staging link you can open every week. Real usage of that first slice usually reshapes the rest of the plan, which is exactly why it comes first.
Who sets up the payment provider, and where does the money go?
The payment account is opened in your business's name, so funds go from your customer to your provider to your bank — never through me. I integrate whichever provider fits your market, then build the unglamorous half: webhooks, refunds, failed and duplicated payments, and reconciliation you can audit. The API keys stay yours, and I can be removed from the account at any time.
Would an off-the-shelf SaaS be cheaper than building this?
Up front, almost always — and if a subscription tool already fits how you work, I will tell you that during the free consultation instead of quoting you. Custom is worth it when the workflow is the business: a two-sided marketplace, pricing rules no product supports, data you cannot hand to a third party, or per-seat fees that grow faster than your revenue.