How much does custom software cost?

How much does custom software cost? Rough ranges

These are rough, typical ranges for agency-built software in the US. They vary widely by region, team, quality bar and scope, so treat them as a way to sense-check a quote, not as a price list.

• Small internal tool, roughly $15,000 to $50,000: one team, a handful of screens, a simple database, maybe one integration. Think a job tracker, an intake form with an admin view, or a replacement for a shared spreadsheet.
• Mid-size web app, roughly $50,000 to $150,000: several user roles, a customer-facing side, payments or a portal, reporting and a few integrations with tools like accounting or email.
• Complex platform, $150,000 to $500,000 or more: many user types, heavy business rules, mobile apps alongside the web app, compliance requirements, large data volumes or real-time features.

What drives the cost up or down

Software is priced by effort, and effort comes from a short list of things. Knowing them lets you trim a quote without gutting the project.

• Number of features and screens. Every screen has to be designed, built, tested and maintained.
• Business rules. Approvals, pricing logic, scheduling constraints and exceptions take far more time than simple data entry.
• User roles and permissions. Each extra type of user (staff, managers, clients, vendors) multiplies the paths to build and test.
• Integrations. Connecting to accounting, payment, CRM or industry systems depends on how good their APIs are, and some are painful.
• Data migration. Moving years of messy records from spreadsheets or an old system takes real work to clean and check.
• Platforms. A web app alone costs less than a web app plus iOS and Android apps.
• Compliance and security. Health, financial or legal data adds audit trails, access controls and review time.
• Design polish. A clean internal tool costs less than a customer-facing product that has to look and feel premium.

The hidden costs after launch

The build quote is rarely the full cost. Budget for these from day one so the software does not stall a few months after launch:

• Hosting and infrastructure: servers, databases, file storage, backups and monitoring, billed monthly and growing with usage.
• Maintenance: security updates, library upgrades and fixes as browsers, phones and third-party APIs change. A common rule of thumb is to budget a meaningful share of the original build cost every year.
• Changes and new features: your process will change, and every change after the project closes is usually billed as new work.
• Third-party services: email and text sending, maps, payments, e-signature and AI services usually charge per use or per month.
• App store fees if you ship mobile apps: Apple and Google both charge developer account fees and take a commission on certain in-app sales.
• Your own time: someone on your team has to answer questions, review work and test. That time is real, especially during discovery.

How to estimate your project before you talk to anyone

1. Write down the problemOne paragraph on what is broken today and what it costs you in hours, errors or lost sales.
2. List the usersEvery type of person who will log in, and what each one needs to do.
3. List the must-havesOnly what you need to launch. Put everything else on a later list.
4. Note every system it must connect toAccounting, payments, email, your website, industry tools. Integrations are a big cost driver.
5. Gather your dataFind out where the existing records live and how clean they are.
6. Compare against the ranges abovePlace your project in a size band, then add hosting, maintenance and changes for at least three years.

Getting an accurate quote

Two quotes for the same idea can differ by a factor of five, usually because each vendor imagined a different project. The fix is to hand every vendor the same written brief (your problem, users, must-haves, integrations and data) and ask them to price the same scope. Ask what is included: design, testing, project management, hosting, and how changes after launch are billed. Be wary of any firm price given before anyone has asked how your business works.

If you do not have a brief yet, our guides to the software development process and to writing a requirements document walk through it.

Upfront project fee vs. a monthly plan

The traditional model is a large project fee paid in stages, then hosting and change requests billed separately afterward. It works well when the scope is fixed and you have the cash on hand, but it front-loads the risk, and the software often freezes once the budget runs out.

Zoti also works on a monthly model. Custom projects start at $499/month, covering design, development, hosting and ongoing changes, with a written quote before any work starts. That spreads the cost, keeps the same team improving the software after launch, and makes the long-run cost easier to see. For businesses that prefer a single project, Zoti also offers one-off builds with a deposit and milestones. Whichever model you pick, compare the total cost over three years, not just the first invoice.