You have an idea for an app or a system that will take the manual work off people — and the first question is "how much?". You search, you get a range from 20k to 500k, and you close the tab none the wiser. Because the price of custom software doesn't come from a price list — it comes from your scope, your integrations, and who runs the system two years from now. Here's what it really depends on, and how not to overpay or get stuck with the cheapest bidder.
The price of custom software isn't a line on a price list — it comes from scope, integrations and upkeep. Anyone who quotes a figure before knowing your process is guessing.
The biggest cost isn't on the build invoice. It's the cost of technical debt left by the cheapest bidder: a rewrite from scratch when the project stalls or no one will touch it.
The price is pushed up by what a demo doesn't show: integrations (payments, messaging, AI, external systems), scale, and whether anyone will maintain the system afterwards.
"Cheap and by yesterday" usually ends in two quotes: the build, then the fix after someone else. An honest estimate starts with questions about your process.
The real question isn't "how much does an app cost" — it's "what does the risk of it stalling or going down cost me" — and what a scope closed once, properly, is worth.
Let's be honest up front: no one credible will quote you the price of custom software from a one-line description. It's a bit like asking "how much is a house" — depends whether it's a studio flat or a warehouse with industrial fit-out. The "20k to 500k" range you'll find online is true and useless at the same time.
The price comes from three things that usually aren't on paper yet at the start: scope (what exactly the system has to do), integrations (what it has to connect to) and upkeep (who runs it as it grows or the law changes). A software house that quotes a figure before asking about these is either guessing, or selling you the lowest number to hook you — and topping it up later.
So instead of a price list, we'll give you something more useful: a map of what actually pushes the price up and down. With it, you can judge any quote yourself — and spot the one that looks suspiciously cheap.
Break it into the four levers that actually move a quote:
An honest estimate starts with a conversation about those four things, not with a number. Once we know them, we give a concrete figure for your scope — not a range plucked from the ceiling. See how it comes together in finished systems: our case studies.
| An honest estimate | The cheapest quote | |
|---|---|---|
| Starting point | Questions about your process and scope | A figure after one email |
| Integrations | Priced up front, with the risk | "We'll manage it somehow", added later |
| Upkeep | In the plan from day one | Not in the quote |
| Scope | A closed first stage | An open "let's add more" list |
| A year on | You extend the system | You pay again — for the fix |
| What you buy | A closed problem | The lowest number up front |
For a real estate business we built a full CRM from scratch — with a buyer portal (ClientPortal) and the integrations that make the difference in both price and behaviour: payments (Stripe), messaging (Twilio, WhatsApp, Gmail/Outlook), webhooks and AI (OpenAI, e.g. listing translation). We've developed it continuously since 2022. It wasn't a one-off rollout — it's a system that grows with the business. And because Tesoro is our own product, we run it with our own skin in the game.
“The cheapest quote is usually two quotes: one to build it, one to fix it after someone else. An honest estimate costs more on paper and less in reality.”
As much as the scope, integrations and upkeep add up to — not a price list. A credible supplier quotes only after talking through what the system has to do and connect to. The "from–to" ranges online are true and useless at once; we give a concrete figure for your scope after a conversation about the process.
Same logic: scope (how many screens, roles, rules) and integrations (payments, messaging, AI, external systems) decide it — not whether the app is mobile or web. Don't mistake a range for an estimate; an estimate starts with your process.
It depends on scope, but we rarely build "everything at once". We stage it: first the version that pays back fastest in practice, then development. That keeps the project from dragging on, and you see a result before you spend the whole budget.
Because they measure different things. The cheapest usually leaves out integrations and upkeep, or guesses the scope — and tops it up later. Often the lowest number up front means a second bill: fixing someone else's technical debt.
Yes, if your process is standard and a boxed tool handles it — then buy the box; custom will only burn budget. Custom software only pays off once the process is your edge, or when nothing ties together what you already have. We wrote about how to decide that in what a software house is.
An app, a portal or one hard integration with a clear scope. We'll ask the right questions and price the concrete thing — no ceiling-plucked ranges and no open-ended "let's add more".
Get your scope pricedA WMS, a SAP integration, a document flow — something your operations depend on. Let's talk through the process and the cost of risk before a number lands.
Let's talk about your process
