What drives custom software cost? Custom software pricing and how to read a quote
What drives custom software cost? Scope, roles, integrations, platform, testing and support, and how to read a quote from a custom software company.
Custom software cost depends less on the number of screens than on scope, the complexity of business rules, user roles, integrations, platform choice, testing and support after go-live. Before talking about price, the goal, users, data and business rules should be clear, and quotes should be compared on the same scope. A quote without a written scope is the vaguest one, even if it looks cheap.
A company’s management wants a custom request and approval application for internal use and asks three software firms for quotes. The brief is one page; the quotes look nothing alike. One is a summary of a few lines, another runs to pages of items, and the third just says “to be implemented as needed”. The prices are not close to each other either. Management looks at the price table to work out which one is “right”, yet most of the difference lies not in the figures but in what each quote counts and what it leaves out. Without giving a fixed price, this article explains what determines custom software cost and how to read a quote.
Custom software cost is the total cost of designing, developing, testing, launching and supporting an application built from scratch, or heavily adapted, to fit an organisation’s own business rules, user roles and integrations. There is no single unit price; the figure only becomes meaningful as the scope becomes clear.
How is software development cost estimated? The factors
Cost is usually determined not by the question “how many screens?” but by the sum of the factors below. Have an answer for each row before you ask for quotes.
| Factor | Why does it affect cost? | Prepare before asking for a quote |
|---|---|---|
| Scope and business rules | Every rule, decision point and exception means design and testing effort | Write the process down step by step; list the exceptions and decisions |
| User roles | The screens and permissions of each role are designed and tested separately | Write down what each role will see, do and approve |
| Integrations | Every connected system adds data mapping, error handling and testing | Decide which systems exchange which data, and in which direction |
| Platform | Web, mobile browser or a native mobile app each take different effort | Clarify which devices users will use, and where |
| User flow and design | Design effort grows for screens with many users and frequent use | State how often screens are used each day rather than how many there are |
| Data to migrate | Cleaning and transferring old data is a separate work item | Note where the data lives and how tidy it is |
| Reporting | Every report affects the data model and validation | Separate the reports that will really be used |
| Testing and acceptance | Validating with real scenarios takes time | Define the acceptance criteria and who will do the testing |
| Go-live and infrastructure | Hosting, backup and installation are cost items | Think about where the application will run and who will manage it |
| Support and maintenance | Bug fixing and changes continue for the whole period after go-live | Ask about the scope and duration of support |
Besides the items in the table, there is the effort on your side, which often does not show up in the quote: the time of the people who explain the process, delays from managers who make the decisions, running the acceptance tests, training staff. If this work slips, the project drags on and the total cost grows. Discuss at the quote stage who will handle these tasks.
Ways to keep costs under control
- Limit the first release to the one flow that will be used most; expand once you have seen how users behave.
- Keep the number of roles limited to those that really need separate permissions.
- Split reports into “nice to have” and “we cannot decide without it”; only put the second group into the first release.
- Phase the integrations; connect the essential one first and leave the others for a later stage.
- If part of the scope can be covered by an off-the-shelf module (for example a module such as Sales / Quotation & Customer Management for customer and quote tracking), custom-build only the difference.
Why do custom software prices vary so much?
The differences between quotes for the same need usually come down to these reasons:
- Scope assumptions differ; one counts the admin panel, the other does not.
- Some quotes include testing, data migration and training; others leave them out.
- Support duration and scope are not the same.
- Team experience and ways of working differ; a team that works to understand the need and reduce uncertainty may build the remaining uncertainty into the quote as a “risk margin”.
- If it is not written down how change requests will be handled, today’s price says nothing about tomorrow’s.
How to read a software quote: eight questions
- Is the scope written down? Functions, roles and screens should be listed item by item.
- What is not included? If exclusions are not stated clearly, disputes will follow.
- What are the acceptance criteria? Which scenarios have to pass for the work to count as “done”?
- Who does the testing? The developer, you, or both together?
- How will changes be managed? When a new request comes in, how will it be assessed and priced?
- What is the payment plan tied to? Time, or delivered milestones?
- When does support start and what does it cover? Bug fixes and new features should be counted separately.
- What stays with you? How will access to the data, documentation and, if needed, handover of the work to another team be handled?
Before asking a custom software company for a quote: a one-page brief
Sending the same brief to every firm makes the quotes comparable. The brief does not need to be longer than a page; these headings are enough:
- The problem to be solved and the expected result, in two or three sentences.
- The process steps: who decides what, and in which order?
- User roles and approximate user numbers.
- Existing systems that need to be connected, and the data to be taken from or sent to them.
- Place of use and device: office, field, phone, browser.
- A ranking of must-haves versus nice-to-haves.
A table for putting quotes side by side
Use the table below to compare three quotes on the same basis; fill in each quote’s answer. Every empty cell is a question to ask.
| Item | Quote A | Quote B | Quote C |
|---|---|---|---|
| Scope summary (functions, roles, screens) | … | … | … |
| Out of scope | … | … | … |
| Systems to be connected | … | … | … |
| Platform (web, mobile browser, native mobile) | … | … | … |
| Testing and acceptance criteria | … | … | … |
| Data migration and training | … | … | … |
| Support scope and duration | … | … | … |
| Change process | … | … | … |
| Payment plan | … | … | … |
Will an off-the-shelf package, Excel or WhatsApp do instead of custom software?
If your process is common in your industry and an off-the-shelf product covers it, custom software may be an unnecessary cost. For a small team, low volume and work run by one person, an Excel sheet and a messaging group are often enough too. Things start to break when the work is split across several people, when an approval chain is needed, when you have to look up past records and when reports are requested. If you constantly have to work around the rules of an off-the-shelf product that does not fit you, the total cost of custom software may stay below the cost of forcing an off-the-shelf product to fit. Before deciding, compare both options on the same scope.
How does custom software development work at YazSis?
YazSis Custom Software work starts where off-the-shelf software falls short and is built around an organisation’s own business rules, user roles and integrations. The scope covers web applications, role-based admin panels, workflow systems that manage requests, approvals, assignments and deadlines, mobile applications, API services for exchanging data with other systems, and back-office interfaces for busy operations teams. The work runs in four phases:
- Discovery: the goal, users, data and business rules are mapped out.
- UX and architecture: the user flow and a sustainable technical structure are designed.
- Development and testing: the software is built in modules and validated with real scenarios.
- Go-live and support: the system is put into service, measured and improved through feedback.
The principle is to design the process before the screens, and the architecture of users, data and business rules before the feature list. For a sound conversation about cost, the need should first be mapped out with the same clarity. If you are not sure how clear your processes are, the process discovery in our Digital Transformation work makes this preparation easier.
To clarify your needs before talking about pricing, take a look at the Custom Software page.
Frequently asked questions
What factors affect custom software cost?
It depends on the scope and the complexity of the business rules, user roles, the number of systems to be connected, the choice of platform, the need for data migration, testing and support after go-live. The number of screens alone does not decide it.
How is software development cost estimated?
The process is written down, roles and integrations are listed, the platform and acceptance criteria are defined; then development, testing and support are assessed against that scope. If the scope is unclear, the estimate stays unclear too.
Why do custom software prices vary from firm to firm?
Because the scope of the quotes, the items they exclude, their support periods and the teams’ ways of working are not the same. Before comparing prices, you need to bring the quotes to a common scope.
What should you watch for most when reading a software quote?
Check whether the scope is written down, what is out of scope, the acceptance criteria, who is responsible for testing, the change process, the payment plan and the support scope. Every item left blank or vague is a question that needs to be asked.
What should be prepared before starting custom software?
The process steps, user roles, systems to be connected, existing data and expected reports should be written down. This preparation makes quotes easier to compare and reduces scope disputes later on.
More articles
RFID on-metal tags: metal, liquid and read-zone analysis before installation
A tag that reads perfectly on the office desk may not give the same result in a warehouse with metal shelves and cartons of drinks. We put in order what to measure on site before installation and how to tune the read zone.
November 16, 2026 · 8 min readMobile app development cost and pricing: the key cost items in an enterprise app
Mobile app pricing cannot be reduced to a single figure; it depends on the items that make up the scope. We list the items that drive the cost of an enterprise field app and what you should put in writing before asking for quotes.
November 16, 2026 · 8 min readWhat is an internal audit and how is it done? ISO audit programme, report example, closure
What is an internal audit? It is how you check, from the inside, whether your management system works as written. How to build the programme, what the report contains and how a finding is closed: a simple framework.
November 16, 2026 · 8 min read