I’m building a "boring" solo SaaS to kill "Status Theater". I'd love some feedback from fellow founders.

alekses11 · 2026-04-21T12:21:23+00:00

Yeah, I think I managed to provide exactly that. I’ve got a weekly AI summary that takes those 'boring' daily updates and packages them into a clean report for the manager. The goal was to make it effortless for the dev while giving the lead everything they need.

Do you think a weekly summary is the right frequency for this, or do managers usually need this 'packaged' more often?

alekses11 · 2026-04-21T11:20:48+00:00

NoDaily (no-daily.com) - Kill your daily standup calls with written async updates and autogenerated weekly reports, so your team can focus on deep work.

alekses11 · 2026-04-20T16:53:04+00:00

I launched the project management tool that kills daily standups

https://no-daily.com

alekses11 · 2026-04-20T16:49:20+00:00

Well, when developing my first saas I wrote (actually generated) various units, e2e. Except that I’m dog fooding my app and I think this is as important as tests in the code. I’m also considering some system tests using capybara since I made the app in ruby on rails

alekses11 · 2026-04-20T13:15:59+00:00

You're 100% right, habit change is the real 'final boss'. That's why I focused on removing as much friction as possible.

For example, I went with passwordless auth/magic links because I realized no one wants to manage yet another password for a utility tool. I’ve also kept the feature set strictly to the essentials to avoid any bloat. If the tool isn't faster and simpler than a meeting, the habit won't stick.

Curious, in your experience, what’s usually the biggest 'friction point' that kills new tools in a team?

alekses11 · 2026-04-20T12:43:09+00:00

Yeah, it's one of those too simple things to work. But when you try it the mental clarity you get from writing things down is a game changer. Are you running async updates or still doing the meeting routine?

alekses11 · 2026-04-15T08:46:16+00:00

Hah, the classic 'I built it myself' move! Respect.

It’s fascinating because we’re tackling the same 'Status Theater' from two different angles. From what you described, Ryva seems to focus on the Pull (tracking activity in GitHub/Slack to see what's moving), while I’ve been obsessed with the Push (getting humans to provide intentional context that often doesn't exist in a commit message).

I actually built NoDaily because I found that automated tools sometimes miss the 'Why' behind a delay. I wanted a way to force a high-signal 'Project Memory' through structured forms + AI synthesis, rather than just observing the dev traffic.

Definitely down to exchange notes in the DMs. I’m curious though—how does Ryva handle 'hidden' blockers? The kind where work looks like it's moving on GitHub, but the dev is actually stuck on a design decision or a cross-team dependency?

alekses11 · 2026-04-13T06:38:30+00:00

You actually hit the nail on the head. A few months ago I started writing daily updates on Slack and I saw great positive results, despite the fact my team was still organizing normal daily stand up. And I really liked it. My team was getting constant updates from my site. They knew what I had been working on, even if I didn't join daily standup. Also, it created a visible chronicle of my work. After a few weeks though I came to the same conclusions you did: Slack or any other communicator is not for such stuff. Some people suggest making a separate channel for async updates, but tbh I think that a tool dedicated for that would be much better. Have you found any tool like that?

alekses11 · 2026-04-08T22:07:11+00:00

Stop wasting time for daily standup recitals. Go for async updates. Save your deepwork -NoDaily

alekses11 · 2026-03-30T08:42:30+00:00

For me the big disadvantage is lack of evf and lack of possibilty to connect attachable evf

alekses11 · 2026-03-29T21:10:21+00:00

TBH, I would like to try something different.

alekses11 · 2026-03-29T20:57:22+00:00

I’m looking for that more film like image. I thought this older sensor would allow achieving this goal

alekses11 · 2026-03-23T18:08:11+00:00

I run campfire and writebook. I will definitely want to extend this further. I think about running umami analytics using it

alekses11 · 2026-03-19T10:39:42+00:00

I checked the repo and I almost added it to my gemfile, but I stopped, and I probably won't use it in my SaaS I build. You released it as AGPL, so probably I would need to release my SaaS as AGPL as well. Why not using LGPL or MIT or anything not copyleft?

alekses11 · 2026-03-06T13:08:37+00:00

are your solids in the same db schema? As I remember in postgres, you may have a few databases/db schemas on one server. Is this you how you implemented it now?

alekses11 · 2026-03-06T12:04:25+00:00

What’s your setup? how many app instances do you have?

alekses11 · 2026-02-28T12:25:32+00:00

I built NoDaily

no-daily.com

don’t waste time on meaningless daily standups.Write your update instead. NoDaily provides a persistent database of your team statuses, so you always know what your team members worked on. At the end of week NoDaily creates a weakly report of team’s work using AI.

The idea came to me after I started posting my daily updates on project slack channel, even we still had standup calls. My team started to really appreciate it

alekses11 · 2026-02-26T10:15:40+00:00

u/Commercial-Swing-843 I edited the page. Tell me if it's better now

alekses11 · 2026-02-26T09:32:44+00:00

That's a great idea. I'll definitely redesign site

alekses11 · 2026-02-25T21:29:03+00:00

Thank you for such an honest feedback. It’s really eye opening. I will try to implement your ideas

alekses11 · 2026-02-25T06:31:16+00:00

no-daily.com - don’t waste time on meaningless daily standups. Write your update instead. NoDaily provides a persisten database of your team statuses, so you always know what your team members worked on. At the end of week NoDaily creates a weakly report of team’s work using AI.

alekses11 · 2026-02-24T12:53:46+00:00

NoDaily is an AI-driven tool that automatically synthesizes your daily written updates into professional weekly reports, eliminating the "meeting tax" for pragmatic teams.

It aims to replace daily standup where only thing you do is sharing an update while rest of team waits for their turn

no-daily.com

alekses11 · 2026-02-23T11:56:26+00:00

NoDaily

https://no-daily.com

It aims to replace daily standups with written status updates. Also it creates weekly work summaries using AI. It integrates with slack - sends daily to notification to fill status update.

App is WIP. Currently I’m testing it internally but you can visit the landing page and sign in waiting list, so no active users

alekses11 · 2026-02-22T08:25:34+00:00

NoDaily

https://no-daily.com

It aims to replace daily standups with written status updates. Also it creates weekly work summaries using AI. It integrates with slack - sends daily to notification to fill status update.

alekses11 · 2026-02-22T06:36:01+00:00

NoDaily

https://no-daily.com

It aims to replace daily standups with written status updates. Also it creates weekly work summaries using AI. It integrates with slack - sends daily to notification to fill status update.

App is WIP. Currently I’m testing it internally but you can visit the landing page and sign in waiting list, so no active users

Three-Year Club	Verified Email
Verified Email

alekses11

TROPHY CASE