Async Video Meetings: The Default Coordination Layer

The video call is the highest-bandwidth way humans transfer context. The calendar is the lowest-bandwidth way humans coordinate it. Plus One closes the gap - not by joining your meetings, but by giving you a permanent link where the 1:1 that was not going to happen still happens.

Async video meetings are 1:1s and scheduled calls that run without both people being on the call at the same time. The context still transfers at video-call bandwidth — face, voice, screen, nuance — but the meeting no longer needs a shared 30-minute slot on both calendars. Below is how Waterr's Plus One turns every scheduled call on your waterr.ai/username link into an async video meeting by default, and why that's the coordination layer most teams are missing.

Every important decision in a company still flows through a 1:1. The deal moves on a call. The bug gets triaged on a call. The new hire's question gets answered on a call. The roadmap gets aligned on a call.

And every one of those calls is gated by two calendars lining up.

That is the bottleneck. Not the work. Not the people. Not the tools. The two-calendar problem - two humans, both already booked, trying to find a 30-minute slot that fits both of them, this week, in two time zones, around lunch and the standup and the school pickup. Most of the time the slot does not exist this week. So the conversation waits until next Thursday, and the thing it was about waits with it.

The call is the highest-bandwidth interface humans have ever built. The calendar is the lowest-bandwidth way to schedule it. We optimized the conversation and broke the coordination.

Plus One closes the gap. Not by sitting in on your meetings. By giving you a permanent address - waterr.ai/your-username - where anyone you have allowed can show up and get a real, live 1:1 with your Plus One, on Waterr AI, any time, without you clearing a single slot on your calendar.

That is what we mean by async video calls. The call is synchronous. Your presence on it is not required.

If you saw the launch post for Plus One, this is the longer answer to the question that one only had room to gesture at - what does it actually look like when your Plus One takes a 1:1 for you? The deeper mechanic behind the link sits in Coordination in the Age of AI, which lays out why the personal EA, not a meeting bot, is the right shape for this. The companion read for engineers is Plus One for Developers, where the math gets the sharpest.

Why "async meeting" was always the wrong name

The industry has spent five years trying to solve this with async meeting tools - Loom videos, written updates, transcripts you read after the fact, async standups in Slack threads.

They all share the same problem: they remove the call, not the wait.

When you replace a meeting with a Loom video, the other person still has to watch it, think about it, and write a response. The conversation that would have taken five minutes face to face now takes three days of back and forth video replies. You moved the bandwidth down and the latency up. That is not a coordination win. That is a coordination loss disguised as a productivity tool.

The real unlock is not removing the call. It is removing the requirement that you be on it, at that specific hour, on that specific day.

Your Plus One does not join a meeting that is already scheduled on your calendar. It has its own address. The other person goes to waterr.ai/your-username and gets on a live call with your Plus One right there - your voice, your context, the authority limits you have set. They get a real conversation: questions, answers, follow-ups, clarification, happening at full bandwidth, in real time. You get a brief when it is done.

That is not an async meeting in the Loom sense. It is a synchronous conversation that does not require your calendar to be open, because one of the participants is your Plus One and it is always available at that address.

What actually happens when someone opens your link

Someone who needs twenty minutes of you opens waterr.ai/your-username. They land on a live call with your Plus One. It is not a transcription bot. It is not a form. It is a participant.

It sees the screen share if there is one. It hears the question. It answers what it knows from the context you have loaded into it - the project status, the last decision, the open thread from Tuesday. It asks clarifying questions when the other person is vague. It pushes back when something does not match what it knows about your priorities. It commits to follow-ups inside the boundaries you have set, and it explicitly does not commit to anything that requires a human decision.

When the call ends, you get the recording, the transcript, and a brief that contains exactly three things:

• What was said - the key points, in the structure you read fastest
• What was decided - what your Plus One agreed to on your behalf, and why
• What needs you - the one or two decisions that were deferred to you, with the context to make them in 60 seconds

