Your project, carried to go-live with your team.

Network and systems engineering for MSPs. I work with your engineering team on the backend projects you've taken on for clients, from greenfield builds to production environments due for modernization, whether you bring me in at planning or close to implementation.

Talk through a project See what I take on

An estimated after-hours change window

Example schedule, adjusted to each job
Pre-checks7:00 to 7:30 PM
Cutover7:30 to 9:30 PM
Client validation9:30 to 10:30 PM
7:00 PM 7:30 PM 9:30 PM 10:30 PM
Following morning

The plan is agreed before the window opens. Cutover and validation get room to run, and each change has a go/no-go point on the schedule. If something doesn't validate, we decide what to do from the plan rather than in the moment. Documentation and the handoff come the next morning, once everything has settled.

One engineer from planning to cutover

Project overflow tends to land on the nights and weekends your own team doesn't have. I work with your engineers and project manager from requirements through the change window, and hand the work back documented.

Design and buildout

New builds, or extending and cleaning up what's already in place. Network and firewall designs, identity and tenant architecture, and a build plan your project manager can schedule against.

Staging

Gear configured, tenants prepared, and migrations planned and discussed before the window opens, so cutover night is orchestrated for implementation and validation instead of discovery.

Cutover and implementation

I'm on the call or on site when the change happens, working through the plan with your team and validating with the client as we go. Booked in blocks, evenings and weekends.

What I've designed, deployed and migrated

Every plan starts from what the architecture needs to be stable, then fits the equipment and licensing the client already has.

Networks and security

Built around sound Layer 2 and Layer 3 design, whatever the platform.

  • Switching and routingVLANs, trunking, inter-VLAN routing and site-to-site connectivity
  • FirewallingPolicy, NAT, VPN and segmentation, from new deployments to replacements
  • Site networksNew offices, refreshes and moves, wired and wireless

Microsoft cloud and infrastructure

Identity, files and desktops, on-premises and in Azure.

  • Hybrid identityOn-premises Active Directory synced to Entra ID
  • SharePoint and OneDriveConfiguration, and migrations from file shares and servers
  • Azure Virtual DesktopHost pools, images, profiles and networking, built from scratch
  • Endpoints and virtualizationIntune, plus VMware and Hyper-V hosts and migrations

My background is in MSP work for legal, law enforcement, healthcare, manufacturing and finance clients. That means a lot of changes made under pressure, in environments where downtime is noticed right away, and the change-control habits that come with it.

How a project runs

  1. Scope

    We agree on deliverables, access, the change window and who talks to the client.

  2. Plan and prepare

    I work with your team to plan and prepare ahead of time, using a lab or staging environment where one exists, and write out the plan for the window.

  3. Cut over

    We work through the plan together in the window and validate each step with the client.

  4. Hand off

    The next morning: as-built documentation, final configs and a short summary of what changed.

Backups and shared responsibility

I lean on backups and plan every change around them. What can be backed up, and how well, depends on the tools, storage and budget each environment has, so before any window we go over together what's covered, how it's checked, and where the gaps are.

Where coverage is thin, we plan around it and agree on the fallback up front. Good outcomes come from both sides doing that due diligence.

What I need from you

  • A defined scope or work order, and one point of contact
  • Access to the client's equipment, tenants and documentation
  • Your SOPs and standards. If your team has a set way of doing a task, I'll follow it.
  • The client's current backup coverage, including any known gaps
  • Client communication and scheduling, handled on your side

What you get back

  • Work that's validated with you before I hand it back
  • A back-out plan agreed before each change
  • As-built documentation and configuration exports
  • A short summary your team can pass on to the client

Have a project that needs a night or a weekend?

Send the scope, the platforms and the timeline. I'll tell you whether it's a fit and when I can start.

support@nsr-compute.com

Monroe, Louisiana. Central time. Evenings and weekends, on site within driving distance or remote.