A standardization deal needs certainty where model availability cannot be guaranteed.
Engineering wants continuity before its incumbent renewal while Security and Procurement will not accept an unverified commitment.
Who you’d be doing this for
“I have a renewal deadline on Friday, and I still need to explain what happens if that model disappears.”
Bethlehem Kassa · Chief Information Security Officer
He must sign off on the developer-tool standardization for a healthcare organization with strict vendor-risk obligations.
What is at stake
A 2,400-seat agreement is blocked by a redline tying price and continuity to a third-party model. You must weigh the renewal deadline against commitments that could survive neither legal nor product reality.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- renewal deadline vs durable commitments
- model continuity vs contract certainty
- revenue urgency vs commercial precedent
- developer workflow value vs procurement simplicity
Why Cursor
Cursor runs agent sessions, chat messages, and tab completions through a shared stack whose model mix affects enterprise commercial commitments.
Written with these in mind
Not your kind of problem? 42 more at Cursor, 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.