Rising production usage is colliding with a finance team that cannot budget variable consumption.
The customer needs room to grow on Workers AI and R2, while procurement needs a commitment it can model.
Who you’d be doing this for
“Finance asked me for next quarter’s number again, and I’m still rebuilding it from request logs.”
Lorena Monteiro · VP of Engineering
Owns the application development organization using Workers AI and R2 in production.
What is at stake
Workers AI and R2 usage rose 41%, but procurement has delayed the expansion twice. You must weigh predictable commitment against the customer’s need to keep scaling.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- growth flexibility vs budget certainty
- architecture evidence vs commercial simplicity
- quarter-end timing vs durable terms
Why Cloudflare
Workers AI and R2 adoption turns developer-led usage into an enterprise agreement only when the commercial model matches the deployed architecture.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.