A one-page note that hands your partner the prospect, the room, and the play. Five minutes the night before. The call walks in coordinated instead of cobbled together.
Download it, paste it into Claude, ChatGPT, or Cursor as a system prompt, and give your AI the discovery transcript and the partner's name. The brief comes back in the same nine-section format.
Download the prompt for your AIThere is a moment on every joint sales call where you can feel whether the team did the work or not.
It happens about four minutes in.
The prospect says something specific. A number. A name. A line they have already said out loud to one of you on a different call. And your partner, who you brought in to close the back half of the deal, looks at the prospect like the prospect just made it up.
You watch the prospect notice. You watch them adjust their posture by half an inch. You watch the room go from "this team has it together" to "I am explaining my own business to two strangers again."
The deal does not die there. It just gets harder. From that point on you are spending energy patching the seam instead of moving the conversation forward.
Most operators blame the partner.
Or they blame themselves for not picking a better partner.
The partner is fine. The pick is fine.
The thing that is missing is a brief.
A short, written, one-page note that goes to your partner the day before the call, and tells them everything they need to walk into the room already knowing the prospect.
Five minutes to write. Saves the hour-long call.
I learned this the hard way and now I do it before every joint call I run with anyone. Coaches with platforms. Consultants with delivery partners. Specialists I bring in when a deal needs more horsepower than I deliver alone. Same shape every time.
Here is exactly what goes in it.
The first thing on the page is what the prospect actually wants.
Not your interpretation. Not "they want a better system." Not "they want growth."
One sentence the prospect said to you on a previous call, in quotes, with their name in front of it.
If you cannot find a one-sentence quote that captures the North Star, you do not know it well enough yet, and the call is not ready. Get on the phone with the prospect for fifteen minutes before the joint call and listen for it.
This single quote does more for your partner than any amount of context you could write in your own voice. It anchors them in the prospect's language before they say a word.
Right under the North Star, three lines that orient your partner to the business.
What the company does.
Roughly how big it is, in a way the prospect would describe it.
Where it is in its life cycle (early, scaling, mature, transition).
Three lines. Not three paragraphs.
Your partner does not need to be able to write the company's annual report. They need to be able to nod when the prospect mentions a thing about their business and not need it explained.
This one matters more than people think.
Most prospects who book a joint call about anything serious are not at zero. They have tried something. A vendor that disappointed them. A tool they like. An internal experiment that almost worked. An advisor who got them part of the way there. They want credit for the ground they have already covered.
Walking in and explaining a category to someone who has been living inside it for eighteen months is the fastest way to lose them.
List what they have already tried in your category. Two lines. The vendor that did not deliver. The platform they cancelled. The internal hire that left. Whatever the prior attempts were.
Your partner now opens the conversation a layer above where a cold pitch would start, and the prospect feels the difference immediately.
Three to five bullets. Specific. In the prospect's words where possible.
Not "operational efficiency." Not "growth strategy."
"Get the weekly client report off my plate."
"Stop my team from rebuilding the same proposal four times a quarter."
"Give my second-in-command something to lean on so I am not the bottleneck on every decision."
If the prospect named the use cases on a prior call, copy them in. If they did not, you guess from what they did say, and you mark it as a guess. Your partner needs to know which bullets are quotes and which are inferences.
This list is the spine of the call. Everything you and your partner say should connect to one of these bullets.
Who is going to be on the call.
Names. Roles. One line on each one.
The decision maker is obvious. The other people on the call are not. The COO who is quiet on the screen is often the person who actually runs the day-to-day. The technical lead who is on for "five minutes" is the one who will tell the founder yes or no after you hang up. The board observer the prospect did not warn you about is a real risk.
If you know who is going to be in the room, name them. If you do not know, write "TBC" and ask the prospect to confirm before the call.
Your partner now knows whose face to read when a hard question lands, and who to bring back into the conversation when the room goes quiet.
Two short lists.
Tech stack: the systems and vendors the prospect already runs the business on. CRM, accounting, project management, the tools and people you already named in Step 03. Your partner can now scope a recommendation that fits inside what already exists, instead of pitching a teardown.
Budget signals: anything the prospect has said, on or off the record, about what they are willing to spend. A range they named. A comparable engagement they referenced. A line like "I am not bashful about an investment as long as the return is there." If they have not said anything, write "no signal yet" and let your partner price from the value of the work, not from a number neither of you has heard.
The single fastest way to wreck a joint call is for one of you to quote a number that is wildly off from where the prospect's head is. The brief prevents this.
This is the section most operators forget, and it is the section that makes joint calls feel coordinated instead of competitive.
Two or three sentences. Plain language.
Where you stop. Where they start. What gets handed off, when, and how the prospect experiences the seam.
If you are the front of the deal and your partner delivers the back, say so. If your partner is the platform and you deliver the specialist piece inside it, say so. If the two of you are co-delivering and the prospect should think of you as one team, say that too.
Without this section, both of you walk in with a private theory of how the deal works, and your theories quietly conflict on the call. The prospect feels it as confusion. You feel it as friction. The deal stalls.
Five sentences in the brief retire that whole risk.
The last section is the play.
Who opens. Who handles which segment. Who closes. Where you are going to hand the floor over and what cue you will use to do it. What you do not want said. What you do want said.
If there is a piece of the conversation your partner runs better than you, name it explicitly and let them run it. If there is a piece you run better, claim it the same way.
This is not a script. It is a play call.
The prospect will not see this section. They will see the result of it, which is two people who finish each other's sentences without stepping on them.
Get the brief into your partner's hands the evening before the call, not five minutes before.
One link. Not an email with eight attachments. Not a document buried in a shared drive they have to go find.
I host mine on its own short URL so my partner can open it on their phone in the car on the way to the call. The brief is short enough to skim once and re-skim twice. That is the design.
If your partner has questions after they read it, you have time to answer them before the call instead of in the first three minutes of it.
The window between "they read it" and "the call starts" is the part that does the actual work. That window has to exist.
The first time you build one of these, it takes longer than five minutes because you are figuring out the shape.
The second time, you copy the same nine sections, change the names, and fill in the blanks.
Three briefs in, the structure is muscle memory. You can produce one in a single short session at the end of the day before the call.
If you have a partner, an assistant, or an AI you trust to draft the first pass, hand them the source material from your earlier conversation with the prospect and the nine-section structure. Let them draft the brief. You spend your time reading and correcting, not writing from scratch.
The format I use:
North Star: [one-sentence quote, in their words] Company: [three lines] What they have tried: [two lines] Desired use cases: [3-5 bullets] The room: [names, roles, one line each] Tech stack: [list] Budget signals: [what they said, or "no signal yet"] How my piece fits with yours: [2-3 sentences] How to run the call: [the play]
Nine fields. One page. Five minutes.
The first thing that changes is the first four minutes.
Your partner walks in already calibrated. They greet the room by name. They reference the prospect's North Star in their own opening. The prospect feels the difference instantly. You can watch their shoulders drop.
The second thing that changes is the seam between you and your partner. The handoffs get clean. The pricing conversations stop being awkward. Neither of you contradicts the other, because both of you read the same page the night before.
The third thing surprised me when I first noticed it.
The prospects start treating the two of you as a unit. They stop running parallel decisions ("do I hire her, or do I hire him") and start running one decision ("do I hire this team"). Joint calls that used to feel like two pitches start to feel like one offer.
A partner brief is not extra work. It is the work that makes the call possible.
Most operators run joint calls and hope the chemistry shows up. The brief replaces hope with a five-minute artifact that puts the chemistry in the room before either of you opens your mouth.
If you want to see this method run as a standing skill inside an Executive AI Operating System, that is one of the bundles The Affluent Affect installs. The agent reads the prior call transcript, builds the brief in the nine-section format, deploys it to a private link, and hands you a draft you spend five minutes correcting before it goes to your partner. The structure is the same. The work just shrinks.
Either way, the next joint call you run, write the brief.
This is a portable prompt that runs the partner brief inside any AI. Paste it into Claude, ChatGPT, or Cursor as a system prompt or project instruction. Then give it a discovery call transcript and the partner's name. The AI produces the brief.
Read it in your browser, or download the raw markdown to paste into Claude, ChatGPT, or Cursor. Yours to keep.