DealForge autonomously sources, scores, and writes investment memos on venture deals. Stop manually hunting.
1,180+ deals tracked · 22 AI investment memos · Updated daily
We just launched a proof-of-life platform that delivers your pre-written messages when you stop checking in. Here's the stack and what we learned while building it
Hey r/SaaS, Founder here. We just shipped **LastReach** ([lastreach.app](https://lastreach.app)) — a platform where users write messages, set up check-in intervals, and if they stop responding, the platform automatically delivers those messages to their designated recipients via email or SMS (more delivery options incoming). Think of it as automated message delivery triggered by inactivity. You configure how often you want to check in (daily, weekly, etc.), and if you miss your check-ins and don't respond to the reminders, your pre-written messages get sent to the people you chose. **The problem we wanted to solve:** I realized that if something unexpected happened to me, there were things I'd want specific people to know — and no simple tool existed to handle that reliably and privately. Password managers store credentials, wills handle assets, but nobody was handling the *words*. The messages you'd want delivered to your partner, your kids, your business partner or friends (or maybe to all of them). **Tech stack:** * Next.js (App Router) on Vercel * Prisma ORM + PostgreSQL * NextAuth for authentication * Tailwind CSS + Framer Motion * Twilio for SMS delivery * Claude API (Haiku for visitor chatbot, Sonnet for authenticated users) * next-intl for full bilingual support (English/Spanish) * Zoho Mail for transactional email **A few things I learned the hard way:** 1. **Email logo format matters more than you'd think.** I spent hours debugging email rendering issues before discovering WebP is incompatible with most email clients. Had to switch everything to PNG. Tiny detail, wasted a full evening. 2. **Streaming chatbot speed is experiential, not theoretical.** I tested Claude's streaming output at different throttle rates. 25ms/character felt robotic and too fast. 35ms/character feels natural. You can't decide this from a spec sheet — you have to watch real users interact with it. 3. **The "Honor Commitment" policy was critical to get right.** If a user sets
Heuristic score based on available signals. Funding: $0, Source: reddit_startups.