Ask most software agencies what a project costs and you’ll get “it depends — book a call.” That’s not wrong, but it’s not helpful either. So here are the actual ranges, what pushes projects toward the top or bottom of them, and how to keep your project from wandering upward.
The short answer
For small and mid-size businesses, most custom software projects land in these ranges:
- Workflow automation or integration: $3,000 – $15,000. Connecting your existing tools, eliminating a manual process, automating reports or data entry. The fastest payback of anything on this list.
- Internal tool: $8,000 – $30,000. A quoting tool, scheduling board, admin panel, or job tracker — one app that replaces a spreadsheet jungle.
- Customer-facing web application: $15,000 – $60,000. A client portal, booking system, or the app your customers log into. The polish customers expect adds cost.
- Mobile app: $20,000 – $75,000+. Cross-platform (one codebase for iPhone and Android) sits at the lower half; fully native development roughly doubles it.
- Full software product (something you’ll sell): $50,000+ to launch a solid version 1, and ongoing investment after.
If a quote comes in wildly below these ranges, ask what’s missing — usually it’s testing, or the part where you own the code, or the developer’s availability after launch.
What actually drives the price
Software cost is mostly people-hours times complexity. Five things move the needle more than anything else:
1. Number of screens and roles. An app where everyone sees the same thing is cheap. An app with admin views, customer views, and manager approvals is three apps wearing a trench coat.
2. Integrations. Every system your software must talk to — accounting, CRM, payment processing — adds work. Well-documented modern tools (Stripe, QuickBooks Online) integrate cheaply; legacy systems with no API integrate expensively.
3. Custom design vs. clean-and-standard. Internal tools can use proven, standard interfaces and save real money. Customer-facing products justify design spend.
4. The unglamorous 30%. Login and security, error handling, testing, deployment. Every real project carries this overhead; quotes that ignore it become change orders later.
5. Scope creep. The biggest budget-killer isn’t the estimate being wrong — it’s the project quietly growing. “While you’re in there, could it also…” is how $20k projects become $45k projects.
How to keep the cost down (without getting junk)
- Start with version 1, not version perfect. Launch the 20% of features that deliver 80% of the value. Real usage will tell you what to build next — and it’s rarely what you’d have guessed.
- Fix the scope in writing. A fixed-scope, fixed-price agreement moves the estimating risk onto the developer, where it belongs. (This is how we work, and it’s why our quotes take a little longer to prepare — we’d rather sweat before signing than invoice surprises after.)
- Consider whether you need custom at all. Sometimes a $50/month off-the-shelf tool covers 90% of the need. A good developer will tell you so and lose the sale. We’ve done it; the referrals that follow are worth more than the project was.
- Ask about the total cost of ownership. Hosting, maintenance, and updates typically run 15–20% of the build cost per year. Anyone who quotes a build price without mentioning this is leaving out a chapter.
The comparison worth making
A $12,000 automation that saves one employee five hours a week returns roughly 250 hours a year — it pays for itself in under twelve months, then keeps paying. Meanwhile, the SaaS subscriptions it replaces or the hire it delays never stop billing you. Custom software isn’t cheap; the honest question is what the manual status quo costs, because that number is rarely zero.
Get a real number for your project
Ranges are useful; a quote is better. Describe your project in two sentences — we’ll tell you what it takes, honestly, within 24 hours. If the honest answer is “you don’t need custom software for this,” you’ll get that answer free of charge.