Aaron Weaver

Twenty years in the seat

I’ve spent twenty years building and running operations inside service, engineering and field-driven businesses in Texas, including scaling a multi-market firm past $10M as VP of Operations and co-owner. I’m also a co-founder of TCB Structural.

I focus on what’s actually happening in a business, not what’s supposed to be happening. Most operational problems aren’t people problems. They’re system and accountability problems.

I’ve been in the field, in the office and in the owner’s chair, so I usually know where the work is breaking before I open a single tool.

Longhand first.

You need to understand how to do it longhand before you can take a shortcut (use AI).

I ran my first change management project about fifteen years before I knew the term existed. I started as a scheduler, picked up certifications, and ended up managing inspection teams across five Texas markets. Every city ran its own way, with its own systems and its own reporting. What worked wasn’t a mandate. It was being honest about the goal and inviting the people affected to help build the fix.

At my prior company, CRM, projects, process, invoicing and client communication each lived in a different spot, and the gaps between them were where things got lost. I never set out to build an ERP. When I co-founded my next company, I just needed one place where the work actually lived, so I built it myself out of necessity, one connection at a time.

Along the way I learned the efficiencies, then simple automations and integrations to tie it all together.

Now I use automation, AI and LLM tools to go even further.

The tech is the easy part to learn. The full picture of how a business operates takes years of experience.

How I work

1. Identify what actually happened, not what someone thinks happened. Then decide: one-off, or something the system will keep producing.
2. Define why. Root cause, not the first plausible story.
3. Measure what it cost. Real numbers, even rough ones. What gets quantified gets taken seriously.
4. Track it, to find out if you called it right, and later, whether the fix held.
5. Improve the checkpoint that should have caught it.
6. Repeat, because the first version is never the final one.

None of this is complicated. It just takes consistency and discipline.

What owners say

Questions owners ask