readywhen

Solo founder here, no team — the balls I drop are promises to myself buried in notes and community DMs, not handoffs to other people. Does readywhen earn its keep in that single-player case, or is the real magic the cross-team follow-up chasing?

The framing resonates - commitments scattered across Slack, email and meetings is a real pain. My hesitation is around trust. When I say "I'll handle it" in a meeting, that often means I need to think about HOW first. An AI that proactively drafts a brief or sends a follow-up before I've figured out my approach could create awkward situations. How configurable is the "proactive" behavior - is there a review window before anything goes out?

"Without being asked" is the part most tools get wrong. They wait for you to ask.How do you keep context coherent when a decision spans weeks of Slack, email, and meetings?

@meandering_sancar Hello, the approval step is the part I like most here. A Chief of Staff agent should not just capture commitments and create more reminders — it should understand context, draft the next step, and know when the human needs to approve before anything moves forward.

The "nothing sends without your final tap" part makes sense, but also feels like where this could get tricky at scale. If I'm making ~30 commitments a day and getting 30 drafts back, that's just a new backlog. How do you think about that as volume grows? Is there some triage layer, or does everything need the same level of review?Congrats on the launch!

The hardest part of a Chief of Staff role isn't capturing commitments, it's knowing when not to follow up. How does readywhen learn a user's working style over time so it doesn't create unnecessary reminders or actions for low-priority commitments?

would use this to stop dropping the "leave it with me" commitments that get buried in launch-week Slack threads and community DMs. The first thing I would test is how it decides something is an actual commitment versus noise — a throwaway "we could maybe do X" should not become a tracked follow-up. When it does catch one in Slack, does it link back to the exact source message

The idea of catching promises and surfacing them ready-to-approve is brilliant. Congrats! Does it integrate with common meeting tools like Fireflies or Otter yet?

Catching commitments where they already happen is the useful part. Most follow-ups don’t fail because people need another task list, they fail because the promise gets buried. The approval step also keeps it practical.

This is neat. How does it handle the same commitment appearing in both email and Slack?

Hey PH community,Excited to hunt readywhen today 🎉 Here's the gap nobody talks about 👇 Sales got a CRM. Engineering got Jira. Support got a ticketing system. Every team's work became trackable.But the person holding it all together? They got memory and willpower.The exec layer never had a system of record. Decisions, promises, "leave it with me" moments... they live in your head until they don't.That's what makes readywhen click for me. It catches the commitments scattered across Slack, email, meetings and docs, then quietly drafts what's next. You just approve.A real Chief of Staff for founders and leaders who've been running without one. 🙌Huge respect to Sançar and the team for building this. They're here all day, so drop your questions and feedback below ⬇️

Congrats on the launch! The commitment detection looks like the whole ballgame. Wonder how are you guys tuning toward precision over recall? Can users teach it what isn't a commitment? An hour of false positives and people may stop trusting the inbox. Cheers!

I would use this to stop dropping the "leave it with me" commitments that get buried in launch-week Slack threads and community DMs. The first thing I would test is how it decides something is an actual commitment versus noise — a throwaway "we could maybe do X" should not become a tracked follow-up. When it does catch one in Slack, does it link back to the exact source message so I can verify the context before I approve the draft it writes?

Hi, I'm Adam and I'm a senior engineer working on readywhen! 👋It's been a fun ride so far getting this together, and the feedback from our initial users has been very positive and super useful - I can't wait to see how it evolves in the next weeks and months and how people will respond to what we have planned!Happy to answer any questions 🤝

Congrats on the launch, sounds v helpful! How does it build an initial idea of priorities from a user's context?