How to brief your cofounders before investor calls
A shared pre-call brief keeps cofounders aligned on context, objections, roles, and the call outcome.
The CEO had taken four calls with this fund. He knew the partner had passed on two competitors for being "too horizontal," that she'd asked twice about gross margin, and that the goal of this call was to get a second partner in the room. None of that made it to his cofounder, who joined the Zoom thirty seconds before it started.
So when the partner asked, "How do you think about the wedge," the technical cofounder, trying to be helpful, described the full platform vision: six product lines, every vertical, the horizontal play. The exact thing the partner had passed on competitors for. The CEO watched her face close. The call ended polite. The intro to the second partner never came.
Nothing went wrong technically. The product answer was fine. The team just sent two different companies into one call, and the investor believed the one that scared her.
What teams do today, and why the second voice breaks the call
The default is that one founder owns investor relationships and the others get pulled in as needed. The CEO carries the thread. The technical cofounder joins for the architecture questions. The commercial cofounder joins when it's a later-stage fund that cares about pipeline. This is reasonable. Cofounders have day jobs inside the company and cannot sit in every call.
The problem is the handoff. The owning founder has four conversations of context: what this investor believes, what they pushed back on, what got them leaning in, what the call is actually for. The joining cofounder has, at best, a calendar invite and a vague "it's the fund we liked." So they default to the only safe move they know, which is to pitch the company as hard as they can. They re-explain the thing the investor already accepted, re-open an objection the CEO had already closed, or volunteer the vision in a way that reads as unfocused.
The damage is specific. Investors read cofounder alignment as a proxy for execution. If two founders give two different answers to "what's the wedge" or "who's the customer," the investor does not conclude that you're flexible. They conclude you haven't decided, and a team that hasn't decided is a team that will burn the round arguing. The call was supposed to reduce their risk. The second, uncoordinated voice added some.
There's a quieter cost too. The owning founder spends the call doing cleanup. Instead of advancing toward the outcome, they're reframing their cofounder's answer in real time, which the investor notices. Now the subtext of the call is "these two aren't on the same page," and that subtext outweighs anything in the deck.
The framework: one call, one brief, four things every founder must hold
The fix is not "rehearse more" or "let one person do all the talking." It's a small artifact: a pre-call brief that the owning founder fills in once and every founder on the call reads before joining. It carries the four things a cofounder needs to not contradict the round.
1. The investor's thesis. What does this fund or partner already believe about your market, and why are they taking the call? One or two lines. "She believes vertical AI beats horizontal; she's looking for the category winner in [vertical]." This tells the joining cofounder which version of the story lands and which version kills it.
2. The prior context. What has already been said across previous calls. What they accepted, so you don't re-explain it. What they pushed back on, so you don't reopen it. Where the last call ended. This is the single most valuable block, and the one that lives entirely in the owning founder's memory by default.
3. The likely objections and who answers them. The two or three concerns this investor will probably raise, and the named founder who owns each answer. "Gross margin: CEO. Technical moat: CTO. Why now: CEO." Pre-assigning answers stops the scramble where two people start talking or, worse, no one does and the CEO covers for a gap that's clearly someone else's.
4. The one outcome you want. Every call has exactly one job. A second partner in the room. A term sheet conversation. A specific intro. Permission to send the data room. If the cofounders don't share the same target, they'll optimize for different things in the same hour. The technical cofounder will go deep on architecture when the actual job was to get to a partner meeting.
These four are the spec. Everything else, the deck, the demo, the metrics, is delivery. The brief is what keeps delivery pointed in one direction.
The 10-minute pre-call ritual
The brief is useless if it's written and never read together. Build a fixed ritual in the ten minutes before the call. Not a meeting. A scan and a sync.
Minutes 0 to 4, silent read. Everyone joining the call reads the brief. Alone, on their own screen. No one explains it out loud yet, because explaining out loud is how the context stays in the owning founder's head.
Minutes 4 to 8, the owning founder adds the live color the brief can't hold. "She was warmer on the last call than the notes suggest." "He just led a round in our space last week, so he'll move fast or not at all." "Don't bring up the [competitor] comparison, it went badly last time."
Minutes 8 to 10, confirm two things only: the one outcome, said out loud by whoever is driving, and the objection ownership, confirmed by name. "If margin comes up, that's me. If they ask about the data pipeline, that's you. Our job today is a second-partner intro, nothing else." Then you join.
Ten minutes. The cost of skipping it is the Lisbon-shaped call above.
Before and after
Here's the wedge question from the opening story, with and without the brief.
Before (no brief):
Partner: How do you think about the wedge?
Technical cofounder: Great question. So the long-term vision is a full platform. We start with [feature] but really we're building horizontally across [vertical A], [vertical B], and [vertical C], because the same engine powers all of them. Eventually every team in the company touches it.
The partner who passed two competitors for being "too horizontal" just heard a horizontal pitch from the technical founder. The CEO now spends three minutes walking it back.
After (brief read; thesis and objection ownership known):
Partner: How do you think about the wedge?
Technical cofounder: We start narrow on purpose: [specific job] for [specific user] in [vertical]. That's where we win first and where the data compounds. [CEO] can speak to how we sequence beyond it, but the wedge is deliberately one thing.
CEO: And to your earlier point about staying focused: the expansion is a later-stage decision. Right now everything we ship serves that one wedge.
Same product. Same founders. The difference is that the technical cofounder knew the investor's thesis was "vertical and focused," knew the wedge answer was the CEO's to frame, and handed it off cleanly instead of free-soloing the vision.
The reusable artifact: the cofounder pre-call brief
Copy this. The owning founder fills it in. Everyone joining reads it in the ten minutes before the call.
COFOUNDER PRE-CALL BRIEF ================================= Investor: [Name, fund, role] Call date/time: [____] Who's joining: [names] Call # with this investor: [1st / 2nd / Nth] 1. THEIR THESIS (why they're taking this call) - Believes: [what they think about your market] - Looking for: [the kind of company they want] - Read on us so far: [warm / curious / skeptical] 2. PRIOR CONTEXT (what's already been said) - Accepted (don't re-explain): [____] - Pushed back on (don't reopen): [____] - Last call ended on: [____] - Open thread / promised follow-up: [____] 3. LIKELY OBJECTIONS → OWNER - [Objection 1] → [founder name] - [Objection 2] → [founder name] - [Objection 3] → [founder name] 4. THE ONE OUTCOME (the single job of this call) - [e.g. second partner in the room / data room access / term sheet talk] - NOT today: [what to deliberately not chase] 5. LANDMINES (say out loud in the sync) - Don't mention: [____] - Tone note: [____] PRE-CALL RITUAL ================================= [ ] 0-4 min: everyone reads this brief, silently [ ] 4-8 min: owner adds live color not in the doc [ ] 8-10 min: confirm the ONE outcome + objection owners by name POST-CALL (2 min, before you scatter) ================================= [ ] New objection raised? → log it [ ] What did they accept today? → log it [ ] Agreed next step + who owns it: [____]
The post-call two minutes matter as much as the prep. That's how the brief for call number four gets written: from what actually happened on call number three, not from memory three weeks later.
Roles: who carries what on the call
The brief assigns objections, but teams also drift when default lanes aren't clear. A rough division that holds for most founder-led calls:
The CEO owns the narrative arc, the why-now, the ask, and the outcome. They drive. When in doubt about who answers, it defaults to them.
The technical cofounder owns the moat, the architecture, and the "can you actually build this" questions. Their failure mode is over-answering, going deeper than asked and drifting into vision. Their rule: answer the question asked, then stop.
The product/commercial cofounder owns the customer, the wedge in practice, pipeline, and pricing. Their failure mode is contradicting the CEO's framing of the market. Their rule: same wedge story as the brief, every time.
These are defaults, not walls. The point is that before the call, every founder knows their lane and knows that stepping into someone else's lane uninvited is how a coordinated team starts to look like an argument.
Where this breaks at scale, and where RoundOS fits
One brief for one call is easy. The owning founder remembers everything because it's fresh.
The trouble starts around call fifteen across eight investors. Now "prior context" means recalling what this specific partner accepted versus what a different partner at a different fund pushed back on, which objection your last milestone just answered, and where each thread went cold. That context lives across your email, your calendar, your meeting notes, and your head. Reconstructing it into a brief before every call is exactly the work founders skip when they're busy, which is always. So the team falls back to the cold join, and the round starts contradicting itself again.
This is the work RoundOS is built for. It pulls the round out of your email, calendar, and meeting notes and keeps the context per investor: what each one said, what they objected to, when you last spoke, where the thread stalled. Before a call, it can assemble the pre-call brief from that history and your current company context: the investor's prior objections, what they accepted, the open follow-up you promised, and the metrics that changed since you last spoke. Your cofounder reads a brief built from the actual record instead of a thirty-second hallway summary. You're confirming the outcome and the lanes, not reconstructing four calls from memory while the Zoom clock runs.
The manual brief is the move. The system is what lets you still run it on call number fifteen.
Run one brief before the room opens.
Write the outcome and objection ownership, then say both out loud before the investor call starts.