Executive search

From founder to first salesperson: transfer relationship context, not just contacts

Prepare a founder-to-salesperson handover with sourced buyer context, live commitments and decision boundaries. Use the relationship brief and a worked example.

By LaisyPublished

A founder hands a new salesperson a CRM record marked “interested.” The buyer only asked for a product overview, but the founder also promised to check whether the product supports shared mailboxes. A salesperson who sees the stage but not the promise might send a proposal when the buyer is still waiting for a technical answer.

Before changing the owner in the CRM, give the salesperson enough context to explain what the buyer said, what is still owed, and who can act next. This is a handover method for founder-led teams, including search and advisory firms that are bringing in someone to run business development.

Copyable founder-to-salesperson relationship brief

FieldWhat to record
Relationship and originAccount, people relevant to the next step, and how the conversation began. Note whether the founder should make the introduction.
Buyer statementWhat the buyer actually described or asked for, with the source and date.
Founder interpretationThe hypothesis and what would confirm it. Keep it separate from anything the buyer said.
Current stateWhat has happened, what has not happened, and any conditions that matter to the next step.
Open commitmentWho promised what, when it is due, and where the promise is recorded.
Decision boundaryWhat the salesperson can decide and who approves exceptions such as pricing or product commitments.
Next actionOwner, action and trigger. For a blocked action, record who will clear the blocker.
Disclosure and acceptanceWhich sources may be shared, what stays restricted, and the responsibilities the salesperson has accepted.

Link to the existing brief, CRM record or permitted conversation instead of duplicating its full contents. HubSpot’s record-creation guidance shows how properties, associations and existing logged activities can sit together on a record. None of those mechanics substitutes for the founder introducing a new point of contact when an introduction is needed.

Keep the buyer’s statement separate from your interpretation

Write “The buyer asked for a product overview on Tuesday” before “They may be evaluating alternatives.” The first sentence can be checked against a source. The second belongs in the brief only if it helps the salesperson decide what to ask, such as whether the overview is for the buyer alone or for a wider evaluation group. A nonreply does not establish lack of interest, and a founder’s hunch about budget is not a budget objection.

The candidate research-note method applies the same distinction to a different subject: record what the source establishes before adding anyone’s assessment. Share the relevant, permitted evidence rather than forwarding every thread connected to the person.

Assign the promise and the decision separately

Name the action the salesperson can take without asking and the decisions they cannot make. For example, they may send the buyer an overview and arrange a technical call, while the founder must approve a custom product commitment. Atlassian’s DACI framework distinguishes getting a decision made from having the authority to make it. Use your own approval rules, especially where more than one person must agree.

Look for the promise in the actual message or call record, not only in the stage label. If someone other than the salesperson owes an answer, leave that obligation with them. The executive search client update template offers a related format for separating confirmed progress, decisions needed and next actions.

Worked example: three different handover states

A fictional founder reviews eight business-development conversations before transferring follow-up.

StateFictional countNext move
Ready to transfer3The buyer asked for a next step within the salesperson’s authority. The salesperson accepts the task and checks the source.
Shared responsibility2The founder keeps a promise already made; the salesperson takes the follow-up after the promised answer is ready.
Needs clarification3The notes are incomplete or ambiguous. Assign the question to someone who can resolve it before sending anything beyond what was agreed.

For the shared-mailbox question, the founder owns checking support. The salesperson can send the overview the buyer already requested, but leaves out any unverified claim and schedules the technical follow-up once the founder has an answer. For another account tagged “likely interested,” the source only shows that the buyer asked for general information. The salesperson corrects the record and sends the requested material instead of advancing the deal. The counts illustrate different states, not a staffing ratio or sales-performance benchmark.

Test the handover before transferring the rest

Ask the salesperson to pick one live relationship and explain the buyer’s last request, the source, the next action they own, and the specific decision they would escalate. If they cannot answer from the records they are allowed to see, fix the brief. Do not treat the name in an owner field as proof that they have accepted the responsibility. The assignment handover guide describes a related receiving-owner check for client work.

Mark the version the two of you reviewed; Google Docs version history supports named versions if that is where the brief lives. Update the live record when new evidence arrives and retain the date and source of the change. A PMI conference paper distinguishes recording lessons from retrieving them for use. If the same gap shows up repeatedly, keep a short reusable example of how to handle it rather than copying private buyer histories into training materials.

For a small trial, agree the actions to test and what would keep ownership with the founder. The pilot success criteria guide shows how to set a stopping point. A satisfactory handover means the salesperson can take the agreed next step and point to the source. It does not require handing over every account or getting out of sales altogether.

Frequently asked questions

Does changing the CRM owner transfer the relationship?

It changes the internal record. The new owner still needs the buyer context, accepted responsibilities and an introduction if the situation calls for one.

Should the founder share every historical conversation?

No. Point to the relevant source where access is appropriate. If it contains information outside the salesperson’s role, give them a limited summary they are allowed to use.

Can AI perform the handover without the founder’s review?

It can help organize permitted records. It cannot establish an undocumented promise, infer permission to share a record, or give someone the authority to approve a commercial decision.