eambutu
Joined 8 years ago
Karma
219
Submissions
58
Member since
Aug 27
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
2019-2020: We prototyped lots of telepresence ideas, our work shown here: https://siemprecollective.com/
2020-2022: We built https://gather.town, which during COVID blew up across every use-case possible: conferences, birthday parties, weddings, universities. It was a good business during COVID but eventually started to shrink.
2022-2025: We built Gather for remote workers, which was a long grind into in Audio/Video, performance, and making a game-interface that was good for work but replicated the parts of in-person work people enjoyed. It's a decent business, but didn't match our ambitions with how we wanted to change work for the better.
2025+: We have lots of ideas for how we can make work a lot better with AI. The general theme is, "can we make work as fun as a video game?" Idea being: video games are super similar to work at its core, and AI can both 1.) dramatically change how people need to spend their days, and 2.) help you "game design" someone's work day.
The Grapevine system is the first tablestakes layer people need to have for us to build the products we're excited about. Surprisingly, "company context" was not as good as we thought despite it being such an obvious, big business opportunity. So while I agree it's "basic," it does seem necessary, and is also not the full-scale of what we want to achieve still :)
Comment · 1 year ago
Ah to be clear, the team is staffed well enough on Gather that the experience will be equal, if not better, than what you've been using already. So we haven't been telling customers to migrate (and unfortunately, there aren't many good alternative products right now).
Comment · 1 year ago
Yep, the other commenter is right--85% is helpful AND accurate. I'd love for you to give it a try and see if 85% is not good enough though. There's always more to push on quality and the more real feedback we get the better we can prioritize what people need.
Comment · 1 year ago
Yep, makes a lot of sense. We architected our system to be easy to self-host & open-source in the future for this very reason, though we decided to launch with hosted because it's easier to improve and iterate.
Comment · 1 year ago
No self-hosted version yet. You would need to trust us in the same way you trust your other SaaS apps that host company IP (e.g. Slack, Notion, Github, etc.)
I get that's a big ask from a startup. If it helps, we are a company that's been around for 4+ years and have built a work tool (https://gather.town) used for 100k+ people for their daily work, Sequoia-backed, are SOC II certified, and go way beyond that for the security considerations for this product.
Comment · 1 year ago
The Gather work product is unfortunately going into maintenance mode. We still have a strong team working on the core AV and performance, and the business is very decent and more than supports that team (and we still use the Gather product heavily ourselves).
However, it didn't reach the growth trajectory we needed, so a majority of the company will be working on Grapevine + new products instead.
Comment · 1 year ago
Our experience, especially with the most recent reasoning models, is that the LLM's are a lot better now at sifting through the garbage. So if you last gave these products a try more than a month ago, I would try them again.
(Additionally, there are a lot of details that do make a big difference in data processing / search algo too, which have taken our own internal accuracy on hard questions from 30% => 80%+)
Comment · 1 year ago
Thanks for using it! Any feedback on what could be made better? And did you guys try any of the alternatives before using Grapevine?
Comment · 1 year ago
Fortunately, Grapevine is just the name of our system, we let people white-label their Slack bot when they actually set it up :)
Comment · 1 year ago
I can't speak for other people, but our strong opinion about how companies should work is to reduce the massive amount of chores and tedium that exist in our work days today.
With the company GPT, we want to tackle things like: 1.) having to answer a repeated question from a colleague, 2.) answering questions to coworkers that are purely informational, and eventually 3.) things like standup updates, written updates to leadership on status, etc.
I think human interaction at work is one of the most valuable experiences if you're lucky enough to have good colleagues and interesting work. But I think they should almost entirely be around creativity, decision-making, debate, etc. rather than sharing information that exists elsewhere.
Comment · 1 year ago
In terms of what businesses we're targeting: we wanted to provide either 1.) a turnkey solution for a company GPT for all the people who don't have it yet, or 2.) a higher quality company GPT for people who do have an internal solution.
Our sense is that ~70% knowledge companies at large still don't have a custom GPT yet, and that of the people who do, our system can be more performant because we're spending more effort than their internal team is. There's a lot of details we've solved on data ingestion and search algo that improved our accuracy dramatically, and things breadth of data connectors is the kind of thing that is expensive for an internal team but worth it if you're providing the service at large.
Not sure what you mean by "data seems to be stored outside of the customers control," but fortunately I think many SaaS apps that were trying to lock down customer data from themselves are walking that back a little bit.
Comment · 1 year ago
tl;dr, We built an internal GPT that connects to all your data sources (Slack, Notion, Gdrive, codebase, etc.) and it works remarkably well. Don’t take our word for it though, you can get set up in under 30 minutes, for free, at https://getgrapevine.ai
Like many of you, we were interested in a ChatGPT that fully understands your company. We tried all the existing tools (including expensive enterprise ones), but while they were good at answering “what is X team’s Q4 goal,” they weren’t good at the day-to-day questions that actually blocked people.
So, our founders and early engineers created a set of 100+ representative questions, from hard technical questions to company-specific knowledge questions. At first, the state-of-the-art “enterprise search” products were getting about 50% of them correct, and our in-house system was getting 35%. But as we solved details in data processing, search algorithm, and more, we eventually achieved 85%. (For reference, the best human score our founders got was 70%)
It’s changed the way we work: popular engineering channels that have 5+ questions / day are fully answered proactively by AI, and people across departments go to the bot first for bug reports, incidents, and support tickets. Our 15+ beta customers have been consistently surprised by the quality of answers too.
We’d love for everyone to try it out themselves! We put a lot of effort into making it easy to set up (less than 30 min) and the first month is free. Grapevine is built with our company’s SOC 2 Type II standards and if it doesn’t work out, it’s super easy to delete your data.
Lastly: for the AI-native companies. We started down this path because we saw it as a prerequisite for all the interesting agents we wanted to build for ourselves. Expect additional launches very soon on how to build on top of Grapevine, and a few cool applications of our own!
I can't speculate exactly on the work that other companies have done, but my guess is we were way more focused on the type of questions people actually ask to each other. We know there's still a lot more you can do to continue to improve it, and so it's up to other folks if they do it too.
Lastly, a few ways we want to be distinguished from all the other offerings are: 1) super easy to setup, 2.) very developer friendly