Notebook · Signal 2

“Unlimited” until the fair-use clause wakes up

Marketing pages love the word unlimited; contracts love footnotes. Throttling, soft caps, and overage ladders often appear in terms rather than pricing pages. Before you model unit economics for a busy season, locate the clause that triggers rate limits or extra charges—and assume your usage will grow if the tool actually works. The unpleasant surprise is rarely “we grew”; it is “we grew into a pricing tier nobody modeled.”

What to search for in the agreement

Look for definitions of “reasonable,” “fair,” or “excessive” use; for API rate limits that differ by endpoint; for token accounting that excludes certain features from the headline allowance. Map those clauses to your expected peak week, not your average week—especially if AI adoption is contagious inside the company once it proves useful.

Procurement and finance alignment

This signal belongs squarely in procurement & security next to SSO and retention—not because it is “security” in a narrow sense, but because it is a contractual risk that becomes an operational incident when invoices jump. Layer six of the seven-layer framework is where commercial mechanics get explicit: build a three-scenario cost model before you sign.

Three scenarios worth modeling before you sign

Build at least three cost curves: baseline adoption (what you expect if the tool works as sold), contagious adoption (what happens when one team’s success pulls in adjacent teams), and stress (marketing launch, seasonal spike, or API-heavy integration). For each curve, include not only tokens or seats but failure costs—throttling that forces manual fallback, or overages that trigger approval workflows that slow revenue. If the “success” scenario is the only affordable one, you are not buying capacity; you are buying a lottery ticket with enterprise branding.

Organizational behavior that turns soft caps into hard crises

Fair-use clauses do not wake up because usage grew; they wake up because usage grew in a pattern nobody monitored—new hires defaulting to the most expensive path, scripts polling endpoints too eagerly, or “just testing” workflows left on in production. Operational hygiene matters: dashboards for weekly burn against allowance, alerts before soft limits, and a named approver for new high-volume use cases. The alternative is surprise invoices paired with political fights about who “wasted” tokens, which helps nobody ship better software.

Renegotiation: when the contract and the reality diverge

If you are structurally above the tier you purchased, renegotiation beats silent overages—but only if you bring usage data, business justification, and a credible alternative, even if you prefer not to switch. Vendors respond to churn risk and expansion revenue, not to moral appeals. Document how your workload differs from the vendor’s assumed shape (batch vs. interactive, peaky vs. flat). Pair the conversation with ROI evidence so finance sees the request as portfolio optimization, not engineering whim.

Related signals

Pair with onboarding as TCO for hidden services cost, maintenance versus accuracy for ongoing labor, and authoritative customer truth before you pay to sync two systems that disagree.