Office moves & new sites
Cabling, comms room build, connectivity ordering, hardware relocation and a working desk on day one.
Home/Services
Everything between the socket and the screen
WB Tech Systems is registered under SIC code 62090 — other information technology service activities. In practice that means we take operational responsibility for the systems an organisation depends on every day, and we do not stop at the boundary of any one vendor's product.
Service line 01
Managed IT support & service desk
One route in for every user, staffed by engineers who already know your estate. We triage against agreed priorities rather than volume, so a warehouse scanner that has stopped the loading bay outranks a font that looks wrong in a slide deck.
- Unlimited user ticketsEmail, phone and portal, with no per-incident charging and no cap on how often people ask for help.
- Priority-based response targetsP1 in 30 minutes, P2 in 2 working hours, P3 in 1 working day — written into the agreement, not aspirational.
- Remote-first, onsite when neededMost faults clear faster over a remote session; hardware, cabling and site work get an engineer in person.
- Monthly reporting that means somethingTicket volumes, recurring causes and the fixes we propose so the same fault stops coming back.
How we grade an incident
Priority is set by business impact, not by who raised it.
- P1 — Site or critical system down
- 30 min
- P2 — Degraded service, team blocked
- 2 hrs
- P3 — Single user fault or request
- 1 day
- P4 — Scheduled change or advice
- 3 days
- Monitoring alert
- Auto-raised
Targets are for first meaningful response by an engineer. Resolution times depend on the fault and are reported against each month.
Under management
The components we monitor, patch and document as standard.
- Physical & virtual servers
- Monitored
- Firewalls & edge routing
- Managed
- Switching & structured cabling
- Documented
- Wireless networks
- Managed
- VPN & remote access
- Managed
- UPS & comms room environment
- Monitored
- Broadband & connectivity suppliers
- Liaised
Service line 02
Network & infrastructure management
Infrastructure fails quietly long before it fails loudly. A disk in a degraded array, a firewall running firmware three years old, a switch port flapping at 2am — all of it is visible to monitoring and invisible to everyone else until the morning it is not.
- 24/7 automated monitoringAgents on servers and network devices raise a ticket automatically, day or night, before a user notices.
- Published patch windowsOperating system and firmware updates applied on an agreed schedule, tested first where the change carries risk.
- Capacity and health reviewDisk, memory, licence and warranty headroom reviewed monthly so replacements are planned rather than emergency-purchased.
- Documentation you can readTopology diagrams, addressing plans and firewall rule justifications kept current — the comms room stops being a mystery.
Service line 03
Endpoint & device lifecycle
A device is only cheap on the day you buy it. The cost sits in the build, the licences, the support calls it generates, and the data left on it when someone leaves. We manage the whole arc so none of those become someone's side job.
- Standard buildsOne agreed image and application set per role, so any replacement machine behaves like the one it replaced.
- Zero-touch enrolmentNew hardware ships to the user and configures itself on first sign-in — no engineer visit to hand over a laptop.
- Starters, movers and leaversAccounts, licences, group membership and device access processed to a written checklist, with leaver access closed the same day.
- Refresh and secure disposalAn asset register with warranty dates and refresh planning, and certified data erasure or destruction at end of life.
Lifecycle stages we own
Each stage has a checklist and leaves a record on the asset.
- Specify & procure
- Stage 1
- Build, enrol & encrypt
- Stage 2
- Issue to named user
- Stage 3
- Patch, monitor & support
- Stage 4
- Reassign or refresh
- Stage 5
- Wipe, certify & dispose
- Stage 6
Tenant administration
Routine work that keeps a cloud workplace from drifting.
- Identity & group management
- Ongoing
- Multi-factor & conditional access
- Enforced
- Licence right-sizing
- Monthly
- Mailbox & shared mailbox hygiene
- Ongoing
- SharePoint & Teams structure
- Reviewed
- Access & permission review
- Quarterly
- Renewal & term tracking
- Diarised
Service line 04
Cloud workplace & Microsoft 365
Cloud tenants drift. Licences outlive the people they were bought for, permissions accumulate, and a shared folder that started as a convenience ends up holding the only copy of something important. Administration is what stops that happening.
- Licences matched to headcountUnused and over-specified licences identified every month — this alone often pays for a meaningful part of the support fee.
- Access that is granted, not inheritedPermissions reviewed on a schedule, with joiners given a role and leavers removed the same day.
- Sensible structureTeams, sites and shared drives organised so people can find things without asking, and so backups know what to protect.
- Migration when you need itMoving from on-premise Exchange, Google Workspace or a legacy file server, planned around your working week.
Service line 05
Backup, continuity & recovery
A backup that has never been restored is a hypothesis. We treat recovery as the service and the backup job as an implementation detail, which means testing restores on a schedule and writing down how long each one actually took.
- Monitored jobs, on-site and off-siteFailures raise a ticket automatically. Nothing depends on someone remembering to check a console.
- Scheduled restore testingSample restores performed on a documented cycle with the result and elapsed time recorded and shared with you.
- Agreed RPO and RTOHow much data you can afford to lose and how long you can afford to be down, decided by you and engineered to.
- Cloud data includedMicrosoft 365 mail, OneDrive, SharePoint and Teams content protected — the platform's retention is not a backup.
- A continuity plan people can followWritten steps, contact tree and priority order for bringing services back, kept somewhere reachable when the network is not.
Recovery planning
Set per system during onboarding, then engineered to.
- Recovery point objective (RPO)
- Agreed
- Recovery time objective (RTO)
- Agreed
- Off-site copy
- Standard
- Immutable retention
- Where supported
- Restore test cycle
- Scheduled
- Written test result
- Every test
Service line 06
Deployments, migrations & IT projects
Project work is quoted as fixed scope and fixed price, planned around your operating hours, and carries a rollback position at every stage. If a cutover has to happen at 2am on a Sunday so the warehouse opens normally on Monday, that is when it happens.
Mail & file migrations
Exchange, Google Workspace and file-server moves to Microsoft 365 with mailbox and permission mapping checked before cutover.
Server & storage replacement
Specification, build, data migration and decommissioning — including virtualisation consolidation and end-of-life Windows Server upgrades.
Network & wireless refresh
Site surveys, switch and access-point replacement, VLAN and guest network design, and firewall rebuilds with documented rules.
Security hardening
Multi-factor rollout, admin account separation, endpoint protection, patch remediation and preparation for a Cyber Essentials assessment.
Windows & application rollouts
Estate-wide operating system upgrades and line-of-business application deployments, piloted with a small group before the full rollout.
How an engagement runs
No open-ended day rates
Whether you are taking managed support or a single project, the shape is the same: we agree what is in scope, what it costs, and what "finished" looks like before any work starts.
Step 01
Conversation
A short call about how you work, what breaks, and what you are trying to change. No charge and no obligation.
Step 02
Audit or scope
For support, an onboarding audit of the estate. For a project, a written scope with assumptions and exclusions listed.
Step 03
Fixed proposal
One document: what we will do, what it costs, the response targets that apply, and the date it starts.
Step 04
Delivery & review
Work delivered against the scope, then a review — monthly for support, at handover for a project.
Next step
Tell us what needs looking after
Users, sites, servers, and who supports you today — that is enough for us to come back with a realistic proposal rather than a brochure.
Or email support@wbtechsystems.org