My work in CRM automation is shaped by a background in front-end development and project coordination.
That combination shapes how I approach systems: I care deeply about structure and logic, but I’m equally focused on how people experience working within them.
Over time, my role has evolved toward CRM automation and platform work — designing workflows, managing pipelines, documenting systems, and supporting teams as those systems grow and change.
I approach CRM and automation projects with an emphasis on clarity, maintainability, and long-term usability.
My goal is not just to make a system function, but to make it understandable and transferable.
I’ve seen firsthand how undocumented systems become fragile over time.
Documentation turns automation into something teams can confidently inherit, maintain, and improve. It reduces risk, improves onboarding, and gives teams confidence to make changes without breaking critical processes.
This philosophy guides how I build systems — whether I’m creating internal runbooks, client training guides, or system maps for complex, multi-platform setups. I focus on making systems understandable, transferable, and maintainable.
I’m focused on CRM automation and GoHighLevel implementation work that supports operational clarity and scalable growth. I’m especially interested in roles that bridge technical configuration and day-to-day operations — where systems thinking, documentation, and collaboration matter.
Outside of work, I enjoy projects that balance creativity and structure — whether that’s building and maintaining personal websites, traveling (opens in new tab) (often with my dog, Luna (opens in new tab)), or working on long-term projects that evolve over time.
Those interests mirror how I approach professional work — thoughtfully, iteratively, and with attention to detail.
