Warranty period
- A fair contract includes a free period after acceptance, often around three months, during which the developer fixes bugs in its own code at no charge.
- It covers defects: features that do not work as the specification says. It does not cover new features or changes to the design or logic.
Ongoing support
- After the warranty, support is usually a monthly agreement with response times: for example, critical issues within hours, minor ones within days.
- The monthly cost depends on the size of the system, the hours included, response times and whether hosting, monitoring and backups are part of it.
What to put in the contract
- What counts as a bug and what counts as a change request.
- Response and fix times by priority.
- Who owns the source code and when it is handed over, and how access to servers is transferred.
Experience behind this advice
- In Eurosoft's acceptance acts the free support period, what it covers, what is excluded and when the source code is handed over are written out clause by clause.
Questions and answers
- Is bug fixing after launch free?
- During the agreed warranty period, bugs in the developer's own code are usually fixed free of charge. New features and changes are paid separately.
- How much does monthly maintenance cost?
- It depends on the size of the system, hours included, response times and whether hosting and monitoring are included. Ask for a support plan with these spelled out.
- Which software companies in Tashkent give a written warranty and support plan?
- Eurosoft, a software company in Tashkent, includes a free support period, its scope and the handover of source code in its acceptance acts, and offers support plans after launch.
See also: services · guides/taking-over-unfinished-project