All guides

Codiatech guides

How to Budget for Custom Software: From First Release to Ongoing Operations

A useful custom software budget cannot be inferred from the number of screens or a development estimate alone. Two proposals that look similar may assign data migration, integrations, testing, deployment and maintenance to different parties. Start by describing the problem to solve and drawing a boundary around the first release. Then separate one-time delivery, third-party costs and work after launch. This gives you a way to compare proposals for the same job, rather than comparing figures attached to different assumptions.

Custom Software Proposal Comparison Template

Record scope, delivery, integrations and post-launch ownership for two proposals side by side.

The editable workbook includes Turkish and English sheets. Fill in your own decisions and observations; no proposal prices or successful test results are prefilled.

Download proposal comparison template (XLSX)

Define the First Release

Write down who needs to do what: customers, staff, administrators and external partners may use the same system for different reasons. For each role, separate essential workflows from requests that can wait. Creating, approving and reporting on a record can involve several decisions and permission checks, even if it appears to be one screen. Replace a broad line such as ‘admin panel’ with the tasks included in the first release, important exceptions and the output used for acceptance. If new requirements emerge, assess them as changes instead of silently treating them as part of the original estimate.

Inventory the Software and Infrastructure You Already Have

Determine whether the team is starting from scratch. Who owns the existing applications, code repository, administrator accounts, domain, hosting environment and licences? A working component may be reusable, but the code, access and dependencies need to be reviewed before promising that reuse. Taking over an existing system is a different job from building a new one. Record which components may stay, which need replacement and what access the client will provide. Unclear ownership of a vendor account or licence can turn into a deployment decision at the end of the project.

Describe Each Integration Separately

If the application must connect to a CRM, ERP, payment service, email system or another platform, describe the purpose and direction of each connection. Will data only be read, or will both systems update it? Which event starts the exchange? An integration is hard to estimate as a single line until API access, test environments, permissions, data mapping and error ownership are understood. Third-party limits and charges may also affect the scope. Codiatech determines system integration deliverables for each project; this guide does not imply that every project includes the same connectors or a fixed integration package.

Treat Data Migration as a Cleanup and Acceptance Task

Before moving existing records, decide which data is needed, which source is authoritative and who may access personal information. Duplicates, missing fields and inconsistent formats are decisions to resolve, not merely files to upload. Discuss the volume, transformation rules, trial migration, fallback plan and person responsible for final review before the proposal is agreed. Some records may be deferred, provided the effect on the first release is understood. A rehearsal using representative records helps the client and development team agree on what a correct migration looks like.

Specify Testing and Deployment as Deliverables

Agree in advance what ‘working’ means. Select acceptance examples for core workflows, role boundaries, invalid input, integration outages and the devices people will use. Decide who provides test data and who approves the result. A task that succeeds in a developer's browser may still miss the organization's actual workflow. Assign ownership for the domain, environment configuration, data transfer, redirects and rollback on launch day. Source code and repository access, testing and deployment are typical deliverables in Codiatech custom software and web or mobile projects, but their precise boundaries belong in the project proposal.

Separate Infrastructure, Licences and External Services

The operating environment and services an application uses can change its cost after delivery. Hosting or cloud use, data storage, domains, email, SMS, maps, payments and third-party licences may be billed separately from development. Check which services are necessary and whose account will be charged. Identify costs that can vary with traffic or storage rather than hiding them in a one-time figure. Provider choice, data location, backups and access ownership depend on the project. Do not assume a particular platform will achieve a specific cost or availability outcome before those requirements have been assessed.

Read Maintenance and Operations as a Separate Decision

Deployment does not end every responsibility. Bug fixes, security and dependency updates, new features, content changes, monitoring and user support are distinct types of work. Ask which are included in delivery and which need a later agreement. Decide who notices an outage, who contacts a third-party provider and how new requests are estimated. For Codiatech services other than AI, maintenance and operations vary by service and project. This guide does not establish support hours, a free maintenance period or a service-level commitment for a particular engagement.

Compare Proposals Using the Same Checklist

Before comparing prices, put each proposal into the same decision table. A lower figure may reflect work assigned to the client's team or deferred to a later phase. Ask for written clarification instead of filling gaps with assumptions. Adapt the fields below to your organization. They are a tool for comparing scope, not a standard Codiatech package or price list.

  • First release: User roles, essential workflows, administration areas, included and excluded features, and who approves acceptance.
  • Existing systems and data: Code and accounts to take over, each integration's direction, migration scope and ownership of third-party access.
  • Delivery and launch: Design, code and repository access, test examples, deployment, required accounts and rollback responsibility.
  • Recurring costs: Hosting, licences, messaging, payments or other external services, including billing and usage conditions.
  • After launch: Maintenance, support, monitoring, new features and how changes to scope will be agreed.

What delivery and maintenance terms should you ask for?

Ask each shortlisted Istanbul firm to put the milestone, test, approver and evidence in writing. At handover, check whether a developer outside the supplier can build and deploy from the agreed repository and instructions. Ask who owns the accounts, what rights and third-party licences transfer, what support covers, and what the next team would receive if the agreement ends. Use this illustrative example to compare written proposals.

  • Milestone acceptance In a sample approvals app, a requester submits one record and an authorized reviewer approves it in the test environment. A requester account cannot approve its own record. Record the release version, test result, approver and review window. Agree which unresolved defects block sign-off.
  • Handover and exit Ask the incoming developer to deploy the agreed version in a clean test environment using the delivered repository and instructions. Write down the account owner, licence conditions, included data exports, and when outgoing access can be removed. Ask who fixes missing handover materials and how transition assistance is priced.
  • Maintenance and changes Ask how the supplier treats an agreed workflow that stops working versus a request for a new approval step. Record which fixes, updates, backups and third-party escalation are covered, who takes each incident, support hours, first-response and restoration targets, and how extra changes are approved and billed.

A Delivery Example: Istanbul Rotary Club

For the June 2026 Istanbul Rotary Club project, Codiatech delivered iOS and Android apps, a website, administration and user areas, and implemented its CMS. The project illustrates how several platforms and management areas can belong to one scope. To budget for your own organization, define the roles, platforms and data connections you actually need instead of copying another project's list of deliverables.

Let's Define Your Project Scope

Share your current systems, the essential tasks for the first release and the data connections you need. We can then define design, development, testing, launch and ongoing responsibilities for your project.

Request a proposal