- Zen IT Technologies
- Network & Infrastructure
Nobody notices a network that works.
Wi-Fi that drops in the same corner of the office. A firewall carrying rules added at 2 a.m. four years ago. A server room that grew over the years without a plan. Network problems get tolerated for years because each one on its own is survivable. Together, they make an office feel like it is fighting the people in it.
We design networks deliberately: survey first, then channels, then policy. Then we build them and run them. From copper to cloud.
The problem
Most networks were not designed. They were extended.
There was a plan once, for a smaller company in a different office. Everything since has been an addition: an access point where the complaints were loudest, a firewall rule to unblock somebody on a deadline, a switch bought when the ports ran out. Every individual change was reasonable. The result is not.
These are the failures we get called for, and they repeat:
-
Wi-Fi that fails in the same places.
Access points positioned for cabling convenience rather than coverage, channels overlapping each other and the neighboring tenants, and transmit power turned up until the cells collide with themselves.
-
A firewall nobody will touch.
Rules accumulated over years, each added for a reason that was never written down, and now nobody will remove one in case something stops working.
-
Firmware left where it shipped.
Edge devices running the version they arrived with, and a management interface reachable from more places than anyone intended.
-
Core services pointing at themselves.
Time and name resolution configured in a hurry, then quietly responsible for years of certificate and authentication failures that appeared to have nothing to do with either.
-
One flat network.
Guests, staff, printers, cameras and IoT sharing a single segment, because separating them was always going to be a project for next quarter.
-
A server room that grew without a plan.
Unlabeled cabling, no patching record, and a rack only one person knows well enough to work in safely.
-
Nothing written down.
No topology, no VLAN plan, no channel plan. The next change is guesswork and the last one cannot be reversed.
What we do
- Wireless design and RF survey
- Core network services
- Office and site buildout
Monitoring and documentation
-
Wireless design and RF survey
Predictive survey before any hardware is bought, based on floor plans and construction materials rather than on where the sockets are. Access point placement, channel plan and transmit-power plan designed together, because raising power without planning channels is what causes most of the problems it is meant to solve. Controller configuration, followed by a validation survey to confirm the design survived contact with the building. High-density and multi-floor environments included, where the interference that matters is usually coming from your own floors.
-
Firewall, VPN and edge security
Policy review and rule consolidation, with each surviving rule attributable to a reason. Review of what is reachable from outside, with management interfaces limited to the networks and locations they should be reachable from. Firmware assessment and a sequenced upgrade plan where the version in place has known issues. Site-to-site and remote access configured and documented, including migration toward identity-aware access where that is the direction.
-
Switching and segmentation
VLAN design that separates guests, corporate devices, printers, cameras and IoT, with inter-VLAN policy written deliberately rather than left open. Uplink and trunk design, PoE budgeting that accounts for what the access points actually draw, and a documented port map so the next person can find things.
-
Core network services
DHCP, DNS and NTP designed deliberately rather than inherited from whatever the router happened to provide: consistent DHCP options across sites, appropriate internal or managed resolvers, reliable time sources, and upstream services configured without circular dependencies. Unglamorous, and the cause of a surprising share of certificate and authentication failures.
-
Office and site buildout
New offices, relocations and floor expansions, from server room to desk. Structured cabling and rack design, meeting-room and AV technology, physical security and IoT equipment, and the coordination with contractors and landlords that decides whether the network is ready on the day people arrive.
-
Monitoring and documentation
Uptime and reachability monitoring with alert routing that goes to a person rather than an inbox. Topology, VLAN map, channel plan and runbooks maintained as part of running the environment, so somebody other than us can understand how the network is built.
Technical notes
Why office Wi-Fi fails at capacity, not coverage
Adding access points to a congested floor usually makes it slower.
How it runs
-
Survey.
What is actually deployed, what it is configured to do, and where the RF environment is causing problems. Predictive modeling for new sites, on-site measurement for existing ones.
-
Design.
Access point placement, channel and power plan, VLAN and policy model, and the upgrade sequence. Written and agreed before hardware is ordered.
-
Deployment.
Installed, configured and validated around the business, with as little disruption as possible. Existing services stay up during the transition.
-
Managed.
Monitored, patched and adjusted as the office and the headcount change. The channel plan survives someone else touching it because it is documented.
Proof
-
An office Wi-Fi deployment that stopped generating tickets.
AI infrastructure company
Predictive RF survey, channel and transmit-power planning, followed by a controller rebuild. The Wi-Fi support queue emptied and stayed empty.
-
A multi-floor office network designed before the fit-out.
Technology company
Access point placement, channel plan and switching designed from floor plans ahead of construction, so the network was commissioned alongside the office rather than remediated after everyone had moved in.
-
Core network services rebuilt across sites.
Financial services company
Internal time and name resolution moved off self-referential upstream configuration onto dedicated internal services, rolled out across sites by DHCP option, with the design and a runbook handed to the internal team.
Client examples are anonymized by design. References are provided privately, on request, and with the client's consent.
Who this is for
Companies with a physical office where the network has become a recurring subject in conversations it should never appear in: a standup, a board meeting, an all-hands. Teams fitting out a new space, expanding onto another floor, or arriving at a building where the previous tenant's cabling is now their problem.
Also companies who suspect the answer to a chronic complaint is not more hardware. It frequently is not. Adding access points to a badly planned deployment usually makes it worse, and we would rather survey first and tell you that.
If you are fully remote with no office and no on-premises equipment, this is not for you. The expertise does not disappear: VPN, routing and connectivity problems still land on remote teams, and they get the same treatment. But that work belongs inside an environment we already manage, rather than a standalone project.
Frequently asked questions
-
Do we need a survey, or can you just add more access points?
A survey, in almost every case. Wireless problems are usually interference and channel overlap rather than insufficient coverage, and adding access points to a deployment that was never planned typically increases the interference and makes the symptom worse. A survey is a fraction of the hardware cost and frequently reduces the hardware you need.
-
Our Wi-Fi is slow. Is that the internet or the network?
Those are different problems with different fixes, and the answer is usually visible quickly. Circuit saturation, misconfigured QoS, an RF environment where clients are retransmitting, and a DNS resolver adding latency to every lookup all present as “the Wi-Fi is slow” to the person experiencing it. Establishing which one it is takes a lot less time than most people expect.
-
Can you work with our existing hardware, or does this mean replacing everything?
Most engagements start by configuring what you already own properly, and a meaningful share of them end there. Where we recommend replacement, it is because the platform cannot meet a specific requirement such as capacity, standards support or supported firmware. We explain the reason before anything is ordered.
-
Do you do the physical work, or only the design?
Both, in Israel: server rooms, racks, cabling, access points, switching, and the IT, IoT, security, and AV equipment that goes with them, including meeting-room technology. Internationally, the design, configuration and validation are remote, and we coordinate the physical installation with local technicians. Configuration and management are identical either way.
-
What happens to the network after you build it?
You get the topology, the VLAN map, the channel plan, the configuration and the runbooks, and they are yours whether or not the relationship continues. From there it is either handover to your team or ongoing management as part of a wider engagement.
Find out what your network is actually doing.
A 30-minute call with Jonny. We reply within one business day.