Projects do not fall apart in the tracker. They fall apart between it and the channel.
The plan is in one tool, the conversation is in another, and the gap between them is where things get lost. Ray lives in the channel, keeps the tracker honest about what was actually decided, chases what has gone quiet, and writes the update nobody has time to write.
Ray is on Slack today. Free to start, and nothing sensitive happens without your approval.
- 50 free tasks to start, then 25 a month free
- No credit card
- Nothing sensitive without your approval
How it goes now
The version of this everyone recognises, and nobody has time to fix.
- The plan was accurate on the day it was made and has been drifting ever since.
- A decision gets made in a thread on Tuesday, and the tracker finds out about it whenever somebody remembers.
- Status meetings exist mostly so that everyone can find out what already happened.
- The person who chases people is doing it out of goodwill and their own memory.
How it actually works
No builder, no workflow to configure, and nothing that acts on its own.
Ray reads the channels the project actually happens in
Only the ones you invite it to. It follows what is being decided rather than waiting to be told, and stays quiet when nothing needs doing.
Decisions reach the tracker
Scope changes, new work, dates that moved. Ray writes them into the tools you already use, and every one of those writes shows you a card first.
Ray chases, so a person does not have to
It reads the live state before it asks, so a nudge names where something actually stands rather than just asking for an update.
The update writes itself
Schedule a digest and Ray posts what moved, what is blocked and what is overdue, built from the systems of record rather than from memory.
What that looks like in a channel
Somebody says something. Ray does the rest, and asks before anything leaves the room.
“We agreed to push the migration to next sprint.”
Ray updates the dates on the affected work and shows you exactly what it is about to change before it changes anything.
Jira
Linear
Asana
ClickUp“Where are we on the launch?”
Ray reads the live state across the tools the work lives in and answers in the thread, instead of telling you which four tabs to open.
Notion
Google Sheets
FigmaIt works where the work already is
Each of these has its own page saying exactly what Ray reads and what waits for your approval. Nothing is hidden behind a demo call.
What Ray does not do here
Worth knowing before you try it, rather than after.
- Ray does not draw Gantt charts, roadmaps or burndowns. It has no views of its own at all, because it has no dashboard, deliberately.
- It does not do resourcing, capacity planning or budgets. Those live in your tracker and Ray reads them rather than managing them.
- It will not reassign work or move a date on its own. Every one of those is a write, and every write waits for a person.
- Ray is on Slack today. The other chat platforms are planned, not shipped.
What people ask first
The short answers are here. If we have not covered something, just ask.
Add Ray to one channel and hand it something.
Free to start, no card, about two minutes. Ray sees only the channels you invite it to.