Browser-based software

Custom web application development: portal, internal tool or business app

OmniTechs builds customer portals and internal web applications around one workflow that is stuck in spreadsheets, email or scattered tools. You get a fixed price after a Solution Sprint, the code and data are yours, and you can try Brengo, our own web application in a Groningen pilot, before agreeing anything. The calculator gives a first price indication in two minutes.

By Sina Esfahani · Practice page by OmniTechs in Groningen; amounts follow the current price contract · Reviewed .

What does a web application cost?

A first working version of a portal or internal tool starts at the starting price the calculator on this page shows; the price rises with the number of roles, screens and integrations. In a Solution Sprint of €1,250 excl. VAT we fix screens, permissions and integrations first; after that you receive a fixed build price, not a bundle of hours.

Further development and maintenance run through the COMPANY annual plan from €5,000 per year excl. VAT, or per scoped assignment. Hosting, backups and updates are a separate line in the quote, so you see what the application costs to run per year.

  • Sprint first: €1,250 excl. VAT, screens, permissions and integrations on paper
  • Build: fixed price for the agreed first version
  • Further development: COMPANY from €5,000 per year excl. VAT or per assignment
  • Code, data and hosting account in your name

What will your team be able to do?

Customers can submit and follow a request; staff can review it, make an authorised decision and handle an exception. Those are possible commissioning needs, not ready-made packages. We agree the users, data, permissions and complete task before choosing screens or technology.

Delivery covers the written scope, implementation, acceptance of normal and exception paths, launch and agreed handover. A web application runs in a browser; device installation, offline behaviour and push support depend on the project and target devices. It is not automatically an app-store product or a SaaS business.

Worth investigating when

  • known users must complete a recurring task in the browser
  • roles, data, rules and a process owner are clear enough
  • maintained standard software does not cover the critical workflow
  • the organisation can own security, operations and further change

Choose a simpler form first when

  • public information and contact are the real need — a website may suffice
  • a maintained package already covers the core workflow
  • users and ownership are still unstable
  • systems only need controlled data exchange — an API integration may suffice

Project status

Dated pilot evidence · own product

Brengo: an OmniTechs product

A Groningen transport pilot with requester and provider roles, task status, chat, route context and payment status. Public and guest-accessible captures date from 13 September 2026; protected workflows require sign-in. This is built-product evidence, not customer adoption or revenue.

Explore the Brengo workflow and its evidence

Relevant offer at a glance

Solution Sprint

Paid scope work

€1,250 excl. VAT

An organisation with a non-standard process or product problem that first needs to investigate users, dependencies, risks and scope.

Independent project work that clarifies the problem, users, dependencies, risks and scope before an implementation price is provided.

  • A 60–90-minute problem and process workshop
  • Current-state workflow map
  • User and stakeholder definition

Implementation not included

Annual plans for digital work

Part of a wider annual plan?

When software, automation and integrations add up to a year of work, COMPANY (from €5,000/year excl. VAT) can combine implementation and ongoing work. The proposal selects what is needed.

COMPANY

Build around how your company works.

From €5,000/year excl. VAT

A scoped technology plan for your website, specialist content and SEO, internal software, automation, mobile applications, AI and connected hardware.

The proposal selects the building blocks; not every capability is in the starting price.

  • A written proposal that selects the building blocks your company needs
  • Defined implementation for the plan year
  • Defined ongoing work: operation, maintenance and agreed improvements

COMPANY is not discovery only: the plan covers implementation and ongoing work. The Solution Session and Solution Sprint stay separate and optional.

Just this module?

That works. Request this module on its own, without an annual plan. A paid Solution Session or Sprint is optional.

Request this module on its own: Web app, dashboard or portalCompare the plans

Brengo connects the request, decision and handover

We built Brengo as an OmniTechs product around a local Groningen pilot. The requester enters a route and package, reviews a price and follows the task. A provider accepts the work; status, chat and handover connect the roles. The English case shows the actual public and guest-accessible screens and explains protected implementation paths.

The dated captures demonstrate that built workflow. They do not establish current service availability, usage, revenue or savings, and do not make Brengo a ready-made template for your business.

Start free; choose research only when it helps

Send your workflow or request a proposal directly. The first discussion is free. You do not need to buy a Solution Session or Sprint, or complete a roles matrix, before enquiring.

If you want reserved time to explore the question, the optional paid Solution Session is 90 minutes for €150 excluding VAT. For a scope that needs more investigation, the optional Solution Sprint (€1,250 excl. VAT) delivers agreed research; implementation is separate. We agree the research task before it starts.

