Skip to content
Start a Project

We know roughly what we need — who turns that into a buildable network design?

A standalone design engagement — requirements to blueprint — covering topology, equipment classes, addressing, resilience and staging, delivered as documentation any competent installer could build from.

What's included

  • Requirements workshop and constraint capture
  • Topology and addressing design
  • Equipment class and capacity specification
  • Resilience and failover design
  • Staged implementation plan
  • Build-ready documentation

Design as a separate product exists because building without one costs more than both. The deliverable states not just what to build but why — so future changes are decisions, not archaeology.

Distance does not change the model. For remote and regional sites we often do the design and configuration ourselves, then have a local installer handle the physical work — racking, mounting and cabling to our drawings, with equipment that arrives already configured. The site gets the same engineering as a metro build without flying anyone out for work a good local contractor can do, and the installer is never left guessing at intent.

The same goes for changes over the life of the network. A remote site never needs to wait for us to come onsite: we design and configure the change, and local hands fit it. It is worth a conversation before new equipment goes in, though — we have seen a well-meant local addition conflict with the design it joined, where a quick call first would have produced something better that worked with what was already there.

Common questions

Do we have to have you build it?

No — the design is deliberately installer-independent. Plenty of clients take it to their preferred contractor; some come back to us for the build, and both outcomes are fine.

Ready to start, or not sure this is the right engagement?

Describe your situation in the Connection Brief. If a different engagement — or none — fits better, we'll say so.