Launched this week
readywhen
Your 24/7 AI Chief of Staff for commitments and follow-ups
1K followers
Your 24/7 AI Chief of Staff for commitments and follow-ups
1K followers
Your team’s work lives in project management tools and CRMs. Your exec work is scattered. readywhen catches every decision and commitment across Slack, email, meetings, and docs. Without being asked, it drafts what’s needed next: the brief, the email response, the update. You just approve. It's like having your own Chief of Staff, 24/7.
readywhen
Hi everyone, I'm Sançar, co-founder at readywhen.
If you're a founder, a leader or anyone managing a team, this one's for you.
You end the day having said yes to twenty things. A promise on a call. An ask buried in a Slack thread. A "leave it with me" you meant at the time. By the time you sit down, half of them are gone. And the ones you remember keep you up at night.
None of us drop the ball on purpose. There's just no one whose job it is to catch everything. So we made it someone's job. readywhen is your 24/7 Chief of Staff.
What it does
It captures what you said you'd do across email, Slack, Notion and meetings.
Then it proactively helps to close the loop, with your full business context in mind.
The result: you stay on top of everything, and nothing slips.
Where we are today
readywhen catches commitments wherever they're made, then gets to work. Drafts the reply. Pulls the report. Chases the owner. Prepares the brief. Brings it back done, ready for your approval. Nothing sends without your final tap.
It connects to the stack you already use, so it works with the full context of your business. Your people. Your projects. Your docs. The conversations you've already had. What it brings back isn't generic, it's ready to action.
Under five minutes to set up. No prompting, no skills to build, nothing to maintain. It just runs in the background.
Other AI tools respond when asked. readywhen acts before you ask.
The best way to feel it is to try it yourself. It's free for founders, leaders and team managers. No credit card.
Where we're taking it
A proactive Chief of Staff that learns how you, your team and your organisation work, then spots gaps and closes them before you ask. Switch-on-in-one-click routines. Shared visibility across your whole team. And some very exciting features and capabilities designed specifically for founders and leaders. That's what we're building toward, and it's close.
The team and I are here all day. Share your feedback, your questions, and where a dedicated Chief of Staff would have saved you this week. If you have a feature wish, I want to hear it. And if you want in, join the signup at https://shorturl.at/uA9nd
See you soon 👋
Best,
Sançar
Co-founder, readywhen
@meandering_sancar I once had a colleague who would agree to things in meetings and forget half of them by the next day. This would have saved us so many follow-up messages. Does readywhen catch commitments automatically, or does the person confirm them after the call? Congrats on the launch!
readywhen
@marie_saxon we've all been there!
It's all fully automatic. For example:
- In a call, you say "I'll follow up with an email" -> readywhen catches it, and drafts the email
- Deep in a Slack thread, someone says "Marie, can you send the sales forecast by EoD tomorrow?" -> readywhen catches it and prepares the sales forecast.
Etc
@meandering_sancar this is amazing! I am already in love with your product!
readywhen
@marie_saxon aw thanks! Hope you come and try it out. All feedback welcome!
@meandering_sancar Congrats on the launch! This product would help alleviate those dropped balls, which happen waaaaaay too often when you're juggling all the things!! You're definitely solving a problem many of us have ;)
readywhen
@anna_ludwinowski thank you!
@meandering_sancar The 'AI Chief of Staff' angle is clever. How'd you land on this specific use case? Did you start broader with commitment tracking and narrow down, or did you validate this angle first with users?
readywhen
@clquek great question. Tbh it was more the other way around. The narrow angle was 'we automatically catch your commitments across email, Slack, meetings and docs' but then realised readywhen could act like a 24/7 Chief of Staff, because it kind of becomes your second brain at work.
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?
readywhen
@hazy0 yes! It always links back to the original source, so you can always see exactly why it was added as a commitment. We also have built a dedicated agent that filters out the noise. As you say, there is a big difference between 'we could maybe do...' and 'let's get this done'. readywhen catches those differences.
That source-link boundary is the key bit for me. If the filter can also show why something was rejected as noise, it gets much easier to trust during a launch week instead of second-guessing every captured commitment.
readywhen
@hazy0 agreed. Here's a screenshot of an example of it in practice...
Congrats on the launch, sounds v helpful! How does it build an initial idea of priorities from a user's context?
readywhen
@ferdi_sigona thank you!
And good question. In short, it build a company 'knowledge graph' over time. So the more you use it, the more it understand your company, projects, team, style etc. It then has persistent memory so gets better at helping you get work done.
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!
readywhen
@artstavenka1 greta question, and yes. A couple of things on this:
1. readywhen doesn't just retrieve info (like most AI tools do). It runs regular syncs, build a knowledge graph in the background, and goes through a series of filters (or dedicated agents). This filters out the noise, makes sure only actual commitments are surfaced and helps you understand what the next thing you should do is (just like a great Chief of Staff would).
2. We don't always get it right of course. For those moments, there is a super simple feedback mechanism which means the system continuously gets better.
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?
readywhen
@yagnaveena good question. It builds a knowledge graph in the background, so the more you use it the more it knows your style, your priorities, your team and everything in between. It works like a real Chief of Staff... when you first start working with them, they won't get everything right. As you onboard them and you work together, they'll do a much better job.
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!
readywhen
@jared_salois soon you'll be able to hand over control to readywhen when and where you like but the default is it requires your approval.
For example, you could say: "When a prospect below 200 employees has asked for more information, send them our info pack without my approval."
The way I like to explain working with readywhen is as if you onboarded a real Chief of Staff. When they start, you'll likely want to review everything. When you've worked together and you trust them, you'll start delegating.
That delegation example is the interesting edge. If readywhen sends without approval, I’d want the receipt to be inspectable: source commitment, rule that allowed it, draft or template version, account used, and delivery result.
Is that audit trail already part of delegated routines, or later?
The number of "yep I'll handle that" promises I make and then lose to a Slack thread is genuinely embarrassing. So yeah, I feel personally called out here lol. Curious whether it ever gets too eager and chases stuff I didn't really mean - but the idea's great.
Great idea and realisation as well. Congrats on the launch!
readywhen
@oleg_tsizdyn thank you!
Making sure readywhen filters out the noise and only gives you what is truly something that needs action is a big part of it. Of course, it doesn't always get it right but we make it really easy to provide feedback and that makes it better every day.