Most custom web app projects for small and medium businesses land between $30,000 and $100,000 — but that range is wide for real, specific reasons, and the honest answer to "what will mine cost" depends entirely on what you're building. This guide breaks down what actually drives the price so you can estimate your own project realistically before you ever talk to an agency.

I'm David Campbell, founder of Nerd Stack. We build custom web apps for businesses, and the question we get first is always about cost — usually framed as "ballpark, what am I looking at?" This is the honest version of that answer: the realistic ranges, the five factors that move the number, the pricing models, and the line items most people forget to budget for.

The Honest Answer: The Realistic SMB Range

Published industry data lines up closely with what we see in practice:

So for a typical SMB custom web app — a focused tool that solves one real workflow well — budget $30,000–$100,000. Simple, tightly-scoped tools can come in lower. Complex platforms with many integrations, real-time features, and sophisticated permissions push higher. The rest of this post is about understanding where in that range your project lands.

What Actually Drives the Price: 5 Factors

1. Scope — How Much You're Building

The single biggest cost driver, and the one most under your control. A custom web app that does one workflow exceptionally well costs a fraction of an all-in-one platform that tries to do everything. Scope is also the biggest predictor of whether the project succeeds at all — small, focused builds succeed dramatically more often than sprawling ones. Tight scope saves you money twice: lower cost and lower risk.

2. Integrations

Every external system your app needs to talk to — payment processors, CRMs, email platforms, accounting tools, third-party APIs — is real engineering work. One or two clean integrations are routine. A web app that needs to sync deeply with five other systems is a meaningfully bigger project, because each integration has its own quirks, edge cases, and maintenance burden.

3. User Authentication and Roles

"Users can log in" sounds simple and rarely is. The cost scales with complexity: a single user type with basic login is straightforward. Multiple roles with different permissions, an admin tier, role-based access to specific data and documents, audit logging — that's a substantial portion of many custom builds. When we built Reichelt Capital's private client portal, role-based access to confidential documents and conversations was a major part of the engineering, because for a private investment firm, getting permissions exactly right isn't optional.

4. Custom Admin Tooling

The part clients consistently underestimate. The user-facing side of a web app is only half the build — the other half is the admin panel the operator uses to actually run it. A generic admin is cheap; an admin built around how the operator actually works is more expensive and almost always worth it. The Razz Golf platform's 100% custom admin panel — bulk registration management, flight assignment, partner-course coordination, score entry — was a significant share of that build, because the entire point was an admin that fit the operator's real workflow rather than forcing them onto a generic one.

5. Real-Time and Advanced Features

Real-time updates, live collaboration, notifications, complex search, data visualization, file handling at scale — these are all achievable, and they all add cost. Each "it should just update live" or "users should be able to collaborate simultaneously" is an engineering decision with a price tag. None are dealbreakers; they just need to be budgeted honestly.

Pricing Models: Fixed, Hourly, and Phased

  • Fixed price. One number for a defined scope. Best when the scope is genuinely clear and stable. The risk: anything not in the original spec becomes a change order, so a too-loose spec leads to friction.
  • Hourly / time-and-materials. You pay for the work as it happens at the agency's hourly rate ($100–$250/hr in North America). Best when scope is genuinely uncertain or exploratory. The risk: less cost predictability.
  • Phased. The approach we recommend for most SMB custom builds. The project is broken into phases — each phase has a defined scope and price, ships something real, and informs the next. You get cost predictability per phase, the ability to course-correct between phases, and the option to stop if a phase proves the concept doesn't need to go further. Phased pricing is also how you de-risk: it forces small scope.

The Hidden Line Items

The build cost is not the total cost. Budget for these from the start so they're not surprises:

  • Ongoing maintenance: budget 15–20% of the build cost per year. Software needs security patches, dependency updates, bug fixes, and adjustments as the business evolves. This is not optional — an unmaintained custom app degrades.
  • Hosting and infrastructure: a monthly cost that scales with usage. Modest for most SMB apps, but real.
  • Iteration: the first version is never the final version. The best custom apps evolve as you learn how people actually use them. Budget for a second and third round of improvements after launch.
  • Third-party service costs: the APIs and services your app depends on (email delivery, payment processing, etc.) often carry their own usage-based fees.

The Nerd Stack Project Process

