Waveloom was built by a SaaS founder for his own inbox, so this page needs the least translation. You know the shape: a few threads a day that can change the quarter, buried under everything else.
What your inbound looks like
A trial user from a company you have been trying to reach, asking a setup question. A partnership ask from a bigger platform. A customer replying to a support thread with "we are evaluating alternatives," which support tagged as resolved. An investor intro. A candidate following up. A Linear issue that has been blocking a customer for a week. A Slack mention in #sales that was really a pricing decision.
Under that: GitHub notifications, Stripe receipts, status page emails, tool digests, newsletters you do not remember subscribing to.
Sources you would connect
Gmail for inbound, partners, investors and candidates. Slack for the sales, support and product channels. HubSpot for the pipeline, so the agent knows which trial signups are on a target account. Linear so it can connect a customer complaint to the issue that would fix it. Notion for specs and decisions. Google Calendar so meeting changes show up in the feed and the brief.
Web watches for competitor changelogs, pricing pages, or a question like "who is shipping SSO on a starter plan." See market research for how watches follow a question instead of every update.
Example cards
Invented examples, alongside the one above.
Everything else is dropped. See inbox triage. The morning brief is where most founders start.
It executes two background actions, reply by email and reply in Slack, both only after you approve the exact text. If you want a system that acts on its own, this is the wrong product.