IT outsourcing

IT outsourcing means handing some or all of your organization’s technology work to an outside team while you keep ownership of the accounts, passwords and records that run the business. It suits owners, office managers and CFOs at small and mid sized organizations who have outgrown “the person who is good with computers” but are not ready to hire a full internal department. You can outsource everything, only selected pieces such as devices or networks, or share the work with an internal IT person. Canada Create is a Toronto agency serving organizations across Canada, and this page explains how to make the outsourcing decision well.

Contents

• Should your organization outsource IT?
• Full, partial and co managed outsourcing
• What to keep in house
• Ownership of admin accounts, passwords and records
• Scoping the work before anyone signs
• Onboarding an outsourcing partner
• Service levels written down and measured
• Handover readiness from the first day
• How outsourced IT connects to the rest of your technology
• Privacy rules and data location to plan for
• How we take on outsourced IT
• What IT outsourcing costs
• How to choose an IT outsourcing partner
• Your next step

Should your organization outsource IT?

The question usually arrives sideways. An office manager realizes half her week goes to resetting passwords and chasing the printer vendor. A CFO sees four separate invoices for laptops, a phone system, a firewall subscription and a freelance technician, and nobody can explain how they fit together. An owner hears that the one person who set up the server is retiring in spring. Each of these is a sign that technology work has spread across the organization without anyone deciding who owns it.

Signs the work has outgrown the current arrangement

• Staff lose time waiting for someone who “knows the system” to come back from lunch or vacation.
• New hires sit for their first morning without a laptop, an email address or access to shared folders.
• Nobody can produce a current list of who has administrator rights to email, the website, the accounting system and the firewall.
• The same problems come back every few weeks because fixes are quick patches rather than causes found and removed.
• Projects such as moving files to the cloud or replacing ageing laptops keep slipping because daily interruptions eat the time.

Hiring versus outsourcing

A single internal hire brings one person’s skills, one person’s vacation calendar and one person’s knowledge walking out the door if they move on. An outsourced team brings shared coverage and a broader set of skills, but it does not sit in your hallway and does not know your line of business software on day one. Many smaller organizations find outsourcing fits better than a hire; larger ones often keep one internal person and outsource around them. Neither choice is right by default, and a fair partner says so.

Full, partial and co managed outsourcing

Outsourcing is not one product. The shape you choose decides what you pay for, what your staff still do and how much control stays inside the building.

Full outsourcing

The outside team handles devices, user accounts, Microsoft 365 or Google Workspace, the office network, backups, vendor coordination and planned projects. Your staff call or write to one place for anything technical. This works for organizations with no internal technical person at all, such as a professional office, a clinic or a nonprofit with a small administrative team. The trade off is dependence: you need the documentation and admin access in your name so that the arrangement never becomes a trap.

Partial outsourcing

Some organizations hand over only the pieces that cause the most friction. Common splits include laptops and phones only, Microsoft 365 administration only, the office network and Wi-Fi only, backups only, or a defined project such as an office move or a migration. The rest stays with whoever handles it now. Partial outsourcing is a sensible first step when you want to test how an outside team works before widening the scope, and it keeps costs tied to a clear piece of work.

Co managed IT with an internal person

Co managed IT pairs your internal IT person with an outside team. The internal person keeps the relationships, the knowledge of your specialized software and the judgment calls; the outside team takes routine requests, after hours coverage through agreed channels, patching, documentation or projects the internal person never has time for. The key is a written split of duties so nobody assumes the other side handled something. Co managed setups also give the internal person a bench of colleagues to ask, which helps with retention.

What to keep in house

Outsourcing the work is not the same as outsourcing the decisions. A few things belong inside your organization regardless of the model.

Decisions and budget

Which software the organization standardizes on, how much to spend on hardware replacement, whether staff may use personal phones for work email, and who approves new subscriptions are business decisions. An outsourcing partner should give options and costs in writing, but a named person on your side signs off.

A local point of contact

Someone in the office, often the office manager or operations lead, should be the internal contact who knows how to raise a request, approves new accounts, and can describe a problem on site. This person is not doing technical work; they are the bridge between staff and the outside team.

Knowledge of your specialized systems

Every organization has software that only it uses: a practice management system, a dispatch tool, an estimating program, an inventory database. The vendor of that software usually handles its support. Your outsourcing partner coordinates with that vendor, but an internal power user who knows how the system is used day to day remains valuable and should stay.

Ownership of admin accounts, passwords and records

This is the single most important part of any outsourcing arrangement, and the part most often skipped. If the outside team holds the only administrator password to your email tenant, domain registrar or firewall, changing providers later becomes painful and slow.

Admin accounts in your organization’s name

Every core system should have an administrator account owned by your organization, with sign in protected by multi factor authentication tied to someone on your staff. The outsourcing partner works through its own named admin accounts that you can see, review and switch off. No shared “admin” login that only the provider knows.

