There's a job almost everyone in your company is doing that appears on no org chart: asking other people whether things happened. "Where are we on this?" "Did anyone send that?" "Who owns the rollout doc?" It feels like communication. It's actually a tax — and once you see it, you can't unsee it.
Anatomy of a chase
A decision gets made in a meeting: someone should own the rollout doc before Thursday. The meeting ends. The decision now exists only in the fading memory of six people and a notes doc nobody will reopen. On Wednesday, the person who cared pings the channel: "hey — did anyone pick up the rollout doc?" Two people answer. One of them is wrong. A quick call gets scheduled to sort it out.
Multiply that by every decision, every handoff, every deal that changed stage, every deadline that moved. The chase isn't an event; it's a medium. It's the water your company swims in, and everyone is doing the swimming on top of their actual job.
Process is chasing with extra steps
The standard fix is process: standups so nobody has to ask, status docs so the asking is batched, weekly reviews so the chases happen on schedule. Notice what all of these have in common — they don't remove the work about the work. They ritualize it. The standup is a chase with fifteen attendees. The status doc is a chase someone has to write instead of answer.
A status update is a human doing a database query by hand, slowly, from memory, once a week.
We kept adding process at Fludigo too, until we noticed the absurdity: all the information the chases were hunting for already existed in our tools. The task was done — the board knew. The deal had moved — the pipeline knew. The doc was written — it was sitting right there. The problem was never missing information. It was that the information didn't travel, so people had to.
What "runs itself" actually means
Concretely, in one workspace where everything is connected, the chases we used to run are just… gone:
- A decision in chat becomes an owned, dated task in one click — with the thread attached, so the owner never asks "wait, what was the context?"
- "Where are we on this?" is a question you ask the workspace, not a person. The answer comes with sources, in seconds.
- A deal marked Won creates the handoff task, updates the record, and announces itself. The chase that used to follow every closed deal doesn't exist.
- The week arranges itself on the calendar from work that already has dates. Nobody transcribes deadlines into a planning doc on Sunday night.
None of this is exotic AI. Most of it is just information finally traveling on its own — with an AI teammate handling the parts that need judgment, and showing its receipts when it does.
The week you get back
Here's the test worth running on your own team: for three days, count the messages that are really the question "did a thing happen?" Then imagine the version of your company where that number is roughly zero — not because people stopped talking, but because the answer was already everywhere it needed to be.
That's the company we're building at Fludigo, and the bet behind rubl. Your team's version of it is why we're opening rubl in waves. Stop chasing. Run.
— Jabez, founder · rubl by Fludigo