Get the whole room aligned, even when no one reports to you.
Naomi coaches you on the moments that get four teams down to one plan.
SOC 2 infrastructure Encrypted end-to-end No meeting bots Never trained on calls
After every call
Coaching, notes, follow-ups, and commitments from every call.
01Coaching
Feedback you can use on your very next call.
02Notes
The notes you meant to take, already done.
03Email drafts
The follow-up, drafted and waiting for you.
04Intelligence
A second brain for every commitment.
01Empathy & acknowledgement
Acknowledge the cost before you defend the plan.
— On the call
When the ops lead said the new strategy would double her team's workload, you jumped straight to the ROI slide. She stayed quiet for the rest of the meeting.
↓ Next time
"Name it first: 'You're right, this lands hardest on your team, and I don't want to gloss over that.' Then ask what support would make it workable."
Why it matters
People can't hear the upside until they feel heard. Acknowledging the cost turns a skeptic into a co-owner of the plan.
Before the next call
Open with the ask, then the data.
Lead with the decision, back it with one number, and move the rest to the appendix.
StructuredEmail draft
Copy notes
2027 strategy review — Partner-led growth
Oct 1, 2026 · Daniel Reyes, Elena Marsh, Ana Ortiz, Marcus Lee
Discussed
Elena's three conditions
Payback under 18 months, no new headcount in H1, and one pilot region before any national rollout.
Impact on operations
Ana flagged the partner onboarding load on her team. Daniel to scope partner-side support before launch.
Pilot in the northern region
Agreed in principle. Marcus wants a go/no-go at the November board meeting.
Your to-dos
You committed to these on the call
3 open
Send Elena the revised payback model
By Fri, Oct 9
Draft the ops support plan with Ana
Wed, Oct 7
Book the pilot kickoff with the northern team
Next week
StructuredEmail draft
Copy email✓ Copied
SubjectStrategy review next steps — pilot, payback, ops support
Hi all,
Thanks for the honest pushback today. We aligned on piloting partner-led growth in the northern region first, measured against Elena's three conditions.
Still open:
• Ops support model for Ana's team• Pilot success metric (payback vs. pipeline)
Next steps:
• Daniel: Send the revised payback model (by Fri)• Daniel: Draft the ops support plan with Ana• Marcus: Add the go/no-go to the board agenda
Talk soon, Daniel
Drafted from the call · edit before sendingReady to send
EM
Elena Marsh
CFO · Corvane
4 calls3 open asks
CommitmentDue Fri
Send the revised payback model
Promised to Elena · mentioned in 3 calls
Feedback you can use on your very next call.
The notes you meant to take, already done.
The follow-up, drafted and waiting for you.
A second brain for every commitment.
Empathy & acknowledgement
Acknowledge the cost before you defend the plan.
— On the call
When the ops lead said the strategy would double her team's workload, you jumped straight to the ROI slide.
↓ Next time
"Name it first: 'You're right, this lands hardest on your team.' Then ask what support would make it workable."
Before the next call
Open with the ask, then the data.
Lead with the decision, back it with one number.
StructuredEmail draft
2027 strategy review
Oct 1 · Daniel, Elena, Ana, Marcus
Discussed
Elena's three conditions
Payback under 18 months, no new H1 headcount, one pilot region first.
Impact on operations
Ana flagged the onboarding load on her team.
Northern pilot
Go/no-go at the November board meeting.
Your to-dos2 open
Send Elena the payback model
By Fri, Oct 9
Draft the ops plan with Ana
Wed, Oct 7
StructuredEmail draft
Copy✓ Copied
SubjectStrategy review next steps — pilot, payback, ops
Hi all,
Thanks for the honest pushback today. We aligned on piloting partner-led growth in the northern region first, measured against Elena's three conditions.
Next steps:
• Daniel: Revised payback model (Fri)• Daniel: Ops support plan with Ana• Marcus: Go/no-go on board agenda
Talk soon, Daniel
Drafted from the call · edit before sending
EM
Elena Marsh
CFO · Corvane
4 calls3 open asks
CommitmentDue Fri
Send the revised payback model
Promised to Elena · 3 calls
Use cases
Most of your work happens in conversation. Get better at it.
Did everyone leave with the same plan, or a warm “we’re aligned” that meant four different things?
ClarityStructureEmotional RegulationConciseness
Relationship Building
Did the other team leave feeling their constraints were heard, or steamrolled by your timeline?
Active ListeningEmpathy & AcknowledgmentInclusive LanguageConversation Balance
15 dimensions scored on every call.
Say it in their language, not yours.
Win over the team you can’t tell what to do.
End with one plan, not four interpretations.
Professional Discipline 546
You walked design through the API constraints in your own shorthand. Three of them went quiet.
Try this on your next call
“Let me put that in terms of what you’ll see on screen, not what’s happening in the backend.”
Why it works
Every function has its own shorthand, and yours is invisible to you. When the room goes quiet, that’s rarely agreement. It’s usually people who stopped following two sentences ago. Translate into their world before you go deep, or you’ll ship a decision half the room never actually understood.
Persuasion & Influence 614
You needed marketing to move the date. You explained why it mattered to engineering.
Try this on your next call
“Here’s what this unlocks for your launch, not just ours.”
Why it works
You can’t order another team to care. You have to make the case in their terms, leading with what they get out of it. Influence without authority is really just showing people how your ask serves their goal, and it’s the whole skill of getting things done across a company.
Executive Presence 593
The call ended on a warm “we’re aligned.” Each team left with a different next step.
Try this on your next call
“Before we drop: one decision, one owner, one date. Tell me if that’s not what you heard.”
Why it works
“We’re aligned” is the most expensive line in a cross-functional meeting. Real alignment is a single, stated plan every team can repeat back. Close by making the decision, the owner, and the date explicit, and make the room confirm it, or you’ll find the gap at the deadline.
Your overall score
76+6 vs benchmark
Last 30 days · 18 assessed calls
7d30d90dAll
YouSenior-AE benchmark
Question depth+9
Discovery quality+6
Executive presence+4
Empathy+2
Pacing−1
Confirming next steps−9
Longitudinal intelligence
See whether you’re getting through, team by team, over time.
Naomi tracks how you communicate across functions: whether you translated the jargon, earned buy-in without leaning on authority, and left each call with one shared plan. You see the trend across every cross-team meeting, not a single call, so you know you’re actually getting easier to work with.
Built for every role
Built for everyone who has to work across the org.
The moment that mattered, and what to say next time.
ExampleCaught
You spent four minutes on the product before saying why now.
Try
“Let me start with why now. The market shifted last year.”
ExampleCaught
You asked three yes/no questions in a row, and the buyer never told you what’s broken.
Try
“Walk me through the last time this went wrong. What happened?”
ExampleCaught
They raised workload twice. Both times, you moved to the next agenda item.
Try
“You’ve mentioned workload twice. Let’s stay on that before we move on.”
ExampleCaught
You spent four minutes on the product before saying why now.
Try
“Let me start with why now. The market shifted last year.”
ExampleCaught
You asked three yes/no questions in a row, and the buyer never told you what’s broken.
Try
“Walk me through the last time this went wrong. What happened?”
ExampleCaught
They raised workload twice. Both times, you moved to the next agenda item.
Try
“You’ve mentioned workload twice. Let’s stay on that before we move on.”
ExampleCaught
The number that mattered came eleven minutes in, after the full timeline.
Try
“Bottom line first: we’re behind on Q3, and here’s the plan to recover.”
ExampleCaught
They said “that’s more than we budgeted.” You dropped the price before asking what the budget covered.
Try
“Help me understand what the budget was built around.”
ExampleCaught
You opened your proposal with “I might be wrong, but maybe…” and the hedge undercut a strong idea.
Try
“I’d recommend we test this with one team first.”
ExampleCaught
The number that mattered came eleven minutes in, after the full timeline.
Try
“Bottom line first: we’re behind on Q3, and here’s the plan to recover.”
ExampleCaught
They said “that’s more than we budgeted.” You dropped the price before asking what the budget covered.
Try
“Help me understand what the budget was built around.”
ExampleCaught
You opened your proposal with “I might be wrong, but maybe…” and the hedge undercut a strong idea.
Try
“I’d recommend we test this with one team first.”
ExampleCaught
You did most of the talking. Their one real complaint got thirty seconds.
Try
“Before I go further, what would make this worth it for you?”
ExampleCaught
When the CFO pushed back, your answers got longer and faster.
Try
“Fair challenge. Let me answer it with a single number.”
ExampleCaught
The call ended on “let’s circle back.” No owner, no date.
Try
“Can we hold 20 minutes Thursday to walk your team through the proposal?”
ExampleCaught
You did most of the talking. Their one real complaint got thirty seconds.
Try
“Before I go further, what would make this worth it for you?”
ExampleCaught
When the CFO pushed back, your answers got longer and faster.
Try
“Fair challenge. Let me answer it with a single number.”
ExampleCaught
The call ended on “let’s circle back.” No owner, no date.
Try
“Can we hold 20 minutes Thursday to walk your team through the proposal?”
Cross-functional communication questions, answered.
What is cross-functional communication?
Cross-functional communication is how people from different teams (engineering, design, product, marketing, sales, operations) share information and make decisions together. It’s harder than communicating inside one team because each function has its own priorities, vocabulary, and definition of “done.” Strong cross-functional communication is mostly translation: getting your context across to people who don’t share it, and understanding theirs in return.
What’s the difference between cross-functional communication and collaboration?
Collaboration is the work several teams do together; communication is how they talk while doing it. You can put people in the same meeting and still have four teams leave with four different plans. The failure there is in the communication, not the work itself. Good cross-functional communication is what makes the collaboration actually work: shared understanding, surfaced constraints, and one plan everyone can repeat back.
Why is cross-functional collaboration important?
Because almost nothing meaningful ships from inside a single team. Products, launches, and fixes all cross functions, and the handoffs between them are where timelines slip and trust erodes. Most of that damage traces back to communication: a constraint that never got heard, an ask framed only in one team’s terms, a call that ended vaguely. Get the communication right and the collaboration mostly takes care of itself.
How do you improve cross-functional communication?
Start by seeing how you actually come across to other teams. Most people can’t tell whether they translated their jargon, talked past a constraint, or left a call without a clear owner. Naomi listens to your recorded cross-team calls and scores exactly those habits, then hands you one specific change for next time. Improvement comes from a feedback loop on your real meetings, not another article on “communicating better.”
How do you communicate effectively with other departments?
Anchor the conversation on what the other team cares about. Translate your function’s shorthand into their world, make room for their constraints before you push your plan, and end every call with a decision, an owner, and a date. It sounds simple; the hard part is doing it under time pressure, which is why seeing your own calls scored on these moves is worth more than a checklist.
How do you influence a team you don’t manage?
You make the case in their terms. Without positional authority, persuasion is the whole game: show another team how your ask advances their goal, not just yours, and back it with a clear story rather than a demand. Naomi measures whether you framed your request around the other team’s outcomes and how you handled their pushback. Those are the exact skills that move people who don’t report to you.
How do you get teams that use different jargon on the same page?
Translate, and check that it landed. The fastest way to lose a cross-functional room is to explain something in your team’s language and assume silence means agreement. Usually it means people stopped following. Say it in terms of what the other function sees and cares about, then confirm they’re with you. Naomi flags the moments your jargon likely lost the room and shows you where you did or didn’t bring it back.
Why do cross-functional meetings fail?
Most fail on communication, not competence. The common patterns: someone dominates in their own jargon, a real constraint gets talked past, and the call ends on a warm “we’re aligned” that means something different to each team. None of those show up until the deadline. Naomi scores your calls on exactly these failure modes: talk-time balance, whether concerns were picked up, and whether you closed with one concrete plan.
Can Naomi analyze cross-functional meetings on Zoom?
Yes. Naomi works with your recorded Zoom meetings — you connect Zoom, and Naomi assesses each call and returns coaching afterward. No bot sits in the meeting; the analysis happens privately on the recording, for you. It works the same for a planning session, a design review, a launch sync, or a tense escalation across teams.
Does Naomi share my feedback with the other teams?
No. Your coaching is private to you — it’s built to make you better to work with, not to grade you for anyone else. You see your own trends and recommendations across your cross-functional calls; nobody else does, on your team or any other.
Is there a tool that helps you communicate better across teams?
Most cross-functional tools help you track the work: tickets, docs, roadmaps, shared channels. Naomi is a different layer: a coaching tool that analyzes how you actually communicate on your cross-team calls — whether you translated the jargon, heard the other team’s constraints, and closed with one shared plan — and gives you one specific thing to improve each week. It works alongside whatever you already use to run the work.
How is this different from generic communication advice?
Generic advice tells you to “over-communicate” or “build alignment.” Naomi tells you that on Thursday’s launch sync you spoke for 68% of the time, never translated the deployment risk for marketing, and ended without an owner — then gives you the exact line to try next time. It grades your real cross-functional calls against a research-backed model, so the feedback fits how you actually communicate, not a checklist.
Can cross-functional communication actually be coached?
Yes — working well across teams comes from a set of repeatable habits: translating your jargon, framing asks in the other team’s terms, hearing constraints, and closing with one plan. What’s usually missing is honest feedback, because no one in a cross-functional meeting is there to tell you how you landed with the other functions. Naomi is that feedback loop, cross-team call after cross-team call.
Your reputation across the org is built one cross-team call at a time.
Join the waitlist and turn every cross-functional call into coaching.