The password vault

Credentials for shared accounts, vendor portals and devices belong in a password manager owned by your organization, with the outsourcing partner given access to the entries it needs. If the vault is in the provider’s name, your passwords live in someone else’s house.

Domains, DNS and licensing accounts

Your domain name, DNS settings and software licensing accounts should be registered to your organization, with billing visible to your finance lead. These are the keys to email, the website and many sign in systems. Many owners discover during a dispute that a former provider registered the domain in its own name years ago.

Documentation you can read

The partner should keep written records of your network layout, device list, user list, vendor contacts and how each system is configured, stored somewhere you control. Ask to see it. If the documentation only exists inside the provider’s own systems, it is not really yours.

Scoping the work before anyone signs

A good outsourcing proposal starts from an accurate picture of what exists. Without it, quotes are guesses and surprises turn up in the first month.

The asset list

List every laptop, desktop, phone, tablet, printer, server, network device and piece of shared equipment, with its age, who uses it and where it sits. Include equipment at second locations and at staff homes if it belongs to the organization. Ageing hardware affects scope because older machines take more effort to keep running.

The admin account list

Write down every system that has an administrator: email and productivity tools, the domain registrar, the website host, the firewall, the Wi-Fi controller, the accounting software, the phone system, the backup service. Note who holds the admin login today. Gaps here are common and are worth closing before handing anything over.

The vendor list

Record each technology vendor with its account number, support contact, what it provides and when its subscription bills. This lets the outsourcing partner coordinate vendors on your behalf instead of you passing messages back and forth.

Users, roles and locations

How many people use technology, which roles need which access, and how many sites or home workers are involved all shape the quote. A twenty person office on one floor is a different job from twenty people spread across three branches and their kitchens.

Onboarding an outsourcing partner

The first stretch of an outsourcing arrangement is where trust is built or lost. A careful onboarding avoids disruption to staff who just want their email to work.

Discovery and verification

The new partner checks the asset, account and vendor lists against reality: signing in to each system with access you provide, confirming backups actually run, noting unsupported software and finding accounts belonging to people who left. The findings go into a written onboarding report with items ranked by priority.

Handover from the previous provider

If someone else held the work before, a polite written request for admin credentials, documentation and open issues goes out early. Your organization, as the owner, makes that request; the new partner helps you know what to ask for. Where a former provider is slow, ownership of the domain and core accounts is the first thing to secure.

Cleanup and standard setup

Onboarding usually includes removing stale accounts, putting multi factor sign in on every admin, setting a standard build for new laptops and recording how a new hire is set up. These steps reduce the repeat requests that frustrate staff.

Telling staff how to ask for help

Staff need one clear way to raise a request, what information to include and what happens next. A one page guide pinned in the shared channel does more than a long email nobody reads.

Service levels written down and measured

An outsourcing arrangement should describe in writing what the partner does, how requests are prioritized and what is outside scope. The specific service levels are agreed between you and the partner in the signed agreement, not promised in marketing copy.

What the written schedule should cover

• Which systems, devices and locations are included, and which are not.
• How requests are raised and how urgency is decided, for example a whole office offline versus one person’s mouse.
• What counts as routine work in the monthly fee and what is quoted as a separate project.
• Who on your side may approve new accounts, purchases and changes.
• How and when the partner reports back to you.

Measuring what matters

Counting tickets closed tells you little on its own. More useful questions for a monthly review: which problems came back, and were their causes removed? Which requests took several rounds before they were solved? Which devices or systems generate the most requests and should be replaced? Are new hires ready on their first morning? A good partner brings these patterns to you without being asked.

Asking the staff

The people who use the technology know whether the arrangement works. A short internal check every few months with the office manager and a few staff will reveal friction that reports miss, such as a request process that feels slow or a recurring printer issue nobody escalated.

Handover readiness from the first day

The time to plan for changing providers is at the start, while everyone is getting along. A partner confident in its work does not mind you being ready to move on.

What handover readiness looks like

• A current export of documentation, device lists and configuration notes, available to you on request.
• Admin access to every system already held by your organization, so nothing needs to be “given back”.
• Licences purchased in your name or transferable, rather than bundled under the provider’s own account.
• A written list of any equipment or software owned by the provider and installed on your premises.
• Clear steps for removing the provider’s own accounts and tools when the arrangement ends.

Why this protects both sides

Owners sometimes fear asking these questions will sour the relationship. In practice, a clean handover plan removes the bargaining chips that cause disputes. You stay because the work is good, not because leaving would be a mess.

How outsourced IT connects to the rest of your technology

IT outsourcing sits beside other services you may already buy. Our managed IT services page describes the ongoing day to day care of users, devices and accounts; this page is about deciding how much of that work to hand out and under what arrangement. If you want a roadmap, a budget or an independent view before choosing, IT consulting projects and advice are often the right first step.

