Review your IT. Agree the support.
We review your systems, agree what is covered and plan the switch. You get reports, regular reviews and a written handover if you leave.
Packages
Start with a package
Four packages, each with its price on the page. Pick one and buy it online.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Onshore
US engineers, Central time
Senior engineers
Scope it, then build it
Fix the cause
Not just the ticket
Written handover
If you ever leave
What happens, in order.
Each phase is agreed separately.
Phase 1
First call
45 minutes · no charge
What you are running, what keeps breaking, and who is carrying it today.
What happens, what you get and how to leave
We discuss your sites, staff, systems, recurring problems and current support arrangements. We confirm what we can support and whether an estate review is the next step.
What happens
- Walk the estate at a high level: sites, headcount, what is business-critical
- Establish what is failing now and what it costs when it does
- Identify the contractual constraints: incumbent notice period, renewal dates, leases
- Agree whether an estate review is worth doing
What you get
- A direct answer on whether this is a good fit, either way
- An estate review proposal with a fixed fee, if it is warranted
ExitYou leave with an answer. There is nothing to cancel.
Phase 2
Estate review
1 to 2 weeks · fixed fee
A written picture of what you actually have, which is yours to keep and useful even if you never hire us.
What happens, what you get and how to leave
We review your users, devices, accounts, network, cloud services and backups. You receive an inventory, identified risks and a proposal for the systems we would manage.
What happens
- Inventory of devices, accounts, licenses, circuits and vendor contracts
- Identity and access review: who can reach what, and who still can but should not
- Backup and restore verification, including an actual test restore
- Network and connectivity survey at each site
- Risk register: what is unsupported, unpatched, unmonitored or unowned
What you get
- A written inventory and a dependency map
- A prioritized risk register, worst first, with what each one would take to close
- A service proposal: what we would run, what it costs, and the response targets and notice period we are agreeing to
ExitA fixed-fee engagement with a defined end. Whether to go further is a separate decision.
Phase 3
Onboarding
2 to 6 weeks
Taking custody of the estate, in parallel with whoever has it now, so nothing is uncovered on the day the incumbent stops.
What happens, what you get and how to leave
We agree the takeover plan with you and your outgoing provider, then transfer access, document systems and establish support. Any changes to the agreed scope are confirmed before steady-state service begins.
What happens
- Credential, tenant and domain custody transferred into accounts you hold
- Monitoring, patching and endpoint protection deployed and verified
- Backup regime stood up and a restore tested before the incumbent leaves
- Documentation and runbooks written from the estate, not inherited on trust
- Service desk introduced to your staff, with the escalation path named
What you get
- A signed service agreement with the response targets and notice period in it
- Documentation and runbooks in a system you can read without us
- A verified backup and a completed test restore
- A named contact, and the escalation path written down
ExitIf onboarding shows the estate is not what the review found, the agreement is repriced or ended before steady state begins.
Phase 4
Running it
Monthly, ongoing
The day-to-day service, plus a review cadence that exists so the relationship is examined on a schedule rather than at renewal.
What happens, what you get and how to leave
We handle support, patching, protection, backups and account changes within the agreed coverage. Monthly reporting tracks service performance. Quarterly reviews set priorities for the systems and risks.
What happens
- Service desk for your staff, answered by engineers rather than by a routing tier
- Patching, endpoint protection and monitoring on a schedule you can see
- Joiners, movers and leavers processed as an agreed workflow
- Backup verification and periodic test restores, evidenced
- Quarterly review of the estate, the ticket pattern and the risk register
What you get
- Monthly service reporting: volume, response against target, what broke and why
- A living inventory and risk register, not a document that ages
- A quarterly review with a written recommendation on what to fix next
ExitThe notice period agreed in your service agreement, for any reason, with no exit fee.
Phase 5
Leaving
Planned from the start
The part that decides what the whole agreement was worth, written into it on day one rather than negotiated on the way out.
What happens, what you get and how to leave
We keep accounts and documentation ready for handover. If you leave, we coordinate with the incoming provider, return data and remove our access on the agreed schedule.
What happens
- Handover pack assembled: inventory, runbooks, credentials, vendor contacts, open issues
- Direct handover calls with the incoming provider, included in the fee rather than billed
- Access wound down on your schedule rather than immediately
- Data returned and then certified destroyed
What you get
- A complete handover pack, in formats a competitor can actually use
- Certification that our access is removed and your data is destroyed
- A named contact for a defined window afterward, for the questions that arrive late
ExitNothing to transfer back, because nothing was ever held in our name.
Choose the support you need.
Estate review
Working out what you actually have
- One to two weeks, fixed fee agreed in advance
- Quoted against the size of the estate and the budget you state
- The written picture is a deliverable of the engagement
- No obligation to continue
Full managed service
Handing over the whole IT function
- Monthly, against a service agreement
- Response targets agreed in that agreement, and reported against monthly
- Notice period agreed with you, in the proposal rather than the paperwork
- No exit fee, and no minimum term beyond the agreed notice
Co-managed
You have someone internal and they are drowning
- Monthly, with the split of responsibilities named in the agreement
- Your internal staff keep administrative access throughout
- Escalation available to the same engineers as the full service
- Same notice period terms as the full service
What the monthly fee does not cover
Hardware, licenses and circuits are yours, bought in your name, at what they cost. Project work outside the agreed service, a site move or a migration, is quoted separately and agreed before it starts. A managed fee that quietly absorbs project work is a fee with an incentive to do less of it.
Leaving your current provider
Assume they will not help, because they are usually not obliged to. We plan the handover on that basis and run in parallel through the notice period wherever your contract allows. Tell us the renewal date and the notice window in your first message; it changes the sequence more than anything else about your estate.
Service targets and reporting.
See the standards and what the monthly report contains
Targets are agreed against your estate, then published to you
The floor is printed further down this page: one business hour to an engineer, Monday to Friday, 8 to 18 Central. The per-priority targets above that floor are set in your service agreement rather than printed here, because a single-site office and a five-site operation with a night shift are not the same promise and we would rather not average them. What is not negotiable is that they exist, in writing, before the agreement starts, and that they are the first thing we expect you to hold us to.
Measured against the target that was agreed, not a general one
Every ticket is timed against the target for its priority, and the report shows the distribution rather than the average. An average response time hides the two tickets that took a week, and those two are the ones that decide how your staff feel about the service.
A miss is reported by us before you notice it
Where we breach a target, it appears in the report with what happened and what we changed, and we raise it rather than waiting to be asked. A provider who only discusses performance when the client complains has made complaining the measurement system.
The risk register moves or it gets explained
The register from your estate review stays live. Every quarter each item has either moved, been consciously accepted by you, or carries a reason it did not move. A risk list that is identical four quarters running is not a risk list, it is a document.
The review is where priorities get argued, on a schedule
Quarterly, with the estate, the ticket pattern and the register in front of both sides. This exists because the real failure of a managed service is drift rather than incident: three quiet years in which nobody asks whether what is being run is still what you need.
What the monthly report contains
- Ticket volume by priority, and response times against the agreed target
- Every breach of a target, with the reason and what changed
- Patch status across the estate, including what could not be patched and why
- Backup results, and the date of the last verified test restore
- Joiners and leavers processed, and any access still open that should not be
- Movement on the risk register since the last report
Terms to review before work starts.
Accounts and access, Service and reporting, People, Data and security, Leaving
Accounts and access
The most common form of lock-in is not a clause. It is a tenant, a domain registration or a firewall that turns out to be in the provider’s name.
- Your tenants, domains, licenses and circuits contracted in your name, not resold through ours
- Administrative access held by you throughout, not restored on request
- Our engineers’ access named, logged, and reviewed at every quarterly review
- Any tooling we deploy identified, including whether it stays useful to you without us
Service and reporting
Every provider promises responsiveness. The question is what is measured, who measures it, and what happens on a bad month.
- Response targets written into the service agreement before it starts
- Monthly reporting against those targets, showing the distribution rather than an average
- Every breach reported by us, with the cause and what changed
- A quarterly review with the estate, the ticket pattern and the risk register in front of both sides
People
The named engineer on the proposal and the voice on the phone are frequently different, and continuity is most of what you are buying.
- A named primary engineer, and a named escalation, both in the agreement
- You can require removal of anyone, for any lawful reason
- All service delivery performed in the United States. Nothing subcontracted offshore
- Escalation reaches the engineers who build systems, rather than stopping at a support tier
Data and security
Most privacy law holds you responsible for a breach whether it was your fault or your vendor’s, and a managed provider holds the keys to everything.
- A security requirements exhibit specific to your data, not a pointer to our then-current policy
- Written notice of any actual or suspected incident within 24 hours
- You control the content, timing and method of any notification to your customers or regulators
- Backups verified on a schedule, with test restores evidenced in the monthly report
- A signed BAA where PHI is involved
Leaving
The cost of leaving a managed service is set on the day you sign. This is the group this division published none of until it had written one.
- A notice period agreed with you and stated in the proposal, not discovered in the paperwork
- No exit fee, and no minimum term beyond that notice
- A handover pack as a deliverable: inventory, runbooks, credentials, vendor contacts and open issues
- Direct handover calls with your incoming provider, included in the fee rather than billed
- Your data returned in a platform-neutral format, then certified destroyed to NIST SP 800-88
- Nothing to transfer back, because nothing was held in our name to begin with
Cost, timing and project questions.
Yes, and it is usually the fastest way to get a useful answer: several of the pieces we publish end by asking for exactly that. Two things worth knowing first. This is an ordinary web form: it is encrypted in transit and the message lands in our mailbox and our own console, but it is not a secure document channel, so redact freely. A workbook with the numbers changed, a clause with the parties removed, a day of messages with the identifiers swapped: each of those answers the question as well as the original does, and we would rather read a redacted one. And if you would rather have an agreement in place before you send anything, say so in a line: we work under your paper rather than asking you to work under ours, and we redline rather than refuse.
Yes. Your engineers contribute business knowledge and review the work with ours. Shared development and documentation also prepare your team for handover.
Managed IT covers day-to-day support, access, patching, protection and backups. Cybersecurity covers separately scoped assessments, penetration tests and training. Describe what happened and we will help identify the right practice.
Pricing depends on your users, devices, sites, systems and required coverage. An estate review produces a written proposal for your environment.
One business hour to a named engineer who has read your ticket, Monday to Friday, 8:00 to 18:00 Central. Not an autoresponder and not a queue position, a person, with the ticket open. If your people cannot work, that is where we already are. Outside those hours we are not a standing commitment, and we would rather write that down than imply a rota two people cannot staff: after-hours cover exists where your agreement provides for it, and that agreement names who you call and what it costs. The reason the number is one hour rather than fifteen minutes is that it counts from your problem to an engineer, not to a system acknowledging receipt.
The term and notice period are agreed for your systems and support needs. We state them in the proposal and plan the handover before service begins. Tell us about an existing provider or renewal date on the first call.
Yes. We work under client paper rather than asking you to work under ours, and we redline rather than refuse. Security is handled through an exhibit written for your data rather than a pointer to our own policy, and the terms we will agree to there include notification of any actual or suspected incident within 24 hours, the content and timing of any notification to your customers or regulators left entirely in your control, a BAA where PHI is involved, and support for joint security testing. Questionnaires are part of onboarding rather than an afterthought. Send the requirements early, including whatever insurance you require us to carry, and we’ll flag anything we can’t meet.
Usually one of three ways, and we will tell you which is fastest for your institution rather than the one that suits us. First, subcontracting: we work under a prime who already holds the vehicle, which is the most common route for a firm at our stage and needs nothing new from your procurement office. Second, your own delegated authority: many institutions can issue a purchase order directly for services under their own limit, and those limits are set locally rather than centrally, so the number is yours to confirm. Third, a cooperative or state vehicle you already use. Being plain about that third one: we hold no cooperative or state contract awards today. Awards on those come through competitive solicitation cycles rather than on request, they are published, and any vendor implying otherwise is worth checking. If a vehicle is the only viable path for you, the honest answer is that we are the wrong firm this fiscal year, and we will say so on the first call rather than in month two.
All in the United States, all in Central time. We don’t subcontract delivery offshore. If a role requires clearance, citizenship or on-site presence, tell us early and we’ll be direct about whether we can staff it.
In the engagement agreement, in writing, before any work starts. Ownership and licensing are commercial terms rather than something we publish a standard answer to here, and they are settled with you during scoping. What we will say in general is that we do not rely on “work made for hire” language to do it: work for hire is a copyright doctrine that does not reach patents or trade secrets, and it reaches commissioned work only in nine narrow statutory categories that software is not one of, so whatever is agreed is agreed by express assignment. Any third-party or open-source component we use is listed with its license.
Acceptance criteria go in the statement of work, in objective terms, before the work starts. If something doesn’t meet them we fix it at our cost inside a defined window. Nothing is ever deemed accepted because time passed, and a holdback on each phase is released only on acceptance of that phase. If we can’t get it right, you stop paying for it.
Every change is priced and signed before work on it starts. We also rewrite our own assumptions as your obligations with dates attached, because an unstated assumption is how a contractor creates an exit and a change-order revenue stream at the same time. On estimated work we agree an overrun mechanism up front: modest variance is ours to absorb as the normal play in an estimate, and a large miss means the estimate was a guess, which is our problem rather than yours.
Mutual, with carve-outs that sit outside the cap: IP infringement indemnity, gross negligence, willful misconduct, and deliberate misuse of your confidential information. A cap that swallows the indemnity makes the indemnity decorative. We draw one line deliberately: a confidentiality breach we caused on purpose is uncapped, and one caused by a mistake sits under the cap or under a higher security-specific cap we will agree. We would rather set a cap we can actually fund than promise an unlimited number that nothing funds. We’ll negotiate it against the size and criticality of the engagement, and we’d rather have that conversation on the first call than in week six.
Whatever the engagement agreement says, and it says it before any work starts rather than at the end. Ownership, licensing and where the code and infrastructure are held are settled in writing during scoping, which is also what decides whether an escrow arrangement is worth anything to you. What does not depend on that negotiation: the hand-off phase is in the plan from the start rather than improvised under pressure, your data is exported in a platform-neutral format as well as ours and then certified destroyed to NIST SP 800-88, documentation, runbooks and architecture decision records are written as the work happens rather than assembled at the end, and there is a named handover contact for a defined window after the last day.
Next step
Tell us what’s breaking.
Forty-five minutes, no charge. We’ll say what we’d do, what it would likely cost to run, and where your estate is fine as it is.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.
