Understanding the code
Find the relevant behavior and explain what needs to change.
Make AI part of
how your team ships.
Every change starts with questions. Where does this behavior live? What else will it affect? Bring Cursor into that work, from understanding the code to reviewing the change.
Look at the work your team
needs to move forward.
Start with changes your team already understands. Examine the work, the review, and the decisions around it.
Making the change
Explore an approach, put it into practice, and keep the engineer's judgment in the work.
Reviewing the result
Check the change and decide whether it belongs in the codebase.
From the first question
to the final review.
A practical way to bring Cursor into the work. Keep the question, the change, and the review connected.
Understand what
needs to change.
Ask Cursor to help you find the relevant code and explain how it behaves. Follow that explanation back to the source.
Give the change a clear starting point before implementation begins.
Explore Cursor AgentKeep the work moving.
Bring the task and its constraints into the conversation. Explore an approach, make changes, and keep the next question close to the work.
Official Cursor footage showing a follow-up request queued while the current task runs.
Make the review
part of the story.
Read the change. Run the relevant checks. Explain what you accepted and why. A useful result should hold up when another engineer looks at it.
Evaluate with your teamA tool developers choose.
A team decision that follows.
“Cursor quickly grew from hundreds to thousands of extremely enthusiastic Stripe employees.”
Patrick CollisonCo-Founder & CEO, Stripe
Make your requirements
part of the decision.
A team decision involves more than the editing experience. Bring your engineering, security, and purchasing questions into the conversation.
Read the security informationYour code and data
Review Cursor's current security and privacy information against your organization's requirements.
Your teams and access
Decide who needs access and who will manage the rollout. Confirm the options that fit the way you work.
Your purchasing process
Discuss current plans, commercial terms, and the review your organization needs before a decision.
Give your team
a clear starting point.
Choose real tasks. Agree on what you will examine. Make the next decision from work you can actually review.
Choose the work.
Pick a change in familiar code and one that needs investigation. Give each a clear scope and a named reviewer.
Agree on the review.
Decide what matters before work begins. Include correctness, time spent, reviewer effort, and corrections along the way.
Compare what happened.
Review the finished work together. Discuss where Cursor helped and what you would change before trying it more widely.
Before you bring it
to the team.
What work should we try first?
Start with a small change your team can assess. Use familiar code as a point of comparison, then try a task that needs investigation. Keep the result small enough for a meaningful review.
How should we judge whether it helps?
Look at the finished work and the effort around it. Include correctness, time spent, reviewer effort, and any corrections needed before acceptance. Agree on those criteria before you begin.
What should security and purchasing review?
Start with Cursor's current security information. Discuss your organization's data, access, and commercial requirements, and confirm available options directly with Cursor.
What happens when I select “Talk to Cursor”?
You will go to Cursor's official sales contact page to share your team's requirements. This campaign does not collect your details.
Put your team's next change
at the center of the conversation.
Explore where Cursor could fit, what your organization needs,
and what a useful evaluation would look like.