A while back, I missed another bedtime with my kids because of a "quick sync" that somehow turned into an hour-long meeting, that once again, ended in no clear decisions or next steps. Instead, just another calendar filler that stole my time.
At the time, outside of my day job, I was working on a startup during nights and weekends, so I really felt every wasted hour. My co-founder and I had tried a bunch of AI meeting tools, but instead of improving operations, they all just summarized the chaos of the meeting itself. A bad meeting with lots of noise just produces a cleaner transcript full of noise. And AI can’t really fix that.
So to address the problem, we built an internal tool to eliminate a lot of the meetings that were consuming our calendars but not creating much value, i.e., check-ins, syncs, touch bases, etc..
Instead of joining a group call, the organizer speaks with the AI to set the goals and parameters of the meeting and then it privately and asynchronously interviews participants on their time. The AI asks follow-up questions, challenges assumptions, and explores concerns individually. The AI then synthesizes everything into a single, shared output.
What surprised us wasn't that we had fewer meetings. It was what happened when people stopped discussing topics together in real time. Almost immediately, we noticed patterns:
• People were more honest and focused. Without the cognitive drain of back-to-back calls, the quality of thinking in each conversation was noticeably higher.
• Calendars cleared up.
• Risks and disagreements surfaced more frequently.
• Team members raised concerns they had never once voiced in a meeting.
It’s this last item that stopped us cold because these weren't minor concerns. Some were rather significant (the kind that, if raised earlier, would have changed decisions entirely). These concerns had been sitting in people's heads, unsaid, meeting after meeting, and the moment we removed the group dynamic, they came right out. For example, we discovered one of our team members had serious concerns about one of the models we were using based on their experience, but didn’t want to share with the group, because a few others were such loud proponents of it.
We started digging into why.
Solomon Asch showed through multiple experiments in the 1950s that people conform to group opinion even when the group is clearly wrong, and not just behaviorally, but perceptually conformed. Muzafer Sherif showed something similar in the 1930s, individuals abandon their own judgment and converge toward whatever the group believes. But conformity isn't the only problem, Garold Stasser conducted research in the 1980s and found that groups reliably spend most of their discussion time on information everyone already knows, and systematically miss the critical insights that only one person holds. Essentially, the best information in your meeting is probably never getting said.
Modern meetings create those same dynamics every day.
When people discuss ideas together in real time, their opinions stop being independent. Status, confidence, timing, and social pressure all begin shaping what gets said and shared. Most AI meeting tools approach this as a transcription problem. However, if the meeting itself is producing distorted information, a better transcript doesn't solve much. You’re just getting a cleaner record of a flawed process.
We started to wonder whether the future of collaboration isn't better meetings, but in fact, gathering independent perspectives first, and then discussing them second, only if necessary.
We kept building on that idea, refining it, and it eventually became what we now offer publicly as Noada. It’s named after my daughters because getting time back with them was the original motivation behind all of this.
We're still early and actively learning. Curious whether others have run into this, decisions that got derailed by group dynamics, or concerns that only surfaced after the meeting ended. What did you do about it?
That integration point is where a lot of “AI productivity” tools quietly become address-book products.
For meeting tools, I’d want the privacy story to be very plain: which contacts get imported, which participants are stored, whether transcript-derived notes are kept after the meeting, and whether any of that can leave through a connected CRM/calendar/email tool.
We think about the same thing with https://privacy.fish: email is not just messages, it is a map of relationships. Contact lists, invites, reply chains, and recovery addresses can become sensitive even when the text itself looks harmless.
If Noada can make that boundary obvious early, it probably becomes part of the trust advantage rather than a settings-page problem later.
We saw a similar thing after shipping a tiny collaboration flow, what users say privately is usually the trust question they dont want to ask in the thread. Some teams bolt on a generic consent banner, a few just add a FAQ, I built PrivacyForge because meeting summaries, participant names, and transcript retention rules drift fast once integrations show up. If people got weird in private, I'd bet they want the data-handling answer earlier than the feature tour, ngl.
That's a good point, too. Personally, I find the sharing of contact info across integrations absolutely maddening.
The interesting part is that your story is not really about meetings.
It's about decision quality.
Most meeting tools try to reduce the cost of discussion.
What you're describing is reducing the cost of social distortion before a decision gets made.
That is a very different category.
I'd actually be careful with async-meeting language long term because it keeps the buyer focused on calendars, while the stronger value may be surfacing information that would never have appeared in the meeting at all.
The question I'd pressure-test is whether Noada is helping teams meet differently or helping them make better decisions by collecting independent thinking first.
Those sound similar, but they lead to very different positioning.
Happy to put the tighter version in writing if useful.
“helping them make better decisions by collecting independent thinking first.” that’s where my mind goes as well. Synthesizing what people actually want to say, fast, and helping them not look like idiots vs just collecting, feels valuable, and a great way to reduce the communication tax of human/human work.
The "not look like idiots" idea is really interesting because it flips the value from the organization to the person, and personal incentives like that often drive adoption in a way that organization benefits don’t.
What you're describing is something I know exists because I’ve experienced it. When someone is interviewed by AI and given time to elaborate and had their assumptions challenged, all in private, they show up differently. There’s less social pressure / judgement, so they feel more confident, more prepared, less likely to either self-censor or overcorrect. This is very compelling!
The "communication tax" idea also resonates. A lot of what makes meetings exhausting isn't the time itself, its the overhead associated with the process. For example, the pre-meeting chit chat, reading the room, managing up, figuring out when to push back and when to let it go. If Noada absorbs some of that tax, that might be as valuable as the calendar savings.
Now on to figuring out how to tease out these two ideas in our marketing 😅
Thank you very much for the feedback.
Appreciate that, Elliot.
That tension is exactly the part I’d want to make properly rather than answer casually here.
“Time saved” and “decision quality” may both be true, but they lead to different buyers, adoption triggers, and homepage promises.
DM/email works. Send me the best email and I’ll write the tighter version properly instead of turning the thread into a full teardown.
Thanks, Aryan. My email is: [email protected]
Sent it over, Elliot.
Kept it focused on the main decision: whether Noada should be led by time saved or by better decisions through independent thinking.
Thank you! This is the most useful framing framing advice that I’ve gotten since we launched, and honestly, it’s been sitting in the back of my head since we first decided to build for a public release.
I think you're right that the stronger value isn't async, it's independent thinking before social pressure shapes the output. The async part is just the mechanism. What we're actually doing is removing the group dynamic before it can distort what people say and share.
That said, the reason we've been teetering between the two is that the calendar and time savings have been a genuine game changer in practice, not just in theory. I've personally thoughtfully answered meetings using this mechanism while playing with my kids, in a matter of minutes, in a way that simply wasn't possible before. So we're genuinely uncertain how much people value reclaiming time versus improving decision quality. And, perhaps more importantly, whether those are even separate selling points or just two expressions of the same underlying problem. Still trying to figure that out, as you can tell.
Where I've been hesitant to move fully toward decision-quality positioning is discoverability and adoption. People searching for time-saving meeting tools seem to outnumber people searching for decision quality apps, and we're still trying to find our early adopters. I think decision quality software is undeniably compelling, so maybe we’ve just been optimizing for the wrong audience.
The tension your question surfaces is real: the teams getting the most out of Noada aren't the ones who wanted shorter meetings, they’re the ones who kept finding out that someone had a critical concern that was never raised. This is a decision problem, and not a calendar problem.
If your offer stands, I would genuinely appreciate the tighter version if you're still up for it. Also, happy to DM, if that’s easier for you. Thank you again!
Really appreciate this, Elliot.
That tension is exactly the part I would not answer casually in-thread, because “time saved” and “decision quality” are not just two messages. They point to different buyers, channels, and adoption triggers.
Send me your email and I’ll write the tighter version properly instead of turning this into a full teardown here.