The Career Behind the Perspective

This chapter of my career has focused on applying the same principles that guided my work in enterprise technology — customer understanding, operational clarity, workflow design, and decision support — to building businesses from the ground up.

As a co-founder of Mrs. Clean Inc. in Guyana, I helped establish a Local Content Certified business serving commercial and industrial customers. Building the company required navigating supplier relationships, operational processes, digital presence, and the realities of launching and growing a business in an emerging market.

In parallel, I co-founded Gallivanting Travel, applying customer guidance, workflow design, and decision-support principles to create a more thoughtful and personalized travel planning experience.

Rather than focusing on AI as a standalone technology, my work has centered on reducing ambiguity, improving decision quality, and creating practical systems that help people navigate increasingly complex choices.

My time at iboss introduced me to the rapidly evolving world of cloud security, Secure Access Service Edge, and Zero Trust architectures. The role expanded my perspective beyond infrastructure visibility into identity, access control, and modern security transformation initiatives.

Working with organizations evaluating cloud-delivered security models reinforced a lesson that would follow me throughout my career: successful technology adoption depends as much on organizational readiness, trust, and clarity as it does on the technology itself.

Transitioning into Sales Engineering expanded my role from solving technical problems to helping organizations evaluate strategic technology decisions. I worked closely with executives, architects, administrators, and technical teams to align business objectives with platform capabilities across a wide range of industries.

The position combined technical expertise, customer education, solution design, and executive communication. It also provided opportunities to represent the organization publicly through webinars, customer workshops, industry conferences, and Tech Field Day.

As Ipswitch expanded through acquisitions, enterprise growth, and increasing product complexity, my responsibilities evolved from engineering-adjacent leadership into enterprise escalation management, customer advocacy, product adoption, and long-term customer success.

I became a bridge between customer outcomes, product capabilities, and business objectives — helping organizations navigate complex technical challenges while ensuring they continued to realize value from their technology investments.

This period reinforced a lesson that continues to influence how I approach leadership today: symptoms and root causes are rarely the same thing. Successful outcomes required understanding not only the technical issue, but also the operational, organizational, and business factors surrounding it.

Shortly after joining Ipswitch, I was promoted into a Team Lead role and later assumed multi-team management responsibilities as the organization expanded. As the company grew, I helped build the support organization through hiring, onboarding, coaching, mentoring, and developing new engineers.

As the team grew, I worked to establish consistent investigative methodologies, escalation processes, knowledge-sharing practices, and customer communication standards. Developing people became as important as solving technical problems.

At the same time, I became a key part of the customer-to-engineering information flow connecting support, development, QA, documentation, product management, and engineering leadership.

Looking back, this period established the foundation for how I approach leadership today: investing in people, creating clarity, building alignment, and helping organizations navigate complexity through shared understanding.