Selected work · IT operations and tooling

Systems that
changed the outcome.

Operating results first, then the tools and side projects I build. My contribution is called out plainly on every example.

Operations results

01Service transformation
76% → 96%

SLA recovery program

Service Management Office Lead · Tessenderlo Kerley · 2023 to 2025

Raised incident SLA compliance within the first year by replacing informal triage and escalation with a visible, repeatable operating system.

Service-level agreement compliance on a common 0 to 100% scale
Baseline
76%
Within year one
96%

+20 percentage points. Rebuilt triage and escalation, made performance visible, and coached the team against a shared operating rhythm.

My contributionWorkflow design · KPI reporting · team coaching · escalation ownership
  • ITSM
  • SLA management
  • Leadership
02Team and operating model
1 → 15

Global support at scale

Help Desk Manager · Nextiva · 2016 to 2022

Grew the help desk from one person to fifteen. Built the team, processes and reporting to support company growth from 200 to 2,800 employees across multiple countries while maintaining daily service and primary ownership of P1 and P2 incidents.

Two distinct measures of growth
Company employees200 → 2,800
Help-desk team1 → 15

The measures are shown separately: company growth provides operating context; team growth is my direct leadership result.

My contributionHiring · process design · service metrics · multi-country operations
  • Service delivery
  • People leadership
  • KPI reporting
03Infrastructure modernization
1,000+

Three programs, one global fleet

Service Management Office Lead · Tessenderlo Kerley · 2023 to 2025

Delivered Windows 11, Zscaler and AV infrastructure programs for users across the US and Mexico, on time and within budget.

Three programs delivered across one 1,000+ user fleet
  1. Windows 11Endpoint migration
  2. ZscalerZero-trust deployment
  3. AV infrastructureInfrastructure refresh

All three programs were delivered on time and within budget across the US and Mexico.

My contributionProgram leadership · change planning · vendor coordination · delivery
  • Endpoints
  • Zero trust
  • Change management
04Internal platform
One operating view

IT operations dashboard

IT Leader · Eastside Exterminators · 2026 to present

Created a team-facing home for runbooks, procedures and current platform state so operational knowledge is available without depending on one person.

Conceptual internal operations structure
RunbooksHow work is doneProceduresWho owns each stepPlatform stateWhat needs attention

Conceptual structure only. The live dashboard and company data remain restricted.

My contributionInformation architecture · documentation · operational tooling
  • Runbooks
  • Platform health
  • Continuous improvement
Internal case study · no private data published

Tools I built

05SaaS governance
Usage · spend · access

saasguard

Creator and developer · independent build

Built a consolidated view of SaaS usage, spend and accounts that remained active after offboarding when no existing product answered all three questions.

Saasguard schematic with fabricated demo records for usage, spend and access review.
Conceptual interface · I used fabricated demo names and totals, so no company or employee data is shown.
  • Usage, spend and access signals converge in one review queue.
  • Exceptions identify the next operational action.
  • Microsoft Graph and Microsoft Entra ID supply the underlying signals.
My contributionProduct definition · data model · application development
  • TypeScript
  • Microsoft Graph
  • Entra ID
View source (opens in a new tab)
06Workplace operations
Floor plan as data

Floorcraft

Creator and developer · independent build

Turned desk assignment across multi-floor hybrid offices into a visual source of truth with reassignment history and room to scale beyond a spreadsheet.

Floorcraft public interface showing an office plan with desks and dimensions.
Public interface capture · I designed, engineered and deployed the independent product.
  • The floor plan is the working surface, not a separate attachment.
  • Seats and dimensions stay visible in the same planning view.
  • Assignment history replaces a fragile spreadsheet handoff.
My contributionProduct design · front-end engineering · deployment
  • React 19
  • TypeScript
  • Vite
Open Floorcraft (opens in a new tab)

Side projects

07Consumer web app
Every issue and variant

Absolute DC Tracker

Creator and developer · independent build

Built a public collection tracker for DC's Absolute line covering every series, issue and cover variant, with release dates, pull-list subscriptions, owned/missing filtering and import/export.

Absolute DC Tracker public interface showing collection totals and navigation.
Public preview capture · I designed and built the independent product.
  • Collection totals give an immediate progress readout.
  • Series and release views answer different collection questions.
  • Ownership, upcoming releases and estimated value share one model.
My contributionProduct design · front-end engineering · authentication · data modelling
  • Firebase auth
  • Netlify
  • Variant-level data
Open Absolute DC Tracker (opens in a new tab)
08Personal data tool
Seven tabs, one board

Absolute Run Tracker

Creator and developer · independent build

Turned a seven-tab collection spreadsheet into a live status board that answers two questions on a phone: what to buy next, and what to read next.

Absolute Run Tracker interface showing collection totals, purchasing alerts and navigation.
Public interface capture · I built it to parse the workbook in the visitor's browser.
  • Buy-next alerts separate missing issues from incoming orders.
  • Reading order uses the same collection data for a different decision.
  • Seven workbook tabs become one phone-friendly status board.
My contributionData modelling · front-end engineering · in-browser xlsx parsing
  • SheetJS
  • No build step
  • Laws of UX
Open the run tracker
09Small-business web
Live game schedules

Savage Moose Sports Pub

Creator and developer · built and run for a Kenmore pub

Built and operate the pub's public site: hours, lineup, and an "On the big screen" board that pulls Seahawks, Huskies, Mariners, Kraken and full NFL-week schedules live from ESPN, with a static fallback so the page never shows an empty slate.

savagemoose.org homepage showing the pub's hero, hours and game schedule.
Public site capture · I designed, built and run the site for the pub.
  • Game schedules come live from ESPN, with a static fallback at build time.
  • One page answers the three questions a visitor has: when, what's on, what's pouring.
  • Hours, lineup and tap list sit on one page a phone can read at the bar.
My contributionProduct design · React Server Components · ongoing operation
  • Vite RSC
  • Netlify
  • Live data
Open savagemoose.org (opens in a new tab)
10Reference site
Spoiler-safe by default

The Keywork

Creator and developer · independent build, run at heavensfence.com

An unofficial guide to The Amory Wars, the concept-album saga behind Coheed and Cambria, built so a new listener can explore characters, terms and story beats without being spoiled: every entry is gated to how far the reader has gone. Static HTML, CSS and vanilla JavaScript with no build step and no dependencies; tests run on Node built-ins, and a content check validates every entry. Artwork is used with the rights holder's written permission.

The Keywork homepage at heavensfence.com showing the guide's entry points.
Public site capture · I designed, built and run the guide; artwork used with the rights holder's permission.
  • Every character, term and beat is gated to the reader's chosen progress.
  • No build step and no dependencies keep the site portable and cheap to run.
  • A content check and Node built-in tests pin the data before each deploy.
My contributionInformation architecture · spoiler-gating model · content research · interactive map · tests
  • No build step
  • Vanilla JS
  • Content model
Open heavensfence.com (opens in a new tab)
The operating principle

Make the work visible.
Make the result repeatable.

That applies to a service desk, a global rollout and a product built from scratch.

© 2026 Robert CastoBothell, WashingtonIT operations leadership