The key points
- Roles and permissions are among the biggest cost drivers.
- Multi-tenancy changes the architecture, so decide early.
- Integrations and data migration add scope and testing.
- A proposal after workflow mapping is more reliable than a guess.
Which factors move the price most?
Every distinct type of user needs their own views, permissions and testing, so the number of roles matters more than the number of screens. Multi-tenancy, where one system serves several separate organizations or branches, shapes the architecture from the first line of code and is far cheaper to plan than to retrofit. A two-sided marketplace is a common example, with separate buyer, seller and admin roles from the first version. For two specific products, our school management software pricing guide and restaurant POS pricing guide compare building with subscribing.
Integrations with systems you already use, such as an ERP or accounting package, each need setup, testing and often third-party accounts. Migrating historical data from spreadsheets or an old system depends on its volume and, more importantly, its condition.
- Number of user roles and permission levels
- Whether multi-tenancy is needed now or later
- Integrations with existing systems
- Volume and quality of data to migrate
Why not quote from a feature list?
Feature lists hide complexity. Two systems with the same list can differ by an order of magnitude in effort depending on the rules behind each feature. That is why workflow mapping comes first in custom software work: it exposes the rules before a price is set, so the proposal reflects the real work and surprises are rare. Use the same lens to compare quotes from different suppliers.
What costs continue after the build?
Hosting, third-party services and usage-based charges continue, and so does maintenance, which is separate from the build and part of the support a product needs after launch. We identify these during scoping. Twelve months of support are included with our custom software work, with changes beyond that scoped separately so the arrangement stays predictable.
Prepare for a custom software quote
- How many types of user will use it, and what can each do?
- Is it for one organization or several?
- Which existing systems must it connect to?
- What data must move in, and where does it live now?
- Which parts are essential for the first release?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.