Eodly
One evening report on what your team got done
116 followers
One evening report on what your team got done
116 followers
Eodly sends founders and team leads one report every evening on what their remote team got done. Everyone checks in once a day from Slack, Telegram or Discord, and each update is checked against the actual work in GitHub and Linear. People who worked but forgot to check in still count, and an update that keeps saying almost done while nothing moves is flagged. No time tracking or screen capture. Free for up to 5 people.
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.
@kardelen452289 Love this, and it is closer than you would think. The report does not land in a cold email tab; it comes to you in Slack or Telegram, so you can already reply or react right in the thread. The one-tap version you are describing, a thumbs up on a ship or a nudge to someone who has gone quiet straight from the report, is exactly the direction we want to take it, so it becomes something you act on in ten seconds instead of just reading and writing it down now. Which would you reach for more, the nudge or the reactions?
When will you add support for JIRA ?
@jay_janarthanan1 Jira is on the roadmap, not live yet. Today, the systems of record are GitHub and Linear, and Jira (with ClickUp) is next in that line. We build source integrations demand-first, so a question like yours is exactly what moves it up. Tell me a bit about your setup (team size, Jira Cloud or Server), and I will factor it in, and I am happy to ping you the moment it lands.
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.
@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.