Web application development: from idea to working system

· 9 min read · By Andre Hassler

A custom web application usually costs €4,000 to €25,000+, depending on complexity, and follows intake, technical analysis, a fixed quote, iterative build and delivery. At ultimAItech you always get a fixed quote after intake — no open-ended hourly billing.

Somewhere between "we're still running this on a spreadsheet" and "we paid an outside firm €40,000 for something that never quite worked" lies a third option. A custom web application: built around your process, not the assumptions of a generic tool. In this article I explain what a web application actually is, when it's worth it, and what the journey from idea to launch looks like.

What exactly is a web application?

A web application is an interactive tool that runs in the browser and executes specific business logic — think a customer portal, a booking system, a dashboard with user roles, or a tool that connects several systems together. That's different from a website (which mostly shows content) or a webshop (catalogue plus checkout). A web application is about functionality: users log in, take actions, and the system responds based on rules that fit your business.

ultimAItech builds these kinds of systems for SMBs in Drenthe and Overijssel: from simple customer portals to more complex platforms like VYBR!S, a multi-tenant AI chatbot platform we built from the ground up.

When do you actually need a web application?

Not every process needs custom software. But in a few situations it clearly pays off:

  • You're still running things on spreadsheets nobody dares touch — order management, planning or stock tracked in Excel files emailed around
  • Your clients need their own portal — for documents, statuses or communication, secure and easy to navigate
  • Your booking or request process is just slightly different from what a standard booking tool can handle
  • You want to connect existing tools together — CRM, accounting, stock system — so you're not typing the same thing three times
  • A standard SaaS tool almost fits — you're paying for features you don't use, or missing the one feature you actually need

The steps: from intake to launch

Every project at ultimAItech follows five steps, whether it's a simple portal or an extensive platform:

  1. Intake — we discuss your requirements, business processes and technical context
  2. Technical analysis — we look at the best approach and what already exists, so we don't reinvent what already works
  3. Fixed quote — a transparent price, concrete milestones and a timeline
  4. Iterative build — development with regular feedback rounds and demo moments, so you're involved along the way instead of seeing something for the first time at delivery
  5. Delivery & handover — documentation, admin instructions, training, source code where agreed, and an aftercare period

Technical analysis is the step that's often skipped in cheap quotes — which is why the build stalls halfway through on something that was already visible during the intake.

What does a web application cost?

The price depends heavily on scope and complexity. Indicative ranges:

Solution type Price Notes
Customer portal / dashboard €4,000 – €12,000 Depends on users, roles and integrations
Process automation €3,000 – €15,000 Depends on flows and system integrations
Custom web application €7,500 – €25,000+ More complex flows, multiple user roles, integrations

After intake and technical analysis you receive a fixed price — no open-ended hourly billing where you only find out what it really costs after the fact.

Source code handover. Where agreed in the quote, you receive the source code of your application. No vendor lock-in: you're not stuck with one supplier for every future change.

A real example: VYBR!S

🤖 From idea to multi-tenant AI platform

VYBR!S is an AI chatbot platform we built entirely ourselves: a FastAPI backend with PostgreSQL, Redis and Qdrant, a React/TypeScript admin portal, and a RAG pipeline for training chatbots on a client's own content. The platform is multi-tenant — multiple organisations use the same system at once, each with their own data, user roles and dashboards — and runs in production on AWS EC2.

This is a complex platform, but the principle is the same as for a simple customer portal: start with what's actually needed, build iteratively, and expand once the foundation is solid. See the full VYBR!S case study.

Web application, webshop or website — what do you actually need?

Not sure whether you need a web application, a webshop, or "just" a website? The question that settles it: do you mainly need content and information (website), are you selling products with a catalogue and checkout (webshop), or is it about a process with logic, user roles and actions (web application)? If you're selling products with complex variants or pricing logic, also read custom webshop or Shopify — the same trade-off (template vs. custom) applies there.

Common pitfalls in custom software

Pitfall 1: trying to build everything at once

An application that has to do everything from day one becomes expensive and slow to build. Start with the core function that saves the most time, then expand based on actual usage.

Pitfall 2: no exit path

Always ask about source code handover and documentation. Without it, you're stuck with one supplier — even if the working relationship stops clicking.

Pitfall 3: skipping the technical analysis

A quote without technical analysis is a guess. Take the time to look at what already exists and what the best approach is before the build starts.

Frequently asked questions

What's the difference between a web application and a website?

A website mostly shows content and information. A web application executes business logic: users log in, take actions and the system responds based on rules — like a customer portal or booking system.

How much does a custom web application cost?

Indicatively €4,000–€12,000 for a customer portal or dashboard, €3,000–€15,000 for process automation, and €7,500–€25,000+ for more complex custom applications. The exact price follows as a fixed quote after intake.

How long does it take to develop a web application?

That depends heavily on scope. A simple customer portal can be ready in a few weeks; an extensive platform with multiple modules takes a number of months. You'll receive a concrete timeline after the technical analysis.

Do I get the source code of my application?

Where that's agreed in the quote, yes. That way you avoid vendor lock-in and can continue with another party later on, if that's ever needed.

Can a web application be connected to my existing tools?

Yes, system integrations are a big part of what we build — connecting your CRM, accounting software, stock system or other existing tools. We determine what's feasible and worthwhile during the technical analysis.

Conclusion

Building a web application isn't a leap into the unknown once you know the process. Intake, technical analysis, a fixed quote, iterative build and a solid handover — that's the structure that keeps your project from stalling or costing far more than planned.

Do you have a process that's outgrown a spreadsheet or a standard tool? Schedule a no-obligation intake or send a WhatsApp. We'll look together at whether custom software makes sense — and I'll be honest if it doesn't.

Related articles & pages

Custom software & AI

Customer portals, dashboards and AI chatbots built for SMBs.

View services

Got a process that needs custom software?

Schedule a no-obligation intake. We'll discuss your process and whether a web application is the right fit.