What usually brings people to this.
- Intermittent and prolonged infrastructure downtime
- Infrastructure that cannot scale with the business
- Integration difficulties with other network devices and services
Green-field design, or a considered improvement to what you already run
We design IT infrastructure — networks and systems — against your actual requirements rather than a vendor reference architecture. Engagements are green-field where you are building something new, or improvement-led where an existing estate needs to reach a different standard. Either way the output is a design your team can build from and a plan for getting there.
-
01
Branch and HQ design
Network and systems design covering both branch sites and headquarters, with a consistent standard across locations.
-
02
Data centre infrastructure
Data centre design including routing, switching and server farms.
-
03
Cloud infrastructure design
Cloud infrastructure designed on Microsoft Azure and AWS, aligned with the on-premises estate rather than parallel to it.
-
04
RFP and pre-sales support
Client RFP working and pre-sales support, including solution documentation with bill of quantities and pricing.
How the engagement runs.
A defined sequence, so you know what is happening at any point and what comes out of each stage.
-
01
Requirements and scope
Establish what the infrastructure has to do before deciding what it is made of.
- Business requirements
- Users and sites
- Constraints
-
02
Branch and HQ design
Network and systems design covering both branch sites and headquarters.
- Branch sites
- Headquarters
- Consistent standard
-
03
Data centre infrastructure
Data centre design including routing, switching and server farms.
- Routing
- Switching
- Server farms
-
04
Cloud infrastructure design
Cloud infrastructure aligned with the on-premises estate rather than parallel to it.
- Microsoft Azure
- AWS
- On-premises alignment
-
05
High-level design
Produce the target-state design the build will be delivered against.
- HLD
- Target state
-
06
Solution documentation
Solution documentation including bill of quantities and pricing, with pre-sales support where an RFP is involved.
- BOQ
- Pricing
- RFP and pre-sales support
-
07
Tactical plan and long-term strategy
Separate what should change now from where the estate is going.
- Tactical improvements
- Long-term design strategy
What you receive.
- 01New or improved infrastructure design document
- 02High-level design (HLD) documents
- 03Tactical plan of improvements and recommendations
- 04Long-term design strategy
- 05Solution document including BOQ and pricing
What changes afterwards.
- New or improved infrastructure fit for the current business
- Cost efficiency identified wherever it exists
- Improved user experience
- Strategic alignment between infrastructure and business direction
Technologies and frameworks in scope
- Microsoft Azure
- AWS
- Routing & switching
- Server infrastructure
Before you get in touch.
Is this only for new builds, or can you improve what we already have?
Both — engagements are green-field where you are building something new, or improvement-led where an existing estate needs to reach a different standard.
Do you design against a vendor reference architecture?
No — infrastructure is designed against your actual requirements rather than a vendor reference architecture.
How long does a typical engagement take?
Typically 15–30 days for assessment plus one week for reporting, varying with the size of the estate.
Can you support an RFP or pre-sales process?
Yes — RFP working and pre-sales support is part of the offering, including solution documentation with bill of quantities and pricing.