Applications · portals · online tools

Web applications that do the work, not just look good.

A website talks about your company. A web application works for it: it calculates quotes, takes bookings, guides a client through a configuration, keeps data in order. I design and code these tools personally - from the idea, through the backend, to an interface that needs no manual.

Scope
Portals, configurators, bookings, tools
Architecture
Serverless, low running costs
Standard
Lighthouse 90+ · WCAG · GDPR
Proof
Working applications, live
Applications you can click nowThe Free AI Audit on this domain is a full application: the backend scans the address you give it, calculates a 0-100 score and emails the report. Not a slide, a working tool.
A backend without an expensive serverI build on serverless architecture: you pay for real usage, not for renting a machine. The application runs cheaply and scales on its own.
One person, full accountabilityYou talk to the person who designs and writes the code. No salesperson, no hand-offs between departments.

When a website stops being enough and an application begins

The line is simple: if the visitor needs to do something rather than just read, you need an application. The situations companies come to me with most often:

  • Clients call to ask "how much is it?" - a quote calculator or configurator answers for you around the clock and leaves you a ready lead instead of a phone call on a Sunday.
  • You keep bookings in a notebook or a spreadsheet - a booking system with email confirmations ends double bookings.
  • Your team loses time on repetitive paperwork - an internal tool (an offer generator, a ticket log, an order panel) turns hours into minutes.
  • You want to give clients an account - a client portal with order history, downloadable documents and project status.

See it live

I do not show mock-ups. I show working applications that I built from scratch and that serve real users:

  • Free AI Audit - you enter a website address, the backend fetches it the way AI bots do, runs a dozen or so tests and emails a 0-100 report. Underneath: serverless functions, a results database, rate limits, abuse protection, Polish and English versions.
  • VELOCE - a concept application for premium car rental with a 3D carousel and a racing game that runs in a phone browser. It shows that a web application can also mean an experience people do not forget.
  • The AI assistant on this site - an agent that talks to REELM's clients in Polish and English, collects enquiries and emails them to me. Behind it: a language model plus a serverless function with a rate limit.

What you get when I build your application

The same standard I keep for websites, plus the things that make or break an application:

  • Serverless architecture - no rented server and no administrator; running costs stay small instead of turning into a fixed monthly server bill.
  • A fast, light interface - React where the complexity calls for it, plain JavaScript where it is enough. Lighthouse 90+, tested on a real phone.
  • Security from day one - rate limits, data validation, form protection, GDPR built into the design rather than bolted on in the terms.
  • Integrations - with booking systems, payments, email, spreadsheets and external APIs; also automations that move data where it needs to go on their own.
  • AI where it makes sense - I can build a language model into the application: document analysis, answers to customer questions, content generation. I do this in my own products, including SEZAM, my SaaS for public tenders.
  • The code and access belong to you - no lock-in to a closed platform.

Questions I hear most often

How much does a web application cost?
It depends on the scope: a simple quote calculator or a form with logic is a different project from a client portal with accounts and payments. Every project is quoted individually, free concept and quote within 24h, with the price stated upfront - no hidden costs and no subscription just for the application to exist.

How is a web application different from a website?
A website informs; an application does work: it calculates, books, stores data, logs users in, generates documents. Technically, an application has a backend and state - data that lives between visits.

Which technologies do you build with?
Serverless by default (Cloudflare Workers/Pages, a cloud database), because running costs stay small and no server administrator is needed. The interface is React when the application is complex, or plain JavaScript when that is enough.

Can you integrate the application with the systems I already use?
Usually yes - through an API, webhooks or import and export. Before I promise anything, I read your system's documentation and tell you plainly what is possible.

How long does it take?
A single-purpose tool takes days to two weeks. An application with accounts and integrations takes weeks. I set the deadline when I quote and I keep it.

Will the code be mine?
Yes. I hand over the source code and all access.

Tell me what it should do, I will tell you how to build it.

Fifteen minutes of conversation is enough for me to tell you whether your idea is a simple week of work or a larger project, and what it costs. Every project is quoted individually: free concept and quote within 24h. No obligation.