Custom Software Cost: Development and Operating Budget

Custom software cost extends beyond the development proposal. Workflows, data migration, integrations and responsibilities after launch all belong in the budget. This guide combines cost drivers, a budget template and an illustrative first-year calculation with a proposal comparison.

Why is there no single price list?

An off-the-shelf product can have a listed price because it already exists. With custom software, what you are buying does not exist yet; price follows the size of the work. “Let our dealers place orders” could mean a few-screen form or a platform with credit limits and ERP integration. Giving both the same figure means overpricing one or underpricing the other.

The number discussed in the first meeting is therefore an estimate with considerable uncertainty. A reliable range requires knowing users, workflows, and connected systems. A short discovery exercise clarifies them: in 1–2 weeks, observe the process in context, inventory systems, define first-release scope, and propose a team and timeframe. We cover the steps and outputs in detail in our article about discovery sprints.

Asking for a fixed price before discovery is tempting but risky. The provider either adds a contingency to cover uncertainty or quotes low and turns anything not explicitly scoped into a change request. In the first case you pay for uncertainty upfront; in the second, throughout the project.

Which items determine cost?

The items below change project size most. The question in the final column helps determine each item's weight in your project.

ItemWhy does it affect cost?Clarifying question
Roles, workflows, and rulesEach user group brings its own screens and permissions; amount- or region-dependent approvals multiply test scenarios.How many user groups are there? Are rules documented or held in people's heads?
IntegrationsFor ERP, bank, and e-Invoice connections, the other system's access method and data quality determine the timeline.Does the system have an API, or is file transfer needed? Who is authorized on the other side?
Data migrationCleaning, mapping, and validating old data is separate work.Which data, how many years back, and with whose approval will it be migrated?
Mobile and offlineTwo platforms, app-store processes, and offline data synchronization add work.Is a mobile-friendly website sufficient? Which operations will work offline and who will resolve record conflicts?
ReportingEvery report places demands on the data model and performance.Which report is read today, and for which decision?
Security and KVKKAccess logs, data masking, retention and deletion rules, and hosting location influence design.Which personal data will be processed, and where will it be hosted?
Continuity and performanceAvailability, heavy usage, and backups increase infrastructure requirements.How many hours can the system be down before business stops?
Design depthA customer-facing portal and an internal tool do not require the same design effort.Who will use the product: external customers or an internal team?

Two more items are absent from the table. The first is team composition: seniority, size, and distribution of roles determine both unit rates and speed. The second is time on your side. If the product owner cannot set aside a few hours weekly for decisions, questions wait and the schedule stretches; a longer schedule also costs money.

If personal data will be held in a foreign cloud service, KVKK's cross-border transfer conditions need assessment from the start. This affects hosting selection and contract work.

Plan the budget in five layers

Two products with the same number of screens can require different effort because of permissions, external systems and support expectations. Before requesting a proposal, identify the task the first release must complete, its users and the records being migrated. Verify assumptions such as ready-to-use ERP access.

Include your own team’s time for data preparation, decisions and acceptance testing. That effort has a cost even when it does not appear on the supplier’s invoice; show it separately from cash payments.

Budget layerTypical itemsQuestion to resolve
Initial deliveryDiscovery, design, development, testingWhich acceptance scenarios are included?
TransitionData preparation, migration, trainingHow long will both systems run?
OperationHosting, monitoring, backups, APIsWhich charges are fixed or usage-based?
ChangeFeatures, regulatory or platform changesHow are changes approved and priced?
ExitExports, documentation, handoverCan another team operate the system?

How do you make a rough cost estimate?

A rough calculation before requesting quotes makes them easier to interpret. The logic is simple:

  • Development cost = person-weeks for each role × that role’s weekly rate; summed across roles
  • First-year total = development + migration and training + other one-time setup + 12 months of operating costs

Fill the template below with your own figures. Put currency, price date, and VAT inclusion at the top. Exchange-rate and price changes over several months can distort comparisons; quote validity is therefore part of the template too.

Currency: …… · Price date: …… · VAT: included / excluded · Valid until: ……

ItemHow is it calculated?Amount
Discoverypeople × weeks × unit rate……
Design and prototypepeople × weeks × unit rate……
Development and testingpeople × weeks × unit rate……
Project and product managementpeople × weeks × unit rate……
Integration and data migrationa separate line for each system……
Third-party setup and licensingper product; user- or transaction-based……
Contingency for uncertaintyfor each unresolved question, with its reason……
Operations (monthly)hosting + monitoring + support + licenses……

