Winnipeg / Canada · IT support + professional services

Competent IT, without the lock-in.

Windows, Mac, and Linux support for teams that need an experienced operator without a full-time hire or a managed-service contract.

Engagement
Quoted in writing, bounded
Platforms
Windows · Mac · Linux
Ownership
Client holds every account
Based in
Winnipeg, Manitoba

The problems that bring work here

Each one is common. None of them needs a managed-service contract.

  • The full-time IT hire does not exist. The skills are needed a few days a month, the budget cannot carry a salary, and the posting has been open for quarters.
  • The fleet mixes Windows, Mac, and Linux. Each platform has to work with the same identity, files, security controls, and recovery plan instead of becoming its own unsupported island.
  • A customer or insurer wants evidence. A security questionnaire arrived, the answers exist somewhere, and nothing proves them.
  • The backup has never been restored. It reports success every night, which is not the same as working.
  • Every provider wants a multi-year retainer. For work that needs doing once, then maintained — not babysat.
  • Access, files, and identity accumulated by accident. A personal inbox became the company inbox, passwords live in a chat thread, and nobody is certain who owns the domain.

Each one is survivable on its own. Together they are the reason a lost phone, a departing contractor, or one procurement review turns into a week you did not have.

Three platforms · one standard of care

Windows, Mac, and Linux receive equal support.

Windows

Business desktops, laptops, identity, and Microsoft 365.

Troubleshooting, configuration, endpoint baselines, updates, access, migration, and recovery work for supported Windows environments.

Mac

Apple endpoints integrated into the business environment.

Troubleshooting, enrolment, identity, application, security, update, and recovery work for supported macOS devices.

Linux

Workstations and servers with an explicit operating boundary.

Troubleshooting, access, patching, service configuration, documentation, migration, and recovery work for supported Linux systems.

What gets done

Five areas of work, each quoted in writing before it starts.

Day-to-day support

On-demand help for the people actually doing the work — accounts, email, devices, files, and the odd breakage. Taken as Time & Materials with an estimate or spending cap. No contract, response-time promise, or managed-service expectation either side has to keep up.

Device and endpoint management

Enrolment, baselines, and updates for Windows, Mac, and Linux devices — so the fleet is named, patched, and recoverable instead of personally administered. Where a managed-device program already exists, the work slots into it; where one does not, a bounded one gets set up and handed over.

Infrastructure and projects

Migrations, modernization, and professional-services work with a written scope and a stated deliverable — email and identity moves, server and tooling replacements, and the cleanup of systems that grew by accident. Quoted in writing; no open-ended delivery.

ITSM consulting

Service-management process design (ITIL-shaped, sized to the team you have), PSA and RMM tooling configuration from production experience with ConnectWise-class platforms, service reporting, and runbooks that people can actually follow. See the service-operations catalogue.

Two ways to engage

Choose by how clearly the outcome can be defined.

The part most setups skip

Anyone can configure it. The question is whether it was checked.

The restore actually ran

Backup software reports success on environments that cannot be recovered. An agreed file is restored, timed, and verified, and you get a receipt naming what that test proved and what it did not.

Recovery has a named owner

Break-glass access, recovery codes, and administrator custody are placed with a named person and tested, not left in whoever set it up.

Open items stay open

Every control lands in one of four states with evidence attached. Nothing unresolved is quietly marked as done to close the engagement.

Answers trace to a system

When a customer or insurer asks how data is protected, each answer points at a setting someone read back — not at an intention.

What you are left with

A business that can operate its own systems.

The shape is fractional by design: senior capability when it is needed, without the full-time hire and without the lock-in. Every account, subscription, domain, and credential is in your name from the first day, not transferred later. The guides are written for the people who will actually use them. The engagement ends at a handoff.

There is no retainer, no monitoring contract, and no dependency built in on purpose. If you come back, it should be because the last piece of work held up.