Name what is being supplied
A subscription usually grants access under defined conditions. Custom development may create deliverables with negotiated ownership. Implementation work may configure someone else’s product. The agreement should identify which of these you are buying.
Check the boundaries of use
Ask who may use the software, for what purpose, in which environments and for how long. Confirm whether transfers, sublicensing or resale are permitted. Never assume that paying an invoice transfers every intellectual property right.
Plan the end before the beginning
Understand what happens when a subscription expires or an engagement ends. Consider data export, access to documentation, third-party dependencies and support. Exit arrangements are easier to agree before the system becomes essential.
Keep the evidence together
Store the agreement, licence records, authorised users and renewal dates in a controlled location. Make responsibility for renewals explicit. A clear record helps procurement, finance and technical teams understand the same arrangement.
Practical guidance. Each engagement is tailored to the circumstances; specialist legal, tax or regulatory questions should be addressed with an appropriate professional.