For businesses
Fixed-scope projects with a written statement of work
Some work does not belong in a monthly agreement. A platform migration, a directory consolidation, a disaster recovery audit — these have a defined end state and deserve a defined scope, a written design, and a number you approve before anything starts.
- Written statement of work before any work begins
- Assumptions and responsibilities stated explicitly
- Change orders agreed before scope moves, never after
- No requirement to move your managed services to us
- As-built documentation and runbooks at closure
- Defined hypercare period after go-live
What we deliver
Infrastructure refresh and migration
Hardware and platform changes planned as projects with a defined end state, not as a series of maintenance windows.
- Server, storage, and hyper-converged platform refresh and deployment
- VMware exits to Azure Local, Hyper-V, Proxmox, or Nutanix
- SAN and NAS migrations with minimal-downtime cutover planning
- Data center relocation, consolidation, and decommissioning
- Network refresh across switching, wireless, and firewall estate
Identity and directory projects
The projects where the blast radius is every user, so the staging matters more than the speed.
- Active Directory domain and forest migrations, including after acquisitions
- Microsoft 365 tenant-to-tenant migrations and consolidations
- Entra ID deployment, hybrid join, and conditional access rollout
- Multi-factor authentication programs staged by ring
- Group Policy rationalization and privileged access tiering
Assessments and documentation
Short, defined engagements that produce a decision-grade written deliverable.
- Disaster recovery and backup environment audits with recovery testing
- Microsoft 365 and Entra ID security posture assessments
- Infrastructure and network assessments before a refresh decision
- IT architecture documentation standards and reusable templates
- Vendor-neutral technology selection analysis with costed options
Staff augmentation
Senior engineering capacity for a defined period, working inside your team and your process.
- Interim systems and infrastructure engineering during a vacancy
- Specialist capacity for a program your team cannot absorb
- Knowledge transfer and mentoring for internal staff as a stated deliverable
- Time-and-materials or prepaid block-of-hours arrangements
- Defined start and end dates, with handover documentation at closure
Platforms we work in
Named platforms, not categories — so you can tell at a glance whether we already know your environment.
- Virtualization
-
- VMware vSphere
- Hyper-V
- Proxmox VE
- Nutanix
- Azure Local
- Hyper-converged
-
- HPE SimpliVity
- HPE dHCI
- Storage Spaces Direct
- Nutanix
- Storage
-
- HPE Nimble
- HPE MSA
- HPE 3PAR
- NetApp
- Dell EMC
- Identity
-
- Active Directory
- Entra ID
- Entra Connect
- Conditional Access
- Cloud
-
- Azure
- AWS
- Microsoft 365
- Azure Virtual Desktop
- Google Workspace
How it runs
From first call to sign-off
Every engagement is governed by a written statement of work naming deliverables, assumptions, and who is responsible for what.
-
Scoping conversation
With the engineer who would run the project. We would rather tell you a project is unnecessary at this stage than discover it halfway through.
-
Statement of work
Deliverables, assumptions, your responsibilities, hours, and a schedule of fees. Everything that would otherwise become a dispute later, agreed in writing first.
-
Design and phased delivery
A written design document, then execution in phases inside agreed maintenance windows, with change orders raised before scope moves rather than after.
-
Validation, handover, hypercare
Testing evidence, as-built documentation, runbooks, a knowledge transfer session, and a defined hypercare period after go-live.
Questions
What people ask
Fixed-scope projects with a written statement of work — questions
Do we have to be a managed services client to engage you for a project?
No. A substantial share of our work is standalone project engagements for organizations with their own IT teams, or with a different managed provider entirely. There is no requirement to move your ongoing support to us, and we will not use the project as a sales process for it.
How do you price projects?
From a written statement of work with a schedule of fees showing hours and rate by phase, so you can see exactly what drives the number. Scope changes are handled through a change order agreed before the additional work starts. Assessments and audits are usually quoted as fixed-hour engagements.
What if the scope turns out to be wrong?
The statement of work names its assumptions explicitly for exactly this reason. If discovery contradicts an assumption — an unsupported operating system version, a dependency nobody documented, a firewall change we were told was in place — we raise it, quantify it, and get a change order approved before proceeding. You will not receive an invoice for work you did not authorize.
Can you work with our existing IT provider?
Regularly, and it is a normal arrangement. We are frequently engaged as the specialist layer alongside an incumbent provider who is capable but does not have depth in Linux, cloud architecture, or security. We work through their process and their change control, and we do not compete for their contract.
How far in advance do projects need scheduling?
Assessments and audits can usually start within a couple of weeks. Large migrations are scheduled around your maintenance windows and business calendar, which is normally the binding constraint — school districts work around the academic calendar, manufacturers around plant shutdowns. Bring us in during planning rather than after the hardware has been ordered.
Bring us in during planning, not after procurement
The cheapest hour of any project is the one spent deciding whether it is the right project.