How long until something is actually usable?

You’ll have a clickable staging build inside three weeks and a genuinely usable version around the halfway mark. Full launch is usually 8–16 weeks; anything quoted at four weeks is either tiny or optimistic about your integrations.

Can you take over an application someone else built?

Often, yes. We start with a short paid audit — dependency state, test coverage, deploy path — and give you an honest read, which is occasionally that a rewrite of one module is cheaper than nursing all of it.

Which browsers and devices do you support?

By default the current and previous versions of Chrome, Safari, Firefox and Edge, plus mobile Safari and Chrome, down to a 360px viewport. Anything older is possible but we’ll price it separately so you can see what it’s costing.

What happens after launch?

You either take it in-house — which is why the docs and CI matter — or we stay on a monthly retainer for fixes and small features. Either way the code, repository and infrastructure accounts are yours throughout.

Software & Product Development service

Web Application Development

Q: How much does a web application cost?

Most builds we take on land between $30k and $90k, driven mainly by how many distinct user roles and integrations there are rather than screen count. We quote a fixed first milestone and a written estimate for the rest, and we’ll tell you which third of the scope you probably don’t need.

Software that lives in a browser tab, built to load fast, stay accessible, and survive its second year.

Scope your web app ↗

8–16 wks

typical scope to launch

<2.5s

largest contentful paint budget

wcag 2.2 conformance target

1 wk

release cadence after launch

What is web application development?

A web application is software delivered through the browser, where the browser does real work rather than just displaying pages. The practical difference from a website is state: accounts, permissions, data that changes while someone is looking at it, and a URL you can send a colleague that still shows the right thing.

Most of the cost in a web build isn’t the screens — it’s the boring middle. Session handling, form validation that survives a flaky connection, pagination over 200,000 rows, and a data model that doesn’t need a rewrite when the second customer asks for something. We spend discovery arguing about those, because they’re the parts that get expensive later.

What’s included

What a web build includes

A defined browser matrix

We agree up front which browsers, screen sizes and connection speeds are in scope. Supporting one more old browser is a real cost, so it should be a decision, not an assumption.

Performance budget

Page weight and interaction targets set before build, checked in CI. If a feature blows the budget we say so while it’s still cheap to change.

Accessible by default

Keyboard paths, focus order, contrast and labelling done as we build, aiming at WCAG 2.2 AA rather than a remediation project afterwards.

Data model and migrations

A schema designed for how the business actually works, with versioned migrations so changing it in month nine is routine.

Automated test suite

Unit tests on logic and end-to-end tests on the two or three journeys that must never break. Not 100% coverage theatre.

Handover documentation

A written architecture note, local setup that works from a clean machine, and a runbook for the things that page someone at night.

How a web build runs

Scope and constraints

One to two weeks turning the brief into user journeys, a data model sketch, and the non-negotiables — browsers, load, compliance, integrations.

Design the system, not screens

Components, states and empty cases defined together, so the fifteenth screen costs a fraction of the first.

Build in two-week slices

Every slice ends with something deployed to a staging URL you can click. Scope trades happen in that review, in the open.

Harden before launch

Load testing, accessibility audit, error budgets, and a rehearsed rollback. We launch on a Tuesday morning, never a Friday afternoon.

Stabilise and hand over

Two to four weeks of watching real traffic, fixing what only production reveals, then transferring the repo, docs and on-call knowledge to your team.

Web Application Development FAQ

Most builds we take on land between $30k and $90k, driven mainly by how many distinct user roles and integrations there are rather than screen count. We quote a fixed first milestone and a written estimate for the rest, and we’ll tell you which third of the scope you probably don’t need.

Tech stack

The tools we build with

We pick tools with long support horizons and large hiring pools, because the second team to touch this code probably isn’t us.

Frontend

Next.js

React

TypeScript

Tailwind

Backend & data

Node.js

NestJS

PostgreSQL

Prisma

Redis

Quality

Vitest

CypressWCAG 2.2

Run & observe

Vercel

Cloudflare

GitHub Actions

Sentry

Our work

Related work

All work ↗

Person holding and using a mobile app on a smartphone

Travel

Caravan

A group road-trip coordination app — friends converging from different cities plan stops together, track each other live on a map, and split shared costs.

15feature areas shipped in the MVP

E-commerce

Image Fashionway

A men's and kids' fashion storefront built and launched on Shopify in fourteen working days, with a Tamil Nadu-focused merchandising system.

108 hrsdesign, build, and integration — kickoff to launch

Students in a classroom with a teacher presenting a lesson

EdTech

Welfit

A mobile course platform for tailoring education — Men's, Women's, and Uniform stitching tracks — with DRM-protected video and a full admin dashboard.

3course catalogs — Men, Women & Uniform tailoring tracks

From the blog

Ready to move it into the browser?

Send us the journeys and the constraints. We’ll come back with a scoped build, a performance budget, and the parts we’d cut first.