Not SMBs and SMEs. Big Enterprises would generally be using API buckets or Enterprise-specific consumption models via sales teams and contracts, but most companies would default to subscription tiers - either due to shadow IT paying out of pocket for subscriptions to duck corporate IT, or because they’re too small to negotiate rates and API buckets, or because their IT teams lack the skills needed for the same.
Remember that enthusiasts leaning on API keys and large enterprises are the exception, not the norm, and even some large customers may lean on subscriptions for at-scale adoption and wait for teams to report hitting usage caps before buying more token buckets. Subscriptions are predictable, reliable, and above all else a contractable way to acquire service.
Truth be told, this has been my red flag in orgs and with peers elsewhere for several years, now. Those orgs leaning on subscriptions are in for a nasty surprise within a year or two (like the author, I predict sooner than later), especially if those subscriptions power internal processes instead of AI buckets.
Hell, this is why I think there’s a sudden focus on the “Forward Deployed Engineer” nonsense role: helping organizations migrate from subscriptions to token buckets for processes so the bill shock doesn’t send them running away screaming.
Not SMBs and SMEs. Big Enterprises would generally be using API buckets or Enterprise-specific consumption models via sales teams and contracts, but most companies would default to subscription tiers - either due to shadow IT paying out of pocket for subscriptions to duck corporate IT, or because they’re too small to negotiate rates and API buckets, or because their IT teams lack the skills needed for the same.
Remember that enthusiasts leaning on API keys and large enterprises are the exception, not the norm, and even some large customers may lean on subscriptions for at-scale adoption and wait for teams to report hitting usage caps before buying more token buckets. Subscriptions are predictable, reliable, and above all else a contractable way to acquire service.
Truth be told, this has been my red flag in orgs and with peers elsewhere for several years, now. Those orgs leaning on subscriptions are in for a nasty surprise within a year or two (like the author, I predict sooner than later), especially if those subscriptions power internal processes instead of AI buckets.
Hell, this is why I think there’s a sudden focus on the “Forward Deployed Engineer” nonsense role: helping organizations migrate from subscriptions to token buckets for processes so the bill shock doesn’t send them running away screaming.