A ministry product team reported an 8x reduction in inference costs after switching their sermon outline generator to an open-weight model. The finance review celebrated the move. The obvious reading was that cheaper tokens had solved the scaling problem for good.
The numbers told the opposite story. The cost drop masked a new choke point: every ministry-facing paragraph still passed through an unowned routing decision that determined which model handled which request and which outputs reached volunteers. The savings arrived, but the human gate did not disappear.
This is the foundational misread that causes product teams to treat inference price as the only variable that matters. Once the model itself becomes interchangeable, the latticework Charlie Munger described becomes the required tool. You stop asking which model is cheapest and start asking which mental models must sit on top of the routing layer so the output stays usable in a real church setting.
The Cost Drop That Hid the Routing Decision
The team had measured success by tokens per dollar. After the switch, that metric improved dramatically. What they had not measured was the set of rules that now decided, for any given volunteer request, whether the cheap model received the query or whether it routed to a heavier model with better guardrails.
Without a named owner, those rules lived in a shared document that no one updated after the first month. A children’s ministry outline about baptism ended up in the low-cost path and produced text that assumed the volunteer could explain credobaptism versus paedobaptism in a single paragraph. The volunteer printed it anyway. The routing decision had already been made by default.
Munger’s latticework requires holding the cost model and the ownership model at the same time. Price tells you nothing about who carries responsibility when the output reaches a 7-minute volunteer who has never seen the source material before. The cheaper model simply made the ownership gap cheaper to ignore.
When Full Control Still Leaves the Print Step Exposed
One engineering lead argued that open weights gave them full control. They could inspect weights, change system prompts, and run the model locally. That control existed on the server side. It did not extend to the moment a volunteer hit print on a physical lesson sheet.
The SermonCentral team learned this years earlier with curriculum that reached hundreds of thousands of volunteers. The print step exposed every assumption the product team had made about reading level, cultural reference, and time required. No amount of model control fixed the fact that the routing decision upstream had already chosen which version of the content reached the printer.
The latticework here pairs the control model with the distribution model. You can own the weights and still lose ownership the moment the output leaves the product and enters someone else’s workflow. The exposed print step is the signal that the routing decision was never assigned to a human in the first place.
The One Decision Rule That Survived the Model Swap
Across multiple model changes, one rule remained effective: every ministry-facing output must carry a named owner who can reverse the routing decision within one business day. The rule does not require the owner to write the content. It requires the owner to decide, after the fact, whether the cheap path was the correct path.
Teams that kept this rule also kept a simple reversal log. When a volunteer flagged an outline that felt off, the owner could see which model had handled the request and whether the routing parameters needed adjustment. Teams that dropped the rule after the cost dropped found themselves explaining the same quality issues six months later at higher volume.
The latticework makes the tension visible. Cost accounting and ownership accounting are separate models. Treating the first as a substitute for the second produces exactly the outcome observed: cheaper inference that still requires a human gate on every output that matters.
Your Turn: Apply This Today
- Name the single product owner who can reverse any routing decision on your lowest-cost model by Friday; put their name in the runbook and notify the on-call rotation.
- Build a one-line reversal log that records model used, request type, and whether the output reached a volunteer; require the owner to review the previous week’s entries every Monday morning.
- Pick the three most common request categories this week and hard-code a routing preference for each that the owner can change without an engineering ticket.
- Run a 48-hour test where every ministry-facing output from the lowest-cost model is held for owner sign-off before it reaches the print or export step.
- Document the exact condition under which the owner would force a heavier model instead; publish that condition to the volunteer feedback channel so they know when to escalate.
- Schedule a 30-minute calendar block next week for the owner to compare token cost against reversal frequency and decide whether the current routing rule still holds.
The 8x Number That Never Accounted for Inference Routing showed how teams celebrated savings while the real constraint moved. The PM Role That Stopped Shipping and Started Choosing described what happens when that constraint finally receives an owner.
I consult with product leaders building ministry tools on inference routing ownership, reversal processes, and output quality for volunteer workflows. Let’s talk.