Account mapping

You share an account.
So what?

Chris Messina · 2 October 2026

A shared name on a list doesn’t move a deal. Someone still has to make the right call.

You and a partner know the same account. Looks promising. But what can the partner actually do? Make an introduction? Help connect the software? Advise the buyer? Those are different conversations.

What do you need help with?

In this fictional account example, Larkspur Software wants to sell to Cedarbrook Systems. Crestline may help Cedarbrook connect the software. Its role hasn’t been confirmed.

That’s a reason to ask a question. It isn’t permission to share private notes or put partner revenue in a report.

Check the facts before making the call.

A sales note says Crestline may help. A separate workshop announcement adds context. Neither tells you what Crestline has agreed to do.

Ask what you know, what you’re assuming, and what you need to confirm. Now the conversation has a purpose.

Put a name next to the next move.

Someone needs to ask about Crestline’s role before discussing the account. Name that person. Agree what they need to find out.

Otherwise, the idea stays in the spreadsheet. Or it becomes one more pointless introduction in someone’s inbox.

Don’t count the money twice.

Cedarbrook is a prospect. It has brought in no revenue in this example. A possible sale and booked revenue are different things. Putting them on the same screen doesn’t change that.

A map earns its place when it helps someone make a useful move. Without that, it’s another list.