Once scope is sufficiently clear, choose a standalone implementation proposal or discuss COMPANY (from €5,000/year excl. VAT) for agreed implementation and ongoing work. COMPANY is an optional annual engagement, not a maintenance add-on to the one-time estimate. Not every possible component is included in its starting price.

Choose around the working situation

Describe where users work, which device features they need and what happens when connectivity disappears. A login screen alone does not decide between a browser application and an installed mobile app. The Dutch comparison helps make those requirements explicit.

Start from the critical workflow

Do not start with screens. Define one user who must finish a recognisable task end to end: what starts it, which information is required, which rules apply, which status must be visible, and when the work is truly done.

Include the exception path early: missing input, duplicates, refused approvals, a failed integration or a manual correction. The first release should prove one full workflow including a safe recovery path.

What drives scope and cost?

The existing PWA/web-application starting estimate is €5,000 excluding VAT, one-time, for 5 screens, 1 user role, 1 language and 2 revision rounds. It is a nonbinding starting configuration, not a fixed price for every complete application. Extra roles, screens, accounts, administration, integrations and device features change the scope.

Your written implementation quote covers the complete chosen workflow, including required additions, testing, launch and agreed handover. Hosting, external services, licences and payment-provider costs are separate and confirmed before commitment. Roles, data, migration, permissions, exceptions, accessibility and dependencies affect both price and planning; no standard delivery duration is promised.

Build, accept, launch and hand over

We turn the agreed critical task into a scoped first release. Test realistic normal and exception paths: missing data, an unauthorised action, duplicate input, an unavailable integration and recovery. Agree the acceptance criteria and who signs them off before implementation.

Launch includes the agreed production setup and handover to a named, capable operator. Confirm access, documentation, export, recovery and responsibility for incidents. Acceptance of a working workflow and its operation is the outcome; a prototype or a written proposal is an earlier step.

Who operates the application after launch?

Before implementation, assign hosting, monitoring, backups, restore, updates, incidents and support to named owners with written scope and costs. The generic web-app estimate does not offer website Care or automatically choose self-hosting. An external operator or suitable ongoing work with OmniTechs needs an accepted handover and its own agreement; COMPANY can be considered where its agreed scope fits.

Your business data and content remain yours. Ownership and use of source code, specifications, configuration, documentation and third-party licences are agreed in writing before the build. Define export and exit responsibilities too. Later features, maintenance and migration are not unlimited parts of the original build.

A status change needs a responsible role

In an illustrative portal, a customer supplies a document and a reviewer approves it. Missing input should keep the request with a named owner rather than silently advancing it. Specify who may read, amend and approve each record before deciding how many screens to build.

A shared application is not automatically a SaaS business

Serving several customers adds questions about onboarding, data separation, payment, support and who maintains the service. Prove the recurring user problem and operating responsibilities before adding those commitments.

What to expect

  • A reply to your request within one working day
  • A first clickable version within the Sprint
  • Delivery in weeks, not months, for a first version with one workflow
  • Access for your team without a per-user licence
  • Documentation and handover so another team can continue

Questions about custom web application development

How much does custom web application development cost?

The existing starting estimate is €5,000 excluding VAT, one-time, for 5 screens, 1 user role, 1 language and 2 revision rounds. It is nonbinding; the complete implementation quote includes required additions for your agreed workflow. Hosting, external services, licences and payment-provider costs are separate. Optional paid research and COMPANY are separate choices; you can enquire free without buying either.

Website or web application?

A website communicates and converts. A web application is for known users who must work with data, roles and status. Mixing those without separate scoping creates risk.

Do you build full platforms?

We define what must work for a bounded first release. We do not sell an open-ended “platform” promise.

How long does building a web application take?

A first version with one workflow, for example a request portal with approval, is usually live six to ten weeks after the Sprint. Every extension afterwards is a scoped assignment with its own price and date.

How does this compare with standard software or a no-code tool?

Standard software is cheaper if your process fits it; a no-code tool is fast but ties you to a subscription and its limits. Choose custom work when the process deviates, the data must stay yours or per-user costs run away. The comparison table on this page walks through the trade-off.

Can you take over an existing web application?

Yes, after a free codebase check. We assess structure, dependencies and security and tell you what taking over costs and what has to be cleaned up first.

Which task should your web application complete?

Tell us who uses it, where the work gets stuck and which systems are already involved. The first discussion is free; paid research is an optional next step.