Cisco Meraki · Plan / Build / Operate
Build a new network, take over an existing estate or relieve your IT team: we bring Cisco Meraki from design into daily operations. For single offices, larger networks, branches and IT service providers.
Discuss your Meraki network5 services · Cisco Meraki
From a single office to a branch network: we design, build and operate Cisco Meraki networks. Directly for your business or as the delivery team for your IT service provider.
Discuss your requirementsDownload the Meraki project brief (.md)Editable checklist. No registration.
Dashboard operations, changes, firmware and escalation – managed for you or alongside your IT team.
Build new sites with a reviewed design, a pilot, a cutover plan and documented acceptance.
Align RF design, access switches and network access with your spaces, devices and applications.
Connect sites with Meraki MX, including routing, segmentation and tested failure scenarios.
Change providers or relieve your team with a structured assessment and a controlled handover.
The exact scope follows your environment and its dependencies. Pricing, service hours and response targets are agreed in the proposal.
Technology & operations
Wireless, switching and branch connectivity belong together. We connect technical delivery with the operating model you actually need.
Applications, ports, PoE, uplinks and failure scenarios determine the architecture. You receive a reasoned target design rather than an unchecked shopping list.
RF design, access networks, SSIDs and segmentation. Survey scope and acceptance criteria follow your spaces, devices and applications.
Standards, a pilot and phased cutovers with on-site coordination, a fallback path and documented functional checks.
Connect sites and design routing and firewall boundaries. Circuit and device failures are considered in the design and tested within the agreed scope.
Alert handling, approved changes, firmware and licence planning. With written service hours and explicit boundaries around vendor and on-site services.
Organise roles, naming, templates and recurring checks. Suitable tasks can be integrated into your workflows through controlled use of the Dashboard API.
Working together
You do not need a finished specification. We first establish your current position and the responsibilities you want to delegate.
Capture sites, applications, existing equipment and expectations. A single site or a bounded assessment can be a useful starting point.
Define outcomes, responsibilities, prerequisites and fees. Deployment, remediation and regular operations are clearly separated.
Validate the design and pilot, approve changes and migrate sites. Accept results, outstanding items and operational documentation together.
Your team operates independently, works co-managed with us or commissions agreed operational tasks. The operating model remains transparent.
In plain language
Size alone does not decide. What matters is which applications need to work and who has capacity to run the network.
You need appropriately sized wireless, separate guest access and dependable connectivity. We review existing equipment and establish whether a new deployment, targeted improvement or ongoing service best meets your needs.
Your IT team understands the requirements but lacks capacity for design, rollouts or recurring specialist work. We complement the team through bounded projects or co-managed operations, with clear dashboard access, approvals and documentation.
Different site types need shared standards and documented exceptions. We plan rollout waves, integration with existing networks and ongoing support. For complex campus requirements, we also assess where Catalyst or a combination is a better fit.
You lead the customer relationship; we support technical delivery through Meraki design, migration, rollout or agreed operations. Customer contact, escalation, documentation format and responsibilities are established before work begins.
Tools & platforms
FAQ
Yes, following an agreed assessment. We review authorised access, the organisation, equipment, licences, open issues and handover. Suitable hardware does not automatically need replacing. Device or licence transfers are never assumed without checking.
Yes. Design, rollout, assessment and ongoing support are separate entry points. The proposal defines the outcomes you receive and where project work transitions into regular operations.
Yes. We plan around requirements and existing IT, not a blanket minimum site count. A single office or a clearly defined wireless project can be a suitable engagement.
For customer-owned networks, we plan around customer organisation control and agreed named administrator access. A co-managed model defines which tasks your team and Configlane perform. Existing contracts and ownership are resolved first.
No. Automatic alerts are not the same as staffed round-the-clock response. Available service hours, response targets, escalation, replacement hardware and on-site services are agreed before commissioning. The website alone makes no blanket commitment.
That depends on sites, equipment, complexity and agreed scope. Project work, hardware, licences and ongoing support are separately identified in the proposal. Approximate details are enough to begin; pricing and SLA commitments follow an agreed proposal.
We include licence models, deadlines and responsibilities in planning and prepare renewal decisions. Co-termination, subscription and existing per-device estates differ. Availability, conversion and entitlements are checked for your organisation; licence purchases are not automatically included in operations.
No. Applications, routing, security requirements and your operating model determine the direction. We assess Meraki, Catalyst and combinations. Cloud region, access and privacy requirements are part of project discovery; cloud-managed is not a blanket compliance certificate.
Yes. We can support design, rollout and operational tasks as an agreed white-label delivery partner. Customer contact, responsibilities, handovers and escalation paths are established in advance.
Cloud monitoring for Catalyst stopped working on 31 March 2026, and migrating into Meraki management mode resets the switch. Why the decision now falls earlier than it used to.
6 min readRollout · OperationsOne template per site type, claiming by order claim key, exceptions named rather than collected: the parts of a Meraki rollout that are expensive to correct afterwards.
7 min readProcurement · OperationsCo-termination averages every term onto one shared date, subscription licenses per network. What that means in a branch estate — and why the two models behave fundamentally differently at expiry.
13 min readWireless · Law and engineeringOperator liability is abolished, information and data protection duties remain. What a guest network needs technically and legally — and what it explicitly does not need.
6 min readWireless · Spectrum policyEurope has earmarked the upper 6 GHz band for mobile. Why Wi-Fi 7 is still the right call — if you plan it around 160 MHz and MLO instead of 320 MHz.
9 min readNext step
Briefly describe your situation and the support you need. Together, we establish the right starting point, prerequisites and next step.
Start a Meraki enquiryAssessment → first dependable change
