StartADAM Relays Messages Between Any Messenger Platform

01 /The Concept

Messaging fragmentation has quietly become a real operational problem. Teams and external partners each default to whatever messenger they already use – Teams, Slack, Discord, WhatsApp, Telegram – and important messages get lost or seen too late simply because they arrived in the wrong app. StartADAM is building a cross-messenger relay that makes messenger choice irrelevant: a message sent in one platform arrives in whatever platform the recipient prefers.

The routing is user-configurable – each person specifies their preferred destination, and incoming messages from any supported platform are forwarded there automatically. Current integrations cover Microsoft Teams, Discord, Slack, WhatsApp, Telegram, SMS, Trello, and Jira. The setup works equally well for internal teams and for communication with clients, contractors, or partners who may be on different platforms entirely.

Beyond the core message relay, StartADAM is building an ecosystem of plugins that move work out of standalone tools and into the messenger context. The first, "Control Panel," is a project management plugin that lets teams interact with Trello entirely through their preferred messenger – task reminders, status updates, and notifications all route through each person's chosen channel. If a team member switches messenger preference, nothing changes for the project manager; the system adapts automatically.

Further plugins under development include CRM integration (applying the same principle to sales workflows), a payment integration (enabling transactions directly within a conversation), and a ChatGPT plugin for customer support. Each plugin is priced separately: cross-platform messaging at $13.99 per user per month, the project management bundle at $25.

Launched earlier this year, StartADAM has already signed clients including PricewaterhouseCoopers and Ernst & Young, and closed a $1.9M seed round on the strength of that early traction.

02 /Why It Matters

StartADAM's architecture is conceptually close to Patchworks – [reviewed here](/review/stan-povelitelem-kubikov) – which raised £8.8M to build a data-exchange layer between the many systems e-commerce companies use. Patchworks unifies disparate data flows; StartADAM unifies disparate communication flows. Both operate as a middleware layer that doesn't replace the underlying tools but makes the combination usable.

The structural similarity runs deeper: both platforms accumulate a normalized data layer (unified messages and workflow events, in StartADAM's case) that then becomes the foundation for an application ecosystem. The value compounds as more plugins are built on top of the base relay, just as Patchworks's analytics apps gained power from having all commerce data pre-unified.

StartADAM's own framing – "asynchronous project management" – connects to a broader shift in how distributed teams are structuring work. A [recent review](/review/novoe-ponjatie-pahnet-novymi-dengami) covered Async, which targets the time-synchronization problem: eliminating the need for distributed team members to be online simultaneously by replacing meetings with voice messages. StartADAM addresses the tool-synchronization problem: eliminating the need for team members to use the same applications. The two dimensions of asynchrony reinforce each other – a team that has solved both no longer has to coordinate either schedule or toolstack.

The broader concept is a generational update to BYOD (Bring Your Own Device) – the early 2000s policy shift that let employees connect to corporate systems from personal laptops and phones. That shift was driven by device proliferation. The current shift is driven by application proliferation: people have preferred tools and resist adopting new ones for each employer or client. BYOD is becoming BYOA – Bring Your Own App – and companies that want to attract and retain talent need infrastructure that accommodates this reality.

03 /Opportunities

The general direction is building async communication infrastructure for distributed teams – with the recognition that async now has two dimensions: time (not requiring simultaneous availability) and tools (not requiring identical applications).

For anyone building in this direction, the question is which layer to own. StartADAM owns the transport layer and is expanding into workflow plugins. A competitor might own the workflow layer first and add transport later. Or focus on a specific communication pattern – client-to-company, cross-timezone team standups, external contractor onboarding – and build the transport layer as a behind-the-scenes feature.

The most promising entry angles are vertical: an async communication layer built specifically for software development teams (GitHub, Linear, Slack, and SMS in one relay) or for professional services firms (where partner, associate, and client all prefer different tools). Starting narrow generates the integration depth and proof points needed before expanding horizontally. Which vertical has the highest pain-to-friction ratio is the real design decision.