Managed IT
Managed IT for US companies, with the evidence trail attached
Monitoring, service desk, patching, identity and security operations run as one accountable service — contracted through our Wyoming entity, delivered in your working day, and documented well enough to hand to an auditor or an insurer.
Talk to usThe part US buyers underestimate: proving it happened
Most managed-service comparisons come down to coverage hours and price per seat. Then the renewal on the cyber policy comes round, or a customer sends a security questionnaire, or an auditor asks how privileged access is reviewed — and the question stops being whether the work got done and becomes whether you can show it.
That is the part a thin managed service quietly leaves with you. Patching happens but nobody can produce the compliance rate for last quarter. Multi-factor is on, mostly, but there is no record of who is exempt and why. Backups run and the last verified restore was a year ago, if anyone remembers. None of that is a crisis until somebody asks, and then all of it is.
We run the service so the answers exist before the question does: what changed, when, by whom, and what state the estate is in this month. It is the same work either way — the difference is whether it leaves a trail you can hand over.
How the service is actually staffed
The contract sits with our US entity at 30 North Gould Street, Sheridan, Wyoming, and the engineering is delivered from our centre in Tbilisi with scheduled overlap into US working hours. That is the arrangement, stated plainly, because it is the first thing a careful buyer wants to know and the last thing most vendors put in writing.
What it means in practice: you get senior engineers at a rate that a purely domestic team cannot match, a US entity to contract with and hold to US norms, and a working day that overlaps yours rather than running opposite it. What it does not mean is somebody driving to your office. We have no field engineering team in the United States, and for an estate that is mostly cloud and SaaS that costs you very little — but if your requirement includes on-site hands, hardware swaps or cabling, engage a local provider for that half and we will work alongside them.
What it costs
Our managed IT starts at $1,000 per month. US buyers are used to seeing per-user headline rates of roughly $75-$250, and those are useful for comparison, but they hide the fact that a ten-person company and a hundred-person company are not buying the same service at different volumes.
The floor covers a small estate with 24/7 monitoring, a service desk overlapping US business hours, patching reported as a compliance figure, endpoint detection, tested backup, and the control evidence this page is largely about. Headcount, coverage hours, servers, additional sites and the depth of security inside the contract are what move it.
We scope before quoting. For a service whose value is that it can prove what it did, quoting before looking would be an odd place to start.
What the service covers
24/7 monitoring with a defined path to action
Alerting that resolves to a person and a runbook rather than a dashboard nobody watches, with severity definitions agreed up front so a P1 means the same thing to both of us.
Service desk in your working day
A named route to an engineer during US business hours, with ticket history that shows where time actually goes — which is usually not where anyone assumed.
Patching with a compliance rate
Operating systems and third-party software patched on a schedule, reported as a percentage rather than an assurance, because that percentage is what a questionnaire asks for.
Identity and access management
Joiners, movers and leavers executed and evidenced, MFA enforced with exceptions documented, and privileged access reviewed on a cadence you can point to.
Endpoint protection and response
EDR deployed, tuned and monitored, with a defined containment path — the control most US cyber-insurance applications now ask about directly.
Backup verified by restore
Backups configured and tested by actually restoring, against a recovery objective you agreed rather than one we assumed. A backup nobody has restored is a hypothesis.
Cloud and SaaS operations
AWS, Azure, Google Cloud, Microsoft 365 and Google Workspace administered as part of the service — including the licence and sharing hygiene that quietly turns into an exposure.
Monthly reporting built for handing over
What happened, what changed, what is at risk, and the control evidence behind it — in a form you can forward to an insurer, an auditor or a customer's security team without rewriting it.
Our response targets
| Severity | What it means | Response target | On-site (no US field team) |
|---|---|---|---|
| P1 — Critical | Business stopped. No workaround. Multiple users or a revenue-facing system down. | 15 minutes | Briefed local provider |
| P2 — High | A major function is down or degraded, but a workaround exists. | 1 hour | Scheduled |
| P3 — Medium | A single user, or a non-critical function. | 4 business hours | Scheduled |
| P4 — Low | A request, a change, or a question. Nothing is broken. | 1 business day | Scheduled |
Response target is time to a named engineer working the ticket, not an automated acknowledgement. Targets are confirmed in the contract against these severity definitions — a response time with no severity definition attached is a marketing number.
Frequently asked questions
- Who am I contracting with?
- Our US entity, registered at 30 North Gould Street, Sheridan, Wyoming. That is the party on the agreement, the domestic point of contact, and the entity you hold to US contract norms.
- Where are the engineers?
- Our delivery centre in Tbilisi, Georgia, scheduled to overlap US working hours. We say this in the first conversation rather than the fifth, because a buyer who finds it out late is right to be annoyed.
- Do you provide on-site support in the US?
- No. There is no field engineering team in the United States and we will not imply otherwise. Where physical work is needed we scope it, brief a local provider or your facilities team, verify the result and stay accountable for the outcome. For a mostly-cloud estate this rarely matters; if your estate is hardware-heavy, engage a local partner for that half.
- Can you support a cyber-insurance application or renewal?
- That is much of why the reporting is built the way it is. Insurers commonly ask about multi-factor authentication, endpoint detection and response, patch cadence, backup testing and privileged access review. We operate those controls and produce the evidence for them, so the application is a matter of exporting what already exists rather than reconstructing a year in a fortnight.
- What about SOC 2 or a customer security questionnaire?
- We are not an audit firm and will not claim to certify you. What we do is run the controls that questionnaires and audits examine, and keep the records that make answering them a lookup rather than a project. Most of the pain in these exercises is missing evidence, not missing controls.
- How is it priced?
- Per user or per device with the scope agreed in writing, and we scope before quoting. A published per-seat number without a defined scope tells you nothing — the same figure can cover monitoring only or a full security operation.
- What are your response times?
- Agreed in the contract and tied to severity definitions, with different targets for business-hours and extended coverage. A response target that is not attached to a severity definition is a marketing number.
- What happens if we want to leave?
- You get the documentation, the tooling inventory and the access handover. We would rather be kept because the service is good than because the exit is painful, and building a service you cannot leave is a decision made against the client.
Want a managed service that can prove what it did?
Tell us what is in your estate, what coverage you need, and what your insurer or auditors are asking for. You will get a scoped proposal with the reporting spelled out.
Get started