Why We Built Our AI Project Manager on Email, Not Slack
Every AI tool wants to live in a chat app. We deliberately built our AI project manager on email — the one channel every company already runs on. Here's the reasoning.
When we tell people we built an AI project manager that works over email, the first reaction is often surprise. Email? Isn't that the thing everyone's trying to escape? Why not a slick Slack bot, or a Teams integration, or a native app with a beautiful inbox of its own?
The answer is that we optimized for adoption over novelty — and once you take adoption seriously, email wins decisively.
The tool nobody has to adopt
The single biggest reason enterprise software fails is not features. It's adoption. A tool that 60% of the team uses inconsistently produces a board that's 60% accurate, which is to say useless for decision-making. Every new channel you introduce is another thing people have to remember to check, another login, another habit to build. Change management is where rollouts go to die.
Email is the one channel that requires no adoption at all. Every employee already has it. Every external partner, contractor, vendor, and client already has it. There is no app to install, no workspace to join, no onboarding session to schedule. If someone can write an email — and everyone can — they are already fully onboarded to Vertically. That's not a small convenience; it's the difference between a system people actually use and one they don't.
If someone can write an email, they're already onboarded. That's the whole point.
Email is asynchronous by nature
Project work increasingly spans timezones. Chat apps create a subtle pressure toward synchronous response — the green dot, the typing indicator, the expectation of a quick reply. That works against distributed teams, where the person who needs to answer is asleep when the question is asked.
Email was designed for asynchronous communication. A message sits in an inbox until the recipient is ready to deal with it, in their own timezone, on their own schedule. For an AI project manager coordinating people across the world, this is exactly the right model: ask, wait, follow up, gather, escalate — without forcing anyone to be online at the same moment.
Tone lives in email
There's a more subtle reason, too. The quality of a project manager isn't just what they track — it's how they communicate. A good PM is clear, calm, professional, and persistent without being annoying. Those qualities come through in writing, and email is the medium where professional written communication already lives.
We found that when an AI corresponds over email — full sentences, proper context, the right amount of formality — most people simply respond as they would to a human colleague. The channel sets the expectation. A chat bubble invites a one-word reply; a well-written email invites a considered one. That difference materially improves the quality of the information the system gathers.
What this looks like in practice
A contributor gets an email referencing their task, asking for a quick status. They reply in plain language — "wrapping up, should be done Thursday." Vertically reads the intent, updates the board, and recalculates any dependent dates. If Thursday comes and the work hasn't landed, it follows up. If the slip threatens a downstream deadline, it escalates to the right person with the full context attached.
- No new app for contributors to learn.
- Works for internal teams and external stakeholders alike.
- Asynchronous and timezone-friendly by default.
- Professional tone that earns considered replies.
The boring channel is the powerful one
It would have been easier to build something that demos well in a chat app. But the goal was never a good demo — it was a system that quietly works inside the way companies already operate. Email is unglamorous precisely because it's universal, and universality is exactly what an AI project manager needs to coordinate everyone involved in a project, not just the subset who happen to live in the same chat tool.
Sometimes the most powerful place to put new technology is the most familiar one. We bet on email because it's where work already happens — and that bet is why Vertically requires zero change from the people it coordinates.
FAQ
- Why does Vertically use email instead of Slack or Teams?
- Email is universal — every company and every external stakeholder already uses it, with no new app to adopt. It's asynchronous and timezone-friendly, it carries professional tone well, and it requires zero behavioral change from contributors. That combination makes it the lowest-friction channel for an AI project manager to coordinate real work.