An Operator, Not an Advisor.
I've spent my career right next to the founder or CEO, taking ownership of whichever part of the business was straining under growth.
I ran technology for a family-owned claims firm supporting up to 3,000 field adjusters every storm season. Then I spent nine years running service delivery, reporting to the CEO, first as one of four center directors and then as VP of Service Delivery, while that firm grew from $20 million to $150 million and from 160 people to about a thousand across four acquisitions. Most recently I was brought into a $50 million founder-era manufacturer to build the operating structure it had never had.
Across every one of those companies, the breaking point looked the same: growth outran the old way of making decisions, handoffs between teams started slipping, and everything hard ended up back on the owner's desk. Because I came up through both operations and technology, I don't separate the leadership work from the systems underneath it. I'm comfortable carrying the friction of an overdue people decision in the morning and building the automated scorecard or AI workflow your team needs that afternoon.
I've also done this from the outside, which is how I work now. Two years ago, a construction company doing about $2.5 million a year brought me in when nothing moved unless the founder was in the room. Within 90 days a delivery playbook was running every job under one of the company's own project managers, and the founder got back more than ten hours a week.
Now I do that work directly for founders who are ready to get out of every room, one day a week or every other week, from Fairhope, Alabama and remote, until their own team carries the load.
Trey Sparks on LinkedIn ↗