Shortwave uses Gmail as platform
Jacob Wenger, CPO at Shortwave, on building a standalone business on email
Shortwave is choosing the easiest hard problem, which is replacing Gmail’s interface without replacing Gmail’s infrastructure. That lets it skip running mail servers, spam filtering, and deliverability, and spend its effort on inbox workflows like bundles, pin, snooze, done, real time messaging behavior, and tighter rendering of messy HTML email. The tradeoff is clear, Shortwave can move faster on product, but it stays tied to Gmail as the underlying system of record.
-
In practice, built on Gmail means users connect an existing Gmail or Google Workspace account, Shortwave syncs labels and message state back to Gmail, and people can switch between the two without losing context. That lowers adoption friction because companies do not need to migrate domains, retrain admins, or move stored mail.
-
This is the same basic architecture that made Superhuman viable, a paid workflow layer on top of Gmail and Outlook. The difference is product philosophy. Superhuman optimized for speed and power users at $30 to $40 per month, while Shortwave started with a broader, more opinionated inbox organization workflow and lower pricing.
-
The dependency also shapes the roadmap. Shortwave’s own docs still show Microsoft 365 and Exchange as unsupported, with Outlook only workable through forwarding into Gmail. That explains why getting the Gmail experience right comes first, because until the Gmail wedge is strong, expanding to Outlook or a hosted stack would add infrastructure weight before the core workflow is proven.
The next step is a gradual move from email client to email work layer. As Shortwave adds AI organization, shared archives, CRM links, and native automation, the product can own more of the daily workflow while Gmail fades into the background as plumbing. If that happens, support for Outlook and eventually a fuller independent stack becomes a natural expansion path.