Solution architecture · Customer engineering · Enterprise accounts

I bridge solution architecture, software engineering, AI agents and business strategy.

Sean Crowe · Director of Client Success, CHILI publish · still writes the workaround

Where does my software live?
Cartoon Sean, the calm straight man, reacting to the meter
Process, the robot for leading through a repeatable way of working
Beacon, the compass robot that finds the way through an unfamiliar system
Orchestra, the conductor robot that brings teams and people together
Match, the robot that sees the pattern in a mess

I take on the cross-team problems nobody has defined yet.

How defined is yours?

Click a level or drag the needle. Arrow keys move between options. Home and End select the first and last option.

videos and articles

Latest

two stories

From customer work

A customer expansion

Closing the deal and making the customer successful are two different problems.

A billion-dollar global brand was weighing a ~5x expansion, and their agencies doubted the product could handle their templates. I joined the sales conversations and built a template strategy with the agencies and global marketing. Where the product wasn’t there yet for their workflow, I built a browser extension to bridge it. We went from 7 templates to 20+ in the first few weeks of the launch, the customer stayed and the account grew, and I handed it to the account manager and my support team so it didn’t depend on me.

The roadmap

The decision happened in the conversations before the meeting.

I was part of a cross-functional leadership circle. Slow file browsing and file access kept showing up in support tickets. It would go quiet for a month or so, then come back and cause real pain, and most of the company had filed it under tech debt. Before the meeting I talked separately with the product lead, his manager and one of the developers, and framed it around what it meant for each of them. I wanted their view, and I wanted to give them time to talk it over among themselves before anyone had to decide. In the meeting I laid out the pain, what it was costing us, and the long-term choice we had to make. It went on the roadmap and got fixed. We haven’t had the problem since, and file access is faster.

Open to conversations.

Solution architect, teacher, programmer. Director of Client Success at CHILI publish. Ships real software with Claude Code.

Illustrated Sean smiling and offering an open hand toward the contact links

also a functional programming nerd.

Funki, the functional programming robot