Frequently Asked Questions
About Your IT Services

Our clients are primarily SMBs in the manufacturing, industrial, distribution, and professional services sectors, including accounting, law and engineering firms. These are organizations where a system outage at 7 a.m. can have a direct impact on operations. That is exactly the kind of situation we help prevent.

Our Before/During/After approach is built around a simple idea: understand first, deploy properly, and remain involved over time.
Before: we take the time to understand your business context, your operations, and your real challenges, not just your equipment inventory. During: we structure, deploy, and document every solution. After: we monitor, adjust and remain involved. This is how we help prevent the same problems from coming back.

Yes. We cover Montreal, Laval, the North Shore and the South Shore. Geographic proximity allows us to respond quickly on-site when the situation calls for it. Some emergencies simply cannot be resolved remotely.

Our services typically deliver the most value for companies with 10 to 150 employees. This is where our proactive management model can make the greatest difference. Below that range, IT needs are often too sporadic to justify a managed services agreement. Above it, organizations often already have an internal IT team, which we can support as needed. If your organization falls within that range, it may be worth starting a conversation.

We begin with a full assessment of your environment, including equipment, software, access rights, and vendors. We coordinate the transition with your current provider to minimize disruption. From there, we deploy our monitoring tools, introduce our team to your key staff, and take over support responsibilities. The first month is often the most revealing. That is when we uncover what was poorly documented or left unresolved.

What we see regularly in the field:
Most organizations that come to us have orphaned user accounts, unused licenses, and at least one critical system without a valid backup. That is not a criticism. It is simply what we find, and what we address.

We prioritize Canadian data residency, particularly within the Microsoft environment, where Canadian regions are available. For some third-party services, data residency depends on the provider’s own policies. In every case, we clearly document where your data is hosted and why.

Continuous monitoring, strict access management, proactive updates, and enterprise-grade monitoring tools form the foundation. We also work with a security analyst team available outside regular business hours for critical events. Security is not a one-time project. It is something we actively maintain.

In the vast majority of cases, yes. What determines performance is not the cloud itself, but the quality of your internet connectivity, your server configuration, and the selected architecture. We assess your ERP and your environment before recommending anything. A poorly planned migration creates more problems than it solves.

Public Cloud, such as Microsoft Azure, offers flexibility and budget predictability. Private cloud provides greater control and isolation, which can be relevant for certain compliance requirements. Hybrid Cloud combines both. For most of the SMBs we work with, a well-configured Microsoft 365 environment with Azure covers most core operational needs. We discuss the rest based on your specific situation.

Our agreements are typically annual. That timeframe allows us to complete the integration and improvement phases and produce meaningful results. We make sure you understand every term before anything is finalized.

Depending on the package, our agreements cover monitoring, user support, updates and proactive management of your environment. Larger one-time projects, such as a migration, a new solution deployment, or an in-depth security audit, are handled separately and quoted in advance. This way, you know what is included and what is handled as a separate project before the work begins.

Integration fees may apply depending on the complexity of your environment. They cover the assessment, the deployment of our tools, and the documentation of your assets. This one-time investment allows us to deliver structured service from day one and avoid managing unknowns later in the relationship.

You have access to a team that knows your environment. This is not a call centre with rotating, anonymous technicians. The people who support you understand your configuration, your critical applications, and your history. You do not have to re-explain your context every time you need support.

You can submit a support request by email, by phone, or through our client portal, whichever works best for your team. Every request is logged, prioritized, and tracked through to resolution. You receive a confirmation of receipt and updates as the request progresses.

Security incidents do not happen only between 9 a.m. and 5 p.m. Continuous monitoring means alerts can be tracked, analyzed, and escalated by a Security Operations Centre (SOC), even on a Friday evening. For you, that means critical events can be addressed quickly, rather than waiting until Monday morning.
What we see regularly in the field:
Most ransomware attacks are triggered at night or on weekends, when teams are less likely to be watching. Active detection outside of regular business hours can make a significant difference.

A backup is your spare tire. It can help you recover when a file is corrupted, deleted, or lost. A Disaster Recovery Plan (DRP) is the manual that tells you how to use that spare tire in a real emergency: who does what, in what order, which systems to restore first, and which critical dependencies to account for. One without the other is not enough.

Quebec’s Law 25 does not require perfection. It requires reasonable measures and the ability to demonstrate them. In the event of an incident, what matters is the documentation of your controls and the rigour of your processes. Managed cybersecurity helps you structure these measures consistently and maintain the documentation needed to demonstrate them if required.

In a properly configured Microsoft environment, yes. Canadian regions are available. For certain third-party services, data residency depends on the vendor’s own policies. What we commit to is documenting and explaining each choice clearly, so you know where your data hosted and why.

The impact is rarely limited to IT. An attack can paralyze your operations for days, trigger mandatory legal notifications to clients and partners, generate significant recovery costs, and have a lasting impact on client trust. The goal of a proactive approach is to reduce the likelihood of an incident and shorten recovery time if one occurs.

In the vast majority of cases, yes. Number portability is planned in advance to minimize interruption for your clients and partners.

There is nothing more frustrating than a dropped call with an important client. That is why we do not connect anything until we have assessed your network, configured Quality of Service (QoS) to prioritize voice traffic, and identified congestion points. A poorly prepared network will deliver disappointing results, regardless of the platform chosen.

Yes. Employees can use their business number from their computer or mobile phone, wherever they are. For clients and vendors calling in, the experience remains the same. For your organization, communication management remains centralized.

Teams can become your unified platform for calls, meetings and messaging. Telephony-Teams integration is planned based on your current Microsoft environment and working habits. The goal is simple: one tool, less friction every day.

Savings come primarily from reduced long-distance costs, the elimination of traditional telephone infrastructure fees, and more predictable monthly billing. The exact amount varies based on your current usage, but your cost structure becomes more transparent.

AI must be governed by a clear framework: access controls, data segmentation, and isolated environments. We do not deploy an AI tool without first defining what it can access, what it can do, and who is accountable for it. When personal information is involved, Quebec’s Law 25 also needs to be considered.

This is one of the most concrete use cases. When critical processes are documented and partially automated, the departure of a key employee is less likely to create an operational gap. The way things are done is no longer stored only in one person’s memory. It is reflected in documented workflows and systems.

In practical terms, AI ROI does not appear as a separate “AI Profit” line on a balance sheet. You notice the gain when, for example, an employee stops spending four hours a week copying data from an Excel file into your CRM, or when a report that used to take a full day is ready in ten minutes. We prioritize use cases where benefits can become visible early, not theoretical gains that may only appear years later.

Transparency comes first. We clearly explain what AI does, what it does not do, and where human judgment remains essential. AI automates repetitive, low-value tasks so employees can focus on work that requires analysis, expertise and decision-making. Change management is part of our implementation approach, not an optional add-on.

Copilot respects Microsoft 365 permission settings. A user can only see content they already have permission to view. That said, here is what we see regularly: organizations activate Copilot without reviewing their permissions beforehand. The result is that confidential documents can become visible to people who should not be able to see them, not because Copilot failed, but because access rights were too broad or had never been properly cleaned up. That is why we always start with a permission review before activating Copilot.

Adoption is not measured only in weeks. It is measured by concrete uses that become part of your team’s working habits. A well-targeted initial training session can deliver quick results on a few specific tasks. Continuous improvement follows as your teams discover what genuinely saves them time.