2 min lesson
The instrumentation Cursor gives you
Work through the cases in "The instrumentation Cursor gives you", pairing each signal with the move that fits.
Step 1 of 2
The instrumentation Cursor gives you
Three product capabilities turn this frame from a whiteboard model into something you can actually measure inside an account.
Passively categorises the work developers do in Cursor.
Flags under-specified turns - the moments where a vague prompt should have been a Plan-mode session.
A read on prompting maturity, not just volume.
Line-level human vs. agent co-authorship.
Exposed through an AI-code-tracking API for your own dashboards.
Answers "how much of this actually came from the agent?" with data, not vibes.
In-app reporting on PR velocityHow quickly pull requests are merged; the easiest delivery metric to measure, though it sits furthest from the customer outcome. Press Enter for the full definition., cycle time and revert rate.
Velocity and a quality proxy in one view - revert rate is defects caught.
Shipping incrementally, so the dashboard deepens over time.
Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person. Press Enter for the full definition. is worth a careful pitch, because attribution is exactly where ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. conversations get stuck. Line-level co-authorship through the AI-code-tracking API lets a customer answer "how much of our shipped code did the agent write?" against their own definition of done - which is far more defensible than any percentage you'd quote them.
“We frame ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. as velocity times quality. On velocity I'd rather count features completed than PRs merged - PR count is easy to game and a wall of merged diffs can ship zero usable features. On quality the headline is customer-facing defects staying flat while you ship faster, with code half-lifeHow long code survives in the codebase before it has to change; a maintainability signal that counters 'more lines means more value'. Press Enter for the full definition. and developer sentiment underneath. Conversation InsightsA Cursor analytics view that passively categorises what agents are doing (new features, bug fixes, refactors) so leaders can see where engineering time goes. Press Enter for the full definition., Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person. Press Enter for the full definition. and the in-app roadmap let you measure all of it in your own environment, and it rolls up into time-to-marketHow fast a feature actually reaches customers; the outcome metric the velocity and quality pillars ultimately serve. Press Enter for the full definition..”
Asked "how would you prove Cursor's ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. to an engineering org," don't reach for a percentage. Draw the two axes - velocity and quality - and name the three velocity layers, flagging that PR velocityHow quickly pull requests are merged; the easiest delivery metric to measure, though it sits furthest from the customer outcome. Press Enter for the full definition. is easiest but furthest from value while feature-completion is hardest but closest. Land on time-to-marketHow fast a feature actually reaches customers; the outcome metric the velocity and quality pillars ultimately serve. Press Enter for the full definition. as the north star, then cite the instrumentation (Conversation InsightsA Cursor analytics view that passively categorises what agents are doing (new features, bug fixes, refactors) so leaders can see where engineering time goes. Press Enter for the full definition., Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person. Press Enter for the full definition., the in-app ROI roadmap) so it's measured in their environment, not borrowed from a study.
Learn more
Optional practice
Practice: The instrumentation Cursor gives you
QWhy is feature-completion velocityHow fast a team moves through its roadmap; the hardest delivery metric to measure but the closest to real customer value. Press Enter for the full definition. a better ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. signal than raw PR count, even though it's harder to measure?