2 min lesson
The instrumentation Cursor gives you
Answer this as if it were happening now. "An engineering VP asks for the single ROI metric to put on their board. What do you point to and why?" Say what supports your choice.
Step 1 of 2
The instrumentation Cursor gives you
Cursor's measurement surface turns this frame from a whiteboard model into something you can actually measure inside an account.
Passively categorises work developers do in Cursor as new feature, bug fix or refactor.
Flags under-specified agent turns that would have gone better through Plan modeA mode that makes no edits: it researches the codebase and produces an editable plan you review before any code changes. Press Enter for the full definition. first.
Line-level human vs. agent co-authorship, layered on git blame.
Data comes through the AI code tracking API, an Enterprise-only alpha whose fields may change.
Answers "how much of this came from the agent?" with line-level data.
AI share of committed code and agent edits.
Tab completions and active users.
Covers Agent, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition., cloud and CLI.
A read-only Analytics API pulls the numbers into the customer's own reporting.
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, which is Enterprise-only and still in alpha, lets a customer answer "how much of our shipped code did the agent write?" against their own definition of done. That 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. and 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., plus the dashboard and Analytics API, let you measure it in your own environment, and it all 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," skip the percentage. Draw the two axes, velocity and quality, and name the 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 dashboard and Analytics API) so it's measured in their own environment.
Learn more
Optional practice
Test yourself on 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?