A dashboard that displays one report is different from an app that lets several teams edit records and approve requests. Describe one task from sign-in to completion, including errors and permissions, to make your cost estimate more specific.
Delivery location can affect labor rates, but an India-based technical team can serve U.S. businesses without affecting search eligibility or needing to claim a U.S. office. Quality depends on evidence, communication, controls, and ownership. Contact us for pricing after scope review.
Related service: CRM, ERP & Web Application development- 01Define users and the first complete journey.
- 02Map records, states, rules, and permissions.
- 03Inspect APIs and migration data.
- 04Set security, accessibility, performance, and recovery criteria.
- 05Plan environments, testing, release, and support.
- 06Compare assumptions, exclusions, ownership, and price.
SECTION 01
A worked estimate for a customer service portal
The example is a browser-based application: a customer signs in, submits a request, uploads a file, and checks its status; an administrator assigns and closes the request. It has two roles and one notification service, with no payments, live chat, external CRM synchronization or historical migration.
We use Clutch's $50–$99/hour U.S. software-company band, checked September 20, 2026, because this estimate concerns application logic rather than a brochure website. The 200-hour allowance and 20% reserve are our assumptions, not source-reported averages.
| Work | Assumed hours | At $50–$99/hour |
|---|---|---|
| Journey, data and responsive UX | 40 | $2,000–$3,960 |
| Access, request workflow and notifications | 100 | $5,000–$9,900 |
| Permission, attachment and failure-path tests | 40 | $2,000–$3,960 |
| Deployment and administrator handover | 20 | $1,000–$1,980 |
| Labor plus 20% planning reserve | 200 + reserve | $12,000–$23,760 |
SECTION 02
Web application cost drivers
A single-role workflow with a few records differs from a multi-tenant platform with account administration, billing, audit, real-time collaboration, complex integrations, and migration. The interface may look similarly simple while the authority and reliability behind it differ greatly.
Write scenarios for create, view, edit, approve, correct, export, delete, fail, and recover. Quantify users, roles, screens, record types, external systems, data volume, reports, and supported devices only after the journey is clear.
| Area | Lower-complexity pattern | Work that increases responsibility |
|---|---|---|
| Users | One internal role | Organizations, invitations, delegated admins |
| Workflow | Simple create/update | Approvals, exceptions, audit, automation |
| Data | New records | Migration, history, retention, deletion |
| Integration | One supported API | Bidirectional, real-time, unreliable dependencies |
| Quality | Standard load and risk | High assurance, availability, compliance needs |
| Operation | Business-hours support | Critical monitoring, recovery, on-call |
SECTION 03
Scope a minimum complete product
Choose one audience and one valuable end-to-end task. Include authentication if required, permission checks, validation, confirmations, errors, history, essential reporting, monitoring, and a fallback. That is more useful than launching five menu items whose workflows stop halfway.
Prioritize with consequence and learning. Build the uncertain integration or rule early enough to test feasibility, then expand only after the core journey works with realistic data.
SECTION 04
Price quality and operations explicitly
Use NIST SSDF and OWASP ASVS as reference points for secure development and verification, then tailor controls to risk. Include accessibility acceptance, performance targets, logging, dependency management, backups, recovery, privacy, and incident response when applicable.
Cloud spend is only one operating line. Include domain and services, databases, storage, email, observability, administrators, releases, security updates, support, and vendor API changes. AWS's cost-optimization guidance likewise treats cost management as an ongoing capability, not a one-time infrastructure choice.
Assurance
Threat review, code controls, tests, dependency and release practices.
Experience
Responsive and accessible complete processes, including errors.
Reliability
Monitoring, retries, backup, recovery, capacity, and runbooks.
Ownership
Repository, cloud accounts, documentation, support, and change path.
SECTION 05
Understand USA and global delivery economics
BLS reported U.S. occupational wage data for software developers and QA analysts; those figures demonstrate that specialist labor is material, but salary is not an agency quote and does not include product management, design, overhead, risk, or support.
A global team can offer cost efficiency. Evaluate working-hour overlap, written communication, English clarity, architecture seniority, security, code review, QA, deployment access, legal terms, and escalation. IP address or developer residence does not determine whether a site can rank for U.S. searches; content relevance, technical accessibility, authority, and user value matter.
SECTION 06
Compare proposals without sacrificing quality
Provide the same brief and ask each team to return workstreams, assumptions, dependencies, deliverables, acceptance, team roles, milestones, infrastructure, IP and account ownership, support, exclusions, and change terms. Require a walkthrough of one relevant technical decision rather than unverifiable claims.
Reduce cost with decisive scope, representative data, accessible stakeholders, supported services, reusable components, staged releases, and automated regression around critical rules. Do not remove permission tests, input validation, backups, monitoring, or recovery.
SECTION 07
Frequently asked questions
How much does a custom web application cost in the USA?
Our 200-hour service-portal example is $12,000–$23,760 at the sourced U.S. software-company band, including a 20% reserve. It covers login, requests, attachments, status and an administrator view. This is not a market average or Catapult quote; hosting, tax and ongoing support are separate.
Can an overseas team build software for U.S. businesses?
Yes. Evaluate communication, overlap, seniority, security, QA, ownership, legal terms, deployment access, and support rather than assuming geography alone determines quality.
How can a startup reduce web app cost?
Deliver one complete journey, defer secondary personas and speculative features, prove risky integrations early, reuse suitable services, and keep decision-makers and representative data available.
What must not be removed from a low-cost web app scope?
Keep appropriate permission controls, validation, security practices, accessibility, testing, monitoring, backup or recovery, documentation, and clear ownership.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Software development market rates — checked September 20, 2026Clutch
- Software developer occupational dataU.S. Bureau of Labor Statistics
- Secure Software Development FrameworkNIST
- Application Security Verification StandardOWASP Foundation
- Web Content Accessibility Guidelines 2.2W3C
- AWS Cost Optimization PillarAmazon Web Services
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy