We save your 🕑 and 💶

You bring us a task: “Hi there, could you work out the price, thanks.” How do we do it?

1. An intro call – we get to know the client and the task. We give a preliminary range, e.g. 20000 – 30000 Eur. If the client is happy with the preliminary budget, we carry on.
2. We get to know the context – maybe there are similar systems out there, maybe we have already built something similar.
3. We break the task down – starting with the big chunks. Will it need a design, how many pages, how many integrations? Then we split it into separate tasks – e.g. “Google” login, administrator management, a “Google Maps” or other system integration.
4. We put the nice-to-have features aside for later.
5. We send a preliminary offer for the minimal version of the system (MVP).
6. We refine the project and the price – and clear up the parts of the system that are still unclear.

60 Eur / hour + VAT. That said, we very rarely bill our clients by the hour. Most of the time we give a final price for the whole system.

We believe that agreeing on a fixed budget lowers the client’s risk of surprise invoices and an ever-growing budget. It also makes us calculate the price properly and leave no unclear spots.

Once a month we invoice the share of the project that is done. E.g. if we have done half of the planned work, we invoice 50% of the full amount, minus the 30% advance you have already paid.

This way you only ever pay for the parts of the system that work! And the cherry on top – you get to judge the share of the work that is done yourself 😎

30% of the system budget. It covers the first programming work, so we only send the next invoice once more than 30% of the work is done!

Really minimal ones!

1. Server – the servers we use cost from 35 Eur / month. Most likely, that is exactly what your system’s server will cost. Under a really heavy load, it can grow to 100 Eur / month. That includes backups, a CDN and a pretty fast server.
2. Maintenance of the system’s tools – 60 Eur / month. It is not mandatory, but highly recommended. Once a month we update the libraries and tools the system uses. That keeps it secure and lowers the risk of technical problems.

Why do we ask 20000 Eur for a system that some guy from a “Facebook” group said he would build for 3000 Eur?

1. Quality – the guy from Facebook will not offer anything close to the quality of our systems.

2. Clean code – it takes several times longer than its slapdash equivalent. Writing code that works is much easier than writing code that keeps working for 10 years.

3. Invisible / non-negotiable work – clients often see only the surface of a system and do not always think about the extra optimisation, security, usability and reliability work included in our prices.

4. Building a system takes more than coding – it has to be tested, checked for security and usability, and its design and prototypes have to be drawn. All of that is included in our price.

It can – while the system is being built, clients quite often want to improve or change some parts of it.

Still, we discuss any increase of the budget with the client before doing any extra work. If we do not, the client has every right not to pay extra! 🤞

Sadly, we do not give discounts. But here are a few ways you can lower the price of your system:

1. Draw the design or a prototype yourself.
2. Describe clearly what needs to be built. A technical specification leaves less room for interpretation, so there is less risk of our estimate missing the mark.
3. Drop the nice-to-have features – maybe you do not need a Facebook login and Google alone will do?
4. Accept alternative suggestions – sometimes clients want a feature that is several times more complex than a similar alternative. By taking our suggestions on board, clients can cut the budget considerably!

No, but we have never built a system that cost less than 4000 Eur.