Cost guide

Custom Software Cost in Bosnia: What Changes It?

Custom software cost changes with the number of user roles, the integrations, the data model, the security requirements and the support commitment. Konzept publishes Growth from EUR 14,500, Scale from EUR 29,500 and Enterprise from EUR 44,000. A fixed quote follows a written brief and an agreed scope, not a feature wish list.

Last updated: 2026-09-21 · Author: Konzept team

What changes the cost of custom software in Bosnia?

Custom software cost is set by rules, roles and connections, not by the number of screens. Two products with the same screen count can differ by a factor of three once permissions, integrations and audit requirements are written down.

Konzept publishes three project tiers. Growth starts from EUR 14,500 over 4–8 weeks. Scale starts from EUR 29,500 over 8–14 weeks. Enterprise starts from EUR 44,000 over 14–20+ weeks, and it is the tier that lists full-stack and custom software, API architecture, AI automation, advanced authentication and security.

The pricing page holds the published packages. The starting price is a floor for a scope, not a fixed quote for every brief.

Which scope drivers move the estimate?

Eight drivers explain most of the difference between two software quotes:

  1. Number of user roles, and how differently each role sees the system.
  2. Business rules: approvals, states, exceptions and who can override them.
  3. Data model complexity and the volume of existing records.
  4. Integrations with ERP, CRM, accounting, payment or government systems.
  5. Data migration, cleaning and the cutover plan.
  6. Authentication, permissions, audit logging and retention rules.
  7. Reporting: who reads it, how often, and whether it must be exportable.
  8. Environments and release process, including staging and rollback.

Read software development for the delivery approach. If the brief spans several systems and departments, enterprise solutions is the closer match.

How do integrations change the price?

An integration is a contract with a system you do not control. Its cost depends on that system, not on your own code.

Integration conditionEffect on scopeWhat to confirm first
Documented API with a test environmentRoutine work, predictable estimateCredentials, rate limits, sandbox access
API exists but is undocumentedDiscovery before estimate is possibleWho owns it, and who answers questions
File export or scheduled batch onlyExtra handling for timing and failuresFormat, frequency, what happens on a bad file
Vendor must approve accessWaiting time outside the delivery teamApproval path and expected lead time

Confirm API access before a fixed price is agreed. An integration signed off on assumption is the most common cause of a scope dispute later.

Two builds show how much the answer matters. A law firm client portal costs one thing when practice management software publishes an API and another when it does not. The same is true of a patient booking and telehealth flow and the clinic’s scheduling system.

Is an MVP really cheaper?

An MVP is cheaper only when the scope is genuinely narrower. Many teams cut visual polish, keep every role and rule, then wonder why the saving is small.

A real first release proves one workflow, for one role, end to end. It carries a data model that later phases extend. It measures whether the workflow works in real use.

Write the second phase down at the same time. That list keeps the first release honest, because every deferred item has a home instead of creeping back into scope.

Build or buy?

Buy when an existing tool matches the workflow and the process can adapt to it. Build when the workflow is the advantage, when licence cost scales badly with users, or when the rules have no product-market match.

Compare total cost over five years. Include licences, per-user fees, implementation, training, data export and the cost of leaving the vendor. A build has a higher first-year cost and a different curve after that.

The honest answer is often a mix: buy the standard parts, build the part that is genuinely yours, and connect them.

What does the process look like?

The work follows five steps:

  1. Discovery: workflow mapping, roles, rules, systems and success measures.
  2. Architecture and data model, agreed before the first screen is built.
  3. Iterative build, with working software reviewed at fixed intervals.
  4. Testing: functional, permission, performance and migration rehearsal.
  5. Cutover, training and handover, with a support plan already chosen.

Decisions are part of the schedule. A named owner who can approve rules keeps a software project on time more reliably than any tool choice.

What are the running costs?

Support is EUR 1,200 per month, Core is EUR 2,350 per month and Accelerate is EUR 3,450 per month. Hosting, database services, monitoring and any paid API are billed by those providers.

A quote should separate agency work from third-party running cost. Ask for that split before approval, so the annual figure is visible and not a surprise in month four.

For adjacent cost framing, see website cost Bosnia. If you are also weighing an internal hire, read agency vs in-house.

How do I get a fixed quote?

Send the workflow you want to replace or automate, the roles that use it, the systems it must connect to, the record volume, the reporting needs, the security requirements, the target date and the decision-maker.

A screenshot of the spreadsheet or tool you use today is worth more than a feature list. Start with a quote request, and expect the first call to narrow scope before any number is discussed.

all Konzept guides

FAQ

Questions buyers ask

What changes the cost of custom software?

Roles, rules and integrations change it most. Each user role adds screens, permissions and test cases. Each integration adds a contract with another system. Data migration, audit requirements and security reviews add work that is invisible in a feature list but real in a schedule.

What are Konzept's published software prices?

Konzept publishes Growth from EUR 14,500 over 4–8 weeks, Scale from EUR 29,500 over 8–14 weeks and Enterprise from EUR 44,000 over 14–20+ weeks. Enterprise is the tier that lists full-stack and custom software, API architecture, AI automation and advanced authentication and security.

Is an MVP cheaper than a full build?

An MVP is cheaper only when its scope is genuinely narrower. Cutting polish while keeping every role, rule and integration saves little. A real MVP proves one workflow for one role, with a data model that later phases extend without a rewrite.

How much does an integration add?

It depends on the other system. A documented REST API with a test environment is routine work. An undocumented system, a nightly file export or a vendor who must approve access adds discovery, waiting time and error handling. Confirm API access before the scope is fixed.

Should we build custom software or buy a tool?

Buy when a tool already matches the workflow and the cost of adapting the process is low. Build when the workflow is the competitive advantage, when licence cost scales badly, or when no tool covers the rules. Compare total cost over five years, not the first invoice.

What does support cost after delivery?

Support is EUR 1,200 per month, Core is EUR 2,350 per month and Accelerate is EUR 3,450 per month. Hosting, database services, monitoring tools and any paid API are billed by those providers. A quote should separate Konzept's work from third-party running costs.

Scoping a custom software build?

Send the workflow, the roles and the systems it must talk to.