A platform-sized commitment depends on usage assumptions that do not yet agree.
The customer wants one agreement for its deployed stack, while Legal needs terms that remain defensible after signature.
Who you’d be doing this for
“The board wants one platform decision this month, and procurement just handed me another redline.”
Dusabe Seyoum · Chief Technology Officer
Sponsors the AI platform consolidation and must defend the infrastructure decision to the board.
What is at stake
A $2.5 million agreement rests on usage forecasts that differ by 38% across customer models. You must weigh platform scope against contractual exposure that cannot be cheaply reversed.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- platform consolidation vs contractual containment
- speed to signature vs verified demand
- customer flexibility vs enforceable commitments
- revenue certainty vs legal precedent
Why Cloudflare
Workers AI, R2, D1, and Durable Objects become a strategic infrastructure sale when one agreement must carry the customer’s production 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.