Question 1

How do I know whether I need a web app or a website?

Accepted Answer

If your goal is to be found and explain what you do, you need a website. If people have to log in, enter data and work inside it every day, you need a web app. Half an hour on a call settles it, and if the answer is a website I tell you without dancing around it.

Question 2

How much does it cost and how long does it take?

Accepted Answer

A first usable release usually takes two to four months. The quote is phased: the first phase covers the main flow, the rest is decided after you have seen it working with the real people who will use it.

Question 3

Can I start small and expand later?

Accepted Answer

That is the approach I always recommend. The architecture is set up to grow, but the first release contains only what is genuinely needed: you do not pay for features nobody will use.

Question 4

Where does my clients' data end up?

Accepted Answer

On European cloud infrastructure, with data encryption and automated backups. GDPR-ready by design, not bolted on afterwards to chase a requirement.

Question 5

If I change developer tomorrow, am I stuck?

Accepted Answer

No. Code, database and cloud accounts are in your name, and the build uses standard, widespread technologies: any React developer can pick it up. No locks, by choice.

Question 6

Who maintains it after launch?

Accepted Answer

I do, on a monthly retainer, same as for websites: updates, monitoring, backups and new features agreed month by month. No lock-in.