For context on what you're actually buying, here's how a custom web app project runs with us:

  • Discovery: we map the workflow that's actually breaking — how work moves today, where the friction is, what the software needs to do. This phase defines scope, and scope defines cost.
  • Scoping and estimate: a phased plan with defined scope and price per phase. You see exactly what each phase delivers.
  • Build, phase by phase: each phase ships something real and usable, with the actual users involved throughout.
  • Launch and iterate: the core ships, then we refine based on how it's actually used.
  • Ongoing maintenance partnership: security, updates, performance, and new features as the business evolves.

It's the same disciplined, scoped approach we used on Hey Eduardo — a privacy-first AI desktop product where the client chose a focused custom build over a generic approach — and on the Razz Golf and Reichelt Capital platforms.

How to Get an Accurate Estimate

The estimates that come back vague and enormous are usually a response to a vague request. To get an accurate, actionable estimate:

  • Describe the workflow, not the features. "Here's how this process works today and where it breaks" gives an agency far more to estimate against than a feature wishlist.
  • Identify your true must-haves vs. nice-to-haves. A clear priority list lets an agency scope a realistic phase one instead of pricing everything at once.
  • Share your real budget range. It's not a negotiation tactic — it lets a good agency scope to your budget, building the highest-value phase one within it rather than guessing.
  • Ask for a phased proposal. A phased plan is itself a sign the agency is thinking about de-risking your project, not just maximizing the contract.

Be wary of any estimate built from a feature list with no discovery — and of any agency that doesn't ask hard questions about scope before quoting. Founders who scope to a validated need succeed; CB Insights found that 35-42% of startups fail from building something there was no real need for. The same discipline applies to a custom internal tool: build for the validated workflow, not the imagined one.

Frequently Asked Questions

How much does it cost to build a custom web app?

Most custom web app projects for small and medium businesses fall between $30,000 and $100,000, with roughly 66% of custom software projects landing in that range per GoodFirms. Clutch puts the broader average at $50,000–$250,000. Simple, tightly-scoped tools can come in lower; complex platforms with many integrations and advanced features push higher. The biggest variable is scope.

What makes custom software cost more or less?

Five main factors: scope (how much you're building — the biggest driver), integrations (every external system your app must connect to), user authentication and roles (multiple permission tiers cost more than basic login), custom admin tooling (the operator-facing side is often half the build), and real-time or advanced features (live updates, collaboration, complex search). Tight scope is the single most effective way to control cost.

What's the best pricing model for a custom software project?

For most SMB custom builds, phased pricing — the project is broken into phases, each with a defined scope and price, each shipping something real. It gives you cost predictability per phase, the ability to course-correct, and the option to stop early if a phase proves the rest isn't needed. Fixed price works when scope is genuinely stable; hourly works when scope is exploratory.

What ongoing costs come after a custom web app is built?

Budget 15-20% of the build cost per year for maintenance (security patches, updates, bug fixes, evolution). Add hosting and infrastructure (scales with usage), iteration costs (the first version is never the last), and any third-party service fees (email delivery, payment processing, APIs). The build cost is not the total cost — plan for these from the start.

How long does it take to build a custom web app?

It varies with scope, but a focused, well-scoped SMB custom web app typically takes a few months from discovery to a usable launch, built in phases. Sprawling all-in-one platforms take much longer and fail far more often — which is why scoping small and building in phases is both cheaper and more likely to succeed.

How do I get an accurate quote for custom software?

Describe the workflow that's breaking, not a feature list. Separate true must-haves from nice-to-haves. Share your real budget range so the agency can scope to it. And ask for a phased proposal — it signals the agency is thinking about de-risking your project. Be wary of any large estimate produced without a real discovery conversation.

Bottom Line

A custom web app for an SMB realistically costs $30,000–$100,000, driven mostly by scope — and scope is the variable you control. Build the one workflow that's actually breaking, phase the project, budget for the maintenance and iteration that come after launch, and you have a predictable, de-risked investment in software that fits your business instead of the other way around.

If you want a real estimate for your specific project, book a free call — or read more about our custom web app service and how we scope and phase a build. We'll do the discovery to understand the workflow, then give you a phased proposal with honest numbers — and if a custom build isn't the right call for your situation, we'll tell you that too. To see what custom builds look like in practice, our case study portfolio includes Razz Golf (custom tournament platform and admin), Reichelt Capital (private client portal), and Hey Eduardo (privacy-first AI product).

Still deciding whether to build at all? Start with our guides on the signs your business has outgrown off-the-shelf software and custom software vs. off-the-shelf.

Sources: GoodFirms — Custom Software Development Cost Survey; Clutch — Software Development Pricing Guide; Clutch — Web Development Pricing Guide; CB Insights — Why Startups Fail.