I built a daily work log for myself, and it has grown into a working tool for teams

Wait 5 sec.

I’ve been working with Ruby on Rails for many years, and one thing I’ve wanted to do for a while was build and run a product of my own. That led to SprintCo. I initially built it as a simple daily work log for myself. I wanted a place to record what I’d worked on without the overhead of a full project management tool or the feeling of being tracked. Over time, I realized the same idea could be useful for teams, too. Developers could create a team and invite clients to follow progress, or clients could create a team and invite the developers and testers working on their projects. So I added team support, invitations, shared daily updates, and weekly views. The goal is to give everyone a shared picture of what's happening without relying entirely on meetings or scattered messages. SprintCo now has five active teams. It's still early, but seeing the product move beyond my personal use has been an encouraging milestone. I built and run it using Ruby on Rails, PostgreSQL, and Tailwind CSS. Along the way, I've also been handling deployment, security, product decisions, and figuring out which features are genuinely worth adding. I'm trying to keep SprintCo focused rather than turn it into another all-in-one project management platform. Here's the working product: https://sprintco.dev/?ref=reddit_sideproject I'd appreciate honest feedback, particularly from people who work in teams: What would make a lightweight daily work log genuinely useful to your team, and what would make you reluctant to adopt one?   submitted by   /u/stridepath [link]   [comments]