Launching today
Noah is a proactive AI executive assistant for founders. Claude talks to you; Noah talks to your network. It's like Tesla Full Self Driving, and not cruise control- an autonomous AI EA that manages your calendar, relationships, and follow-ups across email, text, and WhatsApp - so nothing slips. Think of it as an always-on EA living in your SMS and helping you with meeting logistics.
Hey Noah
Hey Product Hunt! 👋 I'm Ashish, founder of Hey Noah.
I spent 14 years bootstrapping a $100M revenue company with 47 Fortune 500 clients. I had an executive assistant who didn't just manage my calendar — she managed my relationships. I had a system for managing my time and relationships.
So we put that playbook into Noah, a Chief of Staff in your pocket. 📱
Text Noah like you'd text a human EA:
"Set up coffee with Sarah next week." → Noah emails Sarah, negotiates times, and sends the invite
"I'm out Thursday and Friday." → Noah reschedules your conflicts and lets people know
Just CC noah on any email — Noah reads Calendly links, handles the back-and-forth, and acts like your true executive admin
Now imagine you're back-to-back in 8 meetings today. Noah connects to your calendar, Granola, Notion, Google Drive, and Slack — posts summaries and action items to the right channels, and knows not to post that private client conversation. At the end of the day, just text: "Noah, send me all the action items from today." Done. ✅
What makes Noah different:
💬 SMS-first — Noah comes to you, not the other way around
🔮 Proactive — surfaces what matters before you ask
📧 The only AI that talks to your clients — doesn't just draft emails, it sends them, follows up, and closes the loop
🧠 Learns you — 10-second setup and learns your meeting preferences, favorite spots, and which meetings to protect
Here's what we're hearing: "Noah is one of the top 9 pins on my iPhone SMS" — CEO of an $80M revenue company. That says it all.
We're a team of 8 in Palo Alto, bootstrapped, and obsessed with getting this right. 🚀
Free 30-day trial, no credit card → Try Noah
Drop questions below — I'll personally respond to every one.
@ashish_toshniwal1 Proactive is the word that makes or breaks these for me. Most founder assistants I have tried are reactive dashboards with a chat box bolted on. What does Noah actually do unprompted in a normal week, and how do you keep proactive from turning into noise I ignore by day three?
Kontrol
@ashish_toshniwal1 @artem_fedorovich
Founding engineer here. A few things Noah does on its own:
- Follows up with people who haven't responded, and asks you what to do if they still go quiet
- Confirms reservations, actually calls the restaurant on the day
- Pulls your Granola notes before a meeting and briefs you on where you left off
- Chases stalled threads and flags scheduling conflicts before they're a problem
- Follows up after calls with notes and action items
On noise: everything's opt-out per category, defaulting off. Noah has to earn the right to interrupt you. It batches non-urgent stuff into one message instead of five, and stops sending a nudge type if you keep ignoring it. All of it's tuned per person, you just tell Noah your preferences.
@ashish_toshniwal1 I like that you're positioning Noah around outcomes rather than prompts. The examples make it feel more like delegating work to an assistant than interacting with another AI chatbot. Curious how users build trust before letting it send emails on their behalf?
Hey Noah
@ashish_toshniwal1 @ir3ne
Hey @ir3ne jumping in for Ashish. This is a fantastic question and one that we think about a lot.
Building trust is extremely important to us, and a unique challenge for an SMS/Email based product (there's very little UX to see, which makes it hard to see the extent of the product).
The general principles we try to uphold are to:
Start small and then build trust after value is proven (Noah does not access your email (only your calendar). It will send emails via Noah's own email address.)
Keep everything as transparent as possible (you are cc'd on every thread)
Build and adhere to preferences for each user (you can review anythign noah sends beforehand).
Reliability is key (we've done a lot of work to make sure Noah stays consistent and feels like an EA).
We'd love for you to check it out, and hear your thoughts on how it feels.
Never guess is the right rule and the hardest one to actually build, because the model that's wrong is usually not the model that's unsure. Your escalation path covers the cases Noah knows it can't resolve, but the expensive ones are the ones it resolves confidently and incorrectly, and those leave under my name in front of a client. I'd want to see how many outbound emails you've sent and how many needed a correction afterwards. That number would sell this harder than the top 9 pins quote.
Hey Noah
@asadmalik901 great call out.
To date, Noah has sent roughly 17,000 emails with our beta user base (all in live, real-world scenarios).
We've designed Noah to send email through its own account with you cc'd (operating just like an EA might for coordinating scheduling), so while we don't want errors, it helps our users mitigate against potential issues.
We know that any error with a client, however small, is how we lose trust. If anything surprised me building this product, it was that the agent work was actually fairly quick. The part that took the longest was building out the guards to protect against all of the small edge cases and nuanced scenarios to make sure Noah performs well in every scenario thrown its way.
@johnbeadle 17,000 is volume, not accuracy. The number I asked about is how many of those needed a correction after they went out, and that's still the one I'd put on the page. Cc'ing me is a decent mitigation but it turns me into the reviewer, which is the job I was trying to hand off in the first place. If the correction rate is genuinely low, say it out loud, it's the strongest thing you've got.
The escalation-path question above is about accuracy. Mine is about disclosure.
If Noah emails my client and they don't know it's Noah, the relationship holds right up until they find out — and then I have a bigger problem than a missed follow-up. If they do know, I'm not sure what's left of the thing it was maintaining. A warm, well-timed note from someone's agent is just automation with better manners.
So what's your position on the recipient knowing? Have you got users who've told their contacts they're using Noah, and did it change how those people replied?
Hey Noah
@you_li525
It's an interesting design challenge we've debated as well. Noah today is its own personality, meaning it sends emails from its own account, with you cc'd.
We found that Noah having its own identity helps reduce friction and mimics the flow most people expect when workig with a great EA. While its fairly clear Noah is not the exec, we've had a few people confuse Noah for a real person, which has been a fun win for our team.
I'm skeptical of "autonomous" claims until I see it handle a messy reschedule with three time zones involved. That's the real test for me.
Hey Noah
@nancy_philip Fair test, and the right one.
The harder parts are the preferences nobody says out loud. Someone is free at 7am but would hate it. In those cases Noah asks instead of picking. Try Noah and test it out. If it fumbles, tell us.
Hey Noah
@nancy_philip we 100% agree! There's a lot of messy work when you start peeling back the layers of scheduling.
Ironically, a lot of these messy rules needed to be codified into our system (can't rely on an agent to perform consistently in every scenario). Danira, on our team used to be a world-class EA who's spent a lot of time writing down her rules to every and each scenario - which Noah is now instructed to follow.
If you've got the messy timezone-related use cases, we'd love to see if Noah holds up (we think it will)!
This looks good, but I would be nervous letting an AI send emails on my behalf. How do you handle that? What if it says something wrong to an important contact?
Hey Noah
@nihalshetty0 Honestly, this is where most of our engineering effort went. Noah earned autonomy gradually, you control what it can do on its own vs what needs your sign-off, and it's designed to know when something is high-stakes and loop you in over before acting.
Hey Noah
Hi All, I lead Product at Hey Noah.
@ashish_toshniwal1 covered the core (text Noah, and it handles the scheduling back-and-forth), so I'll share a few more of my favorite use cases so far:
Add a batch of events from a photo. Take a picture of the kids' school calendar or a season's game schedule, text it to Noah, and every event gets added to your calendar.
Schedule via Phone Call. "Book us a 6pm table at Zuni on Friday." Noah calls the restaurant and books it (assuming the person on the other end is willing to engage).
Schedule across time zones. "Find 30 minutes with our London team next week." Noah handles the time zone translation and manages any back-and-forth.
Connect Granola + Act on Action Items. Set up a skill to have Noah pull action items out of your Granola meetings every day and email next steps to participants.
The hardest part of building Noah has been figuring out how to keep an agent consistent and trustworthy enough to act in high-stakes external settings, while adaptable enough to be personalized to individual preferences. Happy to chat about what's worked (and flopped).
@ashish_toshniwal1 @johnbeadle Amazing launch... congrats team🙌What happens when a client replies with a complex edge-case rescheduling request via email? Does Noah hand off to the human user via SMS
Hey Noah
@ashish_toshniwal1 @johnbeadle @vikramp7470
Thank you!
On edge cases: Noah handles the common ones by itself, like a client proposing a new time or asking to move a recurring slot. Only when the request gets ambiguous or touches something it can't resolve cleanly, it stops and pings you over SMS with the thread's context and at times, with a suggested reply. You confirm or correct in one message and it takes it from there.
We work on a simple rule: Noah should never guess on your behalf. If it's not sure, it asks instead of guessing.
Hey Noah
@ashish_toshniwal1 @vikramp7470
Adding to Navin's answer -
If it's an information-based task and it's clear enough, Noah will usually do it by researching online.
Noah will escalate to the user in a private channel (SMS or email, based on your preference) if it needs clarification or reaches a limitation.
While we cant do everything yet, there's a lot of cool sub-cases Noah can support - calling to book a reservation for a restaurant or tee time is one of my favorites :)
Bhava
Hey team,
this looks super cool. curious if i could connect my multiple accounts in this?
Hey Noah
@riya_jawandhiya Thank you!
Yes, you can connect multiple accounts. Noah reads across all of them when checking availability, so it won't book you into a conflict on one calendar because it only saw the other.
Happy to help you get set up if you run into anything.