What working together means for you.
No discovery-call gauntlet, no sales sequence. Here is the whole relationship, start to finish, so you know exactly what you're signing up for before you write the first note.
It starts with a written note.
You tell me roughly what your infrastructure looks like through the contact form: how many servers, what runs on them, what worries you, and whether you have IT help today. You get a considered, written reply, usually within two business days. If the fit is wrong, I'll say so plainly and point you somewhere better.
The baseline comes before the first invoice.
One afternoon of setting up VPN access so a guided, read-only discovery action produces the baseline document: an honest map of your environment (servers, directory, shares, backup jobs, firewall state, storage), what the first pass found, what's already in good shape, and a scheduled 90-day plan with costs. Nothing is changed while it's written, and all of this is done, by hand, by me. You see exactly what you'd be buying before you owe a dollar. Read a sample baseline (PDF).
One kickoff call, with your keys in your hands.
When you approve the plan, we get on a video call. You meet me, we walk the baseline together, set the maintenance calendar, and name your on-site contact for the rare day something physical needs doing. On the same call, we go through what has been discovered, I ask any questions I have - you do the same, and we both get a full understanding.
The onboarding project, quoted flat.
The 90-day plan is one-time project work: closing the urgent gaps, catching up on patches, proving the backups. It's quoted as one flat number, in writing, before anything starts. Hardware, if any is needed, you get the full specifications and links so you purchase it yourself, no markups, nothing in my name. You own it, end to end.
Then the service goes quiet, on purpose.
Maintenance runs in fixed overnight windows while your office is empty. Questions and requests go through the ticket queue and come back answered in writing. Every month closes with the written health report: what was verified, what was patched, what was found, what needs your decision. Read a sample report (PDF).
Once a year I'll offer a short strategic review call to look ahead at budget, growth plans, and aging hardware before any of it becomes a surprise. Beyond that, meetings only happen when you want one.
Projects beyond the retainer.
Migrations, major upgrades, new capabilities: scoped in writing, quoted as one flat number, executed in scheduled windows with a rollback plan staged first. There is no hourly rate anywhere in this business, which means you never have to wonder whether a recommendation is really a billable-hours generator.
What I ask of you
A named on-site contact. Someone who can plug in a cable or slot a drive with my support and instruction, a few times a year at most. If nobody on your team should ever touch hardware, I can arrange a vetted local technician for a flat coordination fee.
Accounts in your name. Cloud storage, licenses, and support contracts go on your card, at vendor price. It's your infrastructure; you own every piece of it.
Your own cyber liability policy. Serious businesses carry one, and carriers increasingly demand the exact controls this service provides. I supply the documentation your broker needs.
Decisions by reply. When a report recommends something, a written yes or no keeps your infrastructure moving. The reports always make clear what's waiting on you, and nothing else ever is.
A contract you can actually read
The whole agreement is a few pages of plain English, and you can read it right now: sample contract (PDF). There is no hundred-page master agreement, no appendix maze, no clause that needs a translator. It says what I do, what I don't do, what it costs, and who owns what.