Network issues rarely stay in one category. A review that treats them separately misses the real problem
Uneven branch performance, Microsoft 365 lagging outside head office, a looming carrier renewal — each could be treated separately, which is how networks become harder to operate. A Network Review is for when the symptoms cross SD-WAN, firewall, access, cloud and carriers, and the right next step is not yet clear.
- Before the platform decision, not after
- Cross-pillar by design, not a single-category review
- Two to three weeks to a usable recommendation
The situations where the next step is not yet clear.
A Network Review is not for situations where the work is already obvious. It is for the less tidy ones: several connected decisions, symptoms crossing more than one technical area, or a defensible view needed before committing to a platform, carrier or architecture change. Select a signal to see what is usually behind it.
The review comes before the platform decision.
A Network Review is a structured assessment of the current environment. It is not a sales process for SD-WAN, Fortinet or SASE. The output may recommend one of those pathways. It may recommend none of them. It often recommends operating-model work, documentation, lifecycle planning or escalation ownership that the environment has needed for some time, but that no single platform vendor would have raised.
The review covers the surfaces where networking conversations usually concentrate, plus the operating layer that determines whether any of them are being run properly. Where the review identifies a clear next step, the buyer is routed there. Where it identifies operating-model work, that is what the recommendation says. Where no major change is needed yet, that is also what it says.
Seven surfaces, reviewed to the depth each one needs.
Some reviews go deeper in one area than others. A multi-site organisation may need most of the focus on connectivity; an organisation evaluating SASE may need most of the focus on identity and secure access. The bar shows where the review typically concentrates.
The operating layer, the last surface, is the one most likely to be the actual gap, and the one no platform purchase will fix.
Review first. Recommend second. Sometimes the recommendation is to hold.
A defined two to three week engagement, shaped to the environment rather than run from a template.
A structured conversation about what triggered the review, upcoming renewals, performance complaints, insurance questions or project pressure, shaping which surfaces need the most attention.
Site connectivity, firewall posture, secure access, Microsoft 365 paths, carrier contracts, underlay quality, monitoring, documentation and ownership, examined against current state.
Findings prioritised against business impact, upcoming pressure and dependency. The output distinguishes urgent from important, and lifecycle from immediate.
Where a platform is right, the review routes there. Where the right work is operating-model, documentation or lifecycle, it says so. Where no major change is needed yet, that is a valid finding.
One review, five honest outcomes.
A Network Review does not have to end in a platform recommendation. It resolves to whichever of these the environment actually supports, and "hold" is as valid as any pathway.
A useful review does not need to end in a platform recommendation.
Most network reviews lead somewhere by design, to an SD-WAN proposal, a firewall replacement, a SASE platform recommendation. Inlight IT's Network Review does not. Where a platform decision is the right next step, it says so. Where the right work is documentation, lifecycle or operating-model improvement, it says that instead.
01Engineer-led, not vendor-led
The review is performed by engineers who operate these environments daily across SD-WAN, FortiGate, SASE, ZTNA, carrier and Microsoft 365. The recommendation follows the environment, not a vendor relationship or a partnership commitment.
02Cross-pillar by design
SD-WAN, firewall, secure access and carrier are reviewed together because they affect each other. A firewall decision shapes a future SASE design. A carrier renewal shapes SD-WAN viability. Reviewing them separately produces partial answers.
03"No major change yet" is a valid finding
The strongest reviews sometimes conclude that the environment is operating reasonably and that the work the business has been considering is not yet the right priority. That is the recommendation the review will make where the environment supports it.
04Australian network context, defined engagement
Sydney and Newcastle engineers working with Australian multi-site environments, carrier options, FortiGate estates and Microsoft 365-heavy operating models. Two to three weeks from scope to a practical recommendation, written to be usable by the team that operates the environment afterwards.
Recent network, edge and access work
The three surfaces a network review examines: the WAN, the firewall and identity-led access.
Questions that come up before a Network Review starts.
What happens in a Network Review scoping conversation?
A structured conversation about the situations that triggered the question: upcoming renewals, performance issues, insurance questions, project pressure or general uncertainty. The outcome is a clearer view of which surfaces the review should focus on and what a practical engagement would look like.
How long does a Network Review take?
Typically two to three weeks from kickoff to recommendation. The duration depends on the size of the environment, the number of sites in scope and the access available to existing documentation and configuration. The output is a practical assessment with prioritised findings and a recommended next step.
What does the review actually produce?
A structured assessment covering the surfaces examined, with prioritised findings, a recommended next step and, where relevant, a routing to the appropriate pathway (Managed SD-WAN, Firewall Review or SASE and Zero Trust Access). The document is written to be usable by the IT team that will operate the environment afterwards, not as a sales artefact.
Is the review tied to a specific platform like Fortinet or Microsoft?
No. The review is engineer-led and environment-led. Where existing Fortinet, Cisco, Microsoft or other infrastructure is in place, the review accounts for that estate. The recommendation follows the environment, not a vendor relationship.
What if the review finds that no major change is needed?
That is a valid finding and one of the outcomes the review is designed to produce. Where the environment is operating reasonably and the upcoming decisions do not require a major platform move, the recommendation will say so. The review's value is the architectural view, not a forced next step.
Does the review help with cyber insurance or Essential Eight?
Yes, where the review surfaces network areas relevant to those questions: segmentation, secure access, firewall posture, logging, ZTNA readiness. It provides a network-side view that supports those broader assessments, though it does not replace a dedicated Essential Eight Assessment or insurance review.
Should we book a Network Review before SD-WAN, firewall or SASE work?
For organisations where the next step is not yet clear, yes. For organisations who have already self-identified the work as specifically SD-WAN, firewall or SASE, the dedicated landing is the cleaner starting point. The Network Review is for the situations those three do not yet describe.