Software update agreement
A software update agreement provides access to specified updates and releases for a defined period. It may accompany a licence or be sold as a recurring service. Support, installation and major upgrades are included only when the contract says so.
Prepared with AIContent updated
Define updates and licence rights
An update agreement can supplement a software licence or form part of a subscription. State the products, versions, period and covered fixes or enhancements. Usage rights, support and access to a new major release are separate matters.
Only the agreed work is included. Installation, testing, migration and integration changes can be separate tasks. The agreement does not make every release compatible or automatically alter an existing licence.
What does the agreement cover?
Illustrative scope: the actual contract determines the entitlement.
- Bug fixes
- Covered fixes during the agreed term
- Major releases
- Only if included in scope
- Support and installation
- Separate unless expressly included
A software update does not automatically change pricing or licence terms. Communicate contractual changes separately.
SaaS and locally installed software involve different work
A hosted SaaS provider normally operates the application while customers retain relevant access and configuration responsibilities. With locally installed software, the customer may need to manage installation and the supported environment. Establish the actual tasks rather than using SaaS as a name for every software licence.
Maintenance, support and updates can be bundled or sold separately. Define supported versions, technical-change communication and defect handling. The actual service and contract establish the boundaries.
A price is agreed rather than standard
Pricing can use a fixed fee or an expressly agreed basis. As an illustration, 20% of a £100,000 licence price gives a £20,000 annual agreement fee. Three unchanged annual payments total £60,000. That total does not establish that every future cost or version is covered.
Updates already included in an active subscription price do not create additional MRR. A separate eligible recurring service can contribute its normalised value; a one-off upgrade is different. Avoid counting bundled services twice.
Separate delivery, price changes and recognition
A technical update agreement does not itself give unrestricted authority to raise prices or change every contract term. Assess the basis, information and effective date under the actual agreement and applicable requirements. Technical and commercial changes have their own conditions.
Revenue recognition follows the service obligations and relevant accounting framework. An evenly delivered recurring service can differ from a distinct version release or installation. Invoice date, payment and normalised subscription value are separate measures.
Review delivery and actual customer outcomes
Keep release histories and customer entitlements traceable, and establish testing and rollout responsibilities for affected environments. Monitor faults, support work and changing needs. A document does not replace actual delivery or technical checks.
Assess costs and observed customer outcomes when evaluating the agreement’s economics. More upgrades or higher charges can involve additional development, selling and support costs. The agreement does not guarantee lower churn, higher CLV or adequate cash.
Questions and answers
Are updates the same as support?
No. Updates concern covered fixes or versions, while support concerns agreed assistance. They can overlap or be bundled; check the actual scope.
Are all future releases included?
Only if the agreement covers them. Establish major-release rights, installation and migration. The agreement’s name does not prove unlimited entitlement.
How does an update service contribute to MRR?
An eligible active recurring service can contribute its normalised monthly value. Do not count bundled services twice or include one-off upgrades as recurring value. Recognition and payment are assessed separately.
Does an update agreement automatically permit price changes?
No. The basis, information and timing depend on the agreement and applicable requirements. Releasing a version and changing a price are different actions.
Can the agreement raise CLV?
Assess actual demand, retention and included costs. Higher charges can accompany greater service and selling costs. A higher payment alone does not prove a larger lifetime contribution.
