Builder first, consultant second

Local small businesses that are busy and short-handed at the same time. Trades, professional offices, anyone whose work arrives as phone calls and forms and then sits in a queue somebody has to clear by hand.

The pattern is usually the same. The business grew, the process never got written down, and the people became the glue. So I map the work first: how a job actually moves through your shop, where it waits, and what the waiting costs you every week. Some of that gets automated. Some of it just needs to stop being done twice.

Bookkeepers, CPAs, and MSPs usually spot the mess before the owner names it, so I wrote a page for them. What happens to a client you send me

I came up through payments and fintech, working with US Bank, Elavon, and TSYS, then moved into product management in crypto infrastructure at Blockdaemon.

Big companies are a masterclass in process: thousands of people moving work between them, and every improvement starts with someone mapping how the work moves today.

Along the way I picked up lean and six sigma the working way: value stream maps on real walls, timing real handoffs, sitting in the kaizen meetings where the map gets argued into the truth. That habit stuck harder than any job title.

The inventory, tied to things I have actually shipped: