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 on paper.

From €12,000, billed as fixed-price milestones rather than by the hour; the total depends on how many workflows the system has to support. Fixed quote within 48 hours — see what is included.

Get a free consultation Chat on WhatsApp

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

Custom projects rarely derail because of the code. They derail because it was never clear enough what was being built, so every stage here is defined before it starts.

  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 structural changes happen while they're still cheap.
  3. Weekly staging builds: you click through real progress every week instead of reading reports about it.
  4. Launch with ownership: your repository, your servers, your data. Documentation included.

Practical matters, wherever you are

Hiring a developer in another country raises fair questions, and more of them when what you are buying is a system your business will run on. Here are the answers before you have to ask.

The proof

Not a portfolio screenshot, but software running in production. Celina is a two-sided marketplace I founded, built and still operate: orders, live status tracking, identity verification, more than 100 prerendered pages indexed by Google and Yandex, and automated deploys to a server I administer myself with Docker and nginx.

Purchases is a platform in Java 17 and Spring Boot, with JWT authentication and role-based access control on every endpoint. The source is public on GitHub, so you can read how I work before you hire me.

Both systems are mine end to end — architecture, database, front end, servers and deployment — and both are still running.

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 real use of 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 set 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 duplicate 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.
Who owns the code once the project is finished?
You do. The repository, the design and the data transfer to your business on the final payment, documentation included. There is no license and no monthly fee for permission to keep using something you have already paid for. If you later move maintenance in-house or hand it to another team, nothing has to be migrated first.
How do you invoice?
You get an itemized invoice in euros.
Describe your idea — fixed quote in 48h