Ever try to remember advice from a YC podcast that's on the tip of your tongue but can’t quite remember?
Want YC’s perspective for important startup decisions?
Now you can ask “ChatYC” for all your needs! (Unofficial chatbot)
Some examples:
- What should I include in my monthly investor updates?
- Explain like Im five what pro rata means
- Should I hire a lawyer for my early stage startup?
- whats the difference between a priced round and safe?
- What is dilution? Can you explain like I am five
- any tips for traits to look for in founding engineers?
- when should I raise a seed round?
- are startup advisors valuable?
Try it out here! https://www.spryngtime.com/yc-demo
We built this as a proof of concept and to showcase a new tool we’re building: ChatGPT for customer support. We’ve started working with some partners to ingest their public docs (and previous support chats via email/Slack/Intercom/Discord/etc) to help answer customer support and onboarding questions.
Note: This bot was trained on ONLY public content from https://www.ycombinator.com/library - so it might not be able to answer all your questions. But it's a great starting point for new founders!
Does anyone here work on notifications processing pipelines/infrastructure? Specifically triggering of push, email, sms, etc. I’d love to chat with you if you do and understand your architecture designs more and bounce some ideas off of you!
Specifically, I’d love to learn: Do you build notification event processing in house or use a 3rd party API? What are your biggest problems with building/managing this pipeline internally?
For context, when I worked at a tech company, I worked on “saving a search” (think saving a search on Autotrader for any Honda car for less than $20,000). It was cumbersome managing, setting up, and debugging these notification systems. I was curious if others had similar frustrations.
What is that one problem, if solved, would make your job much more efficient?