I'm Sammy. I'm a builder.

I spent my career in finance working almost exclusively with service and consumer businesses, with much of that time focused on residential and commercial services. These are operationally complex businesses where the schedule, the crews, the trucks, the materials, and the invoices all have to line up every single day.

Most were founder-led or family-owned, and I often worked with them through their first institutional partnership, alongside owners and management teams at the board and executive level. In that time, I evaluated and worked alongside businesses ranging from roughly $1 million to more than $500 million in revenue across residential and commercial services, manufacturing, food and beverage, ecommerce, beauty, and multi-unit retail and restaurants. Residential and commercial services were where I spent much of my time, and where I found the work most compelling, but that broader exposure gave me a portable toolkit and a contrarian perspective rooted in bringing proven ideas from leading operating models elsewhere to problems too often viewed through a single industry lens.

I originally found my way into that world for the finance itself, but what kept me there was the people and the work. The best part was never the transaction. It was sitting alongside an owner and management team, figuring out what would unlock the next stage of growth, and helping build the organization, processes, and reporting to support it.

I have always been drawn to building things and figuring out how they fit together, and that instinct has shaped the way I approach these problems. My favorite problems are the messy ones, whether it is a pipeline living in a notebook, the roughest spreadsheet you have ever seen, or a pile of disconnected information that everyone knows holds the answers but no one has had the time to untangle.

I like taking all of that in, finding the structure underneath it, and turning it into something the business can actually run on. That means cleaning up the information, making it visible, and building a way to track it that fits the team's habits instead of fighting them.

I have worked with businesses at every point on the technology curve, from operations run out of journals and notebooks to teams buried under systems far more complex than they need. That range taught me to look at the operating problem and the financial consequence together. It also taught me that the right answer is often neither the most manual nor the most sophisticated one. A process is not better because it looks sophisticated. A system is better when it makes the business easier to run, more profitable, and less dependent on any one person.

Across those businesses, I kept watching the same pattern play out. The reporting gets rebuilt, the processes get documented, the organization gets designed, and the operating machinery finally catches up to the business, but often only when the company is preparing for a transaction or after a new owner has stepped in. By then, the owner has often spent years carrying complexity that better infrastructure could have relieved, and much of the value those improvements create accrues to the next owner.

None of that machinery is a secret, and no owner should have to sell the company to gain access to it. I started Jobcard to make it available earlier, combining institutional operating rigor with modern technology and automation, then purpose-building it around the way your business actually runs across organizational design, process and workflow architecture, and reporting and dashboarding. The result is a practical operating system built for your business, not imposed on it.

There is no single right system and no one-size-fits-all playbook, so every engagement starts with understanding how your business actually runs. I learn the existing processes, tools, habits, workarounds, and points of friction. I look for what is already working, what needs to change, and what the team will realistically use.

The goal is not to pile on more technology or replace what already works. It is to build the simplest durable system that solves the problem and keeps working as the business changes. Then we scope the build together, with a clear view of what matters now and what can wait.

I'm based in Los Angeles, and when you work with Jobcard, you work directly with me. I learn how your business runs, design the system around it, and work hand in hand with you through implementation to make sure it works in practice.