min.
The AI teammate that does the little things right.
76 followers
The AI teammate that does the little things right.
76 followers
min. remembers, schedules, takes notes, and follows up. For you and your team. Invite min@getmin.ai to a team meeting, Cc it to help you schedule, or ask it to set a reminder for a follow up. No sign ups required.
Free Options
Launch Team / Built With
Context.devAPI to scrape anything for AI, 20,000+ developers trust us.
Promoted
Sup PH 👋
I'm Eric, one of the builders here at min.
We built this because we kept hitting the same wall. The notetakers could summarize a meeting fine, but none of them knew the customer context on the other side, so every time I wanted to give my Claude Code context I was dumping dozens of meetings and 20 threads into a context window. I was raw dogging the rest of it in my head. So we built the thing we wanted: an AI that has already been in every conversation you've had with a customer.
It runs on your email and meetings and builds context for everyone you work with. I have it connected to my Claude Code, bringing every customer context into my building process is a complete game changer.
PH gets 6 months of recall history for free instead of the typical 3 on the free tier!
Hey PH!
We built min. out of a pain WE faced every day. We couldn't all jump on every customer call, sales sync, or user interview together, and catching up afterward was a nightmare. Sifting through email threads, reading transcripts, or watching meeting recordings to get the scoop wasn’t efficient.
We wanted a tool that did two things seamlessly:
Summarize & Provide Context: Give us a living, one page briefing of the entire account history so we could get the scoop in 60 seconds.
Consult & Dive Deeper with AI: Allow us to ask AI specific questions grounded in those exact calls and emails: "Where are they skeptical?", "How do I progress this deal?", or "Draft a follow-up email addressing their budget concerns."
That’s how min. was born!
I’d love to hear from you: How does your team currently handle context when someone can't make a call?
@fadi_kanaan1 honestly right now it's a Slack thread someone half-remembers plus a Notion doc nobody updated after week two, so I get the pain. the thing I keep chewing on with min. is the other side of the call: you're building "a living AI" for every customer from their emails and meetings, and then asking it things like where are they skeptical, essentially interrogating a model of a person who never agreed to be modeled that way. most CRMs store what was said, this one seems to build something closer to a standing profile you can query about someone's own doubts. does the customer have any visibility into that, or any way to know that's happening on the other end of the relationship
@fadi_kanaan1 @galdayan Thanks for the question. Everything you query is completely private. What I felt while using a lot of AI tools is that it plays really safe and tries to cover all of its bases. We wanted something a little more opinionated, something that amplifies tiny signals in data that are otherwise dismissed by a person's bias. I discovered that a lot of times when faced with a neutral AI, I'd almost just query it like a database, but if I'm faced with a persona of a customer, I'd be more incline to ask the right questions. At the end of the day, its really a UX choice we made to steer user behavior.
@fadi_kanaan1 @eric_wang29 makes sense that the query data itself stays private, that part I wasn't worried about. the thing I was actually poking at is different - not who can see the answers, but whether the person being modeled knows a profile of their doubts exists at all. if it's purely a UX choice on your end to steer user behavior, does that choice ever get disclosed to the customer, or is it entirely invisible to them by design
follow up is where every deal quietly dies, good angle 👏 does it learn my tone over time?