Do not hide contingency; state which open question it covers. As discovery resolves questions, this allowance shrinks.

Which expenses begin after launch?

  • Hosting and infrastructure: servers or cloud services, database, backups, domain.
  • Monitoring: error logging, availability monitoring, and alerts.
  • Security updates: new library versions; for mobile apps, annual operating-system changes and app-store rules.
  • Support and minor enhancements: user questions, bug fixes, small improvements.
  • Third-party fees: e-Invoice provider, SMS, maps, payment infrastructure, and app-store accounts.

Rather than estimating these expenses as one percentage, list them individually: fixed costs as monthly amounts, support and minor enhancements as a monthly pool of hours with response times.

First-year budget: a worked example

The following figures are illustrative assumptions, not Codariva prices or market averages. They use one currency and exclude tax and exchange-rate effects. Here, “first year” adds initial delivery and transition costs to 12 months of operation after launch; it is not a 12-month cash-flow forecast starting with development.

AssumptionIllustrative value
Initial development€20,000
Migration and training€2,000
Fixed monthly operating cost€400
External service cost per transaction€0.015
Monthly transactions20,000 transactions

First-year total = €20,000 + €2,000 + 12 × (€400 + 20,000 × €0.015) = €30,400.

At 40,000 monthly transactions, the same assumptions produce €34,000. An unchanged development price therefore does not mean an unchanged annual budget. Check actual supplier terms for volume tiers, free allowances, exchange rates, taxes and minimum commitments.

This narrow example does not quantify new features, separately charged support, exit costs or internal staff effort. Add the relevant lines to your own budget; do not treat an unknown cost as zero. Separate payment instalments from the start of operations and avoid counting a one-time charge again as a monthly cost.

How long does it take? A hypothetical example

For example, a distributor wants to move dealers' repeat orders from phone calls to a portal. Suppose the first release is narrowed as in our article on defining MVP scope: dealer sign-in and pricing, baskets from previous orders, order tracking, and a read-only account summary. Prices and stock are imported from ERP several times a day by file. The portal is a mobile-friendly website; there is no separate mobile app.

StageWeekRecommended team (time allocation)Person-weeks
Discovery1–2Product manager (full-time), designer and technical lead (half-time)4
Definition and prototype3–4Designer (full-time), product manager and technical lead (half-time); prototype tested with dealers in week 34
Build (3 sprints)5–102 developers (full-time); designer, tester, and product manager (half-time)21
Total10Launch with a pilot dealer group29

This table is a hypothetical scenario; the actual team and timeline are set after discovery. Transfer the person-week total into the template above and multiply by the provider's weekly unit rate for a rough development cost. A 6–12-week first-release target can only be considered with narrow scope and verified access; it is not a delivery promise for every project. The table changes as scope grows:

  • Promotion and discount rules: a medium-sized addition; depends on how well the rules are documented.
  • Real-time, bidirectional ERP integration: large; depends on the ERP API and the authorized person on the other side.
  • Payment through the portal: large; adds payment-provider, reconciliation, and security work.
  • Mobile app for field sales: a separate stage with its own discovery and team.

Sequencing these additions rather than loading them all into the first release also lets large programs launch in stages: the first stage follows its own scope, and later stages follow the roadmap. Our Dealer Ordering Platform product concept, prepared for the fictitious X Dağıtım, shows what this staging might look like on screen.

Before requesting quotes, document roles, data sources, and the first-release boundary in the project brief tool. For more detailed acceptance criteria, use the example software project requirements checklist.

Fixed price or time and materials?

The same scope can be priced under different models. The right model depends on how much uncertainty remains.

ModelWhen is it suitable?Who bears the risk?
Fixed priceScope is documented, narrow, and validated by discovery; few changes are expected.Estimation risk sits with the provider; in return a contingency is built into the price and each change is billed separately.
Time and materialsScope will be clarified through user feedback; priorities may change.You bear it; manage it with a budget cap, end-of-sprint demos, and regular spending reports.
Dedicated team modelA continuously evolving product; your product owner makes the decisions.You own prioritization; the provider owns team continuity and work quality.

