
r0cket
Smarter outreach. Not harder.
B2B / Sales / SaaS · Founder
Problem
B2B sales teams spend too much time on manual lead research, contact finding, and generic outreach. Scaling personalized outreach is slow and repetitive.
Strategy
Product-centric workflow: define products and attach documents for semantic context; run lead-gen and contact-gen via configurable n8n webhooks; then run outreach (manual or scheduled) with Gemini-generated personalized emails sent through EmailJS, with state tracked in PostgreSQL.
Architecture
Next.js 16 App Router front end with dashboard (products, companies, contacts, campaigns). Elysia API mounted under /api for typed CRUD and workflows. PostgreSQL + Prisma + pgvector for products, documents (embeddings), companies, contacts, and campaigns. Inngest for cron-based scheduled campaign execution (every 15 min). Lead-gen and contact-gen triggered via internal API calls to Next.js workflow routes that invoke n8n webhooks. AI (Gemini) for document embeddings and outreach email generation; EmailJS for sending.
Execution
Implemented products with document upload (PDF/MD/TXT), chunking, Gemini embeddings, and pgvector storage. Company and contact management with status and ordering. Campaigns support manual and scheduled runs; scheduled runs use Inngest cron to find due campaigns and fan-out to run full pipeline: lead-gen → contact-gen → outreach. Outreach uses Gemini to generate per-contact subject/body/CTA from product and company research, then EmailJS with rate limiting; sent state and email content stored on contacts.
Solution
r0cket unifies products, documents (with semantic search), companies, contacts, and campaigns in one app. Users run lead-gen and contact-gen workflows (n8n), then execute outreach with AI-personalized emails at scale, either on demand or on a schedule.
Measurable impact
Centralized B2B outreach pipeline: one place to manage products, leads, contacts, and campaigns; AI-personalized outreach at scale; scheduled campaigns reduce manual triggering; semantic product context improves relevance of generated emails.