ModuleChat
The scroll is where decisions used to die.
In rubl, “someone should own this” becomes someone owning it — one click, thread attached, done by Thursday. Chat that ends in work, not in scrollback.
Live demo — real interface, sample data.Turn Maya's message into a task — the thread comes with it.
# sales
Tom · 9:42
Acme call went well — they want the rollout plan by Friday.
Maya · 9:44
Someone needs to own the rollout doc before Thursday.
What changes
Talk becomes work.
Chat in rubl replaces the separate chat subscription, and the daily excavation of “what did we decide?”.
Messages become work
Any message becomes a task with the conversation attached. The person doing the work sees exactly why it exists.
Threads know their subject
The #sales conversation about Acme is linked to the Acme deal. Open either and the other is one click away.
Channels, DMs, the usual — minus the noise
Everything you expect from team chat, plus a workspace that absorbs the actionable parts so the channel doesn't have to be the system of record.
Searchable with its context
Search finds the message and what it was about — the deal, the doc, the task it became.
One workspace
Connected to everything else.
Chat isn't an integration — it shares one workspace with every other module, so context never gets copied between tools.
Straight answers
What people ask about Chat.
Can we replace Slack with this?
Teams in early access do exactly that. Channels, threads, DMs, and mentions are all here — and the actionable messages stop getting lost.
Do guests and clients get chat access?
Per project, yes — clients see the channels you invite them into and nothing else.
What happens to important messages?
They become tasks, doc lines, or deal notes — linked both ways. The scroll stays a conversation; the work lives where work lives.
Get your week back.
Early access opens in waves. Leave your email — and bring the whole team when it's your turn.
That didn't go through — mind trying once more?