Models can be combined: fixed-price discovery, a capped time-and-materials first release, and a dedicated team afterwards. For small work with genuinely clear scope, fixed price is often the simplest option.

The schedule also includes access delays, data correction, business decisions and acceptance testing. A fixed-price proposal needs explicit exclusions and a change process; time-and-materials work needs a spending limit and reporting; a retained team needs clear roles and capacity. None of these models removes uncertainty from an undefined scope.

Is maintenance included in the build price?

Only if the agreed scope says so. Defect correction, operation and new development should be described separately. Compare licences, account ownership, support coverage and handover documents alongside the proposals.

How can you reduce budget safely?

The safe way to lower budget is to reduce the work, not keep the work unchanged and cut quality.

  • Narrow the first release. Start with one user group and one main workflow.
  • Bridge integration first. Start with files or manual transfers and add full integration when volume requires it.
  • Use existing components. With mature services for authentication, payments, notifications, and e-Invoice, there is no need to build them from scratch. For accounting, payroll, or standard CRM, an off-the-shelf product is often the better choice.
  • Consider a mobile-friendly website. Without offline operation or device-specific features, a separate mobile app is not essential in the first release.
  • Divide into stages. Reassess whether to continue at the end of each stage.

A cheap quote may omit automated tests, security checks, data migration, acceptance testing, documentation, a backup plan, or a post-launch warranty. Removing them from a quote does not remove the work; it moves it into the final project weeks or the maintenance bill.

Consider a smaller user group, fewer reports or a narrower first integration. Do not remove access control, recovery arrangements or acceptance testing merely because users do not see them on a screen. For every postponed feature, identify the manual task that remains and who will perform it.

What should a quote include?

Quotes under the same “dealer portal” heading may price different work. The two examples below are fictional; they contain no price recommendation or real customer results.

Example scenario: two different scopes under the same “dealer portal” heading
Check Example quote A Example quote B
ERP connection Prices and stock are imported by file; an employee enters orders into the ERP. API transfer, duplicate checks, and an error queue are included.
Legacy data A customer-cleaned file is imported once. Field mapping, rehearsals, and record reconciliation are included; the business owner decides on cleanup.
Acceptance testing Working screens are demonstrated; failed-transfer testing is unspecified. Acceptance scenarios for permissions, pricing differences, connection outages, and repeat submissions are documented.
After launch A bug-fix period is specified; monitoring and support are quoted separately. Monitoring, support hours, and maintenance boundaries are documented; third-party fees are separate.

Work absent from quote A is not automatically unnecessary; nor is every item in quote B mandatory for the first release. Choose the needed scope and ask both providers to quote the same boundaries. Then compare one-time development, manual work by your internal team, and ongoing costs over the same period; do not count an unknown item as zero.

The following conditions should also be in writing; ask the provider for any that are missing.

Quotation checklist

  • Scope: roles, workflows, and screens, separating the first release from later stages.
  • Exclusions: a list of work deliberately left out.
  • Assumptions: for example, who provides ERP access and test data, and when.
  • Team: roles, seniority, and time allocation for each role.
  • Timeline: stages, demo frequency, and go-live criteria.
  • Pricing model and how change requests are charged.
  • Currency, VAT inclusion/exclusion, validity date, and payment plan.
  • Acceptance criteria and acceptance-testing duration.
  • Ownership of source code, design files, domain, and cloud accounts.
  • Third-party licenses and whose name they will be in.
  • After launch: warranty period, support model, and response times.
  • Documentation and handover conditions for another team.

We also summarize the factors determining budget and timeline on our custom software development service page. We prepare quotes around these headings; when uncertainty is high, we recommend a discovery sprint first.

Technical references and scope

This guide describes a budgeting method; it is not a quotation or a delivery commitment for a specific project. The AWS Cost Optimization Pillar is a technical starting point for monitoring cloud usage alongside expenditure. Using this planning approach does not require choosing AWS.

Let's clarify the budget together

Read on
Related service

Custom Software Development

Scope, recommended team, timeline, and delivery conditions: how the factors determining cost are handled in a project.

Other articles
Your own calculation

See how much time your manual process takes

Use the free automation savings calculator to compare monthly workload, potential time savings, and operating costs using the same assumptions. The result is not a quote or a guarantee of cash savings.