I’ve always been curious about how things work behind the scenes.
I came from sales development, where I worked in Salesforce and HubSpot. Over time, I found myself paying more attention to the systems around the actual selling: how information moved between people, where handoffs broke down, and whether the CRM reflected what was really happening.
That gradually pulled me toward CRM and operations work.
Working in sales development gave me firsthand experience with Salesforce as part of the day-to-day sales process. I maintained records, worked through lead and opportunity handoffs, used reports to understand activity, and saw how unclear data or process rules could create friction for the people using the system.
More recently, I’ve been building my own Salesforce and HubSpot projects to go deeper into that kind of work. When I want to understand something better, I usually learn by building it, testing it, and working through what doesn’t behave the way I expected.
I usually want to understand the process before I automate it. That means looking at who owns each step, what the next person needs, and what should happen when information is missing.
Where I’m headed
I’m looking for CRM and operations work where I can help support and improve the systems revenue teams rely on. I love learning how systems and processes fit together, where they break down, and how different people approach improving them. I want to bring my own ideas to that work, learn from the people around me, and keep building from there.