Trois-Rivières, serving all of Quebec 450 231-3836 info@oktosolutions.ca
FR

Terrebonne

IT services in Terrebonne: backup for the person already running your IT

You have someone in-house. That person knows your software, your staff and the story behind every workstation. That person is also alone, and it shows the day vacation starts. OKTO Solutions does not take the seat: we cover what one person cannot carry, from Trois-Rivières, about 124 km from Terrebonne.

Advisor standing and presenting a diagram on a laptop to a seated client

In Terrebonne, an SMB that already has an in-house IT person can keep that person and add backup through co-managed IT. A written split states what the person retains and what OKTO Solutions takes on: continuous monitoring, patching, cyber defence, projects and absence coverage. The service is offered remotely from Trois-Rivières, about 124 km away.

How do you back up an IT lead in Terrebonne without replacing that person?

A Terrebonne business that already has someone on IT does not need to replace that person to cover what slips through. OKTO Solutions offers its services to SMBs in Terrebonne from its office in Trois-Rivières, about 124 km away, in co-managed mode: a written split of responsibilities between the in-house resource and OKTO’s team. The mandate starts with what the person in place keeps, most often the relationship with employees, the line-of-business software and the decisions. OKTO takes continuous monitoring, patching, cyber defence, backups, projects and vacation coverage. The IT lead consults the same alerts, the same tickets and the same documentation as OKTO’s team, in OKTO RMM and OKTO PSA. Administrator accounts, licences and data stay in the company’s name. Work is done remotely, with visits scheduled as needed. OKTO has no premises in Terrebonne and stations no technician there.

Where it starts

How can you tell a lone IT person needs help?

It is never about skill. It is about the hours in a week, and about what happens when that person is away.

Nobody is watching at night

A backup fails at 11 p.m., a server runs short of space on Saturday. Your technician finds out on Monday, along with everybody else.

Projects have waited for months

Passwords, printers, new accounts: the day goes there. The migration planned for spring is still on the list in the fall.

Everything lives in one head

Two weeks of vacation become a risk. A resignation would become a crisis. No organization should lean that hard on a single person.

If you have nobody in-house, this is the wrong model. Look at our managed IT services instead, where OKTO takes on the whole thing.

The dividing line

How is it decided who does what?

In writing, before anything is touched. Co-management fails when a task belongs to no one, or when two people do it twice.

We begin by meeting your IT lead. Together we draw up what is covered today and what has been sitting for lack of time. Nothing goes to management that your lead has not seen first. Next comes the split, line by line: support, patching, accounts, security, backups, network, projects. The result is a short document management can read in ten minutes.

That document moves. It is reviewed at follow-up meetings, since the right distribution changes when the team grows or a project shifts priorities. Three starting points are common: monitoring and security only, first-line support on top of that, or one-off backup for a project or a leave.

The split document: each area lands in the column of whoever carries it, and nothing is left without an owner.

What does not change

What stays in your hands?

More than people expect. Co-managed IT puts a team behind yours. It does not move the ownership of your IT.

  1. Administrator accounts. They stay in your company’s name. Ours are tied to named individuals, so they can be withdrawn at any time.
  2. Licences and subscriptions. Attached to you, not to your provider.
  3. Domain names and data. Same rule, no exception.
  4. Documentation. The documentation of your environment is yours, and your IT lead reads it just as we do.
  5. The relationship with employees. Your in-house person is the one who knows the people and the quirks of each team.
  6. Decisions. Your lead approves maintenance windows, rules on exceptions and sets project priorities.
The real test. A co-managed agreement has worked when, six months in, your IT lead is the one defending it in front of management.

The same keys

Does your IT lead see what we see?

Yes, and it is a condition. A provider that keeps its screens to itself creates a black box, and the person in place ends up feeling watched instead of supported.

So your lead works in the same two platforms as our team. OKTO RMM handles monitoring and remote execution. OKTO PSA holds the tickets and the history. A ticket can move from your lead to us and back again without information getting lost on the way. When a network, server or security problem has your lead stuck, escalation needs no justification.

Both tools are developed by our team. A report or an access your lead needs can be adjusted without going through a foreign vendor. And if management wants an IT roadmap and a predictable budget, the vCIO module can be added to the agreement.

One ticket console: the in-house lead and the OKTO technician work in it at the same time.

The ground

Terrebonne, about 124 km from our office

Terrebonne is the seat of the Les Moulins regional county municipality, in Lanaudière. Autoroutes 25 and 640 cross its territory.

At that distance, co-managed IT has a plain advantage: you already have the on-site presence. Your in-house person sees the staff, handles the hardware and knows the building. What is missing can be delivered remotely, namely monitoring on evenings and weekends, specialists to escalate to and extra hands for projects. We have no office in Terrebonne, and our trips start from Trois-Rivières, by appointment.

The Base, Standard and Complet plans also serve as the base of a co-managed agreement. If security is what brings you here, the managed cybersecurity page describes that part, which fits well with a team already in place. Other territories are gathered on the service areas page. To talk it over, use the contact page, ideally with your IT lead in copy.

Questions and answers

Your questions about co-managed IT in Terrebonne

Will co-managed IT end up replacing our technician?
No. The mandate opens with the list of what your in-house person keeps. We take what holds that person back: monitoring, patching, security alerts, repetitive requests. Several co-managed agreements exist precisely to keep someone who was burning out.
Can we hand you monitoring and security only?
Yes, and it is the most common way in. Your technician keeps all contact with employees. We take continuous monitoring, patching and cyber defence. The agreement can widen to first-line support later, or shrink if you hire.
Who holds the administrator accounts in a co-managed agreement?
You do. Administrator accounts, subscriptions, domain names and data stay in your company’s name. Our access is tied to named individuals and can be withdrawn at any time. The documentation of your environment belongs to you.
What happens if our IT lead resigns?
Nothing is lost, because the documentation, the access and the history of interventions are already shared. Our share can expand while you recruit, then return to the planned split once the new person has started.
Do you travel to Terrebonne?
When needed, by appointment. The work is done remotely and visits are scheduled when they are necessary. Our office is in Trois-Rivières, about 124 km away, and we have no premises in Terrebonne. Your in-house person remains the on-site presence.
How long is the commitment?
The initial commitment is 12 months. After that the agreement renews monthly, with 60 days of notice. Scope and split are written from the start and reviewed at follow-up meetings.

Backup for your IT in Terrebonne?

We meet your IT lead first. We look at what is covered today, then propose a dividing line you can accept, change or turn down.

Reviewed by , president of OKTO Solutions · updated