Two pages in this batch go deeper on specific pieces you might outsource: Microsoft 365 support, for email, Teams and file sharing administration, and Data backup, for what to copy, where copies live and how restores are tested. Security planning sits with our cyber security services, and organizations that want ongoing security work alongside outsourced IT can read about managed security services. Your website lives on business website hosting that your outsourced team should know about, even if a different team manages it. Front desk calls that interrupt staff can be handled by an AI receptionist that answers the phone, and customer records belong in a CRM such as CS+, which we set up and connect as part of our CRM setup and automation work.

Privacy rules and data location to plan for

An outsourcing partner with administrator access can see your organization’s data, so privacy obligations come along with the decision. The partner works for you, but the legal responsibility stays with your organization.

Breach reporting under PIPEDA

PIPEDA puts the reporting duty on your organization, not on the provider: when a breach of security safeguards poses a real risk of significant harm, the Privacy Commissioner of Canada and the individuals involved must be told, and a record of every breach must be kept. Your signed agreement with an outsourcing partner should say how the partner tells you about a suspected incident, what it hands over and how it helps you keep those records.

Quebec and Ontario health information

Organizations operating in Quebec have additional obligations under Law 25. Health custodians in Ontario, such as clinics, follow PHIPA when they handle personal health information. If either applies, raise it at the scoping stage so the partner’s access and processes are set up with it in mind.

Where your data lives

Some organizations prefer, or are required, to keep data in Canada. Microsoft and other cloud providers offer Canadian data centre regions, and the region a tenant uses is something to confirm during onboarding. Software licences are paid to the vendor and shown separately from our fees. This is a marketing observation, not legal advice.

How we take on outsourced IT

Canada Create follows the same plain steps for any outsourcing arrangement, whether you hand over everything or a single piece.

A free review

We start with a conversation about what prompted the question, how many people and locations you have, what is working, what is not and who does the work today. You do not need a perfect asset list for this call; rough numbers are fine.

A custom proposal

You receive a written proposal describing the model (full, partial or co managed), the systems in scope, how requests are handled, what is included in the regular fee, what is quoted as a project, and fees quoted in writing. Licences and hardware appear as separate lines.

Onboarding

Onboarding follows the steps above: discovery, verification of admin access, cleanup, documentation and a short staff guide, with all core accounts confirmed in your organization’s name.

Monthly reporting

Each month you receive a plain summary: requests handled, recurring issues and what was done about them, devices or systems that need attention, and projects in progress. Accounts and documentation stay yours throughout.

What IT outsourcing costs

Every IT outsourcing arrangement is quoted in writing after the free review. There is no single price because organizations differ in how much they hand over and how complicated their setup is.

Common pricing models

• Per user: a monthly fee for each person supported, covering their devices and accounts. Simple to budget when headcount changes.
• Per device: a fee for each laptop, server or network device managed. Useful where shared equipment outnumbers people, such as a warehouse or a lab.
• Project based: a fixed scope such as an office move, a migration or hardware replacement, quoted separately.
• Co managed blocks: an agreed share of work alongside your internal person, priced by the duties taken on.

What drives the quote

Number of users and devices, number of locations, the age of the equipment, how many specialized systems need vendor coordination, how much cleanup onboarding requires, and whether after hours coverage through agreed channels is part of scope. When comparing quotes, look at what is excluded as closely as what is included; a low per user figure with a long list of extra charges can cost more than a higher figure that covers the real work.

How to choose an IT outsourcing partner

Comparing outsourcing providers is easier when you ask the same questions of each and listen for specifics rather than slogans.

Questions worth asking

• Who owns the accounts? The answer should be you, including admin access to email, the domain, the firewall and every licence.
• Where is our documentation kept, and can we have a copy at any time?
• How do you decide what counts as routine work versus a separately quoted project?
• How would you work with our internal person, if we keep one?
• What does your monthly report show, and can we see an example with private details removed?
• How do you coordinate with the vendors of our specialized software?
• What happens to your own tools and accounts on our systems if the arrangement ends?

What to be cautious about

Be wary of a provider that wants to register your domain or licences in its own name, will not show its documentation, bundles hardware into the fee without listing it, or answers the ownership question vaguely. These are the arrangements that become hard to change later.

Your next step

If you are weighing whether to outsource IT, or whether your current arrangement is set up fairly, book a free review. Bring whatever you have: a rough count of staff and devices, the vendors you pay and any recurring problems that frustrate the team. Canada Create will come back with a written view of which outsourcing model fits and what it would cost, quoted in writing. Call (416) 273-9030, Monday to Friday, 9 am to 6 pm, and Saturday, 10 am to 2 pm. After hours, our 24/7 AI agent answers the toll-free line, +1 (800) 808-9235, and we’ll follow up the next business morning. You can also reach us through our contact page. Our office is at 126 Willowdale Avenue, Suite 3, Toronto, and you can read more about our agency before you call.