No "summary of the meeting." No generic action items. A brief written specifically for the person who was not there. Because that person is you.

The other side of this matters just as much. You load your Plus One with context 24 hours a day, not in a scheduled slot. You say the whole thing at 11pm after a hard call, or at 6am before a board meeting, with no thirty-minute window forcing you to compress it. Whatever you have loaded is what your Plus One carries into the next 1:1 it takes on your link.

Where this changes how teams actually work

The link is not a single use case. It is a coordination primitive. Once a team has it, it shows up everywhere a calendar used to be the bottleneck.

Engineering and QA. A developer ships a build and the QA team has questions. Today, that is a 30-minute call scheduled two days out, by which time the developer is on the next ticket. With Plus One, QA opens waterr.ai/developer-username immediately and gets on a live call with the developer's Plus One. It walks through the change, answers the questions it can, captures the ones it cannot, and sends the developer a brief: "QA found two edge cases. Here they are. Here is what I told them. Here is what needs your call." The developer reads it in 90 seconds and replies. The bug does not sit for two days.

Developers protecting flow. This is the case where the link matters most, and we wrote a dedicated post on it because the math is so lopsided. A senior engineer mid-refactor has the entire module graph loaded in their head - types, call sites, invariants, the four places a change cascades. A 15-minute "quick call" from a PM, designer, or customer costs the next two hours of context-rebuilding. Instead, that person opens the engineer's link and takes the call with the engineer's Plus One. It sees the screen share, asks the follow-ups a good EA would ask, captures the constraints, and hands the developer a message with notes, a recording, a transcript, and a prompt formatted to drop straight into a coding agent. The PM gets their question answered. The engineer stays in flow.

Customer support. A user hits a problem in your product and clicks "Talk to support." Instead of a chat queue with a five-hour SLA, they land on the support team's link and are in a live video call within ten seconds with the support Plus One. It sees the screen, walks through the issue, reproduces it, captures the context, and either resolves it directly or routes a precise brief to the human agent who needs to make the call. The customer never sits on hold.

IT helpdesk. Same shape. An employee needs a license, a permission, a reset, a question answered about the VPN. They open the IT team's link, get a live call with the IT Plus One, which executes what is authorized, captures what is not, and routes the rest. The IT team stops being a queue and starts being a decision layer.

Revenue blocked by the GTM team. This one is structural. The revenue team is always on customer calls. The internal teams who need them - product, engineering, ops - are always blocked. Instead of waiting for the internal sync to get scheduled, the internal team opens waterr.ai/gtm-lead-username and gets on a live 1:1 with the GTM lead's Plus One right now. It carries the customer context the GTM lead has loaded into it. It captures the asks the internal team is making. The GTM lead reads a brief between two customer calls and replies once. The internal projects stop stalling on "waiting for sales."

Recruiting screens. First-round interviews are the highest-volume, lowest-leverage calls in any company. A candidate opens the hiring manager's link and the first-round screen runs there - scenario-defined questions, persona matched to your culture, real-time evaluation across communication, technical depth, and fit. You read a ranked brief on the candidates worth your time. You take the second round.

Vendor and partner calls. Every quarter is full of "check-in" calls with vendors and partners. They want to hear from a human. Most of them do not need a decision from you. They open your link, take the call with your Plus One, which captures any real asks and surfaces the ones that need you. Your calendar gets the hour back.

Onboarding. New hires have a hundred questions in the first week and no one to ask without feeling annoying. Instead of waiting for a scheduled onboarding session, they open the team lead's link - waterr.ai/team-lead-username - any time a question lands, and get a live call with the team lead's Plus One. It is context-rich, infinitely patient, available in every time zone, and able to escalate the questions that need a real human. The new hire ramps faster. The team lead gets the hour back.

