Senior IT help, beside the team you already have.
Most companies your size don't need another IT department. They need one experienced person who owns the parts that go badly wrong: the servers, the cloud bill, who can get into Microsoft 365, and whether the backups would actually restore. We do that work every month, alongside whoever handles the day to day.
- Servers, virtualization and the end-of-support roadmap
- Cloud architecture, cost and migrations
- Microsoft 365 identity, access and email security
- Backup verification and a quarterly restore test
- Security posture, patching and the risk register
- Project scoping, delivery and documentation
- Day-to-day user requests and password resets
- Desk-side help and hardware handling
- Vendor relationships you want to keep
- Purchasing decisions and budget authority
- Anything your internal person enjoys doing
Who this is for
- Companies of roughly 25 to 200 people with some IT already in place: one internal person, an office manager who absorbed it, or a break-fix vendor who answers when called.
- Teams that need senior judgement more often than they need extra hands.
- Owners and operations leads who want one accountable name for the infrastructure.
Who this is not for
- Companies with nobody technical at all and no plan to change that. You would be better served by a full managed-services provider, and we will say so on the first call.
- Companies looking for a one-off fix with no interest in a monthly rhythm. Start with an assessment instead; the deliverable stands on its own.
We would rather lose the lead than take the wrong client. If either of these describes you, we will say so on the first call and point you somewhere better.
What you get every month
- 01
A named senior architect
One person who knows your environment and answers for it, with the escalation path written down.
- 02
Monitoring and patching
Servers, endpoints and Microsoft 365, kept current on a schedule you can see.
- 03
A restore test, not a green dashboard
Every quarter we restore something real to an isolated location and write down how long it took.
- 04
A standing monthly call and a written roadmap
Thirty minutes a month, and a document you can hand to your board or your accountant.
- 05
Project work at a known rate
Migrations, upgrades and clean-ups, scoped in writing before they start.
How it is scoped
An agreement scoped to your environment and agreed in writing before the thirty-day transition starts. Server count, number of sites, compliance obligations and whether you have an internal IT person are what shape it. The plans page lays out the three tiers and what each includes.
Response commitment
Monitoring runs continuously. Every agreement states a response target and names the escalation path for an outage outside business hours, matched to what your business needs. The figures are written into your agreement before it starts, not quoted from a brochure.
How it starts
- 01AssessmentOne to three weeks, read-only access. You get a written picture of what you run and what is at risk. The deliverable is yours whether or not you go further.
- 02Thirty-day transitionWe document the environment, fix the handful of things that cannot wait, and agree in writing what we own and what stays with your team.
- 03Steady stateThe monthly rhythm starts: patching, the monthly call, the roadmap, the quarterly restore test, and it holds from here.
Common questions
Do we have to replace our current IT vendor?
No. Most co-managed clients keep whoever handles the desk and the hardware. We take the infrastructure, cloud, identity and backup work, and we put the split in writing so nobody wonders who owns what.
What is the contract length?
Month to month after the thirty-day transition. If we are not earning our place, you should be able to leave without a fight, and the documentation we produce goes with you.
Do you resell licences or hardware?
We will tell you on the scope call. The advice on what to buy is never tied to what we earn from selling it.
What happens if something breaks outside business hours?
Every agreement names a response target and an after-hours escalation path for outages, matched to what your business needs. We agree that on the first call and put it in writing, so you know exactly what happens before it happens.
Can we start with an assessment and decide later?
Yes, and most clients do. The assessment is a fixed-scope piece of work with its own written deliverable. Co-managed is a separate decision after you have read it.
Describe your week. We'll tell you if this fits.
Fifteen minutes with the architect who would lead the work. If co-managed is wrong for you, you will hear that first.