Nobody quotes you a price upfront. Agencies speak in ranges so wide they're useless. So here's what custom software actually costs — phase by phase, with real numbers from real projects — and a break-even comparison to what you're already paying for SaaS that almost works.
If you searched "how much does custom software cost," you've already seen the answer: "It depends." Followed by a range so wide it covers a used car and a beach house.
That's not helpful. So let's be specific.
If you're still on the fence about whether to build at all, here's the business case for why companies are ditching SaaS for custom apps — the math before the costs. For the costs, keep reading.
For a focused business tool — something that replaces 2–4 SaaS subscriptions and automates a specific workflow — the realistic range is $8,000 to $20,000. That's a one-time cost. No monthly per-seat fees. No vendor lock-in. The code is yours.
For that range to mean something, you need to understand what's inside it.
Every custom software project has the same four phases. The costs vary based on complexity, but the structure is consistent.
This is where most projects fail before they start. A cheap discovery skips straight to code — and the first two months of development become expensive rework when requirements turn out to be wrong.
Good discovery covers: mapping your actual workflow (not the idealized version), identifying the 20% of features that do 80% of the work, and producing a spec document tight enough to get a real estimate from.
At FrictionKit, this is the Friction Audit — a half-day session that costs $500 and produces a written spec with cost estimates for your top 3 friction points. If you decide to build, the $500 applies toward your project.
Not visual design for its own sake — workflow design. How does a user move through the app? What does the data model look like? Where does the tool hand off to your existing systems?
For internal tools (used by your team, not the public), design costs are on the lower end. For client-facing tools where polish matters, expect higher. Either way, time spent here is paid back many times over in development speed.
This is the biggest line item and the biggest variable. What drives cost up:
What keeps cost down: a tight scope from Phase 1, focusing on the core workflow, and deferring "nice to have" features to a second version after you've validated the core.
Shipping to production, setting up hosting, documenting how to use and maintain it. This is often under-scoped and then rushed. Budget for it explicitly.
Ongoing hosting costs are typically $20–$100/month depending on traffic and infrastructure needs — orders of magnitude cheaper than per-seat SaaS.
See exactly where your SaaS stack is costing you.
✓ Check your inbox!
Here's what these phases add up to across two actual projects:
Real-Time Metal Quote Tool — built for a metal fabricator who was losing 2–3 days per quote to manual part nesting and pricing lookups. (See the case study →)
| Phase | What It Covered | Cost |
|---|---|---|
| Discovery | Friction Audit — workflow mapping, spec document | $500 |
| Design | Quote workflow, part library UX, pricing logic | $2,500 |
| Development | Auto-nesting engine, live metal price API, PDF quote generation | $8,500 |
| Deployment | Production hosting setup, team onboarding, docs | $750 |
| Total (one-time) | Quoting time cut from 2 days to <10 minutes | $12,250 |
AI Invoice & Effort Tracker — built for a dev agency replacing hours of manual timesheet categorization with an AI-powered dashboard. (See the case study →)
| Phase | What It Covered | Cost |
|---|---|---|
| Discovery | Friction Audit — timesheet flow, categorization rules | $500 |
| Design | Dashboard structure, AI tagging logic, data model | $3,000 |
| Development | AI line-item categorization, per-project P&L dashboard, CSV import | $7,500 |
| Deployment | Hosting, data migration from old tools, handoff docs | $500 |
| Total (one-time) | Eliminated ~8 hrs/week of manual categorization work | $11,500 |
The question isn't "is custom expensive?" It's "is custom expensive relative to what I'm already paying?"
Run the numbers for yourself:
For context: most SaaS stacks we audit run $800–$2,200/month. At $1,500/month ($18,000/year), a $12,000 custom build pays for itself in 8 months — then saves $17,640 every year after that.
By year 5, you've saved more than six times the build cost. That's not a rounding error. That's a real financial decision.
A client came to us paying $2,200/month across four tools that didn't talk to each other. Three years of SaaS subscriptions had cost them over $79,000 — for software they complained about every week. A custom replacement would have paid off in month 6. The math made us both uncomfortable.
Recognizing the point where SaaS stops making sense isn't always obvious. See 5 Signs Your Business Has Outgrown SaaS for the patterns that show up before the $79K surprise.
Even experienced buyers miss these:
Every "can we just add..." mid-project is expensive. A feature that takes 2 hours to describe takes 20 hours to build correctly. The fix is a tight spec before development starts — which is exactly what the Friction Audit produces.
Connecting to a third-party API sounds like a half-day task. In practice: authentication flows, rate limits, data format mismatches, error handling, and "we deprecated that endpoint last month" surprises. Budget integration work at 2–3x what you'd naively estimate.
You will see the first version and want to change things. This is normal and healthy. Budget for 1–2 rounds of revision after the initial delivery. Most good agencies include this; most clients don't ask.
Custom software doesn't break on its own — but the world around it changes. Dependencies update. APIs change. Business rules evolve. Budget $500–$2,000/year for maintenance, or keep an ongoing relationship with your builder. The alternative is paying for rewrites every few years.
Custom isn't always the right answer. Don't build custom if:
Custom software makes sense when your workflow is stable, your current tools are fighting you, and the math on fees vs. build cost favors building. For a quick way to see what your entire SaaS stack actually costs, the real cost of your SaaS stack breaks down typical spend by company size — with the exact framework for running the replacement math yourself.
If you're not sure which camp you're in, the Friction Audit answers that question directly — with numbers, not opinions.
Every legitimate software shop quotes based on scope. Scope requires a spec. A spec requires discovery.
Anyone who gives you a confident number after a 20-minute call either:
The honest path: start with a defined discovery process. Learn what you actually need before you commit to building it. The $500 Friction Audit is that process for us — and it's the only way we quote projects accurately.
After the audit, you'll have:
If the math doesn't work, we'll tell you. We'd rather lose a project than build something that doesn't pay off for you.
See exactly where your SaaS stack is costing you.
✓ Check your inbox!
Related Reading
Half a day to map your workflow, identify your top 3 friction points, and get a real cost estimate for fixing each one. If custom software makes financial sense for you, we'll tell you exactly what it costs and why. If it doesn't, we'll tell you that too.