Infrastructure is a service, not a server room
Uptime only matters because people are trying to work. Every decision — architecture, vendor, monitoring threshold — gets judged by what it does to the person at the other end.
About
Technology that holds up under operational pressure
Sixteen years spent close enough to the infrastructure to know how it fails, and close enough to the business to know what that costs.
My career began where most infrastructure careers do — with cabling, switches, servers, and the phone ringing. It progressed quickly: by 2009 I was carrying a CTO mandate at Gloria de Dapitan, accountable for technology direction rather than only its execution.
The years that followed at Astoria Plaza and, after returning to the group, at Astoria Vacation and Leisure Club, were the ones that shaped how I work. Multi-vendor networks, Nutanix hyperconverged infrastructure, virtualization, monitoring, backup and disaster recovery — alongside supervision of a support team, vendor relationships, procurement, and the documentation that makes a technology function survivable.
Two projects define that period. Representing IT on a Bids and Awards Committee for a GPON infrastructure project taught me that procurement without a post-installation audit is a promise, not a delivery. Planning and executing a data-centre co-location after a serious server-room water incident taught me that continuity planning is only tested once, and always without warning.
More recently my work has moved up the stack: Microsoft 365 and SaaS administration in an education-facing environment, CRM specialism at Booth & Partners, and current business-systems and automation work in financial services — Zoho CRM and Zoho One, APIs, workflows, dashboards, data migration, and AI-assisted automation of manual processes.
I have also studied cybersecurity, data science, data analytics, Python, and JavaScript. I list those as study and exposure rather than professional ownership, because I would rather be accurate than impressive.
Professional philosophy
Three things I hold to
Verify what was promised
Specifications, vendor commitments, and installed reality drift apart quietly. Auditing after delivery is not distrust; it is the only way procurement means anything.
Document it or you do not own it
Undocumented infrastructure belongs to whoever last touched it. Runbooks, diagrams, and training are how a technology function survives its own staff turnover.
Contact
Let's talk
Open to conversations about IT infrastructure, technology operations, service delivery, and business-systems leadership.