Is everything included?
No. Recurring support and administration can fit monthly care; migrations, broad deployments, formal reviews, and specialist work are scoped separately.
Practical questions
Use these boundaries to decide what belongs in a first conversation and what must be confirmed in writing.
Fit
The service is direct IT care for Canadian professional and small-business teams; it is not white-label fulfilment.
No. Recurring support and administration can fit monthly care; migrations, broad deployments, formal reviews, and specialist work are scoped separately.
No response-time commitment is published here. Required hours, channels, urgency handling, and written commitments must be confirmed during fit.
The website and introduction path are English/French. Delivery language needs are confirmed before engagement.
Working safely
The introduction should contain business context, never credentials.
Team size, locations, important tools, recurring interruptions, an upcoming change, and communication preferences.
Passwords, recovery codes, tokens, private keys, sensitive client data, or unrestricted system exports.
The business must identify appropriate owners for access, cost, downtime, procurement, and exceptions.
Scope
A fit conversation establishes the environment and boundaries before implying coverage.
Microsoft 365, identity, collaboration, and workplace context are central, but tenant condition and exact responsibilities must be understood.
Vendor coordination can be part of care. Another provider’s contract, response, product, or delivery date cannot be guaranteed.
A concise discovery separates urgent ownership gaps, recurring care, project work, and specialist needs.
If the boundaries fit, prepare a short service brief without credentials.
Book a white-glove introDescribe the interruption, the change ahead, and how your team prefers to be kept informed. A short note is enough to begin a service-fit conversation.