Offer and sources reviewed
The official MSP NOC page describes Basic monitoring, Advanced monitoring with maintenance/remediation, and Custom scope. It offers continuous, after-hours and weekend coverage and device-linked fixed monthly pricing. Reviewed 2026-10-06. A quote is needed for an amount and the final inclusions.
Its tool section shows Atera, Datto, Kaseya, N-able and Automate names or logos. That is published product-name evidence, not proof that a particular bidirectional workflow works. The About page states ISO 27001:2022 certification; this site has not independently validated scope or current validity. Reviewed 2026-10-06.
Start with a tier and an action boundary
| Buying need | Tier or scope to investigate | Written acceptance question |
|---|---|---|
| External eyes with internal resolution | Basic monitoring | Which alerts receive triage and which are merely forwarded? |
| Maintenance and approved fixes | Advanced | Which actions need approval and who owns a failed change? |
| Unusual clients or supported systems | Custom | Which requested actions are included, excluded or add-ons? |
| A night/weekend gap | Agreed coverage window | Who accepts unfinished work at the end of the shift? |
Use the tier names to open a discussion, not infer a scope from a checkmark. For example, backup checks may mean a daily status check, an investigation of a failed job, or a restore test. List those as separate requirements. For patch management, specify approvals, reboot windows, rollback authority and applications excluded from automated changes.
The NOC guide provides a responsibility matrix. Your retained service manager should own client commitments and authorize the provider's boundary. Outsourcing execution does not eliminate the need to monitor the outcomes you promised clients.
Treat headline metrics as questions
The NOC page presents an average first-response figure below ten minutes alongside other operational metrics. It does not establish a contractual deadline for every severity in your proposed service. An average and an individual incident commitment measure different things.
Ask which incidents enter the sample, what first response means, what period is measured, and which exclusions apply. Request the severity/clock matrix in the order form. Keep acknowledgement, action start, mitigation, restore and resolution distinct in your SLA worksheet. A provider report becomes more useful when you can trace an entry back to your ticket record and reproduce its timing.
Device-linked pricing still needs a workload definition
No public currency amount is established here. Ask whether all clients and asset types use the same billable unit, whether there is a minimum commitment, and what causes a price change. Separate routine monitoring from maintenance, custom runbooks, migrations and optional administration services. Record setup, excess usage and exit work rather than treating silence as zero cost.
Use the cost calculator for your own assumptions. Include retained management and the cost of escalation your internal team still handles. A device count does not show how many noisy alerts, failed backup jobs or approval-dependent fixes enter the queue.
Security, access and a useful pilot
Ask for current certificate evidence, the legal entity and scope it covers, and the data-processing boundaries of your proposed service. This profile does not prove data residency, staffed delivery locations, background checks or independent validation of controls. An office address and a marketing coverage region are different facts.
Choose a limited client environment and agree a rollback route before access is granted. Test correct ticket mapping, an authorized remediation, an approval-required action and a revoked credential. Request an audit trail that identifies the actor and the work. A failed integration should create a visible exception rather than silently losing an alert. These are suggested acceptance cases, not reported Infrassist test results.
Published client interviews
Clutch publishes two client interviews, reviewed here on 2026-10-06. Its May 27, 2020 interview identifies Anton De Jager, CEO of Core Networks, and covers IT staff augmentation for security-product support. He reports accommodating support and describes technical interviews used to assess engineers before hiring. Clutch labels the interview verified; MSP Shortlist has not independently contacted him or audited that engagement.
The June 5, 2020 interview identifies Anuj Jain, CEO of Cybersec Consulting, and concerns a January-March 2020 Azure cloud-security project. He reports satisfactory delivery and also suggests broader cloud expertise. These are older project and staffing experiences, not measurements of today's pooled NOC service. The recorded project investment is not a current NOC rate.
For your buying decision, ask for a recent reference using the proposed service tier and stack. Reproduce relevant technical questions in your pilot rather than converting these interviews into an overall provider score. This site did not conduct the interviews.
Next step
Use the integration worksheet to capture the actual workflow. Compare Worksent's evidence if it is also on your list, or return to the directory and prepare one matched RFP. The site has not operated this service and does not award a quality score. Read the methodology or submit a sourced correction.