97 karma · joined April 20, 2023
Martin is an AI personal assistant. Text, call, or email Martin. It manages your calendar, inbox, to-dos, reminders, notes, messages, calls, and more.
Why work at Martin?
- We've built the most advanced AI personal assistant on the market, light years ahead of Siri and Alexa.
- 5 months since launch, Martin has completed over 500,000 tasks for 30,000 users, and our user base is growing 10% every week.
- Our team is lean but effective, with a culture of shipping fast and obsessing over user experience.
- You’ll have a large impact on our product direction, which will be reflected in significant equity compensation.
- Our mission is to build the most impactful consumer product since the iPhone.
Apply at: https://www.ycombinator.com/companies/martin/jobs/
A lot of power users use it to organize their digital life in one place (to-dos, reminders, schedules) and then they use the social integrations (slack, email, sms) to move the information around.
1) DM the Martin bot in Slack to reach Martin.
And 2) Ask Martin on any platform (web, sms, iOS app) to read/send/react to messages as you directly from your own Slack account.
You can download our iOS app here - https://apps.apple.com/us/app/martin/id6453473083.
I’m curious what exactly people say causes them to make the switch from Cursor to Codebuff? Or do people just use both?
We can certainly publish more privacy guarantees in the future - thanks for the suggestions. Our business model is subscriptions, so we won't be going anywhere near ads or data sharing.
We'll be experimenting a lot and releasing updates to Martin's home screen layout and feed soon! There's a good chance this will come with changes in how we do task management altogether.
Also totally hear you on the personal database idea. We've been toying with similar ideas for a while. Many users already do this with Martin, basically brain dump in a long voice session, and it'll suggest reminders/calendar events for you. We're still figuring out how to display this personal DB info to the user in a UI though, so would love to hear your suggestions.
We recently got our CASA Tier-2 compliance done (Cloud Application Security Assessment). We've also gone through Google's OAuth compliance process for every new integration we add that's related to Google. These assessments scan our app and make sure that our software meets pretty stringent standards when it comes to data security and encryption, and that we're not using the data for anything other than the specific features we promise (i.e. not sharing or selling to advertisers, etc.). You can read more about CASA here (https://appdefensealliance.dev/casa). We haven't gone through SOC2 yet, but planning on soon once we have a few more integrations.
- I totally resonate with your criteria for an AI PA - this is very much what we're working towards with our email integration. We had been focused on voice for a while, but recently started tackling all the email use cases. Really want to get these right for you!
- Sorry for the poor onboarding job - we should make it more clear that you have to sync your calendar before we send you an email inviting you to send and forward scheduling items to Martin.
- For sending emails to contacts, this is one of our upcoming integrations that we've been building for a while - but just not ready yet! We want to make it able to send/reply to emails and fully act on threads that you attach it to. This means issuing you a unique email address for "your Martin" and managing it's behavior on threads and memory of other contacts. It's a harder problem than we first anticipated, so we're working through it steadily! It should be ready in the next month or so. For now, the communications feature is just limited to texting contacts on your behalf.
- For "deep searches", it definitely isn't the greatest at digging into a topic or generating a thorough briefing for you right now. We're not sure how deep we'll go into this use case in the future, but we do plan on integrating with more specialized functions, like LinkedIn, Twitter, Maps, etc. which should make this a lot better.
Sorry again for the poor onboarding experience. I think we also got an email from you, so will reply there as well to ask for more feedback!
Exchange is on our list! Started the Microsoft compliance process a couple months ago - expecting to get support for at least outlook or word rolled out this year.
- Right now, we use a combination of RAG and chain of thought for storing memories. At different time intervals, we'll create memories at different levels of granularity. For example, at the end of every conversation, we'll embed some vectors based on specific commands from the user. At the end of each day, we'll have the LLM reflect on key questions related to a user's routine. And every few days, it'll reflect on the user's short/long term goals. This has worked to some degree, but we're still in the very early stages of figuring out how to do long-term memory for an assistant.
- Scaling the number of tools is definitely a struggle since we want to make our integrations as thorough as we can. It takes time, so we just try to keep growing the list consistently. We have an internal goal of adding at least one new major integration every month.
- Love the idea of bringing your own API keys/endpoints. We've gotten this feedback before, so we'll seriously consider it in our next few sprints!