IT operations, run quietly

IT is the thing that
gets left behind.
I pick it back up.

Running a growing team is already a full-time job on its own. I handle the email, backup, devices, and offboarding underneath it — so it stops being anyone's problem but mine.

Book a short call See what's covered
Sound familiar

Nobody signed up to own this.

IT usually isn't a dedicated role at small, growing teams — it's whatever gets bolted onto someone's actual job. These are the gaps that show up almost every time.

01
No structured email backupIf an inbox is deleted or compromised, there's nothing to restore from.
backup
02
No real storage policyFiles live wherever someone happened to save them — personal drives, random shares, old laptops.
storage
03
No formal onboardingNew hires get access to things ad hoc, and nobody's tracking what they were actually given.
onboarding
04
No formal offboardingPeople leave, and their accounts, files, and access just... stay open.
offboarding
05
No one actually owns itIT isn't anyone's full-time job, so it only gets attention after something breaks.
ownership
What's covered

One person, the whole stack.

Not a helpdesk queue. One point of contact who already knows your setup and keeps it running without being asked.

$ mail --backup daily

Email & backup

Scheduled backup for mailboxes and files, so a deleted inbox or a bad click isn't a lost afternoon.

$ device --enroll

Device management

Laptops and phones enrolled, encrypted, and managed centrally — set up once, remote after that.

$ user --add / --remove

Onboarding & offboarding

A repeatable checklist for day one and last day, so access is granted deliberately and revoked completely.

$ access --review

Security & access

Sign-in policies and access controls tuned to how your team actually works, not locked down by default.

$ storage --structure

Storage & policy

A shared drive structure per team or brand, with clear rules for what lives where.

$ support --watch

Ongoing support

Direct line for whatever comes up — a password reset, a new hire, a weird login alert — handled without a ticket number.

Currently keeping IT running for
R Group Hayat Infrastructure
How it works

Three steps, then it's quiet.

No lengthy onboarding process. Most of this can start within a week.

Step 1

Audit

A short look at how your team currently handles email, devices, storage, and access — no changes made yet.

Step 2

Set up

Backup, policies, and onboarding/offboarding checklists put in place around your existing tools.

Step 3

Maintain

Ongoing monitoring and support, so it stays handled instead of drifting back to nobody's job.

Sayed Sadiq, Founder of Knightworks
SS
Sayed Sadiq
Founder, Knightworks
MSc Cybersecurity — Coventry University, UK
Who's behind this

One person. No layers.

I'm an IT analyst with a Master's in Cybersecurity from the UK, currently managing Microsoft 365, device policy, and onboarding/offboarding for a growing list of companies — from single-site teams to multi-brand groups running several ventures under one roof.

You get one person who already knows your tenant, not a rotating support queue. When something needs fixing, I fix it. When something needs setting up properly the first time, I set it up properly the first time.

Companies managed5+ ongoing
Response timesame day
StackM365 / Entra ID / Intune
Contractsmonth to month
Get in touch

Let's take IT off your plate.

A short call is usually enough to see where the gaps are and whether this is a fit.

Email me Book a Google Meet