Subscription mechanics
Set the subscription term, renewal steps, price review process and cancellation notice. Customers and sales teams should know when a commitment starts and how it ends.
Technology and digital agreements
SaaS, Software and Digital Contracts Drafted Properly
In technology deals, the argument is rarely about price. It's about who owns the code and who carries the downtime. Evergreen Covenants Ltd. drafts terms that make ownership, service levels, subscription mechanics and exit rights clear to commercial and technical teams.
terms / product / service
Clear rights. Clear responsibilities.Ready for review
For start-ups and founders
Technology NDAs that protect the useful detail
A technology NDA should cover what people will actually share: architecture, datasets, pricing models, product plans and investor discussions. It should also say who may see that material and what they may use it for.
One-way terms can suit a focused disclosure. Mutual terms fit discussions where both sides share confidential material. Details matter. Evergreen Covenants Ltd. sets out permitted disclosures, a workable confidentiality period and how retained general knowledge is treated.
Founder roles and ownership need their own terms. See founder and ownership agreements when the discussion goes beyond confidentiality.
Subscriptions and software rights
SaaS agreements and software licensing
SaaS agreements UK businesses use should match the way the product is sold and supported. A clear clause map helps teams find the terms that matter before a customer signs.
Acceptable use and data handling
Define permitted users, usage limits and responsibilities for customer data. Address integrations with customer systems so each side knows what it must maintain.
Service levels and remedies
Describe uptime measurement, planned maintenance windows and remedies for repeated service failure. Link the service promise to support capacity and the product's real operating model.
Software licence scope
For on-premise or embedded software, specify permitted users, territory, term and sublicensing rights. Software licensing agreements should separate the licence from support and maintenance duties.
Support with defined boundaries
IT support and maintenance agreements
IT support contracts work best when the service desk knows what to do next and the customer knows what sits outside the fee. Set the operating rules before the first incident.
Response and resolution
Separate acknowledgement targets from resolution estimates. Set priority levels that reflect business impact.
Clause prompt · Severity levelsEscalation and cover
Name escalation steps, service hours and any out-of-hours cover. Avoid implied round-the-clock availability.
Clause prompt · Service hoursMaintenance and change
Agree patching duties, planned maintenance notice and approval for changes that may affect live systems.
Clause prompt · Change approvalExclusions and review
Set fair exclusions for unsupported systems and customer-side faults. Add review and renewal dates for legacy terms.
Clause prompt · Scope review
Projects change; contracts should say how
Web and app development contracts
A web development contract should tell both sides what happens when scope moves, testing finds a defect or a project stops before launch. Projects change.
Web development contracts
Break work into phases, record acceptance criteria and set a change-control route. Address hosting, domain control and handover of access credentials on completion.
App development agreements
Define platform scope, testing responsibilities and defect correction periods. Deal with app-store submissions, third-party services and maintenance after release.
Scope, price and change
Set how new requests are estimated and approved before work begins. This keeps mid-project changes visible instead of burying them in informal messages.
Acceptance and exit
Specify testing windows, what counts as a defect and warranty periods after launch. Cover termination for convenience and payment for usable work already completed.
Clear ownership for digital work
Intellectual property assignment for agencies
Digital agency contracts should separate project deliverables from tools and know-how that existed before the job. The agreement can then assign the agreed rights while preserving a practical way to reuse background materials.
Rights assigned to the client
State which deliverables transfer and when the transfer takes effect, often on payment. Identify the material covered instead of relying on a broad label such as "all work".
- Identify copyright and design rights in agreed deliverables.
- Address moral rights waivers where appropriate.
- Record any third-party or open-source components and their terms.
Tools retained by the agency
Keep reusable frameworks, templates and general know-how distinct from client-specific work. A licence-back can give the client the rights needed to use deliverables without transferring every underlying tool.
- List background IP that stays with the studio or agency.
- Grant a defined licence for embedded or necessary tools.
- Confirm subcontractor contributions are covered by written terms.
Make the next deal easier to run
Get your technology terms ready for the next deal
Tell Evergreen Covenants Ltd. what you're building, who will use it and how you charge. We can help bring sales, product and support terms into a consistent set.