Suggestion: section on cost-aware system design (per-seat vs per-call tradeoffs)

[patl4588]

Suggestion / discussion: would a section on cost-aware system design be welcome? Specifically:

• Fan-out patterns and how per-call billing ends up cheaper than per-seat at scale
• Cap-and-shed patterns when using metered third-party APIs
• Tradeoffs between flat-rate vendor contracts vs pay-per-call

I've been collecting real examples at patl4588/awesome-saas-replacements. Happy to draft a PR with a new subsection if this is in scope for the primer — or leave it out if you'd rather keep the focus narrower.

Thanks for this repo — it's helped a lot of people.