Launching today
Eodly
Know what your team actually shipped today
36 followers
Know what your team actually shipped today
36 followers
Eodly reads Slack, Telegram, Discord, GitHub and Linear, and sends founders one sourced page each evening: who shipped, who's quiet, who's slipping, and any status that doesn't match reality. Your team never logs in. A chief of staff, not surveillance.
Eodly
different angle from the team-morale question above: what about false positives on the "status doesn't match reality" flag specifically. someone could be genuinely blocked on a design review that's happening in a call, or deep in research that doesn't produce commits or messages for two days, and that would look identical to actual slipping from the outside signals you're reading. does the founder get any confidence level on those flags, or is it presented as flat fact each evening? seems like the credibility of the whole digest hinges on that ratio being low
Eodly
@galdayan Exactly the failure mode we built against, so good question. The flag isn't "no signal = slipping." It only fires when someone's own check-in claims progress that the system of record contradicts. A day in a design review or heads-down in research doesn't trip it: if they check in and say so ("in review," "deep in the refactor, no PRs yet"), that's the context, there's no claim to contradict. No check-in and no activity just surfaces as silent, a neutral "hasn't checked in," never as "slipping." Anyone marked off on the calendar is suppressed entirely.
On confidence: it's never a verdict. Every flag shows the claim and the evidence side by side ("said almost done; Linear shows no movement since Tuesday") and is dismissible in a click. We show the receipts, and the founder judges. You're dead right that the whole thing lives or dies on that false-positive ratio, which is exactly why it surfaces its sources instead of asserting a conclusion.
Congrats on launching!
Curious, how does the "chief of staff, not surveillance" framing land with team members? How have folks reacted to being flagged as "quiet" or "slipping"?
Eodly
@grace_knowhow Thanks! The key thing: team members never see the flags. Their whole experience is one friendly DM in Slack or Telegram for a one-line update, no dashboard, no login, no scoreboard. The "quiet" and "slipping" synthesis is the founder's private read, never broadcast back to the team, and there's no per-person leaderboard anywhere (and never will be; that's a hard line for us). Anyone marked off isn't flagged at all.
Honestly, it's early post-launch, so I won't pretend I have a large sample of reactions yet. But the bet is simple: if the team's only touchpoint is a 20-second DM and nobody gets graded in a UI, it stays a tool that helps the founder rather than one that watches the team. Happy to report back as more teams run it.
The evening digest idea is genuinely useful, especially catching when someone's Slack optimism doesn't match their Linear tickets. Liked that it pulls from multiple sources without making the team log into yet another tool.
Eodly
@eminenv9f Thank you, you nailed the two things we care about most: the cross-source catch (Slack optimism vs the Linear reality) and never making the team log into yet another tool. That's basically the whole thesis. Appreciate you taking a proper look.
This looks like something I'd like to use. How do we trigger the Eodly check from, lets say, WhatsApp? Do I have to tag it in a message and it checks whats happening, or is it only a daily overview kinda report?
Love the evening digest concept, really cuts through the noise. One thing I'd want is a quick way to reply or comment on an entry straight from the email, like a thumbs up on a ship or a nudge to someone quiet, so I can act on it without opening another tab.