In 2026, a production custom app for a small business — dashboards, workflows, roles, integrations, web and mobile — runs from $12,000 fixed when built AI-accelerated by a small senior team. Comparable agency quotes typically land between $50,000 and $250,000. The difference isn't quality. It's headcount you never meet, hourly incentives, and risk padding — all billed to you.
Where the money actually goes
Every custom build, anywhere, is made of the same six pieces. What varies is how much each one costs to produce:
- Scoping and design decisions — understanding the business, choosing what not to build. Senior judgment; can't be automated; shouldn't be long.
- The visible app — screens, forms, tables, flows. High volume, low novelty. This is where AI collapsed the cost most.
- The business logic — the rules that make it your app: how quotes get approved, how stock moves, who sees what. Medium volume, all judgment.
- Integrations — payments, email, accounting, whatever you already run. Cheap when the counterpart API is good, expensive when it's a 2009 SOAP service.
- The unglamorous 20% — auth, roles, edge cases, error states, deploy pipelines, backups. Invisible in demos, mandatory in production.
- Coordination — decisions moving between people. In a two-builder team this is a conversation. In an agency it's a department.
Notice which pieces got cheaper since AI entered the loop: the visible app, the test coverage, the scaffolding — the volume. And which didn't: judgment, integration archaeology, taste. Our stack post covers exactly how that split works in practice.
Why agency quotes run 5×
When an agency quotes $75,000 for what we'd build at $12,000–$18,000, the delta is rarely the code. It's structural:
- Layers of people between you and the builder. Account manager, project manager, delivery lead, QA coordinator. Each is a salary on your invoice and a relay hop for every decision. None of them write code.
- Hourly billing rewards slowness. When revenue = hours × rate, efficiency is a business problem. Nobody at an hourly shop is incentivized to make the build take three weeks instead of twelve. We wrote a whole post on this.
- Risk padding, priced in silently. Vague scope means the quote carries a 30–50% buffer for the unknowns. You pay the buffer whether or not the risk lands.
- The offshore markup chain. Plenty of agencies sell senior local faces and deliver offshore delivery teams. You pay onshore prices for offshore code plus a coordination tax in both directions.
- Pre-AI cost structures. Many shops still price as if every form and every test were typed by hand, because their delivery process still works that way. Their cost basis is their problem; their quote makes it yours.
Real numbers
Ours are public, because fixed and public is the point:
| Build | Price | Timeline |
|---|---|---|
| Prototype Sprint — deployed, clickable, real code | $3,500 fixed | 1 week |
| Online Store — checkout, variants, admin | from $6,000 | 1–2 weeks |
| Custom App / Internal Tool — web + iOS & Android | from $12,000 | 2–4 weeks |
| Operations System — inventory, orders, logistics | from $12,000 | 2–5 weeks |
Every price includes the unglamorous 20%, deployment, and handover — full package details here. 50% starts the build, the balance is due when it ships, and you own the code, the accounts and the keys outright.
How to read any software quote
Whoever you hire — us or anyone — these five questions expose most of the padding:
- "Who exactly builds this, and can I talk to them?" If the answer is a delivery team you'll never meet, the quote includes a coordination department.
- "Is the price fixed, and what happens if you're wrong?" Hourly with an estimate isn't a price, it's an opening bid.
- "What's explicitly out of scope?" A quote without exclusions is a quote that hasn't been thought through — the buffer is hiding somewhere.
- "Do I own everything at the end?" Code, repo, cloud accounts, domain. Anything the vendor keeps is leverage for the next negotiation.
- "What does 'done' mean?" Deployed to production with real data, or 'feature-complete in staging'? The gap between those two phrases is where projects go to die.
The bottom line
Custom software stopped being an enterprise-only purchase. The build cost collapsed; most quotes just haven't caught up. If the numbers you've been hearing are five figures deep and measured in quarters, get a second number — or first check whether you should build at all.