Select Interactive

Guide

Custom web application cost: the six drivers that move the number.

Every quote for a custom web app is a function of the same handful of things: how many objects and roles the system has to model, what it must talk to, what data has to come across, what documents it has to produce, where it runs, and how it keeps changing. This page walks through each driver with the projects we have shipped, so you can read a scope the way we do. No figures here. Scope first, then a conversation.

Get a scoped conversationBuild a project blueprint

Who This Is For

Who this guide is for

  1. Operations and finance leaders

    01

    You own a process that has outgrown its spreadsheet or SaaS tool and need to bring a credible scope to budget planning.

  2. IT and product leaders

    02

    You are comparing a custom build with low-code and off-the-shelf options and want to understand what the custom path actually involves.

  3. Founders and executives

    03

    You want to know which decisions move the number before you ask anyone for one.

Not for

Anyone looking for a published rate card or a calculator. Cost depends on scope and specifics, and we quote fixed fees after a discovery phase.

Cost Drivers

The six things that move the number

Spreadsheet grid becoming a database

1. Objects and roles

The largest driver is how many distinct things the system models and how many kinds of people see them differently. A manufacturer with contacts, contracts, locations, and sales figures is several objects. Seven roles on one dataset is seven interfaces.

  • Rees-Jones Holdings: employees, managers, directors, executives, HR, C-suite, and IT each get a different interface and different data. Role count set the scope.
  • MJEC: manufacturers, contacts, contracts, locations, divisions, departments, documents, notes, and sales targets, each a modeled object with history.
  • Alcon: products, sales history, revenue models, market data, forecast versions, and notes per change.
Integrations and identity

2. Integrations and identity

Every system the application has to read from or write to adds a contract to honor: an identity provider, a CRM, an ERP, payroll, a payment processor, a city events API. Single sign-on and directory sync are their own line.

  • Arlington Sports Commission: live city event data from the arlington.org API.
  • Performance Course: Braintree payments, Twilio, and SendGrid in one registration platform.
  • Enterprise web development covers SSO, systems of record, and agent-ready handoff (OpenAPI, llms.txt, MCP).
Spreadsheet grid becoming a database

3. Data migration from the workbook or the legacy system

Years of history in a workbook or a retired platform have to be mapped, cleaned, and loaded with the same care as the application itself. The messier the source, the larger this is.

  • Alcon: sales history and revenue models structured with the data science team before the first screen.
  • EZ Storage: a legacy ASP.NET 2.0 site replaced, with live inventory carried into the new platform.
  • Foundation for Contemporary Arts: 1,100+ CMS-managed pages migrated and maintained.
Charts and generated documents

4. Reports, documents, and visualizations

Dashboards, charts, exports, and generated documents are each a feature, not a byproduct. A branded PDF from live data is a real piece of software.

  • MJEC: on-demand PDF brochures filled from live manufacturer data, with filters by location, equipment, and product type.
  • Alcon: multi-year projection curves and scenario comparison in shadcn/ui charts.
  • Rees-Jones Holdings: live dashboards and charts on annual compensation and benefit data.
One dataset, several role-specific doors

5. Hosting, security, and operations

Where it runs and what it must prove: audit logs, snapshots, role-based access, security headers, uptime. Internal tools and public tools carry different requirements, and a system that spans both carries both.

  • MJEC: audit log of every change, rolling seven-day database snapshots, Firebase role-based auth, deployed on Azure.
  • Dave Campbell's Texas Football: 20M+ visits a year with 99.9% uptime through peak season.
Attributed history and recovery points

6. Cadence after launch

A system a business runs on keeps changing. Whether you want a handoff, a retainer, or a quarterly release cadence changes how the engagement is shaped and priced.

  • MJEC: quarterly review and release cadence since 2025.
  • Rees-Jones Holdings: launched 2024, with new phases and features each year.
  • JTaylor: an intranet maintained and extended since 2014.

How We Scope

How we turn a problem into a fixed fee

We quote fixed fees after a discovery phase, or work on a retainer. Discovery is where the six drivers above get real numbers attached, in your context.

The process, the people, the current tools, and what hurts. Bring the spreadsheet or the line card, not a specification.

Objects, roles, integrations, migrations, documents, and operations written down and agreed. This document is the basis of the fee.

The functional design is decomposed into tickets and sprints, so the plan is concrete before work begins.

Weekly check-ins, a shared staging environment, working software every sprint, and support after launch.

FAQ

Questions we hear about cost

Because cost depends on scope and specifics, and a number without a scope misleads in both directions. Share your project through contact or the project blueprint and we will give you a tailored estimate after discovery.

Objects and roles. How many distinct things the system models and how many kinds of people need a different view of them.

Often. A conventional React, TypeScript, and TanStack codebase with shadcn/ui components means less bespoke UI work and a team your own developers can hire for.

Sometimes up front, and the difference is ownership and fit rather than a simple comparison. We will tell you when a low-code tool or an existing product is the right answer.

When one person uses it, the data is not sensitive, and nobody is waiting on it. We say so in the first conversation.

Most projects are scoped and delivered on a fixed-fee basis after a discovery phase, and retainers are available for ongoing partnerships. How discovery is structured is part of the first conversation.

Keep Going

Related solutions, process, and reading

Solutions

Process and services

Reading

Start A Conversation

Bring the scope. We will bring the number.

Tell us the objects, the roles, what it must talk to, and who is waiting on it. A technical conversation, then a fixed fee after discovery.

Start a conversation
All solutions