The media platform wants lower delivery costs without repeating its launch-day failures.
Procurement protects spending predictability while engineering protects a reliable path for public media.
Who you’d be doing this for
“Our launch stream slowed twice, and now finance wants a number I can stand behind.”
Ijeoma Okafor · VP of Engineering
She owns the application platform that stores and serves customer-uploaded media through R2.
What is at stake
R2 reads rose 240%, but two launch-day incidents have stalled the enterprise expansion. You must weigh a fast commercial close against a proposal the CTO and procurement lead can verify.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast close vs verified customer economics
- launch reliability vs limited technical capacity
- self-serve momentum vs enterprise commitment
Why Cloudflare
R2 usage becomes durable enterprise revenue only when developer adoption and production architecture hold together.
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.