Software licences · Subscriptions · Renewals
Choose the licences. Understand the commitment.
Adding users, comparing plans or approaching a renewal? IPCONNEX helps Montreal businesses source software subscriptions and clarify what they cover, how they are billed and when changes can be made.
Start with your users and existing subscriptions. Products, quantities, terms and service work are confirmed in your proposal.
Two terms to distinguish
Billing is not the commitment.
Billing frequency
- When payments are due. For example, an eligible subscription may be billed monthly.
Commitment term
- How long the subscription runs. Monthly payments can still be tied to an annual commitment.
Subscriptions we can discuss
Match access to the work. Make renewals easier to plan.
Review what people use before adding another subscription. Identify existing licences, needed features and any setup or support that sits outside the subscription itself.
Microsoft 365 & Teams
Compare requirements for email, office applications and collaboration. Check the selected plan’s features, any separate Teams requirements and the licences needed for each user.
Example discussionReview a new employee’s needs before assigning the same plan used by a colleague with different responsibilities.
Backup & security subscriptions
Discuss backup products such as Veeam and the security subscriptions your environment needs. Specify protected workloads and required features; configuration and recovery testing need their own scope.
Example discussionConfirm which systems a proposed backup licence covers and who will configure, monitor and test the backup process.
Meetings & collaboration
Review subscriptions such as Zoom against how your team hosts meetings and works with external participants. Check existing tools before adding overlapping products.
Example discussionIdentify who needs to host meetings and which capabilities they need, rather than assigning every user the same subscription.
Azure & cloud services
Clarify the services, billing model and administrative responsibilities for a cloud requirement. Consumption-based services need different planning from a fixed number of user licences.
Example discussionDefine who can provision cloud resources and how usage will be reviewed before starting a new workload.
Explore ongoing IT supportNeed migration, configuration or account administration? Explore systems services
From selection to renewal
Review the need. Record the terms.
Licensing decisions affect both access and future commitments. Agree on the product and commercial terms before ordering or changing a subscription.
Review users & subscriptions
Identify current products, quantities, renewal dates and the features your team needs. Note existing supplier agreements and any planned staffing changes.
Confirm the proposal
Specify products, quantities, commitment terms, billing frequency, renewal settings and costs. Separate licences from implementation, migration and ongoing support.
Coordinate changes & renewals
Agree who approves orders and changes, who maintains renewal records and how advance review is handled. Check supplier rules before changing quantities or ending a subscription.
Before you subscribe
Know what you are agreeing to.
How do we choose the right plan?
Start with each user’s tasks and the features required. Review existing subscriptions and check the exact product terms before ordering. A familiar product name does not mean every plan includes the same applications, security features or collaboration options.
Does monthly billing mean we can cancel every month?
Not necessarily. Billing frequency and commitment length are different. An annual commitment may be billed monthly. Cancellation and refund rules depend on the product and agreement, so confirm those terms and any permitted change window before ordering.
Can we add or remove licences when staffing changes?
The rules for adding seats, reducing quantities and changing plans can differ. Some reductions may need to wait until renewal or an allowed change window. Tell us about planned changes early so we can check the applicable terms; removing a user account does not necessarily end the subscription charge.
Are setup, migration and support included?
Not automatically. A licence provides the rights and features specified by the product; it does not by itself include IPCONNEX implementation or support. Account setup, migration, security configuration, backup testing and ongoing administration must be listed in the service proposal where needed.
How are renewals and supplier changes handled?
We agree which subscriptions we manage, who approves renewals and how review dates are tracked. Confirm auto-renewal settings, notice requirements and available end-of-term options. Moving an existing subscription may depend on product eligibility and supplier cooperation; keep current access and coverage in place until the transition is confirmed.
What should we share to get a proposal?
Tell us the products you use, user quantities, needed features and known renewal dates. Mention whether you need licensing only or help with setup and support. We confirm product availability, billing arrangements and costs in the proposal. Do not send passwords, recovery codes, payment details or confidential records through the enquiry form.
The next step
A new subscription or a renewal coming up?
Tell us what your team needs and what you already use. We can help define the licences and any service work required, with the terms made clear before you commit.
Products, quantities, commitment terms and costs are confirmed in your proposal.