Judge the process, not the pitch.
4UIT exists because most small businesses do not have an IT problem — they have an ownership problem. This page is how we run things when we are given that ownership: the principles, the cadences, and the tests every decision has to pass.
There are no team photos on this page. The restore tests are the biography.
An IT provider asks for the keys to everything you run, so the only honest way to introduce one is to show how it behaves with them. What follows is the operating system of the company itself — the part a headshot cannot tell you and a sales call will not.
Six rules, and what they cost us.
A principle that never costs anything is a slogan. Each of these regularly does — in revenue, in growth rate, or in easy sales not made — which is how you know they are real.
| Principle | What it means | What you notice |
|---|---|---|
| 01Boring is the goal | What it meansDrama is evidence of a process failure somewhere upstream. The estate should be quiet enough that you forget it exists | What you noticeFewer surprises, and a quarterly review that is mostly “nothing to report” |
| 02Evidence over assurance | What it meansA claim without a dated artefact behind it is marketing. Restores are tested, patches are reported, reviews are written | What you noticeYou can ask for the proof of anything we say, and get a document |
| 03The documentation is yours | What it meansAsset register, credentials, diagrams, runbooks — built in systems you hold keys to, handed over in full if you leave | What you noticeNo hostage-taking, and an exit that takes thirty days, not a lawsuit |
| 04Scope is written down | What it meansThe boundary between included and quoted lives on the sales page, not in an appendix | What you noticeNo surprise invoices, and no month-four argument about what “support” meant |
| 05Senior people only | What it meansNo tier-one script readers. The person who answers has root on your environment and the context to use it | What you noticeNo tier-one triage call before you reach someone who can actually change anything |
| 06No when it is honest | What it meansBelow ten seats we recommend a contractor. Repair jobs that are not worth it get told so. AI licences that will not pay for themselves stay unsold | What you noticeAdvice you can take at face value, because it regularly costs us revenue |
The sixth one does the most work. An advisor who never says no is a salesperson with a better title.
Structure is the product.
Tools change every few years. The way work moves through the company is what you are actually buying, and it looks like this.
See it priced and scoped
One operator, end to end
The engineer who scopes your environment is the one who builds it, documents it, and answers when it misbehaves. Context never gets lost in a handover because there is no handover.
Everything on a cadence
Nightly jobs checked each morning, patches weekly, security review monthly, restore test and business review quarterly, lifecycle annually. The rhythm is the product; the tools are interchangeable.
Vendors held at arm’s length
We resell almost nothing and take no volume kickbacks that would bias a recommendation. When Sophos or Microsoft is the right answer, it is because it is the right answer.
Small on purpose
Growth is rate-limited by the standard, not the pipeline. Every environment gets the same seven documentation artefacts and the same cadences, or we do not take it on.
Five tests, applied in order.
Every technology choice — ours or yours — runs the same gauntlet. Most vendor pitches die at the second test, which is the point of having it.
Does it reduce risk?
Availability, recoverability, security. If a change does not move one of these, it needs a very good reason to exist.
Is it boring?
Proven beats novel. We adopt technology on its second act, when the failure modes are documented and the forums are full.
Can we support it at 7am?
If the answer relies on a vendor’s support queue or a specialist we do not have, it does not go in.
Is it worth your money?
Cost against measurable effect, in writing. Plenty of good technology fails this test for a twenty-person company.
Would we run it ourselves?
Every layer we deploy for clients runs on our own estate first. Nothing ships that we have not lived with.
It is why the stack is Sophos and Microsoft rather than eleven point products, why we have not sold Copilot to most clients yet, and why this site has no chat widget. Fewer moving parts, each one owned.
What working with us feels like, on a calendar.
The full version — response targets, scope boundary, onboarding sequence — is written out on the Managed IT page, where it belongs.
The ones people actually ask.
If yours isn’t here, ask it directly — you’ll get an answer from an engineer, not a form letter.
4UIT Inc. is an independent Ottawa company, founded in 2025, owner-operated. There is no parent MSP, no franchise playbook, and no private-equity roll-up behind it — which matters because it means nobody upstream sets a ticket quota or a sales target.
No. Support is answered in Ottawa by the engineers who run the environments. We use vendors where they are genuinely better — Sophos analysts watching endpoints overnight is a good trade — but the person you speak to works here.
Small, senior, and honest about it. We take on clients at a rate the standard can survive, and we say no when we are at capacity rather than letting quality quietly stretch. If you need a 200-seat provider with an account team, we will tell you that too.
Because the company should be judged on how it operates, not on who smiles in a headshot. The processes on these pages — the restore tests, the cadences, the scope tables — are the biography.
Documentation is the answer. Every environment carries the same seven artefacts, kept current, in systems you hold keys to. Any competent engineer could pick up where we left off — which is exactly the standard that keeps us honest.
Yes. Co-managed arrangements are common — we take monitoring, patching and security while your internal person keeps the day-to-day, or the reverse. The boundary gets written down, like everything else.
Next
Twenty minutes tests all of it.
Everything claimed on this page is checkable on one call — ask for a restore test date, a sample quarterly review, or the scope table. We would rather be tested than trusted.