Article
How much does custom software cost? A practical guide
How much does custom software cost? Understand bespoke software cost, what shapes a written quote and why a first version starts with a clear scope.
Published 29 October 2026Updated 17 November 20268 min readCustom softwareMVPSmall business
How much does custom software cost? It depends on what the first version needs to do, the data it handles and the software it connects to. First we'll understand the problem, then I'll send you a written quote.
What affects the quote
- The tasks the tool needs to support and which features are actually needed to start.
- The data that needs to be imported, organised or kept up to date.
- The existing business systems the software needs to exchange information with.
- The people who will use the workflow and the steps that are still manual today.
You might need simple business software, an internal tool or a connection between programs. Before I write code, I'll send you a clear list of what I'll do and what I won't.
How I estimate the work and why I leave room
I start from the time I expect to spend on the project. I do not count development alone: I need to gather information and understand how you work. You do not have to arrive with everything ready. Some information emerges while we build the tool, so timelines carry some uncertainty. I leave reasonable room in the quote for these points and for unexpected issues.
I do not want to come back asking you for an extra payment for every detail that emerges during development. The scope remains what we agreed; it does not become a promise of unlimited changes. If we deliver on time without changes, the quote still has value: it supports the quality of the work and the flexibility to adapt it. That is what I want to cover, not just time spent writing code.
When I choose a subscription rather than a project
Sometimes you do not just need a program built. You want someone you trust to follow technical matters: assess a feature, compare tools, research the market to see whether a solution is suitable. These activities take effort even without development. They come at different moments, not all together when you ask for a quote.
In those cases we can choose a subscription that includes my availability for your matters. You use it according to the needs of the work, with a clear limit: one task and one commitment at a time. That keeps a project with a defined scope separate from ongoing support. They are two different ways of working, chosen according to what you need.
Start with an MVP
MVP means minimum viable product: the first version someone can use. It doesn't mean rushing. We start with the features that matter and leave the rest for later.
To decide whether a process change is enough or dedicated software is needed, start with the people doing the work, the data and the tools already involved. Sometimes a spreadsheet only needs organising; in other cases the existing tools do not cover the process.
The price published on this site
Custom software development is quoted after the call. The published price belongs to a different service: the fractional CTO retainer starts at €2,000 per month. I do not use that retainer as the price of a software project.
A software quote defines the included work, timeline, steps and payments. See the custom software service and bring the process you want to simplify to a call.
Off-the-shelf or bespoke software: comparing the full cost
Before estimating what to build, ask whether anything needs building. An existing product may cover the task; in other cases the need lies in a missing connection between tools already in use. Comparing a product purchase price with a development quote is not enough. Understand what people still need to do: enter data, check it and move it between places. Start with that journey rather than the label off-the-shelf or bespoke.
An internal spreadsheet tool, a lightweight business application and an integration are not three sizes of the same package. They involve different information and constraints. If a spreadsheet contains rules known only to its owner, those rules need understanding first. When connecting two applications, what they allow you to exchange matters. I do not attach price bands to these labels: that would suggest precision before understanding the work.
Reading the quote: discovery, data, integrations and checking
Discovery means understanding who will use the tool and which task it should simplify. It does not mean asking you for a perfect technical specification before talking. Tell me about the work and I gather the information needed to define a first version. Some details become clear during development. That is why I allow for reasonable uncertainty without presenting it as an offer to change anything at all.
For data, we look at what already exists and what needs organising. For integrations, we look at which applications need to communicate and what information must pass between them. For checking, we return to the original task: can the person do it with what we built? These are practical questions to clarify in the scope, not extras to leave until the end. A total only makes sense when the work it covers is understood.
What to consider after the first version
Putting a first version online lets us observe how it is used and choose what to improve. It does not mean every future development is included in the initial price. The first version has a scope; later requests need discussing against it. Maintenance and ongoing support also need clarifying rather than being automatic promises hidden in the word delivery.
For BaseCamp Studio I develop features inside an existing product, including semantic search and automatic tags. With EcoToGo the context includes the shop, business software and logistics handoffs. These examples show why software cannot be assessed only as a finished screen: where it fits into the work matters. They are not packages to replicate or numerical outcomes to transfer to another project.
How to compare two software quotes
Put the included work side by side, not just the totals. Do the proposals describe the same first version? Do they consider the same data and connections? Do they explain exclusions? A lower figure may describe different work. A higher figure alone does not prove better quality. Asking for an understandable explanation of the scope is more useful than looking for a universal custom software price.
Bring an example of the handoff you want to simplify and the tools involved to the call. You do not need to share confidential records to explain a task. We can begin with how the work happens and what gets in the way, then understand which information is actually needed. My custom software service starts there, not with a feature price list.
Frequently asked questions about software costs
A quote should make the work clear rather than hide uncertainty. These are useful questions to ask before comparing figures.
Why is there no single price?
Because a software label does not describe the work. Features, data and connections change the scope. Before starting, I send a written quote after understanding what is needed, rather than assigning a fixed price to a need we have not yet understood.
What information is needed for a quote?
Who does the task, what the first version needs to do, which data it uses and which applications are involved. You do not need every answer ready: gathering and clarifying information is part of my work. Start with the problem you face today.
What about existing data and integrations?
We consider them in the scope, not as details to leave until the end. Tell me where data lives and who updates it. I assess which connections the first version needs. Imports and integrations depend on the applications involved.
What happens after delivery?
We look at how the delivered version is used and agree any next steps. Maintenance, further development and ongoing availability should not be assumed to be included. They need clarifying in the quote according to the need.
How are extra features handled?
We discuss them against the written scope. Information discovered during the work and a new feature are not automatically the same thing. A reasonable allowance for uncertainty is not a promise of unlimited changes.
Is the €2,000 retainer the software price?
No. It is the starting monthly price for fractional CTO work, a different service. A software project is defined in a written quote. We choose between a project and ongoing work according to the need, not by treating the retainer as an automatic development estimate.