Article Software

The web application development process, stage by stage

What actually happens at each stage of a web application project, what the client is asked to provide, and what should come back at each step.

In this note

A stage-by-stage walk through a web application project, showing your inputs and the outputs you should expect at each point.

7 min read
A web team holds a sprint planning meeting around a table with laptops and a large monitor showing a project board.

Published by

VSN Editorial

Date

Oct 14, 2026

Read time

7 min read

A web application is not a website with more pages. It has users who sign in, data that changes, rules that decide what happens next and, usually, connections to other systems. Building one is closer to building software than publishing content.

If you have never commissioned one, the web application development process can feel opaque. This guide walks through each stage, what you will be asked to provide, and what you should receive before moving on. The labels vary between teams, but the work underneath is similar.

Stage 1: Discover the job the application must do

Discovery turns an idea into a shared understanding. The team learns who will use the application, what those people need to get done, and what already exists: current tools, spreadsheets, websites, data and systems.

Good discovery spends more time on the work than on the screens. It asks how a request moves through your business today, where it stalls and which mistakes are costly.

You bring

  • Access to the people who do the work today and the people who will approve the project.
  • Examples: forms, spreadsheets, reports, screenshots of current tools.
  • Known constraints: budget range, timing, hosting preferences, required integrations.

You get back

  • A prioritised brief describing users, goals and success measures.
  • A list of open questions and risks.
  • An initial view of what belongs in the first release.

Stage 2: Define pages, flows and architecture

Definition is where decisions are written down. The team maps the user journeys and key screens, the roles and permissions, the data the application stores and the systems it connects to. They also propose the technical approach: the platform or framework, the hosting model and how the frontend and backend divide the work.

This is also when acceptance criteria are agreed. An acceptance criterion is a testable statement, such as “a customer can reset their password from the sign-in screen and receives the email within the agreed time.” These statements are what the build will later be checked against.

You bring

  • Decisions on priorities, roles and business rules.
  • Confirmation of who owns each third-party account and its costs.

You get back

  • User journeys or a sitemap, and a list of key screens.
  • A technical approach with its main trade-offs.
  • Milestones, acceptance criteria and a list of client dependencies.

Stage 3: Design the experience

Design usually starts with wireframes, simple layouts that show structure and content without visual styling. They are cheap to change, so this is the best time to test whether a flow makes sense to real users.

Once structure is agreed, the visual design defines colours, typography and reusable components. Responsive behaviour, accessibility expectations and empty, loading and error states should be designed too, not left for developers to improvise.

You bring

  • Brand assets, real sample content and timely feedback.
  • Two or three people who can try the wireframes and say where they get stuck.

You get back

  • Wireframes for the key flows, then visual designs for agreed screens.
  • A component set that keeps the rest of the interface consistent.

Stage 4: Build in reviewable increments

Development turns designs and rules into working software. On a well-run project you see progress as working features at regular intervals, not as a single reveal at the end.

The backend handles data, business rules, permissions and integrations. The frontend handles what users see and do. Between them sits an API, the contract that defines how the two exchange information. Integrations with payment providers, CRMs or other systems are built and tested against the providers’ test environments where available.

You should be able to click through real progress long before the final deadline.

— VSN Editorial

You bring

  • Feedback at each review, within the agreed time.
  • Test accounts and API credentials for third-party services, shared securely.

You get back

  • Working increments demonstrated at agreed checkpoints.
  • A record of decisions and any change requests with their impact.

Stage 5: Verify the important paths

Testing checks the application against the acceptance criteria. That typically includes the main user journeys, permissions, forms, integrations, error states and agreed browsers and devices. Depending on scope, it may also include accessibility, performance and regression checks.

You will be asked to take part in acceptance testing: using the application as your team would and confirming it does what was agreed. Fixes are then prioritised against the written scope.

You bring

  • People to run acceptance tests with realistic scenarios.
  • Clear, reproducible reports of anything that looks wrong.

You get back

  • Test results against the acceptance criteria.
  • A list of known limitations, if any, before launch.

Stage 6: Launch and hand over

Launch is a checklist, not a moment. Domain, hosting, environment settings, administrator accounts, backups, analytics access and any data migration must be ready. Someone needs to own the rollback plan if something goes wrong.

Handover means leaving you able to run what was built: access to accounts, deployment steps, technical notes, admin guidance and the list of third-party costs. If your project replaces an existing site or platform, our website migration checklist covers the extra steps.

Stage 7: Support and improvement

After launch, real users find things nobody predicted. A support arrangement covers updates, monitoring, fixes and small improvements within a defined service window. Larger features are usually scoped as new pieces of work. For what to budget, see website maintenance cost.

How to keep the process on track

Most delays in a web application project come from the client side of the table as often as the development side, and they are just as preventable.

  • Name one decision-maker who can approve scope, designs and acceptance without waiting for a committee.
  • Agree feedback windows. If reviews come back within an agreed number of days, milestones hold.
  • Keep a decision log. A shared document listing what was decided, when and by whom prevents the same debate twice.
  • Treat changes as changes. New ideas are welcome, but each one should be estimated and approved before it joins the build.
  • Prepare content and data early. Real content exposes design problems; real data exposes rule problems.

The web application development process at a glance

StageMain questionKey output
DiscoverWhat job must the application do?Prioritised brief and risk list
DefineWhat exactly are we building, and how?Journeys, architecture, acceptance criteria
DesignHow will people use it?Wireframes, visual design, components
BuildDoes it work as agreed?Reviewed increments of working software
VerifyIs it ready for real users?Test results and known limitations
LaunchCan we switch it on safely?Live application, access and handover
SupportHow does it stay healthy?Agreed support scope and improvements

Key takeaways

  • Discovery and definition decide most of the project’s cost and risk.
  • Acceptance criteria written early make testing and sign-off objective.
  • Expect working increments at regular checkpoints, not one reveal at the end.
  • Your team’s input and feedback are part of the timeline.
  • Launch includes access, backups, rollback and a clear handover.

Questions about the development process

How long does a web application project take?

It depends on the number of user roles, workflows, integrations, data migration, design depth and how quickly decisions and feedback come back. A defined scope with milestones gives you a realistic plan for your specific project.

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

A website mainly presents information and collects enquiries. A web application lets users sign in, manage data and complete tasks governed by business rules, often connected to other systems.

Do I need to be technical to commission a web application?

No. You need to know your business process and be available to make decisions. A good team explains technical choices in plain terms and records them.

Can we change requirements during the build?

Yes, through an agreed change process. Each change is estimated for its effect on scope, budget and timing, then approved before it is scheduled.

VSN plans web applications around users, business rules and the systems behind them, with documented milestones and a clean handover. Read about our web development service or tell us what you need to build.

Filed under Software

Keep reading

Related notes