About

Operating foundation

My earliest operating lessons were KPI dashboards, measurement systems, and how service businesses are run when management needs clear visibility. Very early, I also learned a harder truth: the software never captures everything the business actually needs to know.

Real operational truth always spills into side trackers, external workflows, and management memory. That is why I do not confuse CRM usage with operational control.

From there I moved deeper into payroll, pricebook design, dispatch, customer service, and management decision-making. That operating exposure taught me that profit is not only about driving revenue, but about how revenue is structured and protected.

How I build structure

I built an entire pricebook using LLM workflows and schemas. That was not just pricing work. Each service became a mini operating system: service language, warranty framing, execution steps, repeatable structure, and SOP logic embedded directly into the offer.

Later, when I moved from ServiceTitan to Housecall Pro, I experienced the drop in system depth directly. But because I had already learned the underlying operating model, I could still make Housecall Pro perform by layering management structure on top.

That is the core of my work today: bridging the gap between what software can show and what leadership still has to decide, own, and enforce.

Leadership lens

Because I came up inside a family business, I was exposed to management rooms and real decision-making earlier than most operators. My operating philosophy is simple: leadership means making the decisions no one else can make, and taking accountability for the outcomes.

What shapes my approach

• I learned operations inside management environments, not theory-first consulting environments.
• I learned that software visibility is not the same thing as operational control.
• I learned to identify where dashboards stop and management judgment has to begin.
• I learned that profit is structural: pricebook logic, labor, warranty, job steps, service language, and margin discipline.
• I learned to convert messy operating reality into repeatable structure teams can execute.
• I am not trying to be the star. I build rooms that function.