Custom — regulated, multi-site, or project-heavy
When your environment does not fit a standard tier
What Custom — regulated, multi-site, or project-heavy is for
Some environments do not map onto a tier, and pretending otherwise produces a bad engagement. Multiple locations with different connectivity realities. A plant or campus where operational equipment cannot simply be patched. An acquisition that has to be integrated without either business stopping. A new office that needs cabling, connectivity and a working network by a fixed date.
Custom engagements are built around a statement of work: defined scope, milestones, testing and formal acceptance criteria. You know what is being delivered, when, and what constitutes done. That last part matters more than it sounds — most project disputes are really disagreements about what finished was supposed to look like.
Custom work frequently transitions into a managed tier once the project completes, and we plan for that from the start. A build handed over without documentation, monitoring and a support arrangement is a build that degrades from the day it goes live.
What changes for you
A defined finish line
Milestones and written acceptance criteria mean the project has an end, and everyone agrees in advance what reaching it looks like.
One accountable party
Carriers, cabling contractors, equipment vendors and application suppliers get coordinated by us rather than by your operations manager.
A build that stays healthy
Handover includes documentation, monitoring and a support arrangement, so the environment does not start degrading the week after go-live.
What's included
Grouped by what it does for the business, rather than by the tools behind it.
Multi-site and connectivity
- Multi-location, WAN and SD-WAN design with documented failover expectations
- Carrier and ISP procurement, coordination and escalation
- Resilience design matched to what each site actually needs
Physical infrastructure
- Structured cabling for new builds and refits
- Network refresh, relocations and physical moves
- Plant, campus and warehouse environments including ruggedised deployment
Regulated and segmented environments
- Compliance-sensitive workflows and network segmentation
- Separation between corporate and operational networks where a phishing click must not reach the plant floor
- Evidence aligned to what your counsel and auditors require
Delivery discipline
- Phased rollouts with milestones, testing and formal sign-off
- Dedicated project communication and steering rhythms with executive sponsors
- Acceptance criteria agreed in writing before work starts
Transitions
- Coexistence planning for mergers, acquisitions and carve-outs
- Integration with a managed tier for steady state after completion
- Handover documentation your team or another provider can actually use
What Custom — regulated, multi-site, or project-heavy does not include
Worth knowing before a call rather than after one.
- No illustrative monthly range applies — pricing follows discovery and is fixed in the SOW.
- Scope changes go through a written change request. We will not absorb scope creep silently and then argue about it at invoicing.
- Steady-state support after completion is a separate managed tier, quoted alongside the project.
- We will decline work we are not the right party for, and say who is.
Questions about Custom — regulated, multi-site, or project-heavy
- After discovery, and fixed in the statement of work. We do not publish a range because there is no honest one — a two-site network refresh and a regulated multi-campus integration are not the same engagement. Discovery itself is scoped and quoted so you are not committing blind.
- Typically two to four weeks depending on how many sites and systems are involved. It produces a scoped SOW with milestones and pricing. If we conclude we are not the right fit, we say so at that point rather than proceeding.
- Yes, and it is common — a provider handling steady-state support may have no appetite or capability for a multi-site build. We define the boundary in writing so nobody is guessing who owns what mid-project.
- It gets planned around rather than argued with. Where a machine has fixed requirements and cannot be updated, the answer is isolation and monitoring — segment it, watch it, and document the compensating controls. That is a legitimate engineering position, not a failure.
How is a Custom engagement priced?
How long does discovery take?
Can you work with our existing MSP during a project?
What happens to older equipment that cannot be patched?
Not quite right?
Compare all packages →Is Custom — regulated, multi-site, or project-heavy the right fit?
Twenty minutes with an ECS engineer, and an honest answer either way. If a different tier suits you better, we will say so.