SDR: New CRO

A former customer who becomes a new CRO may recognize the platform, yet the earlier account cannot describe the current company’s selling motion. The SDR should use familiarity to discuss reporting lines, partner involvement, manager practices, available data, and executive priorities. Discovery prevents an old plan from being imported into a different organization.

Diego called CRO Tessa and said, “I know you used us at Northstar. What has changed in this company’s coaching environment?” Tessa answered, “Partners report through another unit, and I have not hired an enablement leader.” Diego replied, “That changes who would own a program. Could we hold a short session with the partner leader to understand their motion and identify the manager questions worth solving first?” Tessa named Ravi, the partner vice president, and said the president of the business unit would care about any shared process.

Draft a meeting request that refers to the prior relationship in one sentence, then names two conditions that require discovery. Mention the partner unit and the missing enablement owner. Describe the meeting as a chance to map decision makers and learn where coaching happens. Do not assume the former deployment’s content, governance, or measures fit the new company.

Practice with a CRO who asks, “Why do we need discovery when I already know the product?” Answer, “Your experience is valuable context. I need to understand this company’s managers and partner motion before recommending a useful path.” Ask who can explain the partner workflow firsthand. Have a manager review whether the SDR treated the old account as context. The follow-up should confirm Ravi’s role, the question for the president of the business unit, and the discovery outcome: a shared view of ownership and next steps.