Skip to lesson
Exit
Enterprise Rollout & Adoption1 / 3

2 min lesson

Pilot design: pick, scope, instrument

Start at the first move in "Pilot design: pick, scope, instrument" and carry it through to the proof.

Step 1 of 3

Pilot design: pick, scope, instrumentphase one

  1. 1Pick the right first team. Not the loudest fans and not the hardest skeptics. You want a team with a real, measurable pain, a willing tech lead and a codebase representative enough that the win generalizes.
  2. 2Define success up front. Write the success criteria before day one, tied to a baseline. 'Cut PR-to-merge on the payments service from 4.2 days to under 3' beats 'people like it.'
  3. 3Time-box it. A 30-60 day pilot with a decision date forces a verdict. Open-ended pilots drift into permanent half-adoption.
  4. 4Instrument it. Capture the baseline at day zero across the four lenses or every later result answers 'compared to what?'
Learn more

Full explanation

Environment configuration

Environment configurationthe guardrails

Configuration is where the post-sale, technical half of this role shows. You're not clicking through a settings page; you're matching Cursor's admin controls to this org's security posture so the pilot survives review.

What you stand up before the first engineer logs in
SSO / SAML / OIDC
Identity wired to the org's IdP so access follows the same offboarding as everything else.
SCIM
Automated provisioning and deprovisioning, so seats and access stay in sync with HR/IT without manual list-keeping.
Privacy Mode + ZDR
Two separate controls. Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. is the no-training guarantee - your code is never used to train models - and it is enforceable org-wide. Zero data retention is the retention agreement with the model providers you sanction. Boundary: ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. Press Enter for the full definition. does not apply when teams bring their own API keys, and retention then follows that provider's terms.
Admin policy
Org and group-level controls: model allowlist, RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually. Press Enter for the full definition. and audit logging the security team can actually inspect.
Rules baseline
A starting .cursor/rules set encoding the org's conventions (stack, lint rules, review norms) so Agent output matches house style on day one.
Model access
Which models are sanctioned and any routing constraints - Cursor Router's admin controls restrict which optimization modes members can use, set the default mode, allow or block underlying models and offer soft or hard enforcement of standardizing on Auto. Settle this with security before the pilot starts.