Most of what Alonzo builds is the unglamorous half of answering an RFP: reading the questions out of whatever file they arrived in, holding a draft to its approved sources, and deciding which answers a person has to look at before they go back to a buyer.
The part he is known for is model economics. Which tier each step of a workflow actually needs. Where the quality floor on a cheap model sits this month, which is not where it sat last month. What a provider’s pricing and terms mean for a system you have to keep running for years after the launch post. Tribble’s routing is his design, and so is the decision not to tie the platform to a single provider, which is why a questionnaire does not cost frontier prices end to end and why changing models here is a configuration change rather than a rewrite.
He follows the frontier closely enough to be unimpressed by most of it, and he is usually several steps past a headline before the rest of us have finished reading it. The post below started as him disagreeing with an article in Slack.