Web application

When you need one

It rarely starts with "we need an application". It starts with someone copying the same spreadsheet every week, or three people writing into the same inbox with nobody sure who has already replied. The moment worth building for is when the process exists and is simply tiring.

What that means in practice

A site that runs in a browser, behind a login. Nothing to install, and usable from a phone. It does only what it needs to: if three screens are enough, it has three screens. An application goes wrong when it does more than anyone uses.

How we price it

First we write down what gets built and what does not. Against that we give an estimate in hours, and the hourly rate is published: 20 000 Ft + VAT. We do not quote a fixed project price, because that is either padded or starts moving halfway through. The scope is fixed, the billing is hourly, and both are in writing.

You do not see it first at the end

You can look at what is finished while it is being built. That is not politeness: describing a process is hard, and most misunderstandings surface the first time someone clicks a real screen. Better to find that out in week two than at the end.

It stays yours

The source code goes into your repository and the logins are in your name. We build on ordinary frameworks rather than something we invented, so any developer can take it over.