Ongoing network work
Embedded network engineering for stretched IT teams.
The network work that keeps getting pushed back comes to us: changes, cleanups, upgrades, and the projects waiting on the network to move. We report to your IT director and work alongside your engineers, inside your environment, in your tools and to your standards.
What the work looks like
- Firewall, switch and routing changes, planned to fit the risk
- Cleanup of inherited firewall rules and configurations
- Firmware and OS upgrades, scheduled with you
- Documentation of what's actually running
- The network side of other teams' projects, so they stop waiting
How we work
We match the process to what you need. When uptime matters most, changes come with a written plan, your sign-off and a way back. When speed matters more, we move fast and tell you exactly what changed. Either way, you know what we did.
How it's priced
Ongoing work is how we prefer to work. When we're in your network week to week, we know how it's built and where the risks are, so projects start faster and land cleaner.
Part of that work is paying down technical debt. We make the network more stable, document what's running, and design it so the next change is simple. We build in room for what's coming, so a future change is a configuration update rather than new cabling, and we keep the design consistent, so any engineer can read it and know what to expect.
That makes every project, and every change after it, faster and easier for your team and for ours.
Ongoing work is a flat monthly rate for a set number of engineering hours each week, agreed up front, on a one-year term. The scope is broad on purpose, so you can bring us what you need without a change order for every task. A project does not require it.
We track hours every week. A busy week or two is fine; it evens out over the weeks that follow. If the average runs over your allotment across four weeks, we tell you, and you choose what happens next: hold lower-priority work while current objectives wrap up, add weekly hours to the monthly rate, or scope the extra work as its own project. After-hours work is scheduled with your engineer ahead of time, with critical (P1) outages as the exception.
If the terms change, the new rate starts the day you sign. Earlier days that month stay at the old rate.
The first priority is the reliability and security of what you already run. As day-to-day load comes down, the same hours go toward work that moves the business forward.
We'd like to be your network team for the long haul, and we plan to earn that every year rather than lock you into it. Terms are one year, and we document in your team's own tools as we go, so the documentation is already yours if you go another way.
Who does the work
Senior judgment where it matters, a trained bench for the rest.
Every engineer follows the same method, so your work doesn't change with who's assigned, and it isn't held up waiting on one specific person. The founders still lead architecture and the hardest technical escalations.
Scoped in writing before any work starts. The timeline and price come after technical discovery, not before.
Where we sit on your team
We work alongside your engineers, in your tools and to your standards. We take ownership of your network's projects and problems. We plan the work, do it, document it and tell you what changed. Your IT director sets the priorities.
The short version
Senior network engineers working inside your IT team, reporting to your IT director. Network changes, cleanups and upgrades get done instead of waiting. A flat monthly cost on a one-year term. Scoped in writing before any work starts.