Services
This isn't a menu you assemble — it's one relationship. Below is every function a conventional IT department performs, mapped to the internal role that would otherwise perform it.
A monthly invoice shows one line. It doesn't show what that line covers. This is what an organization would otherwise be staffing internally to do the same work.
Service Desk and End-User Support
| Function | Typical internal title | What we perform |
|---|---|---|
| Tier 1 Support | Help Desk Technician | First-line response for staff: password resets, access problems, printing, mail delivery questions, application errors, and day-to-day usage assistance — including outside normal business hours, as a matter of course rather than as an exception. |
| Tier 2 Support | Desktop Support Technician | Hands-on remediation of desktops, laptops, printers, scanners, mobile devices, and peripherals. Operating system repair, driver and firmware management, hardware diagnosis, replacement staging, and user profile migration. |
Infrastructure and Operations
| Function | Typical internal title | What we perform |
|---|---|---|
| Systems Administration | Systems Administrator | Server operating systems, directory services, DNS, DHCP, file and print services, patch management, storage capacity, and account lifecycle administration. |
| Network Administration | Network Administrator | Switching, routing, wireless access points, VLAN segmentation, quality-of-service, firewall rule administration, and internet service provider coordination and escalation. |
| Network & Systems Engineering | Network / Systems Engineer | Design of the network architecture rather than merely its upkeep: segmentation strategy, redundancy, addressing schemes, capacity planning, and the engineering standards each deployment is built to. |
| Backup and Disaster Recovery | Backup / DR Administrator | Full bare-metal image backups of servers and workstations, platform-level backup of cloud mail and files, restore verification, retention policy, and documented recovery procedure. |
| Telecommunications | Telecom / VoIP Administrator | Business telephone system administration — extensions, call routing, voicemail, auto-attendant, carrier and number management, and handset provisioning. |
| Cloud and SaaS Administration | Cloud Services Administrator | Administration of hosted productivity and collaboration platforms: domain and tenant configuration, license assignment, mailbox and group-address management, security policy, and data governance. |
| Physical Security and A/V | Security Systems Administrator | Surveillance camera systems and recording infrastructure, electronic entry and access control, and audio/visual systems — configuration, stability, and operational readiness. |
| Web and Application Hosting | Web / Application Administrator | Website and hosting platform, document and media publication, certificates, access controls, and content delivery infrastructure. |
| Monitoring and Operations | NOC Analyst | Continuous automated monitoring of device availability, network health, environmental conditions, and system alerting — every hour of every day — with investigation and response to conditions detected outside business hours. |
Information Security
| Function | Typical internal title | What we perform |
|---|---|---|
| Security Operations | SOC Analyst | Endpoint threat detection and containment, secure mail gateway administration against phishing and malicious content, DNS-based content and category filtering, alert triage, and incident investigation. |
| Security Engineering | Security Engineer | Perimeter firewall engineering, encrypted site-to-site connectivity, secure remote access infrastructure, endpoint disk encryption, encrypted mail, and hardened administrative access. |
| Identity and Access Management | IAM Administrator | Centralized identity services, certificate-based wireless authentication, multi-factor and hardware-key authentication, privileged credential custody, and joiner-mover-leaver access control. |
Management, Governance, and Executive Leadership
| Function | Typical internal title | What we perform |
|---|---|---|
| Vendor and Contract Management | IT Manager / Director of IT | Management of every technology and communications vendor you hold — providers, carriers, software and hardware vendors, and trades. Includes active review of what you pay for and whether better terms or better technology exist, plus procurement specification, bill-of-materials development, asset and license lifecycle tracking, change control, and documentation. |
| Technology Strategy | Chief Information Officer | Multi-year technology roadmap, capital and operating budget forecasting, refresh and end-of-life planning, and alignment of technology investment to your operational objectives. |
| Security Governance | Chief Information Security Officer | Risk assessment and posture review, security policy, incident response planning, staff security awareness, data protection and retention standards, and regulatory expectations. |
| Technology Direction | Chief Technology Officer | Vendor-neutral evaluation of platforms and products, definition of technical standards, architectural direction, and independent assessment of proposals brought to you by outside parties. |
The four management and executive functions are performed by Jack Nash personally. The remainder is carried out by our engineering staff and engaged specialists, working to the same standards across the same platforms. More on who that is →
That list is the conventional scope. In practice it runs further — commercial kitchen controls, AV and speaker systems, fire alarm relays. If it's technical and your operation depends on it, it tends to end up on our desk.
The work is set by the environment, not by the payroll.
Measured by headcount, many of the organizations we support are small. It does not follow that the environment is small. A handful of people can be operating a full identity platform, a managed network stack, a surveillance system spanning two manufacturers, a file and application server, a telephone system, and public-facing web hosting.
The work in the tables above is determined by that environment. It does not halve because an organization employs six people rather than twelve.
Nor is it set by the working week. A great deal of what our clients do happens when an ordinary office is closed — weekend operations, evening events, seasonal peaks, services and gatherings.
The technology runs throughout all of it. Wireless carries staff and visitors, access control admits people to the buildings, cameras record, audio systems run, and the phones take calls. Reaching us outside business hours is part of the service rather than an exception to it.
We're frequently called into a new client after sloppy, unprofessional prior work left them with an unstable environment nobody wanted to admit to.
Anyone can plug in a device and call it done. We go the extra mile during design, configuration, and deployment — the unglamorous, nuanced details that separate a professional installation from an amateur one. Proper staging. Real burn-in and testing before anything touches production. Naming conventions, documentation, and configurations built to be maintained by someone other than the person who built them.
It's slower up front. It's also the reason things don't quietly fall apart six months later.
New clients almost always tell us the same thing: "I just want it to work." We tell them: so do we.
Our pricing runs on thin margins by design. Every hour we spend firefighting something that should have been built correctly the first time is an hour that costs us money. An unstable environment isn't just bad for you — it's bad for our business model. Doing it right the first time isn't a courtesy. It's how the math works for us too.
Most providers configure something once and walk away. We don't consider that finished.
A client once asked what we'd actually been doing, since there were no active projects on their books that month.
Our answer: things are always changing. Updates, new features, bug fixes, better ways of doing something we didn't know a year ago. The work doesn't stop just because nothing broke.
We take real pride in what we build, and pride means being willing to revisit and improve it — not just defend the original decision because it's already in place. That ongoing attention is part of the relationship, not a separate line item you have to ask for.
We hold our own tools to the same standard. Every year, we review everything running behind the scenes and ask whether it's actually adding value — for us or for clients. If it isn't, we kill it. We used to run a ticketing system, and spent real hours building out the documentation for it. We decommissioned it a few years ago once it became clear our clients preferred texting or emailing us directly over logging into a portal — they're not generating enough volume to need one, they just want to reach a person. So that's how we work now.
The least visible function on an invoice, and the most valuable over time.
We manage every technology and communications vendor you hold. That is the ordinary part — placing the calls, escalating the faults, holding carriers and suppliers to their obligations so your staff don't spend the day on hold.
The less ordinary part is that we evaluate those vendors on your behalf without being asked to. What you're paying, whether the service still fits, whether better terms are available, whether a better technology has arrived since the arrangement was made. Where we find something, we say so — directly, whether or not a billable event is attached to it.
Because we take no commission and sell no product, that review has nothing riding on the outcome. Recommending that you keep exactly what you have costs us nothing.
In June 2026 the FCC broadened existing restrictions on several surveillance camera manufacturers to cover previously authorized legacy models. Equipment already installed doesn't have to come out — but replacement units, spare parts, and firmware distribution through compliant channels are now materially constrained.
Which means a failed camera may not be replaceable in kind, and a camera that stops receiving patches becomes a slowly worsening security liability.
A client running affected hardware received a planned, budgeted refresh recommendation across their normal replacement cycle. No system had failed. No request had been made. The regulatory position simply changed, and someone was reading.
Identifying an exposure before it becomes an emergency, and folding the remedy into a budget cycle rather than a crisis, is the difference between a technology department and a repair service.
Most engagements start with a structured review of your current environment — what's running, what's exposed, and what's being paid for. Findings first, before anyone talks about an engagement.
See how the review works