What Custom Web Development Actually Costs (And When You Shouldn't Buy It)

Most people asking "how much does custom web development cost" don't need custom web development. They need to stop running the business out of a spreadsheet with fourteen tabs and a macro nobody understands anymore, and they've correctly guessed that the fix involves software. That's a good instinct. It's just aimed at the wrong first question.

Do you actually need custom, or do you need a better spreadsheet?

Here's the test. If your process is one team, one workflow, and a shape a thousand other companies share (quoting, basic scheduling, simple invoicing), an off-the-shelf tool solves that for a tenth of the price of building it yourself. Companies in logistics, healthcare, field services, manufacturing, professional services, retail, fintech, and construction come to us because they've already tried that route and outgrown it. The spreadsheet everyone secretly runs the business on started as a smart shortcut. Then it became the system nobody can replace, with a macro one person understands and no audit trail when something goes wrong.

If your workflow is genuinely specific to how you operate — your dispatch logic, your approval chain, your particular pile of systems that don't talk to each other — that's when custom earns its price.

Not before.

What's actually in a custom web build

A real engagement isn't "a website, but fancier." It's the operational core of the business, built to fit. That means portals and dashboards that match how your team actually works, not a generic template. Role-based access, so a dispatcher sees what a dispatcher needs and a controller sees what a controller needs. Audit trails and approvals, so when someone asks "who signed off on this" six months from now, there's an answer. Reporting built for finance teams specifically, not a dashboard that looks good in a demo and gets exported to Excel anyway. Migration of whatever data you're already sitting on, so day one isn't day zero. Training and documentation, because software nobody knows how to use is just an expensive UI on top of the old problem.

If a proposal doesn't name most of these, ask why.

The stack, and why it's deliberately boring

We build on React, Node, and Postgres. Not because it's exciting. Because it isn't.

Boring technology, on purpose: novelty is a cost paid every year after launch, and the client pays it, not the vendor. A framework that's three years old and fashionable today is a hiring problem and a migration project down the road. A stack with a decade of production use behind it has known failure modes, a deep hiring pool, and no surprises waiting in year three. We're not choosing the interesting tool. We're choosing the one that still works when nobody's excited about it anymore.

Price, timeline, and how discovery turns a guess into a number

Custom web applications start from $45k, typically 10–20 weeks depending on scope. That's a real starting point, not a headline number that quietly excludes the project you're actually asking about.

We don't quote off a phone call. We start with a discovery week: flat $4,800, credited back in full if you continue with us. It ends in a written scope, an architecture sketch, and a fixed estimate. Not a range. A number.

Most estimates in this industry get built backwards. A salesperson gives you a range before anyone's mapped your actual workflow, then the number moves once the engineers see what's really involved. We do it the other order. Estimates come after discovery, not before, which is why the number holds. It's a week of real work, not a sales call dressed up as one — and it's the reason we don't have a change-order conversation three months in that starts with "so, it turns out."

How billing actually works

A fixed-scope project starts at $28k per phase, billed on milestones: roughly 30% at kickoff, the rest on phase acceptance. You're not funding six months of work on faith, and we're not funding it either. Every fixed-scope project includes 30 days of post-launch fixes, so launch isn't the day support ends and problems become your problem alone. Invoices run Net 14. No surprise invoicing, no hourly overage line item you didn't see coming.

Who owns the code when it's done

You do. Outright, from day one. This isn't a license, and it isn't something we hold over you to keep the relationship going. The repos live in your organisation, not ours. The infrastructure runs in your own cloud account, not a shared environment we control.

If you ever want to walk away, you get a full handover: an architecture walkthrough, runbooks, and two weeks of support to make the transition real instead of theoretical.

When we say no

We turn down projects a specialist would do better, or that an existing product already solves for a tenth of the price. You'll hear that in the first call, not the third. If your quoting problem is a Salesforce configuration issue, we'll say so. Building custom software you don't need isn't a favor to anyone, including us.

What a pure web build doesn't cover

A web application engagement is a web application engagement. It doesn't include a mobile app for your field crews. That's its own build, on Swift, Kotlin, and React Native, from $60k over 12–22 weeks, because offline data handling and device management are a different set of problems. It doesn't include AI and automation work — document extraction, search over your own records, accuracy testing against real cases — which starts from $32k over 6–14 weeks. And it doesn't include what happens after launch: ongoing cloud, DevOps, and care is a separate arrangement, from $4.5k a month, cancel with 30 days' notice.

Software is never finished. We'd rather say that upfront than let a launch date imply otherwise.

NDAs and security questionnaires — handled before you ask

We work under NDA by default. We complete vendor security questionnaires as part of onboarding, not as a special accommodation for the client who happens to ask. For a company in healthcare, fintech, or insurance, that's usually the first real question in the room — we'd rather have it settled in week one than negotiated in week six.