2 min lesson
Make the tradeoffs legible
Use the lesson to respond to this: "Finance and Infra keep re-arguing the cost-per-user number every month. What's the structural fix and why does it work?" Keep the answer plain.
Step 1 of 3
Make the tradeoffs legiblethe recurring decisions Finance must own with you
- Latency vs. cost: a faster small model is cheaper but may lower acceptance; price the quality delta, don't just quote the savings.
- Reserve vs. on-demand: reserved cuts unit cost but bets on sustained demand; show the breakeven utilization where the commitment pays off.
- Build vs. buy: an in-house model trades upfront R&D for lower recurring COGS; give Finance the payback period, not a vibe.
You earn a seat in the resource-tradeoff room by being right repeatedly. The first time your attributed total reconciles to the actual bill, Finance starts trusting the next number before they check it. That trust is what lets you influence without authority - your credibility is the only lever you have when there's no thick management layer to escalate through.
Don't present an engineering tradeoff as if the answer is obvious from the engineering side. "We should obviously batch more" ignores the latency cost a product owner cares about. Frame it as a decision with owners - Infra, Finance, Product - and bring the dollar figure that lets them actually decide.