The customer must choose between developer momentum and a defensible standardization case.
Broader access protects engineering adoption, while policy review and cost scrutiny protect the decision to scale.
Who you’d be doing this for
“My CTO wants one answer next week, and I’m still explaining why only two teams are using it.”
Aissatou Balogun · Engineering Administrator
Owns enterprise configuration, policy controls, and the evidence needed to defend the rollout internally.
What is at stake
The customer has 12 days to choose an AI coding standard, while only two teams show sustained usage. You must weigh developer momentum against the policy and cost evidence leaders need to commit.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- developer momentum vs policy assurance
- usage growth vs cost predictability
- technical evaluation vs standardization deadline
- broad access vs audit-ready controls
Why Cursor
Cursor Enterprise is being judged on whether governed developer adoption can justify a single enterprise AI coding standard.
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.