What a Web Development Company Actually Does (And When You Don't Need One)

Two people type "web development company" into Google in the same hour. One wants a new marketing site with a nicer hero image. The other is staring at a spreadsheet with fourteen tabs, three macros nobody remembers writing, and a dispatch board held together by copy-paste. They're done. This piece is for the second person.

If you're trying to replace the spreadsheet everyone secretly runs the business on — the quoting tool, the intake form, the nightly reconciliation one person does by hand — you're not shopping for a website agency. You're shopping for something closer to a software vendor. The work looks different depending on your industry. The buying decision doesn't.

The actual range of work under that name

For this kind of buyer, "web development company" usually breaks into six real categories. A decent vendor tells you which one you need instead of selling you all six.

Custom web applications — portals, dashboards, workflow tools finance and ops teams live in all day. React, Node, Postgres. Typically 10–20 weeks, from $45k. (details)

Mobile apps — iOS and Android for field crews, technicians and customers, built offline-first so a bad signal doesn't cost a day's work. Swift, Kotlin, React Native. Typically 12–22 weeks, from $60k. (details)

CRMs and internal tools — quoting, dispatch, scheduling, invoicing into your accounting package. Typically 8–18 weeks, from $38k. (details)

AI and automation — document and email extraction, search over your own documents, with accuracy testing and a human review step built in, not assumed. Typically 6–14 weeks, from $32k. (details)

Integrations and data — two-way sync with retry and reconciliation, including legacy systems that were never built with an API. Typically 4–10 weeks, from $22k. (details)

Cloud, DevOps and care — infrastructure as code, running in your own AWS account. Ongoing, from $4.5k a month. (details)

Where the work stops

We turn work away. We say so on the first call, not the third. Two reasons cover almost all of it. First, a specialist would do it better, and we'd rather tell you that than take the fee. Second, an off-the-shelf product already solves the problem for a tenth of the price. If your quoting process is unusual enough to need a custom build, that's real work. If it's a standard workflow an existing product already handles, paying us for it is a way to overpay for something you could subscribe to this afternoon.

How the engagement actually starts

We don't quote off a sales call. We run a discovery week — flat $4,800, credited back in full if you continue with us — and it ends in three things: a written scope, an architecture sketch, and a fixed estimate.

Most vendors give you a number before they understand your data, your integrations, or the one legacy system nobody wants to touch. Then they spend the project renegotiating it. We think estimates should come after discovery, not before. It's the only way the number holds.

What happens if the estimate turns out to be wrong

The prices above are starting points, not final quotes. Discovery is what locks the real number for your project. Once it's locked, scope changes get priced before the work starts, not slipped into an invoice after.

A fixed-scope project runs from $28k per phase, billed 30% at kickoff and the rest on phase acceptance, and includes 30 days of post-launch fixes. If something changes mid-phase, you get a price for the change before we touch anything.

Who owns the code

You own the code, from day one. The repos live in your organization's account. The infrastructure runs in your own cloud account. That's a deliberate choice against vendor lock-in. If we disappeared tomorrow, you'd still have the keys.

Who's actually on the project

We work alongside in-house teams — that's normal. What determines whether a project goes well isn't headcount, it's continuity: a named lead stays with your project from the scoping call through launch. No handoff to whoever's free that sprint.

For work that runs longer or needs sustained capacity alongside your team, there's a dedicated squad option — one designer, two engineers, one lead — from $18k a month, billed monthly in advance, on rolling three-month terms.

Boring technology, on purpose

React, Node, Postgres for web apps. Swift, Kotlin, React Native for mobile. AWS and CI/CD underneath. None of that is exciting. Novelty is a cost paid every year after launch, by the client, not the vendor. We'd rather ship something a competent engineer can maintain in five years than something that looked clever in the demo.

NDAs and security review

We sign NDAs by default and complete vendor security questionnaires as part of onboarding. We're not going to claim a formal certification we don't hold. What we will do is answer the questionnaire honestly and put the access controls in place the review actually asks for.

How the bill actually works

Three shapes. Fixed-scope: 30% at kickoff, the rest on phase acceptance. Dedicated squad: from $18k a month, billed monthly in advance, rolling three-month terms. Care and improvement: from $4.5k a month, cancel with 30 days' notice. Everything runs Net 14.

We don't take equity and we don't defer payment. It muddies the relationship, and it has never once made the software better. Cash, milestones, clear scope.

Software is never finished

A launch isn't a finish line. Cloud, DevOps and care runs from $4.5k a month, ongoing, and covers uptime monitoring with a named on-call person, monthly dependency and security patching, and, when needed, rescue work on a codebase someone else left in bad shape. We treat this as part of the product, not a line item sold after the fact. See pricing for how it fits with everything above.

Can you start small

Yes. That's what discovery week is for. $4,800, low commitment, and it tells you what the real project looks like before either of us commits to more. We work remote-first. The spreadsheet doesn't care where you're located.