01 / Why I do this

Growth breaks the office long before it breaks the numbers.

That is the thing I believe about these trades, and almost everything I do comes out of it. A company does not stall because demand dried up or because anybody stopped working hard. It stalls because the office quietly ran out of room, and revenue is the last place that shows up.

So by the time an owner can see the problem in his P&L, he has been living it for a year. He has hired around it twice. He has started believing that the chaos is just what a company his size feels like. And the whole time, the constraint had a name nobody said out loud: a follow-up process living in one person’s memory, a number that only exists after somebody builds a spreadsheet, a phone answered only when the right person happens to be near it.

Left alone, that ends in one place. The owner becomes the constraint. The company cannot grow past him without breaking him, and it cannot sell for what it should be worth, because a buyer looking at it is really buying him.

It is a solvable problem, and it gets treated like a personality flaw instead. I find the thing holding the company back, take it off the owner and off his office, and then go find the next one.

Some of what I build uses AI. That is not what this is. It is the tool that happens to be cheapest right now for work that used to require hiring somebody. If it disappeared tomorrow the job would not change, only how I did it would.

Austin Brooks, founder of Surge Advisory

I’m Austin Brooks. Born and raised in Mesa, Arizona. Married with 2 young kids.

I know what being the constraint feels like from the inside, because I was one.

I started on the phones at a pest control company and worked up to running the inside sales team. Everybody there believed the sales team decided how many jobs got booked. It was not true. What decided it was whether the office got back to people, and how fast. I have never been able to unsee that, and it is why I do not start with your salespeople.

Then three and a half years in B2B software, building sales enablement for a 410-person revenue team. Nearly every problem that got handed to me as a people problem turned out to be a process nobody had written down. Managers wanted to coach harder. The fix was almost always to remove a step, not add effort. That is the lens I bring into your office.

For a stretch of that job I was the constraint myself: running the outreach, the demos, and a good share of the training, because the systems that should have carried that work did not exist. Sixty and seventy hour weeks. A business on the side. I was missing my kids. I did not want anything big that year, I wanted my forty-hour week back.

I got it back by building systems around the parts of the job that were eating me alive, until the work stopped scaling with my hours. That is the whole thing I know how to do, and I learned it on myself before I ever charged anybody for it.

Then I started working with a friend who owns a roofing company, and he was living the week I had just climbed out of. Same sixty hours. Same feeling that the whole thing tips over if he steps away for a few days. So I built him the systems instead of handing him advice, and that is where Surge actually started. Same problem, smaller building, higher stakes.

Most agencies hand you a strategy deck and leave the building to somebody else. I do both, and I think that is the only honest way to sell this. Advice you have to implement yourself is just homework, and you already have enough of that.

Working with me is mostly async. You will not sit on a standing call waiting for an answer I could have typed, and you will not get handed to anyone else. When something breaks at 6am in July, you text me and I fix it.

The deepest work so far has been roofing and restoration, and that is where the numbers on this site come from. The systems themselves are not trade-specific: a quote nobody chased and a referral nobody logged look the same in a clinic, a pest control route, and a professional services firm, because the failure is in how the work moves rather than in what the work is. What does not travel is the benchmark, so I will not quote you an industry average I have not measured.

I build every system myself. That is worth saying plainly before you hire me, along with what I do about it: everything gets documented in writing as it is built, every account and integration is in your name and paid by you, and the offboarding package exists from the first week rather than being assembled on the way out. You can text me when it breaks, and you could also hand the whole thing to somebody else tomorrow without calling me first. Built so you can leave is the only honest version of this when one person builds it.

Tell us what is not working.

Two minutes to write it down, a reply within one business day, and the option to book a call straight away. You keep whatever I find either way.