Pricing tells you what it costs. It does not tell you what actually happens, who does what, or how long you are exposed while it happens. Pick the situation you are actually in below and this page rewrites itself around it, all the way through to booking the one meeting that starts it.
Four situations. One of them is yours. Everything after this point changes depending on which one you pick, because the first thirty days genuinely are not the same.
Nothing is submitted by choosing. You can switch paths at any point.
Your path ยท We have no real IT support
YOU HAVE BEEN RUNNING ON LUCK.
Nothing has burned down yet, so nothing has forced the issue. That is not a strategy, it is a streak. The good news is that starting from nothing is the cleanest build there is: no previous provider's shortcuts to unpick, no undocumented decisions to reverse engineer.
01Day 0
One call, no sales script
Twenty minutes on the phone. We ask what you have, who touches it, and what you are afraid of. You get a straight answer about whether you even need us yet. Some businesses your size do not, and we will say so.
โธ You need: a rough headcount and a guess at how many computers.
02Week 1
We map what exists
We come onsite and inventory everything: machines, accounts, network gear, where the data actually lives, who has access to what. Most owners learn something uncomfortable during this week. That is the point.
โธ You need: two hours of somebody's time and the keys to the closet.
03Week 2 to 6
We build the foundation
Identity and access control, endpoint protection on every machine, verified backups, patching on a schedule, and documentation that did not exist before. Built once, built properly, so it is not rework in two years.
โธ You need: to approve the plan. We handle the rest.
04Day 60 onward
It just runs
Monitoring is live, the SOC is watching, and problems get resolved before you hear about most of them. You get a quarterly review with what broke, what we fixed, and what we recommend next.
โธ You need: nothing. That is the entire product.
!
What this usually costs
The businesses that call us with no IT provider almost never call because they wanted one. They call because something already happened. The median first incident for an unmanaged small business is a compromised email account, and the median cost of cleaning one up after the fact is several times what a year of baseline coverage would have been.
Sixty days from now
โEvery machine is patched, encrypted and monitored instead of whatever it shipped with
โThere is a documented answer to what happens when the person who set this up leaves
โSomeone is accountable at 2 a.m., in writing, with a response time attached
Your path ยท We have an MSP and we are done with them
YOU ARE ALREADY PAYING FOR THIS.
You are not looking for IT support. You already have it. You are looking for the version of it you thought you were buying. That is the most common call we get, and it is also the easiest one to fix, because the gap between what you pay and what you receive is usually measurable within the first week.
01Day 0
Bring your last three invoices
Twenty minutes. We go line by line through what you are billed and what it buys. This is usually the call where somebody discovers they have been paying for seats that left the company in 2023.
โธ You need: recent invoices and your current contract if you can find it.
02Week 1
The quiet audit
We assess your environment without touching your current provider's arrangement. What is actually monitored, what is actually backed up, when the last restore was tested, which admin accounts exist and who holds them. You get that document whether or not you hire us.
โธ You need: read-only access. Nothing changes yet.
03Week 2 to 6
Transition without a gap
We take custody of every credential, stand up our tooling alongside theirs, verify it is working, then decommission theirs. Your notice period runs while we are already covering you. There is no day where nobody is responsible.
โธ You need: to send one notice email. We write it if you want.
04Day 60 onward
The comparison you can prove
Sixty days in you get a side by side: response times then versus now, incidents then versus now, spend then versus now. If it does not read better, you have a decision to make and no contract stopping you from making it.
โธ You need: nothing. The numbers arrive on their own.
!
The part people get wrong
The instinct is to fire the incumbent first and find a replacement second. Do not. Your current provider holds domain registrar access, tenant admin, RMM agents, backup credentials and licensing. Leaving before that inventory is documented is how businesses lose their own email. We run the transition with the outgoing provider still in place, and we have never needed them to cooperate for it to work.
Sixty days from now
โYou own your own credentials, registrar and tenant, in writing, from day one
โResponse times are contractual rather than aspirational
โThe person who scoped your account is the person who answers when you call
Your path ยท We have internal IT that needs backup
YOUR IT PERSON CANNOT SLEEP.
This is the situation nobody wants to say out loud: the business runs on one person, that person has not taken a real holiday in years, and everyone quietly knows what happens if they leave. We are not here to replace them. We are here to make them replaceable in the only sense that matters, which is that the business survives a fortnight without them.
01Day 0
We talk to them, not around them
The fastest way to sink a co-managed arrangement is to arrange it over your IT person's head. First call includes them. We ask what they want off their plate, and it is almost always the same three things: after hours, patching, and the security work they never get to.
โธ You need: your IT person in the room, genuinely.
02Week 1
Draw the line
We agree in writing who owns what. They keep the applications, the users and the institutional knowledge. We take monitoring, patching, the SOC, escalation and the 2 a.m. calls. No overlap, no ambiguity about who is picking up a ticket.
โธ You need: an hour to agree the split.
03Week 2 to 6
Document the undocumented
Everything in one person's head goes into a system: network topology, licence keys, vendor contacts, the reason that one server cannot be rebooted on a Tuesday. This is the deliverable that makes them able to take a holiday.
โธ You need: to protect a couple of hours a week for them.
04Day 60 onward
They do the interesting work
Your internal person stops being a help desk and starts being the person who improves things. Overnight and weekend coverage stops being their problem. Retention improves, which is the return nobody puts in the proposal.
โธ You need: nothing. Ask them how it is going in month three.
!
The bus factor nobody costs out
Single-person IT is not a cost saving, it is an uninsured liability sitting on the balance sheet. When that person leaves, and eventually they do, the successor spends their first six months rediscovering decisions that were never written down. Co-managed coverage is the cheapest insurance policy against that specific failure, and it is the one small businesses skip most often.
Sixty days from now
โYour IT person can be unreachable for two weeks and nothing degrades
โSecurity work that kept getting deferred is somebody's actual job
โThere is written documentation, so the next hire starts at week one rather than month six
Your path ยท Something is broken right now
STOP READING. CALL US.
If you are mid-incident, the rest of this page can wait. The number is (732) 743-5472 and it reaches a person. Incident response is billed at $90 per hour with no minimum, no retainer and no requirement to become a client afterwards. Read the rest of this later, once it is quiet.
01Right now
Containment
We get on the phone and work out what is spreading and how to stop it moving. Isolate first, diagnose second. If it is ransomware or a compromised mailbox, the sequence matters and there is a correct one.
โธ You need: to call. (732) 743-5472.
02Hours 1 to 24
Recovery
Restore from whatever clean copy exists, or rebuild if it does not. We tell you plainly which one you are in within the first hour, because the answer changes what the rest of the day looks like.
โธ You need: someone who can authorise decisions quickly.
03Week 1
How it happened
A written root cause, not a shrug. What the entry point was, how long they were inside, what they touched, and what you are legally required to tell anyone. That document exists whether or not you continue with us.
โธ You need: nothing. It arrives.
04After
Your choice
Once it is stable you decide whether to carry on alone or put coverage in place so the next one gets caught at 2 a.m. instead of 9 a.m. No pressure either way. Plenty of our incident calls stay incident calls.
โธ You need: to decide, in your own time.
!
What matters in the first hour
In a live incident the first hour decides most of the outcome. Do not wipe anything, do not pay anything, and do not turn machines off if you can isolate them from the network instead: powering down destroys memory-resident evidence and can trigger encryption routines that were waiting for a reboot. Disconnect, preserve, then call.
Sixty days from now
โThe incident is contained and you know exactly what happened
โYou have a written root cause you can hand to an insurer or a regulator
โYou are not obligated to anything afterwards
Chapter Three
ONE MEETING. THAT IS THE WHOLE ASK.
Sixty minutes, free, no obligation to use us afterwards. We cover three things in that hour, and you leave with the findings whether you hire us or not.
1
Set your goals
What the business needs from technology over the next two years, and what is currently in the way.
2
Evaluate your IT
We map the environment: machines, accounts, network, backups, licensing, and where the risk actually sits.
3
Review your plan
Findings, priorities and an exact price. The findings are yours either way.
Or skip all of this
PICK UP THE PHONE AND WE WILL SORT IT.
Reading is optional. If you would rather just describe the problem to a person, the number reaches one, and the person who scopes your account is the person who shows up.