The rollout has interest, but large-repository users are not reaching a repeatable first win.
A shared enablement clinic protects broad adoption, while a tailored workflow protects depth for one critical service.
Who you’d be doing this for
“I tried it on a cross-service change, got half an answer, and went back to tracing it myself.”
Benoit Fischer · Staff Software Engineer
She is one of the invited developers working across a large enterprise repository and is expected to model effective Cursor use for her team.
What is at stake
Only 31% of 180 invited developers return in week two after their first agent session. You must weigh broad repository-context enablement against a deeper workflow for one flagship service.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- broad activation vs flagship depth
- shared enablement vs scarce field capacity
- developer focus time vs adoption urgency
Why Cursor
Cursor agent sessions depend on developers establishing useful repository context before the product becomes part of daily engineering work.
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.