Cross-org coordination. The hardest calls to schedule are the ones across companies - your team and the partner's team, your team and the client's team, your team and the agency's team. Six calendars. Two domains. Three time zones. When both sides have a link, either side can open the other's Plus One and get a live conversation without lining up six calendars first.

None of these are meetings your Plus One crashes. They are all real, live, full-bandwidth 1:1s that happen at an address that is always open, whether or not your calendar has room.

The coordination layer, not the meeting tool

Most meeting software optimizes the meeting. Better video. Better audio. Better transcription. Better notes after the call.

We think the meeting is already good. The bandwidth on a video call is fine. The problem is not the meeting. The problem is the scheduling around it - the calendar invites, the reschedules, the time zones, the "let me get back to you," the calls that drift to next week because two people are heads-down on something else.

Plus One does not try to insert itself into every tool where a question might land. It does one thing: it gives every person a permanent address for the 1:1s that were not going to happen. waterr.ai/your-username is the surface. You share it the way you share your email address. Anyone you have allowed can open it any time and get a real conversation with your Plus One, loaded with everything you have told it. They do not need to re-book you next week either - the link is permanent, so they come back to it the way they would reply to a thread.

When this becomes the default - when every person in your organization has a link that can take their 1:1s and route the decisions that need them - three things change at once:

• Throughput goes up. Conversations that used to wait days happen in minutes.
• Calendar load goes down. The number of 1:1s you personally sit through drops, but the number of 1:1s that happen on your behalf goes up. The work moves. You do not.
• Decisions get faster. Your Plus One does not hand you "the meeting." It hands you the one decision the meeting was for, with the context to make it in 60 seconds.

This is what we mean when we say Plus One is the coordination layer for the next decade of work. Not a better meeting tool. Not a smarter calendar. An address where the work stops waiting on the calendar.

What it looks like when every person has one

Imagine the org chart of any company. Every box is a person. Every line between two boxes is a relationship that occasionally requires a real conversation - a sync, a decision, an unblock.

Today, every one of those lines is gated by a calendar. Two calendars, actually. The throughput of the entire company is bounded by the bandwidth of the slowest calendar on either end of every line.

Now imagine every box has a link next to it - waterr.ai/their-username - open at all hours, loaded with their context. The lines between the boxes are no longer gated by calendars. They are gated by context: what the Plus One knows, what it is authorized to commit, what it has to defer back to the human.

This is a different shape of organization. Faster. More parallel. Less dependent on the geometry of who is awake at what hour. Less dependent on whether your VP of Eng was in back-to-backs all day.

The internal benefit is obvious. The external benefit is bigger. Your customers, your partners, your candidates, your vendors - they all stop waiting on your calendar too. They open your link and get a real conversation, in real time, at full bandwidth, with someone who can speak for you within clear authority limits.

That is the coordination layer. Inside the company. Across the company. With every external party your company touches, one link at a time.

The default, not the exception

We believe async video calls - 1:1s where one participant is your Plus One - will become the default coordination mode for organizations within five years. Not for the dramatic calls. Not for the board meeting. Not for the offsite. For the 80% of 1:1s that exist because two humans needed to align on something that mostly did not require both of them in real time.

That 80% is where the calendar costs are. That 80% is where the slowdowns live. That 80% is where a link replaces the wait with a conversation that just happens, instantly, on demand, at an address that is always open.

The other 20% - the high-stakes, high-emotion, high-trust conversations - those stay human. They should stay human. Plus One is not trying to replace the 1:1s that matter. It is trying to delete the ones that never had to be on your calendar in the first place.

The 1:1 still happens. The conversation still happens. The decision still happens.

You just do not have to be the one holding the calendar slot open for it.

That is async video calls. That is the coordination layer.

That is what we are building Plus One to be - the default, not the exception, for how organizations move work forward.

Read next: Coordination in the Age of AI - the full case for the personal EA and the link. Plus One for Developers - the sharpest version of this argument, written for engineers who pay the highest interruption tax. And Introducing Plus One - the short launch note for the broader product.