Frequently asked questions about
web application development

Answers to the questions we get most often about building a web application or portal.

Preparation and strategy

When do you need a web application? We explain the difference from a website and a mobile app, and when a web application is the right choice.

What is the difference between a website and a web application?

Websites present information. Web applications let users do things: log in, enter data, generate reports, manage colleagues. As soon as user input, authentication and business logic are involved, you are talking about a web application.

Examples: a client portal for downloading invoices, a scheduling system for staff, or a dashboard with real-time production data.

Web applications run in the browser, are platform-independent and require no installation on the user's device.

When do I need a web application instead of a website?

A web application is the right choice if:

  • You want to automate internal processes, such as quotes, scheduling or reports
  • Customers or staff need to view or manage data themselves
  • You are using an off-the-shelf package that does not fit your processes
  • You want integrations between systems (AFAS, Exact) and a custom interface
What is the difference between a web application and a mobile app?

Web application — runs in the browser, no installation needed, easier to update, suitable for desktop and tablet.

Mobile app — access to camera, GPS and push notifications, works offline, but requires installation via the App Store or Google Play.

Often a combination is the best choice: a web application for the administrator, a mobile app for the end user. We build both, so you have one point of contact for the entire platform.

Technology and architecture

Which technologies do we use and why? From frontend to backend, APIs and integrations with existing systems.

Which technologies do you use for web applications?
  • Frontend: TypeScript and modern web standards
  • Backend: Node.js or NestJS on Google Cloud
  • Databases: PostgreSQL for relational data, Firestore for real-time applications
  • APIs: clean separation between frontend and backend via REST or GraphQL, so a mobile app can be added later
  • Middleware: Node.js with event-driven architecture for reliable integrations
Do you also build the backend?

Yes. We build the full stack: frontend, backend, APIs and databases. That means one point of contact for the entire technical picture.

We also handle hosting on Google Cloud, monitoring and backups.

Can the web application integrate with our existing software?

Yes. We have extensive experience integrating with systems such as AFAS, Exact, SAP, Salesforce and custom APIs. Middleware that automatically synchronises data is one of our specialities, so you never have to enter data twice or transfer it manually.

During the intake meeting we assess which integrations are needed and whether the available APIs are well documented. Integrations with poorly documented systems require more work and are always listed separately in the quote.

Costs and timelines

What does a web application cost and how long does development take? We give realistic estimates per project type.

What does it cost to have a web application built?

A simple web application starts from €10,000. A full platform with multiple user roles, integrations and custom design can easily reach €30,000 to €80,000+.

The price depends on:

  • Number of screens and workflows
  • Complexity of user roles and permissions
  • Integrations with external systems
  • Amount of custom design work

We work on a fixed day rate and produce a detailed quote per phase. After an intake meeting we give you a realistic estimate.

How long does web application development take?

A simple web application is typically built in 6 to 10 weeks. A complex platform with multiple user roles and integrations takes 3 to 6 months. The preparation phase, from intake meeting to approved quote, takes 2 to 4 weeks.

We work in two-week sprints. After each sprint you receive a working version to test and provide feedback on. That way you do not only discover something works differently than expected at the very end.

Security and privacy

How do we ensure your web application is secure and GDPR-compliant?

How do you ensure the web application is secure?

Security starts at the architecture level. Standard measures we always apply:

  • Encrypted connections (HTTPS)
  • Correct authentication and authorisation
  • Backend on Google Cloud with standard security layers
  • Sensitive data not stored unless strictly necessary

For applications handling medical or financial data we apply additional measures. We follow the OWASP Top 10 as a guideline.

What about GDPR and personal data?

If the web application processes personal data, GDPR applies. We build with privacy in mind by default:

  • Only request data that is necessary
  • Implement correct consent flows
  • Store nothing that is not needed

If we act as a processor of your user data, we draw up a data processing agreement. We also advise you on what you as the data controller need to arrange yourself, such as a privacy statement and a register of processing activities.

After launch

Who owns the code, how does hosting work and what does maintenance cost?

Who owns the code after delivery?

You do. The source code is entirely yours after delivery and payment. We hand it over via a Git repository of your choice.

You are never dependent on us: you can transfer the code to another party or develop it internally. We document the code and architecture for a smooth handover.

There are no licence fees or hidden obligations.

How does hosting and maintenance work after delivery?

We deploy on Google Cloud by default, with monitoring, backups and security updates.

Each quarter we issue an advisory report with recommended maintenance:

  • Framework updates and dependency upgrades
  • Security patches
  • Performance improvements

You decide which work to commission. There is no mandatory maintenance contract. Average annual maintenance costs range from €2,000 to €8,000. Deferring maintenance builds up technical debt that requires a larger catch-up effort later.

Can you take over and further develop an existing web application?

We do this regularly. We always start with a technical review: code quality, architecture, frameworks used and known pain points. Based on that we give honest advice: continue on the current codebase, partially refactor, or start fresh.

Bring as much as possible to the first meeting: access to the repository, technical documentation and an overview of the biggest issues in the current application.

★★★★★

Ready to get started?

Let's grab a coffee. Tell us about your idea and we'll give you our honest take on what's possible.

Schedule a call →
WhatsApp