How Do You Handle Custom Software Development Change Requests?
Change requests during custom software development can be managed without reopening the whole contract. Set a threshold, a decision owner and a migration path before work starts.
You handle change requests without renegotiating the contract by agreeing a change-control clause before work starts. That clause sets a value threshold, names who approves changes, and defines how changes are priced. Use three criteria: a written change log, a fixed approval route, and a migration plan that keeps current operations running. custom software development projects that skip these three points usually reopen the contract for every request.
What should a change-control clause contain in custom software development?
A change-control clause should define what counts as a change, who approves it, and how it is priced, before development begins. Without these three elements, every request becomes a contract negotiation. The clause belongs in the software requirements document, not in a separate side letter.
The clause should state a value threshold. If a change costs less than the agreed threshold, the project manager can approve it without reopening the contract. Above that threshold, a written change order signed by both parties is required. The threshold can be a fixed fee or a percentage of the original contract value; the exact figure depends on the project size and the client's internal approval limits.
The clause should also name a single decision owner on the client side. When more than one person can approve changes, the approval route becomes the bottleneck. A named owner with a named backup keeps decisions moving without escalating to contract level.
Pricing method matters as much as the threshold. Fixed-price changes favour the vendor; time-and-materials changes favour the client when scope is unclear. For changes that touch fewer than three screens, a fixed price per change is usually faster to agree than a rate card. For larger changes, a rate card with a cap is more practical.
How do you migrate to a new system without stopping operations?
You migrate without stopping operations by running the old and new systems in parallel for a defined period and switching over one business process at a time. A single cutover date is the main cause of operational stoppage during legacy system replacement. Parallel running costs more in licence fees and staff time, but it removes the risk of a total outage.
Start with the process that has the fewest dependencies. For a distributor, that might be purchase order approval; for a service firm, timesheet entry. Move a process to the new system only after its data has been reconciled against the old system for at least one full reporting cycle. The length of that cycle depends on your billing or payroll frequency.
Data migration is the step most likely to delay cutover. If the old system has no export function, budget for manual extraction before you sign the development contract. The delivery team controls the import scripts and validation rules; the client controls access to the legacy data and the decision on which historical records to keep.
Keep the old system read-only for a defined period after cutover. Staff will need to look up historical orders or invoices. A read-only period of one full audit cycle is a common minimum; the exact length depends on your statutory record-keeping requirements.
When should a business stop using spreadsheets and commission bespoke business software?
A business should stop using spreadsheets when a single wrong cell can cost money and no one can trace who changed it. That threshold is usually crossed when more than one person edits the same file, or when the file feeds a customer invoice or a regulatory report. Bespoke business software replaces the spreadsheet's flexibility with an audit trail and access control.
The table below compares the two ways of working on the points that decide the purchase.
| Decision point | Spreadsheet | Bespoke business software |
|---|---|---|
| Who can change a value | Anyone with file access | Named users with roles and an audit log |
| Traceability of a wrong figure | Manual search through versions | Record-level history of edits |
| Cost of a new report | Staff time to rebuild the file | Change request against the software requirements document |
| Operational risk during change | Copy the file and hope | Parallel running and staged cutover |
| Handover to a new employee | Verbal explanation of formulas | Software handover checklist and written process |
If a wrong answer in the spreadsheet would cost money, the audit trail decides the purchase. That is the point where a custom software development company earns its fee: not by adding features, but by making the answer traceable.
How much does custom software development cost, and what drives the number?
Custom software cost is driven by the number of distinct user roles, the number of integrations with existing systems, and the amount of data that must be migrated. A system with one role and no integrations costs less than a system with five roles and three integrations, even if both have the same number of screens. The software requirements document is where these factors are fixed.
Change requests affect cost more than initial build in most projects we see. If change requests are priced per request without a threshold, the total cost becomes unpredictable within the first quarter. A threshold clause converts an open-ended cost into a bounded one.
The delivery team controls estimation accuracy and build quality. The client controls the clarity of the requirements document and the speed of approvals. A requirements document that names each approval step and each report is cheaper to build from than one that describes goals.
What should be included in a software handover checklist?
A software handover checklist should include source code access, deployment instructions, database schema, third-party account ownership, and a named contact for each external service. Without these five items, the client cannot maintain or extend the system independently. The checklist is the difference between owning the software and renting it.
- Source code repository with commit history and branch rules
- Deployment script or documented manual steps for each environment
- Database schema with a data dictionary for each table
- List of third-party services and which party holds the billing account
- Runbook for the three most likely operational failures
- Named handover contact on the delivery team for a defined support period
If the client does not hold the billing account for a third-party service, that service is a dependency, not an asset. The handover checklist should record the account owner for every external service the system calls.
We deliver custom software, business systems, mobile apps, websites, IoT systems and AI applications from Chengdu. Our handover practice follows the checklist above, with a support period agreed in the contract. You can see the scope of our service clusters and how we work with Chinese-speaking developers on projects for European and North American clients.
Frequently asked questions
How much does custom software development cost?
Custom software cost depends on the number of user roles, the number of integrations, and the volume of data to migrate. A single-role system with no integrations costs less than a multi-role system with several integrations, even if the screen count is similar. The software requirements document is the main lever the client controls.
How long does it take to build a custom business system?
The build duration depends on how many business processes are in scope and how quickly the client approves each stage. A system covering one process moves faster than one covering five. Approval delays on the client side usually add more time than development delays.
When should a business stop using spreadsheets?
A business should stop using spreadsheets when more than one person edits the same file or when the file feeds an invoice or a regulatory report. At that point, a wrong cell can cost money and the edit history is not traceable. Bespoke business software replaces that risk with access control and an audit log.
What should be included in a software handover?
A software handover should include source code access, deployment instructions, the database schema, and the account owner for every third-party service. It should also name a support contact for a defined period. Without these items, the client cannot maintain the system independently.
How do you handle change requests without renegotiating the contract?
You handle change requests by agreeing a value threshold and a single approval owner before development starts. Changes below the threshold are approved by the project manager; changes above it require a written change order. This keeps the contract intact and makes the cost of each change visible.
Questions we are asked
How much does custom software development cost?
Custom software cost depends on the number of user roles, the number of integrations, and the volume of data to migrate. A single-role system with no integrations costs less than a multi-role system with several integrations, even if the screen count is similar. The software requirements document is the main lever the client controls.
How long does it take to build a custom business system?
The build duration depends on how many business processes are in scope and how quickly the client approves each stage. A system covering one process moves faster than one covering five. Approval delays on the client side usually add more time than development delays.
When should a business stop using spreadsheets?
A business should stop using spreadsheets when more than one person edits the same file or when the file feeds an invoice or a regulatory report. At that point, a wrong cell can cost money and the edit history is not traceable. Bespoke business software replaces that risk with access control and an audit log.
What should be included in a software handover?
A software handover should include source code access, deployment instructions, the database schema, and the account owner for every third-party service. It should also name a support contact for a defined period. Without these items, the client cannot maintain the system independently.
How do you handle change requests without renegotiating the contract?
You handle change requests by agreeing a value threshold and a single approval owner before development starts. Changes below the threshold are approved by the project manager; changes above it require a written change order. This keeps the contract intact and makes the cost of each change visible.
